Microsoft Office 'Unlicensed Product' Activation Failure — Subscription, Credential, or KMS/MAK Validation Issues

Indicators

• Yellow 'Unlicensed Product' or 'Product Activation Failed' banner displayed in Office application title bar
• Office apps open in read-only or reduced-functionality mode — editing and saving documents is blocked
• Repeated sign-in prompts appearing every time an Office application is launched
• Notification: 'We were unable to connect to the Microsoft Store' or similar activation service unreachable message
• Office applications prompt 'Your account doesn't have a license for Office' despite valid Microsoft 365 subscription
• KMS activation returns error 0xC004F074 (The Software Licensing Service reported that the computer could not be activated)

Likely causes

• Microsoft 365 subscription has expired or the assigned license has been removed from the user account in the admin portal
• User is signed into Office with a personal Microsoft account rather than their licensed organizational account
• Cached credentials are stale or corrupted — Office cannot silently re-authenticate to validate the license
• Network firewall or proxy is blocking access to Office licensing endpoints (login.microsoftonline.com, activation.sls.microsoft.com)
• KMS host is unreachable or the KMS activation count threshold has not been met in volume-licensed environments
• MAK key has exhausted its allowed activation count
• Multiple Office installations or mismatched Click-to-Run and MSI versions causing licensing conflicts

Diagnostic steps

1. Open any Office application (e.g., Word), go to File > Account, and note the product name, activation status, and the account currently signed in. Confirm whether 'Product Activated' or 'Unlicensed Product' is shown.
   Identifies the exact activation state and which account Office is using, distinguishing between a subscription issue and an installation/network issue.
2. Check the assigned licenses for the user in the Microsoft 365 Admin Portal: navigate to Users > Active Users > select the user > Licenses and Apps tab. Verify an Office license is assigned and not expired.
   Confirms whether the root cause is a missing or expired license at the tenant level, which must be resolved before any client-side fix will work.
3. Test connectivity to Office licensing endpoints: run `nslookup login.microsoftonline.com` in Command Prompt and `Test-NetConnection -ComputerName activation.sls.microsoft.com -Port 443` in PowerShell. Note whether connections succeed.
   Determines whether a firewall, proxy, or DNS issue is preventing Office from reaching Microsoft's activation and authentication servers.
4. For MSI installs, open elevated Command Prompt, navigate to Office directory (e.g., `cd C:\Program Files\Microsoft Office\Office16`) and run: `cscript ospp.vbs /dstatus`. For Click-to-Run, check: `Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration'` in PowerShell.
   Retrieves detailed activation status, license type, remaining grace period, and any KMS/MAK-specific error information from the local Office installation.
5. Open Windows Credential Manager (Control Panel > Credential Manager > Windows Credentials) and look for any stored credentials referencing MicrosoftOffice, login.microsoftonline.com, or the user's organizational account. Note any stale or conflicting entries.
   Identifies corrupted or outdated cached credentials that may be preventing Office from authenticating silently with Microsoft's licensing service.
6. Run the Microsoft Support and Recovery Assistant (SaRA) tool from https://aka.ms/SaRA-OfficeActivation, selecting the 'Office' category and the 'I'm having problems installing or activating Office' scenario, and review the diagnostic output.
   Provides an automated, guided diagnostic that checks subscription status, network connectivity, installation health, and credential state, and can auto-remediate common activation failures.

Resolution path

• Step 1 — Re-sign in with the correct licensed account: In any Office app, go to File > Account > Sign Out, then sign back in with the user's organizational Microsoft 365 account. Ensure the account matches the one with the assigned license in the admin portal.
• Step 2 — Remove stale credentials: Open Windows Credential Manager > Windows Credentials, remove all entries related to Microsoft Office, MicrosoftOffice16, or login.microsoftonline.com. Relaunch an Office app and sign in again when prompted.
• Step 3 — Run the Office Activation Troubleshooter: Download and run the Microsoft Support and Recovery Assistant (SaRA) from https://aka.ms/SaRA-OfficeActivation. Follow the guided steps; it can automatically re-activate Office, fix token caches, and repair installation issues.
• Step 4 — For KMS environments, re-activate from an elevated Command Prompt by navigating to the Office installation directory and running: `cscript ospp.vbs /act` to trigger KMS activation. Verify the KMS host is reachable: `Test-NetConnection -ComputerName <KMSHost> -Port 1688`.
• Step 5 — If activation still fails, perform an Online Repair: Go to Control Panel > Programs > Programs and Features > Microsoft 365 Apps / Office > Change > Online Repair. This reinstalls Office components and resets the licensing subsystem without removing user data.
• Step 6 — As a last resort, remove all Office licenses using the Office License Removal Tool, uninstall Office completely using the Microsoft Office Removal Tool (aka.ms/SaRA-OfficeUninstallFromPC), and perform a fresh installation, then re-activate.

Prevention

• Implement Microsoft 365 license monitoring alerts in the admin portal or via Microsoft Graph API to notify administrators before licenses expire or are removed from users, allowing proactive reassignment.
• Ensure firewall and proxy allow-lists include all required Microsoft 365 activation and authentication endpoints (login.microsoftonline.com, activation.sls.microsoft.com, ols.officeapps.live.com) so client devices can always reach the licensing service.
• For KMS environments, deploy redundant KMS hosts and configure clients with KMS host failover entries to prevent single-point-of-failure activation outages during maintenance windows.
• Use Microsoft Endpoint Manager (Intune) or Group Policy to enforce periodic Office activation refresh and monitor activation state across the fleet, triggering automated remediation scripts when 'Unlicensed' states are detected.
• Standardise on Click-to-Run deployments via the Office Deployment Tool to avoid MSI/C2R version conflicts, and pin update channels to prevent mismatched component versions that can corrupt the licensing subsystem.

Tools

• Microsoft Support and Recovery Assistant / SaRA (automated Office activation diagnostics and repair — https://aka.ms/SaRA-OfficeActivation)
• ospp.vbs (Office Software Protection Platform script for volume license activation management)
• Windows Credential Manager (stale credential identification and removal)
• Microsoft 365 Admin Portal (license assignment verification)
• Office Removal Tool / SaRA uninstall (clean Office removal for fresh reinstall — aka.ms/SaRA-OfficeUninstallFromPC)
• Test-NetConnection PowerShell cmdlet (network connectivity verification to licensing endpoints)

References

• Unlicensed Product and activation errors in Office — Microsoft Support
• Microsoft Support and Recovery Assistant (SaRA) for Office
• Volume activation of Office using KMS — Microsoft Docs
• Office 365 URLs and IP address ranges (licensing endpoints)