White screen nightmare. My work apps stopped working on my phone after I reset my password.

Question

White screen nightmare. My work apps stopped working on my phone after I reset my password.

Becka 5

I get a white screen when trying to log into my Microsoft apps on my Android for work. I tried everything to fix it but nothing worked. I factory reset my phone and installed everything again, plus the latest version of chrome and Webview. I'm still getting a white screen. My work IT person suggested I reach out to Microsoft for assistance. Help?

nan 0 Reputation points

2026-11-01T15:30:04.95+00:00

I’m also experiencing the same issue and was wondering if it might be related to using Android 14 or below, combined with company policies requiring 2FA authentication (such as Microsoft Authenticator). If so, I’m seeing the same white screen problem and haven’t found a solution yet.

2 answers

Your answer

nan 0 Reputation points

2026-11-01T15:30:04.95+00:00

I’m also experiencing the same issue and was wondering if it might be related to using Android 14 or below, combined with company policies requiring 2FA authentication (such as Microsoft Authenticator). If so, I’m seeing the same white screen problem and haven’t found a solution yet.

Answer 1

Clover-L 110 Microsoft External Staff Moderator

Hello Becka,

Welcome to the Microsoft Q&A forum. Thank you for explaining the issue and the troubleshooting steps you've already tried. Since you've already factory-reset your phone, reinstalled the apps, and updated Chrome and Android System WebView, I wouldn't recommend repeating those steps. As a forum moderator, I cannot remotely access your device to diagnose and fix the issue directly. I can only provide guidance and troubleshooting suggestions based on the information you share. From my research, I found several similar reports from other users on Android 13 and 14 devices. In some of them, the white screen started right after a work password change, just as in your case. One user mentioned it was caused by a certificate issue, but didn't share further details. To help narrow down the issue, could you please clarify a few things?

Does the white screen appear in all Microsoft work apps, such as Teams and Outlook, or only in specific apps?
Can you sign in to your work account through a browser on your phone or another device?
Does the white screen appear immediately after entering your email address, after entering your password, or during the verification process?
Has your IT administrator checked whether your account or device is affected by any sign-in or security policies following the password reset?

If possible, please share a screenshot of the white screen directly in this thread.

Once I have these details, I can help you identify the appropriate next steps.

Best regards.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
nan 0 Reputation points

2026-11-01T15:37:48.85+00:00

Hello, I am experiencing a very similar issue on Android 14.

Teams worked normally on the same phone before I changed my work account password. After the password change, Teams required me to sign in again. When I enter my work email address, the app immediately displays a blank white screen before the password or verification page is loaded.

Microsoft Authenticator itself is still working normally, and the latest version of Teams can still be installed and updated on the phone. The problem therefore appears to occur specifically during the work-account sign-in redirect or authentication process.

1.The issue affects all Microsoft mobile apps that require me to sign in with my work account, not only Teams. The same blank white screen also appears when I try to sign in to other Microsoft apps.

2.I can sign in successfully through a mobile browser if I request the desktop version of the website. Sign-in also works normally on my computer, so my account credentials and the organization’s SSO service appear to be generally functional.

3.Normally, after I enter my work email address in a Microsoft mobile app, the sign-in process redirects me to my organization’s domain-specific SSO page, where I can enter my password and complete authentication.

Now, after I enter the email address, the redirect appears to begin, but the organization’s SSO page never loads. The app only displays a blank white screen. Therefore, the issue occurs before I can enter my password and before any MFA, Authenticator, or passkey verification takes place.

4.I have already reported the issue to my organization’s IT department. They stated that devices running “Android 14 or below” or “iOS 15 or below” may be missing a required certificate after a password change. However, they have not identified the certificate, its issuer, or the official Microsoft documentation supporting this explanation. I am also still waiting for a formal response regarding whether they have checked the Microsoft Entra sign-in logs, Conditional Access results, or the organization’s SSO configuration.

Answer 2

Your work IT administrator should now inspect the failed mobile sign-in in Microsoft Entra and correct any Conditional Access, Intune app-protection, device-compliance, or registration requirement shown there.

A factory reset, app reinstall, and current Chrome/WebView already rule out the main local repair path. Do not factory-reset the phone again.

What your IT administrator should check

Reproduce the white screen and note the exact time.
In the Microsoft Entra admin center, open Entra ID → Monitoring & health → Sign-in logs.
Filter by:
- Your work account
- The recorded time
- Status: Failure
- The affected application, such as Microsoft Teams
Open the failed event and review:
- Failure reason
- Sign-in error code
- Additional details
- Conditional Access tab
- Device ID, operating system, client app, and compliance status

Microsoft documents these logs as the primary place for administrators to identify how Conditional Access policies were applied to a failed sign-in.^1^

The administrator should then act on the result rather than broadly disabling security controls:

Require compliant device: Confirm that this newly reset phone is enrolled and reported compliant.
Require approved client app/app protection: Confirm that your account, Android platform, and Teams are correctly targeted. Android devices must first register with Microsoft Entra when these controls are enforced.^2^
Stale or duplicate device registration: Compare the sign-in event’s device ID with the current phone registration and remove only an obsolete record before registering the phone again.
Authentication or MFA failure: Confirm that your authentication method remains registered and usable after the password change and factory reset.

Authenticator and Company Portal requirements

Whether these apps are required depends on your organization’s mobile-access policy:

Microsoft Authenticator can provide MFA, passwordless authentication, and sign-in approval for a work account.^3^
If your organization uses Intune app protection on Android, Intune Company Portal is required as the policy broker even when full device enrollment is not required.^4^

If Intune app protection applies, IT should verify all of these:

Your account has the required Intune license.
Your account belongs to the group targeted by the Android app-protection policy.
Teams and the other affected apps are included in that policy.
The latest Company Portal app is installed.
You are signing in with the same corporate account targeted by the policy.^5^

Do not independently enroll the phone or delete Authenticator account entries unless IT confirms that the relevant policy requires it; doing so can create another device registration or remove a working MFA method.

Useful isolation test

Try the same work account in Microsoft 365 or Teams through Chrome on the phone:

Browser works, apps fail: Give that result to IT; it points them toward mobile-client Conditional Access, app protection, broker, or device-registration processing.
Browser also fails: Record the complete error and correlation/request details shown on the page. Browser error pages often expose the policy requirement that the app’s white screen hides.^6^

If the administrator cannot identify or correct the failed event, a Microsoft 365 administrator—not the end user—should open a support request through the Microsoft 365 admin center so Microsoft support can review the tenant’s sign-in records and policies.^7^

References