Loading
Ongoing maintenance for Salesforce HelpRead More

Mandatory IP Allowlisting Enforcement for Account Manager Organizations Without MFA in B2C Commerce

Publish Date: Oct 16, 2026
Description

Background and Purpose

Salesforce requires MFA for all platform access to protect merchant environments from account compromise and credential theft. Some operational environments — for example, third-party outsourced call centers or clean-room facilities — maintain strict policies that prohibit mobile devices, security keys, or personal email access, which makes standard MFA impractical there.
To secure logins in these environments, Account Manager enforces IP Allowlisting as a mandatory compensating control. This control ensures that logins without MFA originate only from network locations the organization's administrators have explicitly trusted.

 

Who Is Impacted

The table below shows which organizations must act, and what is required of each.

Organization StatusImpact LevelAction Required
MFA Exempt / Non-MFA (e.g., call center orgs)MandatoryConfigure a trusted IP allowlist and maintain enforcement before April 7, 2027
MFA Enforced (all users)OptionalNo mandatory action; IP Allowlisting can be enabled for extra security
Identity Federation Enforced (Salesforce Core SSO)OptionalNo mandatory action; IP Allowlisting can be enabled for extra security

 

Rollout Phases

Phase 1 — Configuration and Warning (February 10th to April 6th, 2027)
Organization administrators configure and manage trusted IPv4 ranges through the Account Manager UI or REST APIs. Non-MFA organizations that have not enabled IP Allowlisting see warning banners at login and in Organization Settings, flagging the upcoming enforcement date. During Phase 1, logins are not blocked solely for failing an IP check — the warning exists so administrators can confirm their login IPs fall inside the intended allowlist before enforcement begins.
Phase 2 — Mandatory Enforcement (effective April 7th, 2027)
Account Manager automatically enables IP enforcement for every non-MFA, non-SSO organization. Administrators of those organizations can no longer disable IP enforcement. Any login attempt from an IP address not explicitly listed in the organization's trusted allowlist is denied.

 

Real-Life Example

A third-party call center that operates Example Retailer's customer service desk cannot issue agents security keys or allow personal mobile phones on the floor, so it is designated a non-MFA organization in Account Manager. Before April 7, 2027, the call center's Salesforce administrator identifies the facility's static corporate egress IP range, adds it as a single CIDR entry to the organization's trusted allowlist, and verifies a successful test login from that range during Phase 1's warning period. When Phase 2 enforcement begins, agents at the facility continue logging in without interruption, while any login attempt from outside that range — such as a lost device connecting from a public network — is denied.

 

Technical Specifications and Rules

Administrators must follow these rules when configuring trusted IP sets:

  • IPv4 only: Account Manager supports single IPv4 addresses and IPv4 CIDR blocks; IPv6 is out of scope for this control.
  • Entry limit: An organization can define up to 50 IP entries or CIDR ranges.
  • Disallowed ranges: System validation rejects global allowlisting (0.0.0.0/0) and private/local network subnets (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).
  • Evaluation scope: The system evaluates the IP allowlist of the user's primary organization.
  • Enforcement scope: IP Allowlisting applies to interactive user web logins, including direct AM login and federated SSO. API client machine-to-machine grants (for example, client_credentials) are evaluated separately and are out of scope for this control.
Resolution

Emergency Extensions and Support Process

If an organization faces an emergency or operational constraint that prevents configuring IP Allowlisting before April 7, 2027, it must request a temporary extension through the formal Salesforce Exception Approval process; outright exemptions are not available. Contact your Salesforce Customer Success Manager (CSM) or Commerce Cloud Support to request an IP Enforcement Extension.

 

Frequently Asked Questions

  • What error message do users see if their IP is denied? Account Manager shows a generic access-denial message that tells the user their current network location is not trusted and directs them to contact their organization administrator. This generic phrasing prevents leaking details about your network topology.
  • Does IP Allowlisting affect API clients or integration users? No. Machine-to-machine API client access using client credentials is out of scope for this interactive-user control.
  • How does Account Manager verify the client IP address behind proxies? Account Manager evaluates the real client IP at ingress, which prevents client-side header spoofing.
  • How do I configure IP Allowlisting in Account Manager? Organization administrators define trusted IP addresses through the Account Manager user interface. Step-by-step configuration instructions will be published in this article closer to the Phase 1 start date.
Additional Resources

For additional guidance, please contact your Salesforce Customer Success Manager (CSM) or open a case with Commerce Cloud Support.

Knowledge Article Number

005460903

 
Loading
Salesforce Help | Article