Check Microsoft 365 Subscription Status: Step-by-Step Guide

If your Office apps suddenly start throwing up annoying license warnings or locking you out of editing features, the very first thing you need to do is check Microsoft 365 subscription status. As an IT tech, I see this happen all the time when a credit card expires, a billing cycle hiccups, or local token caches get corrupted on a Windows machine. Don’t panic, because sorting this out is usually a straightforward process once you know where to look. We are going to walk through everything from checking your online account dashboard to using deep administrative command-line tools to force a license refresh on your local workstation.

Checking Status via the Microsoft Account Portal

Before diving into complex command-line scripts, you should always verify the source of truth by checking your web browser. Microsoft handles your licensing status cloud-side, meaning your local apps constantly phone home to verify if you are paid up. If your payment method failed or your enterprise organization unassigned your license, the web portal will tell you immediately. To get a complete overview of your account health, head over to the official Microsoft Account Dashboard and sign in with the exact email address tied to your Office installation. If you are managing an enterprise or education environment, your administrators will typically manage these details through the Microsoft 365 Admin Center instead.

Once logged in, navigate directly to the Services and Subscriptions tab. Here, you will see a clear breakdown of whether your subscription is active, when the next recurring billing date happens, or if your account has fallen into a grace period due to a payment failure. If the web portal says your subscription is active and healthy, but your local Word and Excel apps stubbornly disagree, the problem isn’t your account. The issue lies within your local Windows credential cache or corrupted local activation tokens. That is when we need to roll up our sleeves and break out the command line.

Using OSPP.VBS to Verify Local Office Licenses

When local Office apps lose synchronization with your account, the built-in Office Software Protection Platform script is your best diagnostic friend. This script lives inside your Program Files directory and allows you to inspect installed product keys, view partial license statuses, and even strip out bad activation states. You will need to run your command prompt with elevated administrator privileges to query this database properly. Open your Windows start menu, type cmd, right-click Command Prompt, and select Run as administrator.

Depending on whether your Windows architecture is running 64-bit Office or 32-bit Office on a 64-bit operating system, the path to the script will vary slightly. For standard 64-bit installations, you can execute the status query command directly. Copy and paste the following block into your administrative terminal to check Microsoft 365 subscription status locally:

cscript.exe "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /dstatus

If you installed the 32-bit version of Microsoft 365 on a 64-bit machine, the Program Files directory path will be different. Run this alternative command instead:

cscript.exe "%ProgramFiles(x86)%\Microsoft Office\Office16\ospp.vbs" /dstatus

Review the output carefully. Look for lines indicating the license name, license status (which should read as LICENSED), and the last five characters of the installed product key. If you see multiple conflicting keys lingering from an older trial or a previous Microsoft Office installation, they will frequently clash and break your current subscription authentication. You can safely remove old, unwanted product keys by grabbing their last five characters from the dstatus output and passing them into the script using the uninstallation switch.

cscript.exe "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /unpkey:ABCDE

Browse Microsoft Licenses

Clearing Corrupted Windows Credentials and Tokens

Sometimes the underlying issue isn’t the license script itself, but rather corrupted cached credentials hanging out in the Windows Credential Manager. Windows holds onto authentication tokens so you don’t have to log in every single day. When those tokens expire or get corrupted, Office gets stuck in an endless sign-in loop. To fix this, you need to wipe out the cached MicrosoftOffice16 credentials.

You can clear these out manually through the graphical Credential Manager in the Control Panel, or you can use a quick batch command to purge legacy generic credentials associated with Office. Open up your Command Prompt as an administrator and run the following command to see and wipe problematic cached identities:

cmdkey /list

Take note of any target entries containing MicrosoftOffice16 in their names. You can cleanly delete these offending credentials from the command line by referencing their target name directly. This forces your applications to drop all old authentication data and prompts you for a clean, fresh login the next time you boot up Word or Excel.

cmdkey /delete:LegacyGeneric:target=MicrosoftOffice16_Data:adalsvc

Forcing a License Sync with PowerShell

If you have cleared your old keys, wiped out bad credentials, and verified your account online, but your apps still refuse to cooperate, you can use PowerShell to trigger a forced background check. This technique tells the Office Click-to-Run service to re-evaluate its license state and reach out to the activation servers immediately rather than waiting for its scheduled background task interval.

Fire up an elevated PowerShell window by right-clicking your start menu icon and choosing Terminal (Admin) or Windows PowerShell (Admin). Navigate to your Office installation directory and initiate a manual detection sync using the Click-to-Run client executable. Execute this exact command in your PowerShell prompt:

Start-Process -FilePath "$env:ProgramFiles\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" -ArgumentList "/update user updatetoversion=O365Current" -Wait

This forces the background client to check for any pending updates and re-apply system-level licensing flags. Once the process completes, give your computer a quick restart, open up any Microsoft 365 application, and sign back in with your primary account credentials. Your applications should now successfully establish communication with Microsoft servers, clear out any lingering error codes, and display a fully verified, licensed status.