Azure Portal Login stuck on "Let's keep your account Secure"

For the "Let’s keep your account secure" screen, the message means another sign-in method must be added for verification.

For a personal Microsoft account that is blocked on verification or MFA setup, these are the supported actions from the available guidance:

1. Try another verification method if one is available on the sign-in page. A block can be tied to the current method.
2. Switch networks and try again, such as changing between Wi‑Fi and cellular data or using a different Wi‑Fi network.
3. Stop repeated attempts and wait. Repeated retries can extend the block. Wait at least 24 hours, and if needed as long as up to 1 week.
4. Use the Microsoft sign-in helper to identify the sign-in issue and available support options: Start.
5. If the account is locked and the sign-in flow does not show Next, use the aka.ms/ link shown in the sign-in window to submit the account reinstatement request. After submission, a Microsoft Online Safety support agent reviews the request and responds by email. Do not submit multiple requests, because that can slow the response.

For the specific unresponsive Next button behavior in Azure portal, the documented browser-side checks are:

1. Refresh the page.
2. Try a different browser.
3. Use private browsing:
   • Edge: Settings > New InPrivate window
   • Chrome: Incognito mode
   • Safari: File > New Private Window
4. Clear cache and cookies:
   • Edge: Settings > Privacy and Services > Clear Browsing Data
   • Chrome: Settings > Privacy and Security > Clear browsing data

If the account is actually a work or school account, the same message can appear because another verification method is required. In that case, add a method by selecting Next in the prompt, or go to the Security info page of My Sign-ins and choose Add sign-in method. If no alternate method exists and the mobile device is unavailable, the documented path is to contact the organization’s IT help desk.

This is not enough to confirm a Microsoft-side bug. The supported guidance points to verification enforcement, temporary sign-in blocks, account lock, or browser/session issues as the primary causes.

• Verifying your identity when signing in
• Troubleshoot Microsoft verification code issues
• Microsoft account has been locked
• Troubleshoot Azure subscription sign-in issues