'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft Authenticator 8-Digit Code and Azure Sign-In Errors
Question details
The user is unable to sign into the Azure portal because the Microsoft Authenticator app is generating an eight-digit code instead of the required six-digit code, and encountering error AADSTS90072.
- Product
- Microsoft Authenticator and Azure
- Device & OS
- not provided
- Scenario
- Attempting to log into the Azure portal using multi-factor authentication (MFA).
- Observed behavior
- The Authenticator app provides an eight-digit code, and the sign-in fails with error AADSTS90072, indicating the personal live.com account does not exist in the Microsoft Services tenant.
Ensure you know whether the target Azure portal requires a personal Microsoft account or a corporate Work/School account, and have an alternative MFA method (like SMS or backup email) ready.
Verify Account Identity and Target Tenant
Ensure you are using the correct Work or School account rather than a personal live.com account, as mixing them often causes tenant errors.
Error AADSTS90072 typically occurs when a user tries to access an enterprise Azure tenant using a personal Microsoft account that hasn't been added as a guest in that specific directory.
Additionally, personal Microsoft accounts often generate eight-digit verification codes, whereas enterprise TOTP implementations expect a six-digit code.
Sign out of your current Microsoft session in your browser, or open a private/incognito browsing window to prevent cached credentials from automatically signing you in.
Go to the Azure portal sign-in page. When prompted, explicitly enter your Work or School account credentials rather than your personal email address.
Open the Microsoft Authenticator app and ensure you are looking at the code for your 'Work or school account' profile, which should display a six-digit code.
Request Support in the Microsoft Q&A Forum
If you are locked out and your Authenticator app continues to malfunction, you will need to escalate the issue to Microsoft's dedicated MFA support channels.
Avoid Login Hassles with WPS Office
While resolving Azure tenant and Microsoft Authenticator issues can lock you out of cloud services, your daily productivity shouldn't stop. WPS Office is a free, lightweight, and incredibly powerful alternative to Microsoft Office that lets you work offline and online without complex corporate tenant requirements.
- 1. Download the installer: Visit the official WPS website and download the free installation package for your operating system.
- 2. Install and launch: Run the installer, follow the on-screen instructions, and launch WPS Office.
- 3. Open your files instantly: Drag and drop your existing Microsoft Office files directly into WPS to continue working without interruption.
Frequently Asked Questions
Why is my Microsoft Authenticator showing an 8-digit code?
An 8-digit code is typically generated for personal Microsoft accounts (such as @outlook.com or @live.com) using proprietary Microsoft authentication protocols. Work or School accounts, as well as third-party services, standardly use a 6-digit TOTP (Time-based One-Time Password) code.
What does Azure error AADSTS90072 mean?
Error AADSTS90072 means that the user account from an external identity provider (like a personal live.com account) does not exist in the specific Microsoft Services tenant you are trying to log into. You must either use an account native to that directory or have the administrator add your personal account as a guest.
Can I bypass the Authenticator app if it's giving the wrong code?
Yes, if you previously configured alternative authentication methods (such as receiving a text message, a phone call, or using a backup email), you can click 'Sign in another way' on the login screen to bypass the app temporarily.
