Sign-in & Login Problems

Fix Microsoft 365 Sign-In Errors After Clearing TPM (80072EE7)

Maira Mehtab Sep 22, 2026 869 views

Question details

Users are unable to sign in to Microsoft 365 desktop applications such as Outlook and Teams after the system's Trusted Platform Module (TPM) has been cleared, resulting in specific error codes.

Product: Microsoft 365
Device & OS: Windows
Scenario: Attempting to sign in to desktop Office apps after clearing the computer's TPM.
Observed behavior: Desktop applications fail to sign in, often displaying error codes 80072EE7 or 0x80072F9A, while Office on the web continues to function normally.

Before you start

Ensure you have your BitLocker recovery key and system administrator credentials handy, as troubleshooting TPM and encryption issues requires administrative access.

Solution 1Recommended

Gather System Logs and Escalate to Microsoft Support

Since this issue involves deep system components like the TPM and BitLocker, escalating to Microsoft's specialized support or the IT admin community is the most effective path.

Errors like 80072EE7 and 0x80072F9A after clearing the TPM indicate a mismatch between Microsoft 365's hardware-bound authentication tokens and your device's encryption module. Because this often requires unregistering and re-registering the device in Azure AD, specialized administrative support is needed.

Collect BitLocker Details

Open your Windows Settings and navigate to the Device Encryption or BitLocker settings to confirm your drive's encryption status and save the details.

Gather Event Logs

Open the Event Viewer in Windows and save the administrative logs related to Microsoft Entra ID (formerly Azure AD) and Microsoft Office applications.

Post in the Office Management Community

Navigate to the Microsoft Tech Community or Microsoft Q&A forums and post your issue, attaching the gathered error codes (80072EE7, 0x80072F9A) and relevant logs for expert analysis.

Contact Support Directly

If you are part of a corporate network, contact your IT administrator to clear your device's old TPM tokens from the server. For personal devices, use the 'Get Help' app in Windows to open a support ticket with Microsoft.

Use Office on the Web as a Workaround: While waiting for a permanent resolution, you can continue to use Office on the web, as browser-based access bypasses the local TPM token requirements.

Free Microsoft Office alternative

Switch to WPS Office to Avoid Complex Authentication Errors

Tired of dealing with complicated TPM, BitLocker, or Entra ID sync issues? WPS Office is a lightweight, highly compatible alternative that lets you edit your Word, Excel, and PowerPoint files without relying on complex hardware encryption modules for basic local functionality.

1. Download WPS Office: Visit the official WPS Office website to download the lightweight installer.
2. Install and Sign In: Follow the simple installation prompts and sign in using a standard email or third-party account without complex hardware dependencies.
3. Open Your Files: Double-click your existing Microsoft Office files to open and edit them seamlessly in WPS Office.

Highly compatible with all major Microsoft Office formats (.docx, .xlsx, .pptx).Lightweight desktop client that doesn't rely on complex hardware-level TPM integrations for local document editing.Familiar user interface requiring zero learning curve to make the switch.Free to use for everyday productivity tasks.

microsoft office alternative - wps office

Frequently Asked Questions

Why does clearing the TPM break Microsoft 365 sign-in?

Microsoft 365 desktop apps often tie your authentication tokens to your device's physical hardware via the TPM. When the TPM is cleared, these local tokens are invalidated, causing a mismatch with the server and resulting in errors like 80072EE7.

Can I still access my emails and documents while the desktop apps are broken?

Yes, you can use Office on the web via your internet browser. The web versions authenticate differently and do not rely on local TPM hardware tokens.

What are errors 80072EE7 and 0x80072F9A?

These are specific Windows and Microsoft Entra ID network and authentication errors. They indicate that the application cannot securely verify your hardware's cryptographic keys after the TPM state was modified.

Login & Account Issues