Build resilience with credential management
In brief
The article updates guidance on credential-validation dependencies, passwordless authentication, avoiding single points of failure, and contingencies for large-scale disruptions.
What Entra admins need to know
Administrators should consult the revised guidance when reviewing authentication resilience and credential strategy; no mandatory action is stated.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Build resilience with credential management
When a credential is presented to Microsoft Entra ID in a token request, there can be multiple dependencies that must be available for validation. The first authentication factor relies on Microsoft Entra authentication and, in some cases, on external (non-Entra ID) dependency, such as on-premises infrastructure. For more information on hybrid authentication architectures, see Build resilience in your hybrid infrastructure.
The most secure and resilient credential strategy is to use passwordless authentication. Windows Hello for Business and Passkey (FIDO 2.0) security keys have fewer dependencies than other MFA methods. For macOS users customers can enable Platform Credential for macOS. When you implement these methods users are able to perform strong passwordless and phishing-resistant Multi-Factor authentication (MFA).

- The user's device (not pictured)

Your credential strategy should consider the dependencies of each authentication type and provision methods that avoid a single point of failure.
Because authentication methods have different dependencies, it's a good idea to enable users to register for as many second factor options as possible. Be sure to include second factors with different dependencies, if possible. For example, Voice call and SMS as second factors share the same dependencies, so having them as the only options doesn't mitigate risk.
For second factors, the Microsoft Authenticator app or other authenticator apps using time-based one time passcode (TOTP) or OAuth hardware tokens have the fewest dependencies and are, therefore, more resilient.
Additional Detail on External (Non-Entra) Dependencies
| Authentication Method | External (Non-Entra) Dependency | More Information |
|---|---|---|
| Certificate Based Authentication (CBA) | In most cases (depending on configuration) CBA will require a revocation check. This adds an external dependency on the CRL distribution point (CDP) | Understanding the certificate revocation process |
Provisioning multiple credential types gives users options that accommodate their preferences and environmental constraints. As a result, interactive authentication where users are prompted for multifactor authentication will be more resilient to specific dependencies being unavailable at the time of the request. You can optimize reauthentication prompts for multifactor authentication.
In addition to individual user resiliency described above, enterprises should plan contingencies for large-scale disruptions such as operational errors that introduce a misconfiguration, a natural disaster, or an enterprise-wide resource outage to an on-premises federation service (especially when used for multifactor authentication).
How do I implement resilient credentials?
Next steps
Resilience resources for administrators and architects
@@ -8,9 +8,9 @@ ms.subservice: architecture --- # Build resilience with credential management -When a credential is presented to Microsoft Entra ID in a token request, there can be multiple dependencies that must be available for validation. The first authentication factor relies on Microsoft Entra authentication and, in some cases, on external (non-Entra ID) dependency, such as on-premises infrastructure. For more information on hybrid authentication architectures, see [Build resilience in your hybrid infrastructure](resilience-in-hybrid.md). +When a credential is presented to Microsoft Entra ID in a token request, there can be multiple dependencies that must be available for validation. The first authentication factor relies on Microsoft Entra authentication and, in some cases, on external (non-Entra ID) dependency, such as on-premises infrastructure. For more information on hybrid authentication architectures, see [Build resilience in your hybrid infrastructure](resilience-in-hybrid.md). -The most secure and resilient credential strategy is to use passwordless authentication. [Windows Hello for Business](~/identity/authentication/concept-authentication-passkeys-fido2.md) and [Passkey (FIDO 2.0)](~/identity/authentication/concept-authentication-passkeys-fido2.md) security keys have fewer dependencies than other MFA methods. For macOS users customers can enable [Platform Credential for macOS](~/identity/authentication/concept-authentication-passkeys-fido2.md). When you implement these methods users are able to perform strong passwordless and **phishing-resistant** Multi-Factor authentication (MFA). +The most secure and resilient credential strategy is to use passwordless authentication. [Windows Hello for Business](~/identity/authentication/concept-authentication-passkeys-fido2.md) and [Passkey (FIDO 2.0)](~/identity/authentication/concept-authentication-passkeys-fido2.md) security keys have fewer dependencies than other MFA methods. For macOS users customers can enable [Platform Credential for macOS](~/identity/authentication/concept-authentication-passkeys-fido2.md). When you implement these methods users are able to perform strong passwordless and **phishing-resistant** Multi-Factor authentication (MFA).  @@ -26,14 +26,15 @@ If you implement a second factor, the dependencies for the second factor are add * The user's device (not pictured) - -Your credential strategy should consider the dependencies of each authentication type and provision methods that avoid a single point of failure. ++Your credential strategy should consider the dependencies of each authentication type and provision methods that avoid a single point of failure. Because authentication methods have different dependencies, it's a good idea to enable users to register for as many second factor options as possible. Be sure to include second factors with different dependencies, if possible. For example, Voice call and SMS as second factors share the same dependencies, so having them as the only options doesn't mitigate risk. For second factors, the Microsoft Authenticator app or other authenticator apps using time-based one time passcode (TOTP) or OAuth hardware tokens have the fewest dependencies and are, therefore, more resilient. ## Additional Detail on External (Non-Entra) Dependencies+ |Authentication Method|External (Non-Entra) Dependency|More Information| |---------------------|-------------------------------|---| |Certificate Based Authentication (CBA)|In most cases (depending on configuration) CBA will require a revocation check. This adds an external dependency on the CRL distribution point (CDP) |[Understanding the certificate revocation process](~/identity/authentication/concept-certificate-based-authentication-certificate-revocation-list.md#enforce-crl-validation-for-cas)|@@ -45,7 +46,7 @@ For second factors, the Microsoft Authenticator app or other authenticator apps Provisioning multiple credential types gives users options that accommodate their preferences and environmental constraints. As a result, interactive authentication where users are prompted for multifactor authentication will be more resilient to specific dependencies being unavailable at the time of the request. You can [optimize reauthentication prompts for multifactor authentication](~/identity/authentication/concepts-azure-multi-factor-authentication-prompts-session-lifetime.md). -In addition to individual user resiliency described above, enterprises should plan contingencies for large-scale disruptions such as operational errors that introduce a misconfiguration, a natural disaster, or an enterprise-wide resource outage to an on-premises federation service (especially when used for multifactor authentication). +In addition to individual user resiliency described above, enterprises should plan contingencies for large-scale disruptions such as operational errors that introduce a misconfiguration, a natural disaster, or an enterprise-wide resource outage to an on-premises federation service (especially when used for multifactor authentication). ## How do I implement resilient credentials? @@ -58,7 +59,7 @@ In addition to individual user resiliency described above, enterprises should pl ## Next steps ### Resilience resources for administrators and architects- + * [Build resilience with device states](resilience-with-device-states.md) * [Build resilience by using Continuous Access Evaluation (CAE)](resilience-with-continuous-access-evaluation.md) * [Build resilience in external user authentication](resilience-b2b-authentication.md) 