Sign-in & Login Problems

Fix Microsoft 365 'Sorry, That Didn't Work' Sign-In Error

John WilsonJohn Wilson Nov 3, 2026 868 views

Question details

Users are encountering a 'Sorry, that didn't work' error when attempting to sign in to Microsoft 365, Outlook, or mobile mail apps.

How to Fix 'Sorry, That Didn't Work' Sign-In Errors in Microsoft 365
Product
Microsoft 365
Device & OS
not provided
Scenario
Attempting to access Microsoft 365 services, Outlook, or mobile mail applications in an enterprise environment.
Observed behavior
Users receive repeated password prompts or a 'Sorry, that didn't work' error message due to Azure AD Connect synchronization failures.
Before you start

Verify whether this sign-in issue affects all users or only a specific group, and ensure you have administrative access to your organization's Azure AD Connect server before proceeding.

Solution 1Recommended

Restart the Azure AD Connect Service to Restore Synchronization

This is the primary fix when Azure AD Connect synchronization fails, preventing user credentials from syncing to Microsoft 365 cloud services.

When Azure AD Connect stops syncing, cloud services like Office.com and Outlook cannot verify on-premises active directory passwords, leading to authentication failures and the 'Sorry, that didn't work' error message.

1
Log in to the AD Connect Server

Access your organization's Azure AD Connect server via Remote Desktop using enterprise administrator credentials.

2
Check Sync Status

Open the Synchronization Service Manager to verify if the synchronization tasks have stopped completely or are displaying specific error states.

3
Restart the Service

Press Windows + R, type 'services.msc', and press Enter. Locate 'Microsoft Azure AD Sync' in the list, right-click it, and select 'Restart'.

4
Verify Resolution

Wait a few minutes for the initial sync cycle to complete. Have an affected user attempt to sign in to Office.com or their Outlook desktop client to confirm the error is gone.

Restart the Azure AD Connect Service to Restore Synchronization
Check Mobile Access: Once the server synchronization is fully restored, mobile mail applications should automatically stop prompting users for passwords.
Free Microsoft Office alternative

Switch to WPS Office for a Hassle-Free Offline Experience

While Microsoft 365 relies heavily on complex cloud synchronization and Azure AD infrastructure, WPS Office offers a robust desktop suite that works seamlessly offline. Avoid complicated server-side sign-in errors and enjoy a lightweight, highly compatible office suite for free.

  1. 1. Download the Installer: Visit the official WPS website and click the 'Download WPS Office Free' button.
  2. 2. Install the Suite: Run the downloaded installer and follow the simple on-screen instructions to set up the software.
  3. 3. Open Your Files Offline: Double-click your existing Word, Excel, or PowerPoint files to open them instantly without any cloud sign-in prompts.
Works perfectly offline without depending on complex Azure AD cloud synchronization.Highly compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Lightweight installation that doesn't slow down your system or require complex IT deployment.Familiar user interface requiring no learning curve for former Microsoft Office users.Free to download and use for all essential office tasks.
microsoft office alternative - wps office

Frequently Asked Questions

Why am I getting the 'Sorry, that didn't work' error in Microsoft 365?

This error typically occurs when your organization's on-premises Active Directory fails to synchronize with Microsoft 365 via Azure AD Connect, preventing the cloud system from verifying your credentials.

Can a standard user fix the Azure AD Connect sync error?

No, resolving Azure AD Connect synchronization failures requires administrative access to your organization's server infrastructure. You will need to contact your IT support department.

Does restarting the Azure AD Sync service delete any user emails or data?

No, restarting the synchronization service simply forces the server to re-establish its connection with Microsoft 365 and push any pending credential updates. It is perfectly safe and does not delete user data.

Why is this sign-in error only affecting some users and not everyone in the company?

Sync failures primarily affect users who have recently changed their passwords, been newly added, or had their account properties updated during the exact time the Azure AD Connect service was down or stuck.