Salesforce is moving two big pieces at the same time. It changes how you build agents powered by AI and it changes how you log in to your own org.
On one hand, Agentforce DX brings agents into the world of source code and DevOps. On the other, starting in July 2026 Admins will need phishing-resistant MFA to log in.
Two different topics, one underlying idea: professionalizing the platform. Here is the full picture, with the official documentation from Salesforce on the table.
What Agentforce DX is: agents as code in Salesforce
From Salesforce DX to Agentforce DX
If you come from the pro-code world, you already know Salesforce DX. It is the set of tools for building, testing and releasing applications on the platform, and it includes the Salesforce CLI, the VS Code extensions, Agentforce Vibes IDE, DevOps Center and development environments such as scratch orgs and sandboxes.
The news is simple but powerful. Agentforce DX extends those same tools so they also work with agents.
Why Salesforce is pushing toward pro-code
The Agentforce Builder is great for getting started, and nobody is retiring it. Its interface and the Testing Center let you create and test agents with clicks, no code needed.
The point is what happens when the agent gets serious. A modern DevOps process requires storing the agent's source code in a version control system, so that repository is the source of truth for your production org.
The key concept is this: agents are metadata. Just like any other Salesforce customization, and Agentforce DX is what makes it possible to treat them that way.
Create, preview and test from the Salesforce CLI
In practice, the whole cycle lives in your terminal and in VS Code. Agentforce DX provides CLI commands and a VS Code extension to create, preview and test agents outside Agentforce Studio, and to move the agent's metadata between your DX project and your scratch orgs, sandboxes and production orgs.
Creation is a two-step process. The command agent generate agent-spec generates the agent spec in your DX project, a YAML file with the agent's information, and agent create builds the agent from that spec.
To try it out you don't need to open the browser. The command agent preview lets you interact with an active agent for testing purposes.
Agent Script: the agent's logic as source code
The stack is completed by Agent Script. It is the language for building agents that Salesforce documents alongside Agentforce DX within its development tools.
The result is that the agent's logic lives in files you can version in Git. That enables the same DevOps flow you already use with the rest of your metadata.
Low-code and pro-code in the same flow
Here is the best news: you don't have to pick a side. When you build an agent you can switch between low-code tools, such as the Agentforce Builder or Flow Builder in your org, and pro-code tools, such as VS Code and the Salesforce CLI on your machine.
The documentation describes it as an iterative process. Using both types of tools gives you flexibility, and the key is to keep your Salesforce DX project in sync with the org.
How to set up your development environment
The setup is nothing exotic. The basic pro-code tools for creating and testing agents are VS Code and the Salesforce CLI, and the environment is set up very similarly to a traditional Salesforce DX setup, with a few extra agent-specific tasks.
One detail to keep on your radar: the update pace is weekly. Salesforce publishes new versions of the CLI and its core plugins every week, including changes to the Agentforce DX commands and the VS Code extensions.
Phishing-resistant MFA in Salesforce: dates, scope and methods
The key enforcement dates
There are no gray areas here, because the dates are official. Enforcement starts on June 22, 2026 in sandboxes, phased in over approximately 7 days, and on July 1, 2026 in production, phased in over approximately 30 days.
Write down these dates: June 22 for sandboxes and July 1 for production. After that, the login for your privileged users changes for good.
Exactly who is affected
The scope is precisely defined. It affects all users who log in to Salesforce, through the direct UI or through SSO, in production and sandbox orgs, who have the System Administrator profile or any of these privileged permissions: Modify All Data, View All Data, Customize Application or Author Apex.
Watch this detail: it is not only the System Administrator profile. Any user with one of those four permissions is on the list.
Which methods qualify as phishing-resistant
The official definition is concrete. Salesforce considers WebAuthn-based Security Keys and Built-in Authenticators, which it also calls Passkeys, to be phishing-resistant, and it recommends adopting passwordless login via passkeys to speed up access.
The examples come from the documentation itself: Touch ID, Face ID and Windows Hello. They work as Built-in Authenticators, while Security Keys include Yubico's YubiKey and Google's Titan Security Key.
Why your usual authenticator is no longer enough
Here's the part that surprises a lot of people. Salesforce categorizes MFA methods by security strength, and the phishing-resistant category, the recommended one, is reserved for Built-in Authenticators and Security Keys.
TOTP code apps and push notifications fall into the standard category. They remain valid for regular users, but they do not meet the new requirement for privileged accounts.
What happens if your org uses SSO
Using Single Sign-On does not exempt you from the change. For privileged users who sign in via SSO, Salesforce will require signals confirming that the Identity Provider used a phishing-resistant MFA method, and if those signals are not present, the user will have to enroll a compatible method in the Salesforce interface.
The concrete task is to coordinate with your identity team. You need to verify that the IdP is correctly sending the ACR or AMR signals.
The end of automatic exemptions
Exceptions are going away too. After the enforcement date, the Waive Multi-Factor Authentication for Exempt Users permission no longer automatically exempts users from the requirement, and users who have it will be prompted to enroll just like everyone else.
There is a formal path for valid use cases. Restoring the exemption, for example for automated testing tools, requires contacting Salesforce Support for approval.
What to do if an Admin gets locked out
If someone gets locked out, there is a rescue protocol. Another Admin in the org can generate a temporary identity verification code, disconnect the old methods and help the locked-out user re-register.
And if no other Admins are available, there is only one path. Contact Salesforce Support for assistance.
Mandatory MFA for all employees
This change is part of a broader move. Salesforce is also enforcing MFA for all employee logins, both direct UI and SSO: for users without privileged permissions, enforcement starts on June 22, 2026 in sandboxes and on July 20, 2026 in production.
The whole plan is published in one place. The Security-Related Product Updates to the Salesforce Platform page works as a permanent roadmap of critical security changes, designed to give advance notice, technical clarity and architecture guidance.
Checklist to get your org ready on time
Preparation is not complicated, but it takes coordination. The official guide points to these steps:
Enable the methods: make sure Security Keys and Built-in Authenticators are enabled in your org.
Turn on passkeys: you can also enable passwordless login with Passkeys for faster logins.
Review your SSO: verify with your identity provider that it uses phishing-resistant MFA, or enable Salesforce MFA for SSO logins.
Test the flow: confirm that you can enroll and use phishing-resistant MFA methods correctly.
Communicate and pre-register: prepare users for the change and encourage early registration before the enforcement date, to avoid disruptions.
Audit permissions: identify who currently has the System Administrator profile or any of the four privileged permissions.
The common thread: a more professional platform
The two topics seem unrelated, but they tell the same story. Salesforce is raising the bar on the platform's professionalism.
Agents stop being a point-and-click experiment and become metadata versioned in Git, with a DevOps lifecycle. And privileged access stops depending on interceptable codes and relies on phishing-resistant cryptography instead.
In both cases, the one who prepares early wins. The developer who already masters Agentforce DX and the Admin who already has a registered passkey will be a step ahead when everyone else is just starting to react.
Official Salesforce references
Agentforce DX, Agentforce Developer Guide: https://developer.salesforce.com/docs/ai/agentforce/guide/agent-dx.html
Set Up Your DX Environment, Agentforce Developer Guide: https://developer.salesforce.com/docs/ai/agentforce/guide/agent-dx-set-up-env.html
Create an Agent (Agentforce DX), Agentforce Developer Guide: https://developer.salesforce.com/docs/einstein/genai/guide/agent-dx-create-agent.html
Agentforce APIs and SDKs (includes the agent preview command): https://developer.salesforce.com/docs/einstein/genai/guide/get-started-agents.html
Get Started, Agentforce Developer Guide (Agent Script and Agentforce DX): https://developer.salesforce.com/docs/ai/agentforce/guide/get-started.html
Salesforce CLI: https://developer.salesforce.com/tools/salesforcecli
Prepare for Phishing-Resistant MFA Enforcement for Privileged Users including Admins, Salesforce Help: https://help.salesforce.com/s/articleView?id=005321563&language=en_US&type=1
Prepare for MFA Enforcement for All Employee Users, Salesforce Help: https://help.salesforce.com/s/articleView?id=005321561&language=en_US&type=1
Security-Related Product Updates to the Salesforce Platform, Salesforce Help: https://help.salesforce.com/s/articleView?id=005317465&language=en_US&type=1



![Masterclass: Developing with AI on Salesforce: Real Cases and the Tricks [Nobody Tells You]](https://info.vantegrate.com/pulse/images/ia-salesforce-desarrollo-productividad-prototipos-flujo-trabajo-crm-inteligenciaartificial.png.webp)











