Office 0xC004F003: no Office product is attached to this account

Fix it now

Microsoft publishes 0xC004F003 as the Software Licensing Service reporting that the required licence could not be found. On a subscription install that usually means the signed-in identity holds no entitlement; on a volume build it means no key was ever installed. Reinstalling Office gives the same answer an hour later.

cd "C:\Program Files\Microsoft Office\root\Office16"
cscript ospp.vbs /dstatus

1. In any Office application open File, then Account, and read the account under Product Information. That is the identity Office licenses against, and it is often not the one you assumed.
2. If it is the wrong account, choose Sign out, close every Office application, and sign in with the account that holds the subscription.
3. If it is the right account, have an administrator open the Microsoft 365 admin centre, then Users, then Active users, select the user, and open Licenses and Apps to confirm a plan is assigned.
4. Under Billing, then Licenses, confirm the desktop applications are selected inside that plan. A plan can be assigned with the apps cleared inside it, and the client cannot tell the difference.
5. If ospp.vbs is present and reports no installed key, this is a volume build that was never keyed. Install the key with cscript ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX and activate with cscript ospp.vbs /act.

Close every Office application before rechecking. The client caches its last answer and will not re-ask straight away just because something changed in the tenant.

If Product Information now names your plan or your product, you can stop. If not, the next section covers how the check works and which of the five situations you are in.

Why it happens

Two quite different Office families produce this code, and the first job is knowing which one is in front of you. Subscription Office carries no product key: at launch it looks for an authenticated identity, asks Microsoft’s licensing service what that identity is entitled to, and caches the answer in the user’s profile. Volume-licensed and perpetual builds do not sign in at all; they expect a product key, installed locally or issued by a Key Management Service host. Look for ospp.vbs in the Office program folder – if it is there you are on the volume family, and if vnextdiag.ps1 is there instead you are on the subscription one.

Microsoft’s published text for 0xC004F003 is narrow: the Software Licensing Service reported that the required licence could not be found. It publishes the same idea for 0xC004F007 and 0xC004F008 – the licence could not be found. Note what none of them say. Not that the account is wrong, the plan inadequate or the key invalid; only that the licensing service went looking and came back empty. That is why the diagnosis comes from the tenant or the key rather than from the code.

For subscription installs there are two layers to check and people routinely stop at the first. Buying seats does not license anyone: a tenant can own a hundred unassigned seats while a user sits unlicensed, because assignment is a separate act. And inside an assigned plan the individual services can be selected or cleared, so the desktop applications can be switched off within a licence that is otherwise correctly assigned. From the client both states look identical.

Full reference

Matching what you see to what is wrong

The three licence-not-found codes, side by side

They are published as near-synonyms, and treating them as one investigation is correct. What is not correct is inventing a distinction between them – that the local store is empty for one and the service refused for another – because Microsoft does not draw that line. Diagnose from what is installed and what is assigned.

Where each family keeps its licence

Checking the tenant properly

1. Users, then Active users, then the user, then Licenses and Apps – is a licence assigned at all?
2. Billing, then Licenses, then the user or group – are the desktop applications selected inside it?
3. If the licence comes from a group, look at the group rather than the user, because a direct edit will be reverted at the next sync.
4. Confirm how many seats of that plan are assigned against how many are owned, before assuming you need to buy.
5. After any change, have the user close every Office application and sign in again. Waiting for the client to notice on its own is slower and less certain.

0xC004E007 and the temptation to read something into it

0xC004E007 appears alongside these codes and is not in Microsoft’s published Office activation tables. There is no vendor text for it. Describe it for what it is – a licensing-service failure raised in the same exchange – and diagnose from the codes that are documented. Pages that give it a confident definition are reconstructing one, and if that reconstruction happens to be wrong it will send you to the wrong half of this article.

Before you buy a seat

• Look at your assigned-versus-purchased count first. Organisations routinely hold seats bought for people who have since left.
• Confirm the user is not simply signed in with the wrong account, which costs nothing to correct and accounts for a surprising share of these.
• Confirm the machine is not a volume-licensed build that needs a key rather than a subscription, because a seat will not license it.
• If several users are affected at once, check whether a licensing group changed rather than assuming a purchase is needed.
• The browser versions at office.com will keep someone working today while you sort the entitlement out.

Every code this article covers

Confirm the fix worked

1. File, then Account in Word names the subscription or the product against the right account, with no activation prompt.
2. In the admin centre, the plan is assigned and the desktop applications are selected within it.
3. On a volume build, cscript ospp.vbs /dstatus reports the licence status as licensed.
4. Restart and open Excel first; a licence that survives a cold start has been cached properly.
5. Check a second user on the same plan, to confirm the plan rather than one account was the problem.

Questions people ask about this