How to Bypass “Sign in to set up Office” Pop-ups on Activated Installs

The “Sign in to set up Office” pop-up on an already activated install occurs when Microsoft 365 desktop applications detect an unverified identity token or a lingering OEM trial product key coexisting with your valid subscription. Even though your license status under File > Account displays as fully activated, the application background engine continuously triggers activation checks. This behavior interrupts application startup, disrupts local workflows, and causes background cloud file sync locks.

Fast-Fix: The 45-Second Solution

A lingering OEM trial license key or stale Web Account Manager (WAM) identity token forces Office to prompt for credentials despite an existing active activation. Risk Tier: Low (no local data loss). Primary Reset Step: Open Command Prompt as Administrator, run cscript "C:\Program Files\Microsoft Office\Office16\OSPP.VBS" /dstatus, identify the last 5 characters of any residual license key, and remove it with cscript "C:\Program Files\Microsoft Office\Office16\OSPP.VBS" /unpkey:<5-characters>.

Diagnostic Snapshot

• Severity Tier: Low to Moderate (application remains functional, but persistent UI prompts occur).
• Data Safety Risk: Minimal (local documents remain completely safe; cloud sync and AutoSave may stall).
• Common Cause: Orphaned OEM/Factory trial license keys or corrupt Web Account Manager (WAM) identity tokens.
• Admin Requirement: Local Administrator privileges required to execute Command Prompt licensing commands (ospp.vbs).

The System Break (What This Means)

Microsoft 365 desktop applications rely on two distinct validation engines running simultaneously: the Licensing Subsystem and the Identity Service. The licensing subsystem verifies software entitlement on the physical device, while the identity service validates user authentication for cloud services like OneDrive and Exchange.

When a device comes pre-installed with a factory OEM trial key or accumulates stale authentication tokens from previous sign-ins, the two services desynchronize. The licensing engine recognizes the valid subscription, but the identity service detects an unlinked trial key demanding account assignment. Think of it like a vehicle engine with two ignition switches, one key starts the car cleanly, but a second orphan ignition switch in the dashboard keeps buzzing because it isn’t receiving a matching key sequence.

Conflict Escalators

Certain environments and configuration changes increase the frequency of this activation prompt:

• Pre-Loaded Vendor Images: Installing business or enterprise Microsoft 365 Apps on new hardware without first running a clean uninstall or scrub of pre-installed consumer Office versions.
• Modern Auth Switches: Toggling the “New Outlook” switch or launching Microsoft Teams, which forces MSAL identity checks across all installed Office desktop applications.
• Network & VPN Controls: Active VPN tunnels or strict firewall rules that intercept background calls to licensing.mp.microsoft.com, preventing silent background token validation.

Common Misdiagnoses

• Misdiagnosing as an Expired Subscription: Users often assume their Microsoft 365 subscription has lapsed. However, checking File > Account reveals “Product Activated.” An expired subscription revokes license entitlement globally, whereas this bug is an identity mismatch on a fully paid install.
• Misdiagnosing as Network Disconnection: The prompt is frequently confused with general network connectivity errors. Network errors prevent activation entirely, whereas this issue is an identity loop occurring while the system is connected to the internet.

Immediate Action Steps

Step 1: Remove Stale OEM Product Keys via OSPP Script

1. Close all Microsoft Office applications.
2. Open the Start Menu, search for cmd, right-click Command Prompt, and select Run as administrator.
3. Navigate to the Office installation directory by running:DOS cd "C:\Program Files\Microsoft Office\Office16" (If using 32-bit Office on 64-bit Windows, use cd "C:\Program Files (x86)\Microsoft Office\Office16" instead).
4. Query the active license keys on the machine:DOS cscript ospp.vbs /dstatus
5. Look through the output for any LICENSE STATUS: —NOTIFIED— or residual trial keys. Note the last 5 characters of the installed product key.
6. Uninstall the lingering key by running:DOS cscript ospp.vbs /unpkey:<5-CHARACTERS>
7. Relaunch Word or Excel to verify the pop-up has stopped appearing.

Step 2: Clear Cached Office Identity Tokens

1. Open Control Panel and navigate to Credential Manager.
2. Select Windows Credentials.
3. Expand and remove all entries beginning with MicrosoftOffice16_Data: or ADAL:.
4. Restart your computer and open any Office application to establish a fresh identity token.

Step 3: Re-authenticate the Primary Account

1. Open Word and navigate to File > Account.
2. Under User Information, click Sign Out on all active accounts listed.
3. Exit all Office apps, relaunch Word, and click Sign In to attach your verified subscription identity.

Hard-Stop Red Flags

Escalate the ticket immediately if you observe any of the following conditions:

• Account Deleted or Disabled: The sign-in prompt explicitly states “Account Disabled” or “User account does not exist.”
• Tenant Access Block: The authentication screen presents error code CA20001 or “Conditional Access policy enforces device compliance lockout.”
• KMS Host Failure: Running ospp.vbs /dstatus displays error 0xC004F074 (Key Management Service unavailable) on corporate volume license builds.

What the IT Admin Will Check

• Microsoft 365 Admin Center: Confirm that the user account holds an active Microsoft 365 Apps for Enterprise or Business license assignment.
• Entra ID (Azure AD) Sign-in Logs: Check sign-in logs for failure status codes related to Modern Authentication or Workplace Join device registration.
• Registry Subkey Audit: Inspect HKCU\Software\Microsoft\Office\16.0\Common\Identity to ensure invalid EnableADAL or DisableAADWAM DWORD overrides are not forcing legacy auth loops.

Ticket Closed

For low-risk scenarios where File > Account demonstrates active licensing, removing residual OEM keys via ospp.vbs and resetting Windows credential caches resolves the sign-in pop-up permanently. Ensure all Office applications are fully updated following key removal to maintain identity synchronization across cloud services.