The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Rolling out multi-factor authentication across a Salesforce org in stages (opens in a new tab)

You will know how to choose verification methods, phase an MFA rollout to avoid a backlash, handle integration and exception accounts, and prepare recovery procedures before users get locked out.

  1. Pick verification method
  2. Pilot with administrators
  3. Fix friction over one week
  4. Roll out profile by profile
  5. Review enrollment monthly
A staged MFA rollout runs from a pilot to profile-by-profile enablement

The article opens by framing MFA as a requirement for Salesforce sign-in, since a password alone no longer protects customer data in an org. It then sets out a five-part plan for the admin running the rollout. The first step is choosing a verification method: the Salesforce Authenticator app as the smooth default, a third-party TOTP app, or a physical security key, with keys recommended for System Administrators and users with broad data access.

The second step is staging the rollout. The author suggests enabling MFA under Setup, Identity Verification, starting with System Administrators and a small pilot group, running the pilot for a week, fixing friction such as missed enrollment emails or shared devices, and then rolling out profile by profile rather than all at once.

The third and fourth steps cover exceptions and non-human access. Users who cannot use a phone app, such as shared service accounts or kiosk logins, should use a security key or hardware token with a documented owner and review date. API-only and integration users should rely on OAuth flows or locked-down integration users, and the Login History report should be reviewed monthly for logins that bypassed MFA.

The final step is preparing users for recovery, since a new phone lockout is the most common support ticket. The author recommends a one-page guide and admin reset of MFA registration from the user’s record. The article closes by treating MFA as ongoing work, with monthly enrollment checks and quarterly exception reviews.

Read the original at dev.to (opens in a new tab)

Worth reading?

Recommended

Spring '27 release updates that need testing before enforcement, part one (opens in a new tab)

You will learn which of the first Spring '27 release updates, due before the release, affect your org, how to find the affected Connected Apps, SOAP logins and email settings, and how to test and deploy each change safely.

  1. Find impacted features in a sandbox
  2. Test each release update with Test Run
  3. Re-test impacted connections and users
  4. Deploy to Production outside working hours
  5. Check results and keep a rollback plan
The recommended sequence for preparing Spring '27 release updates before enforcement

Tom Bassett’s guide is the first of two parts covering the 16 release updates due to be enforced before, during or just after Salesforce’s Spring ’27 release in January 2027. Salesforce will enforce some updates before the release window, which the author notes is unusual and tied to security. The guide advises testing in a sandbox before deploying to production, ideally outside working hours, with a communication plan and a rollback plan. It also suggests developers use tools such as SFDX, Workbench or Salesforce Inspector Reloaded to find dependencies, and that users check the Winter ’27 release notes, since Salesforce may delay, change or cancel updates. Installed managed packages should be confirmed with their providers.

This part covers the first group of updates. The OAuth 2.0 Device Flow restriction, enforced on November 30, 2026, affects Connected Apps, packaged External Client Apps and Local External Client Apps without a Callback URL. Teams should review Login History for OAuth device logins, which is only kept for six months, migrate affected Connected Apps to External Client Apps, and confirm Local External Client Apps have a Callback URL. The SOAP Login change, effective December 1, 2026, gates access behind the Use Any API Auth permission, so affected users and integrations need a Permission Set granting it, verified through Login History. The email verification exception is being retired: existing Email Domain Allowlists will stop working, so orgs should move to Authorized Email Domains, especially if DKIM verification is turned on, to avoid users being unable to send email. The accessibility change for To Do Lists and Lightning Dual Listboxes, due January 2027, affects users browsing at more than 200% zoom, so custom and Visualforce pages should be tested at that level.

Other updates also due in January 2027 need attention. Aura action responses will no longer return non-public system fields, so Lightning components and their Apex classes must be reviewed for references to undocumented fields, and the author found standard objects were affected too. Salesforce Connect Cross-Org legacy OAuth and password authentication is being removed, so External Data Sources should be migrated to Named Credentials and re-authenticated. Salesforce to Salesforce is being retired, so organizations should check whether it is enabled, export any backup records, and move to an alternative such as Partner Cloud, Data Cloud One, MuleSoft or a third-party tool.

The guide closes with two adjustments Salesforce has made to earlier updates. The OAuth 2.0 Username-Password Flow retirement for Connected Apps is now due on February 20, 2027, and the update to instanced URLs in API traffic is now due in Spring ’27. The author points readers to part two for the remaining updates.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?