# No Strong MFA Configured Detects accounts with weak forms of MFA configured, such as SMS or Email. For Okta OIE environments, users with weak factors configured that are solely defined as recovery methods are excluded from this check. The National Institute of Standards and Technology (NIST) recommends using one-time password solutions or cryptographical solutions such as Google Authenticator, Okta Verify, or Microsoft Authenticator as the second factor of authentication. **Recommended Actions** Encourage users to use stronger authentication on a more regular basis. If that is not possible, we recommend tagging users with administrative privileges in critical services like Okta and Workday, and providing them with physical authentication solutions like Yubikey. **Compatibility** [Microsoft Entra ID](/integrations/azure-active-directory-integration.md) [Okta](/integrations/okta-data-integration.md) [Duo](/integrations/duo-security-integration.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.oort.io/understanding-check-failures/oort-insights/identity-posture-management-insights/no-strong-mfa-configured.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.