Sign-in & Login Problems

Fix Office Sign-In Fails on Pooled Azure Virtual Desktop

WPS Content Manager Sep 28, 2026 869 views

Question details

Users are unable to sign in to Microsoft Office applications when operating within a pooled Azure Virtual Desktop environment.

How to Fix Office Sign-In Failures on Pooled Azure Virtual Desktop Machines

Product: Microsoft Office
Device & OS: Azure Virtual Desktop / Windows
Scenario: Attempting to launch and authenticate into Microsoft Office applications in a pooled virtual desktop session.
Observed behavior: The sign-in process fails entirely. Event Viewer logs display an error stating that Microsoft.AAD.BrokerPlugin settings failed to load, triggering error code -2147024893.

Before you start

Verify whether the issue affects all users in the pooled environment or just specific user profiles, and keep the exact Event Viewer logs handy for your IT department.

Solution 1Recommended

Escalate to IT Administrator for a Microsoft 365 Support Request

Because standard Azure Active Directory broker troubleshooting is often insufficient for pooled virtual environment errors, escalating the issue via the Microsoft 365 admin center is the officially recommended approach.

Error code -2147024893 related to the Microsoft.AAD.BrokerPlugin in pooled Azure Virtual Desktop (AVD) setups usually points to complex profile roaming or token caching issues (such as with FSLogix).

Resolving this requires backend diagnostics from Microsoft support, which can only be requested by a tenant administrator.

Export Event Viewer Logs

Open Event Viewer, navigate to the Application and Services Logs, and export the exact logs showing the Microsoft.AAD.BrokerPlugin failure (error -2147024893).

Contact the IT Department

Provide the exported diagnostic logs to your organization's IT administrator to prove the AAD broker plugin is failing upon sign-in.

Open a Microsoft Support Ticket

The IT administrator must log in to the Microsoft 365 admin center, navigate to the 'Support' section on the left sidebar, and click 'New service request' to initiate an escalation.

Escalate to IT Administrator for a Microsoft 365 Support Request

Admin Privileges Required: Only users with Global Administrator or specialized support roles in the Microsoft 365 tenant can create support requests.

Free Microsoft Office alternative

Try WPS Office for a Hassle-Free Desktop Experience

If Azure AD Broker Plugin errors and Office sign-in failures are disrupting your workflow, consider using WPS Office. It provides a highly compatible, free alternative that lets you edit documents seamlessly without relying on complex enterprise cloud authentication.

1. Download the Installer: Visit the WPS Office website and download the free installation package for Windows.
2. Install on Your Desktop: Run the installer. The lightweight application deploys quickly without heavy registry overhead.
3. Open Your Files Directly: Launch WPS Office and instantly open your existing Word, Excel, and PowerPoint files without needing complex Microsoft 365 sign-ins.

Bypasses complex Azure AD broker plugin dependencies for offline document editing.Fully compatible with Microsoft Office formats including .docx, .xlsx, and .pptx.Lightweight architecture makes it ideal for local desktops or virtual environments.Familiar tabbed user interface requires almost zero learning curve.

microsoft office alternative - wps office

Frequently Asked Questions

What does error code -2147024893 mean in Event Viewer?

This specific error code indicates a failure in loading or registering the Microsoft.AAD.BrokerPlugin package. It means the system cannot process Azure Active Directory authentication, thereby blocking access to Microsoft 365 apps.

Why does this Office sign-in issue primarily affect pooled Azure Virtual Desktop machines?

Pooled environments use dynamic profile management systems like FSLogix. If temporary profile data, authentication tokens, or broker cache directories are not properly synced or excluded during a session transition, the sign-in plugin gets corrupted.

Can an end-user fix the AAD Broker Plugin error manually?

Generally, no. Fixing broker plugin issues in a pooled virtual desktop requires administrative access to re-register Appx packages across the server or adjust Microsoft 365 backend configurations, which must be handled by an IT administrator.

Login & Account Issues