We are announcing the deprecation of Exchange ActiveSync (EAS) certificate-based authentication (CBA) directly to Exchange Online. By the end of 2026, Microsoft will no longer support direct CBA connections from EAS mobile email clients to Exchange Online. After that date, any EAS clients using CBA will need to authenticate via Microsoft Entra ID rather than sending client certificates directly to Exchange Online.
With immediate effect, we will roll out blocks so no new tenants can use the legacy flow, ensuring they can take advantage of the benefits of using the Entra ID flow from the very start.
Important: This change does not affect other Exchange Online authentication scenarios such as Outlook Mobile or Exchange Server/on-premises. It is specific to Exchange ActiveSync (EAS) clients (such as native built-in mobile email apps) using CBA against Exchange Online. This retirement is part of our ongoing efforts to strengthen security by eliminating legacy auth patterns in Exchange Online.
Why Are We Retiring Direct EAS CBA?
Certificate-based authentication for EAS was introduced as a way for organizations to allow mobile device access without passwords, using client certificates for a highly secure, passwordless sign-in experience. With CBA, each user has a certificate verified by the tenant's root certificate authority, and the user can authenticate via a TLS handshake using the public key of that certificate – meaning no private key or password is ever sent over the network, providing a more secure alternative to basic authentication. The previously published guidance for this config is here.
However, the current direct-to-Exchange implementation of EAS CBA is considered a legacy authentication method. In the present flow, user certificates are pushed to mobile devices during configuration. When users connect to EAS to sync email, Exchange receives the certificate and does all the onward processing and validation itself.
This design presents a significant concern as the client itself never obtains a standard OAuth access token – a departure from modern authentication practices – and Exchange relies on this internal, high-privilege mechanism to access data. Furthermore, Azure AD classifies direct certificate-based authentication between the client and Exchange Online as a form of "legacy authentication," meaning it will be blocked by any Azure AD conditional access policies that block legacy authentication. This creates an all-or-nothing challenge for administrators trying to enforce modern security controls while still allowing CBA.
The new model requires EAS clients to perform certificate-based authentication directly via Microsoft Entra ID, just as other client apps do. The proposed secure flow works as follows: the client sends its certificate to Entra ID (Azure AD) for validation; Entra ID validates the certificate and returns an OAuth access token to the client; the client then presents this OAuth token to Exchange Online for authentication. By moving certificate authentication fully into Microsoft Entra ID, admins can uniformly enforce modern security controls and policies for all client access, with no exceptions for certain protocols.
This change also continues our ongoing effort to modernize Exchange Online authentication stack. Over the past few years, we have phased out older authentication methods like Basic Auth, and we recently introduced dedicated ActiveSync CBA endpoints – such as outlook-cba.office365.com for worldwide multi-tenant, outlook-dod-cba.office365.us for DoD, and outlook-cba.office365.us for GCC-High – to support TLS 1.3 and strengthen security and reliability. Requiring Entra-based CBA is the next logical step in this journey, closing one of the last remaining gaps in legacy auth removal.
How do I know if I am Impacted?
If you aren’t sure if you use Exchange ActiveSync CBA or Entra-Based CBA, there’s a couple of ways you can figure that out.
Firstly, ask the person who manages your Mobile Device Management (MDM) configuration. If the auth type used is set as Certificate, rather than OAuth, that could indicate you use this configuration.
The other method is to check Entra’s sign-in event logs. Requests using Exchange CBA show up with the client app of ‘Exchange ActiveSync’, and Authentication Details will show a certificate is being used. Here’s how that flow looks in Entra’s sign-in logs reports:
"Certificate” would be shown as Authentication method:
We will send Message Center posts to tenants using Exchange CBA in the next week calling attention to this change. We’ll update this post once those posts have been sent.
Please note that CBA authentication is something that you must configure deliberately and if your organization never configured it, this deprecation does not impact you.
How to Migrate to Entra-Based CBA
We understand that some organizations have been relying on CBA with Exchange ActiveSync to enhance mobile device security. To ensure a smooth transition, we recommend administrators start planning now to move those devices to the new Entra ID-based CBA method well before the end-of-2026 deadline. The PKI and CA setup for Entra CBA and EAS CBA are fundamentally the same, which should simplify the transition. Below are key steps and considerations for a successful migration:
- Enable Microsoft Entra CBA for your Tenant: Ensure your certificate authorities (CA) are configured in Microsoft Entra ID. At least one CA and any intermediate CAs must be configured, each user needs access to a certificate issued from a trusted PKI, and each CA should have a certificate revocation list (CRL) referenceable from an internet-facing URL. Microsoft provides detailed guidance on setting up Entra CBA in documentation.
- Prepare User Certificates: Verify that each user's client certificate contains the correct identity information. For Exchange ActiveSync clients specifically, the certificate must include the user's routable email address in Exchange Online, in either the Principal Name or the RFC822 Name value of the Subject Alternative Name (SAN) field. Microsoft Entra ID maps the RFC822 value to the Proxy Address attribute in the directory. More info here. If your current certificates were used for direct EAS CBA, they likely already meet this requirement – just verify the presence of the user's email in the certificate's SAN.
- Update Device Configuration: Plan how your mobile devices will perform certificate authentication against Entra ID. In many cases, this may involve updating the device's email profile or MDM/Intune device configuration profiles. The new flow might require collaboration with third-party client vendors to support the change. Consult your mobile device or mail app vendor for specific instructions on enabling Entra (Azure AD) authentication with client certificates. When the feature is configured, users will see a certificate selection prompt during sign-in rather than entering a password.
- Test and Monitor: We recommend testing the new Entra CBA login flow with a pilot group of devices and users before broad rollout. Monitor your Entra ID sign-in logs and Exchange ActiveSync device reports to identify any remaining devices using the legacy CBA method. Proactively reach out to users still on the old method and assist them in moving to the updated configuration.
- Deprecation Timeline: Keep the end-of-2026 deadline in mind for planning. We suggest completing the transition well in advance of this date to avoid any service disruption. In the interim, we will share more details through the Message Center to directly impacted tenants, and update documentation as needed to support your migration.
Conclusion
We strongly encourage any customer still using direct Exchange ActiveSync CBA to begin planning the move to Entra-based CBA now. The Microsoft Entra method offers equal or better security – it's certificate-based, phishing-resistant, and passwordless, but with far better integration into our modern authentication ecosystem and security controls. This change will help protect your organization's data by ensuring all Exchange Online connections follow the most up-to-date security standards, and it eliminates the reliance on internal high-privilege tokens that carry unnecessary elevated rights.
We understand that making changes to your authentication infrastructure can be challenging, which is why we've set a long runway until the end of 2026 for this transition. We'll continue to provide guidance and support throughout this period. Thank you for your cooperation in adopting these security improvements – together, we can ensure a safer, more secure Exchange Online experience for all our customers. If you have any questions or need assistance with setting up Entra CBA, please reach out to Microsoft Support (Entra / Identity) or your account team. We're here to help make this transition as smooth as possible.
The Exchange Online Team