Microsoft Lists sign-in failures: diagnose and fix fast

Microsoft Lists stopping at the sign-in screen is usually caused by one of three things: your account (credentials or MFA), your browser/device state (cookies, extensions, cached auth), or a tenant/IT policy blocking authentication. Quick tests — a private/incognito window, a different browser or device, and clearing Microsoft auth cookies — will show which of those is the cause and often restore access within minutes. If those steps fail, IT must check licenses, Azure AD sign-in logs, Conditional Access and service health.

I can’t sign in — what exactly is happening right now?

Stuck on sign-in page
Endless spinner after you enter credentials
Sign-in error with a code or message (for example: "We can't sign you in" or AAD error)
Bounced to a different/personal Microsoft account
Blank page or redirect loop

When it appears: right after you click Sign in; after an MFA prompt; after selecting an account; or only in one browser or on one device.

Match your situation to the list above before trying fixes: a bounced-to-personal-account symptom points to account/tenant confusion; an endless spinner or blank page suggests cookies, blocked frames or network/proxy blocking; a visible AAD error code usually requires an admin to check sign-in logs and Conditional Access.

Is this my device/account or my organization’s problem? Quick checks to narrow scope

Before you start

• Product and versions: Microsoft Lists in browser (Edge/Chrome/Firefox/Safari) or Lists desktop/mobile apps.
• Privileges needed: none for the user checks below; admin checks described later require tenant admin roles.
• Restart/backup: no restart required for the quick checks; no data at risk.

Do these safe checks first. They tell you whether to keep troubleshooting locally or contact IT.

1. Open a Private/Incognito window and try lists.office.com or lists.live.com.
2. Try a different browser (if you used Chrome, try Edge or Firefox).
3. Try a different device (phone on cellular or another PC).
4. Sign into another Microsoft service (office.com, outlook.com) using the same account.
5. Ask a colleague to sign in to Lists — if they can, it’s likely your device/account.

If Lists works in a private window or on a different device, the issue is local (cookies, extensions, cached auth). If everyone in your org is blocked or you see Conditional Access errors, it’s likely a tenant or policy problem.

Safe, fast fixes you can try in order (no admin rights needed)

Where to act: your browser or device. Privilege: standard user.

1. Use a private window (fastest, non-destructive test).
2. Sign out of all Microsoft accounts in the browser, then sign in with your work account.
3. Clear cookies for Microsoft auth domains only (least disruptive).

Browser settings > Privacy and security > Cookies and site data > See all cookies and site data > search microsoft and remove relevant entries

Expected result: sign-in page prompts for credentials and completes auth. If it still fails, stale cookies were not the only cause.

4. Disable browser extensions temporarily (adblockers, privacy tools can break auth).
5. Try a different browser or the Lists mobile app as a workaround.
6. Remove and re-add the account in Windows/Office (if using desktop sign-in).

removing an account may sign you out of Office apps; you won't lose cloud data.

1. Open Windows Settings > Accounts > Access work or school > Select account > Disconnect.
2. Re-add using Connect.
3. Update your browser or Lists app to the latest version and retry.
4. If using the Lists app and the app is corrupted, sign out in-app, then sign in again. Only reinstall if sign-out and re-sign-in fail.

Expected result for these steps: successful sign-in or a clearer error (MFA prompt or AAD error code). If you get a new error code, capture it for IT.

If you see MFA or Conditional Access prompts that won’t load, try these fixes

Problem: MFA prompt does not appear, shows a blank frame, or loops.

1. Allow pop-ups and redirects for Microsoft auth domains.

Browser settings > Privacy and security > Site settings > Pop-ups and redirects > Add
Domain: https://login.microsoftonline.com

Expected: MFA prompt appears. If it does not, your browser is blocking the frame.

2. Temporarily enable third-party cookies (some MFA flows use cookies inside an iframe).

Browser settings > Privacy and security > Cookies and other site data > Allow third-party cookies (temporary)

Expected: MFA or consent frames load. If enabling cookies fixes it, consider whitelisting auth domains instead of permanently allowing third-party cookies.

3. Complete MFA on the Microsoft Authenticator or choose an alternative method (text, call) shown during sign-in.
4. If an authenticator app push is blocked by OS-level notifications, open the app to see pending requests.

If these steps don’t show MFA, collect the browser console logs and an exact timestamp for IT to check Conditional Access and sign-in failures.

What IT admins should check next (licenses, AAD sign-in logs, conditional access, and service health)

Where to act: Microsoft 365 admin center and Azure portal. Privilege: Global Admin or appropriate roles.

1. Verify licensing

Microsoft 365 admin center > Users > Active users > Select user > Licenses and apps

Expected: user has a license that includes SharePoint/Lists (for example, Microsoft 365 license that includes SharePoint Online). If not, assign an appropriate license.

2. Check service health

Microsoft 365 admin center > Health > Service health

Expected: no ongoing outage affecting Lists/SharePoint. If there is an outage, follow Microsoft guidance and notify users.

3. Review Azure AD sign-in logs

Azure Active Directory > Monitoring > Sign-ins

Expected: locate the failed sign-in entry for the user and timestamp. Note the failure reason: Conditional Access, MFA failure, invalid credentials, blocked by tenant, or device compliance.

4. Inspect Conditional Access policies

Azure Active Directory > Security > Conditional Access

Expected: determine if a policy is blocking the user (for example, requiring a compliant device, specific location, or blocking legacy auth). If a policy is the cause, either create a targeted exception, modify the policy scope, or apply a trusted location.

5. Check Named Locations and network-based blocks (VPN/proxy IP ranges) and device compliance in Intune.
6. If sign-in errors reference application or service principals, check expired credentials or misconfigured app registrations in Azure AD.

What to do if logs indicate MFA/CA block: either adjust policy scope, add an exclusion for affected users/clients, or provide a compliant device path. If license or service problems are found, resolve them or escalate to Microsoft support with collected sign-in IDs.

How to confirm sign-in is fixed and what to do if it isn’t

Verify the fix

1. Open lists.office.com or the Lists app and sign in.
2. Create a small test list (Title: "Sign-in test") and add one item. Successful creation confirms read/write access.
3. Test from another environment (private window and another device).

Expected: you can open Lists, create and edit a list without authentication errors.

If it isn’t fixed — short escalation checklist to give IT or Microsoft support

• Exact time(s) of failure (timezone).
• Username (UPN) and tenant ID.
• Browser/app and version, and whether issue occurs in private window or another device.
• Exact error message or AAD error code (copy/paste if present).
• Screenshots of the error and Azure AD sign-in log entry if available.

Temporary workarounds while IT investigates

• Use the Lists mobile app on cellular data.
• Open lists.live.com (personal service) if your work allows temporary personal lists — be careful with corporate data.
• Ask IT to share the list content via SharePoint link or export while sign-in is blocked.

How to prevent this in future and common things teams miss

For users

• Keep browsers and the Lists app updated.
• Avoid signing into personal and work Microsoft accounts in the same browser profile when possible.
• Whitelist these domains in browser or network policies: login.microsoftonline.com, login.windows.net, microsoftonline.com, office.com, sharepoint.com.

For admins

• Monitor Service Health and subscribe to incident notifications.
• Document Conditional Access exceptions for service accounts and service principals.
• Regularly check app registrations and service principal credentials for expiration.
• Use named locations and granular policy targeting instead of broad-block rules.

Common oversights

• Multiple Microsoft accounts cause account/tenant selection problems.
• Stale cookies or blocked third-party cookies prevent MFA frames from loading.
• Pop-up blockers hide the MFA consent/push frame.
• Conditional Access policies applied too broadly or missing trusted locations.

Conclusion

If a private window or a different device lets you sign in, fix the local browser state (clear Microsoft cookies, disable extensions) and use that environment. If sign-in still fails everywhere, give the exact error, timestamps and a screenshot to IT so they can check licenses, Azure AD sign-in logs and Conditional Access. Meanwhile, use the Lists mobile app or ask for a temporary SharePoint link to continue working.

Frequently Asked Questions

What does an Azure AD error code mean and should I share it with IT?

An AAD error code indicates the specific failure reason (for example, MFA required, blocked by policy, invalid credentials). Copy the full error text and timestamp and share them with IT — that lets admins find the exact sign-in log entry and resolve the issue faster.

Will clearing cookies cause me to lose my data?

Clearing cookies removes browser session data and site preferences; it does not delete content stored in Lists or SharePoint. You will need to sign in again to Microsoft services after clearing cookies.

Why do multiple Microsoft accounts cause sign-in problems?

Browsers cache session tokens and can send the wrong account to Microsoft auth, which may be a personal account instead of your work tenant. Use separate browser profiles or a private window to prevent that confusion.

When should I contact Microsoft support instead of my IT team?

Start with your tenant IT for account, policy or license problems. Contact Microsoft support if tenant admins confirm a Microsoft service outage or if admins need Microsoft to investigate a service-side issue.