How to Fix Microsoft 365 Mobile Sign-In Fails for New Users
Question details
Newly created Microsoft 365 accounts are unable to sign in to the service on mobile devices, whereas older existing accounts function without any issues.

- Product
- Microsoft 365
- Device & OS
- Mobile devices
- Scenario
- Attempting to access Microsoft 365 services and Office applications on a mobile device using a newly provisioned user account.
- Observed behavior
- The sign-in process fails for new accounts, potentially blocked by Conditional Access, multifactor authentication (MFA), or mobile application policies, while existing accounts remain unaffected.
Ensure you have Azure AD administrator or global administrator privileges to review Conditional Access policies and manage user MFA and device settings in the Azure portal.
Reset MFA and Re-register Mobile Device in Azure Portal
Use this diagnostic approach to clear potential device registration conflicts and reset the MFA configuration for the newly created user.
Sign-in failures for new users on mobile devices are often caused by misconfigured conditional access rules or stalled MFA synchronization. By clearing the device registration and resetting the MFA state, you force Azure AD to process the sign-in request from scratch.
Log into the Azure Portal as an administrator, navigate to the affected user's profile, and temporarily disable multifactor authentication (MFA).
Go to the Devices section in Azure Active Directory, locate the affected mobile device associated with the user, and delete the device registration.
Wait several hours to ensure that the removal of the device and the MFA changes fully propagate across all Microsoft 365 servers.
Re-enable MFA for the user. Have the user configure the Microsoft Authenticator app again from scratch and attempt the mobile sign-in.

Switch to WPS Office for a Hassle-Free Mobile Experience
If strict Conditional Access policies and Microsoft 365 mobile sign-in errors are slowing down your team's productivity on the go, try WPS Office. It provides a lightweight, easy-to-use alternative with excellent mobile apps that require less complex administrative setup while maintaining full compatibility with your existing Microsoft Office files.
- 1. Download WPS Office: Visit the Google Play Store, Apple App Store, or official WPS website to download the free mobile app.
- 2. Install and Launch: Install the application and open it on your mobile device. You can start using it immediately without complex Azure AD administrative setups.
- 3. Open Office Files: Tap on any existing .docx, .xlsx, or .pptx document on your device to open, view, and edit it with seamless format compatibility.

Frequently Asked Questions
Why does Microsoft 365 mobile sign-in fail only for new users?
New users might be subject to recently updated Conditional Access policies, default security defaults in Azure AD, or incomplete synchronization of their newly assigned licenses and MFA states across Microsoft's servers.
How do I check Conditional Access policies affecting mobile sign-in?
Sign in to the Azure portal as an administrator, navigate to Azure Active Directory > Security > Conditional Access, and use the 'What If' tool to test the sign-in scenario specifically for the newly created user on a mobile device.
Can Intune Mobile Application Management (MAM) policies block new accounts?
Yes, if an app protection policy is targeted at all users but the new user hasn't fully registered their device or met the required device compliance standards, the mobile Office apps will inherently block access.
How long does it take for MFA and device changes to propagate in Microsoft 365?
While some changes apply within minutes, removing device registrations and resetting MFA states can sometimes take up to several hours to fully sync across all interconnected Microsoft 365 and Azure AD services.




