diff --git a/docs/identity/authentication/concept-authentication-strengths.md b/docs/identity/authentication/concept-authentication-strengths.md
index 853e15eaf2f..70b003b543f 100644
--- a/docs/identity/authentication/concept-authentication-strengths.md
+++ b/docs/identity/authentication/concept-authentication-strengths.md
@@ -100,6 +100,9 @@ Conditional Access administrators can also create custom authentication strength
   
   When the user unlocks their Windows device by using Windows Hello for Business, they can access the resource again. Yesterday's sign-in satisfies the authentication strength requirement, and today's device unlock satisfies the sign-in frequency requirement.
 
+- **Authentication strength and registration of security info**: Registering security info requires an MFA session no older than 10 minutes, leading to an interactive request for MFA if such requirement isn't met. This can lead users to choose an MFA method that, when combined with the first factor authentication method previously used, doesn't satisfy the enforced authentication strength, resulting in the error *"Let’s try something else. Another sign-in method is required to access this resource. Close your browser and try again, but choose another way to sign-in"*.
+
+
 ## FAQ
 
 ### Should I use an authentication strength or the policy for authentication methods?