Microsoft 365 app showing expired license error — safe fix

An "expired license" message means the app can’t read a valid license token. Most often this comes from stale authentication, a device clock mismatch, or a local credential cache problem, not a billing cancellation. Start with three quick checks: network/service status, system time, and which account is signed in. If those pass, try the safe sign-out/sign-in steps, then clear local credentials or ask your tenant admin to confirm license assignment.

What does an "expired license" error actually look like

This section shows the common visual states so you can match the message before trying fixes. Identify which one you see and capture a screenshot before changing accounts or making system changes.

• An activation banner, colored ribbon, or message across Word, Excel, PowerPoint, or other Office apps saying the product is disabled, expired, or needs attention.

• The app opens in read-only or reduced-functionality mode; you can view but cannot edit or save.

• Repeated sign-in prompts or a sign-in loop that ends with an expired/license-warning message.

• A blocking modal or dialog with wording such as "Product deactivated", "This product is unlicensed", or "Your account needs attention".

Product deactivated
This product is unlicensed
Your account does not have a license for Microsoft 365

If the app crashes, shows unrelated errors, or can still create and save new documents without a banner, this troubleshooting path may not apply.

Before you start (scope and safe checks)

Start by confirming this article applies and run three quick, reversible checks. This saves time and avoids unnecessary changes.

This article applies to Microsoft 365 apps (Word, Excel, PowerPoint, Outlook, Teams) on personal or managed Windows and macOS devices. You do not need admin rights for the user-level fixes. Stop and escalate to IT if a step requires elevated rights you don't have.

Run these checks now:

1. Network and service health.

• Confirm the device is online and can reach Microsoft sign-in services.

• If you suspect a wider outage, ask your tenant admin to check service health in the admin portal.

2. System date and time.

• Ensure your device clock, date, and timezone are correct; large clock skew can invalidate authentication tokens.

3. Which account is signed in.

• Open File > Account (or Account pane) in the Office app and note the email shown. Confirm whether it is a personal Microsoft Account (MSA) or a work/school Azure AD account.

If any check fails, fix that issue and re-open the Office app before continuing.

Decision tree: account/token vs device cache vs tenant/license

Use this decision tree to choose the smallest fix that will likely resolve the error. Follow the branch that matches your situation.

• If the correct account shows in File > Account and the app is licensed on another device or in a browser, the problem is probably a stale local token: follow Branch A (credential/token refresh).

• If the same account shows the expired-license error across multiple devices and web sign-in shows no license, the issue is likely tenant/license assignment: follow Branch C (tenant/admin checks).

• If the problem is only on this device and signing out/in didn’t help, the issue is likely local credential stores or Office activation cache: follow Branch B (device/profile fixes).

• If the device is managed (Intune or Conditional Access), try Branch A first; if that fails, collect information and escalate to your IT admin because policies may block token refresh or license checks.

Stop and contact IT or Microsoft support if a step requires admin rights you don’t have or if the error returns after fixing it on multiple devices.

Branch A — Safe credential and token fixes (sign out, refresh, browser test)

Sign out and refresh tokens first; these steps refresh OAuth tokens and SSO cookies without deleting user files. Try them on every affected device before doing local cleanup.

1. Close all Office apps (Word, Excel, Outlook, Teams).

2. In the affected app, open File > Account and choose Sign out.

3. Wait 15–30 seconds after signing out before continuing.

4. Open a browser in a private/incognito window and sign in at the Microsoft web portal using the exact account that should have the license.

5. If you used a normal browser window, clear Microsoft SSO cookies or sign out of login.microsoftonline.com sessions.

6. Re-open the Office app and sign in with the same account.

After sign-in the banner should disappear and editing should be restored.

If web sign-in shows the expected license but the app still reports expired, go to Branch B.

Branch B — Device and profile fixes (Credential Manager, Keychain, Office repair)

If token refresh didn't help, remove local credential entries and repair Office. These steps are reversible and do not delete user documents.

1. Remove stored Office credentials from Windows Credential Manager.

• Open Control Panel > User Accounts > Credential Manager > Windows Credentials.
• Remove entries that contain MicrosoftOffice or references to login.microsoftonline.com for the affected account.

2. On macOS, remove Office and auth keys from Keychain Access.

• Open Keychain Access, search for Office, MSAL, adal, or the account email, then delete matching items.

3. Run Office repair on Windows.

• Windows: Settings > Apps > Microsoft 365 Apps > Modify > Quick Repair. If Quick Repair fails, run Online Repair.

4. On macOS, sign out from all Office apps, delete cached credentials in Keychain (step 2), then sign back in. A full uninstall/reinstall is a last resort and only if instructed by support.

5. For Outlook-specific problems, remove and re-add the email account inside Outlook profile settings rather than uninstalling Office.

Get-ChildItem -Path $env:LOCALAPPDATA\Microsoft\Office -Recurse | Where-Object { $_.Name -match "licensing|token" }

After these steps, repeat the Branch A sign-out/sign-in sequence. If the app still shows expired, collect logs and proceed to Branch C.

Branch C — Tenant and admin checks (what to ask your admin)

If the same account shows the error on multiple devices or web sign-in shows no license, the issue is likely tenant-side or license assignment. Ask your admin to verify assignment and check sign-in activity.

1. Ask your tenant admin to verify license assignment in the Microsoft 365 admin console.

• Admins: Users > Active users > select the user > Licenses and Apps to confirm a license is assigned.

2. Ask the admin to check Azure AD sign-in logs for the user for errors such as missing licenses or Conditional Access blocks.

3. Confirm there is no tenant mismatch: users in multiple tenants can be signed into the wrong tenant in the app. Ask the admin to verify the UPN and tenant ID match the expected tenant.

4. If an admin recently changed subscriptions or moved users between tenants, the admin may need to reassign licenses or run a license sync. Administration actions are required; do not attempt tenant-level fixes unless you are an admin.

What to ask IT or the admin to provide back to you: whether a license is assigned, the timestamp of the assignment, any relevant sign-in error codes from Azure AD logs, and whether Conditional Access or licensing changes were applied recently.

How to confirm the app is licensed again (verification)

Verify the fix both in the app and in your account portals so you know editing is fully restored. Check in the app, test editing, and confirm the license in the portal.

1. In-app checks.

• Open File > Account and confirm the correct account email appears and no activation banner is visible.

• Open and edit a document, then save to confirm editing is allowed.

2. Web checks.

• Sign in at the Microsoft 365 portal with the affected account and confirm the subscription/license is visible under account views.

3. Admin checks (if you have an admin or if you asked one).

• Admins: verify the user has an active license in the admin console and review Azure AD sign-in logs for successful token issuance.

If the app still shows expired but web and admin portals show a license, collect logs and escalate.

What logs and screenshots to collect before escalating

Collect screenshots, timestamps, and sign-in diagnostics to give IT or Microsoft support a clear escalation packet. Include what you already tried.

1. Screenshots.

• Screenshot of the expired-license banner or dialog in the app.

• Screenshot of File > Account showing the signed-in account and any product status text.

• Screenshot of the web portal showing the account's subscription/license (if accessible).

2. Error details and times.

• Note the exact text of the message and the local time the error occurred.

3. Sign-in and diagnostic logs (user-level).

• On Windows, capture %LOCALAPPDATA%\Microsoft\Office\16.0\Licensing or token-related logs if present; do not delete files.

• On macOS, note Keychain entries you removed and times of removal.

4. Admin logs to request.

• Ask the admin for Azure AD sign-in logs for the user around the error time, with any error codes.

5. Steps already tried.

• List which branches and steps you performed (Branch A sign-out/sign-in, Branch B credential removal, repairs) and the results.

Provide these artifacts to IT or Microsoft support when you open a ticket to speed diagnosis.

Conclusion

Start with the three fast checks: network/service, system time, and which account is signed in. If those pass, try the safe Branch A sign-out/sign-in and browser test. If that fails, clear local credentials and run Office repair (Branch B). Only then ask an admin to check license assignment or Azure AD sign-in logs (Branch C). If fixes fail across devices, hand the escalation packet to your admin or Microsoft support.