Content reviewed: 12 October 2026

Windows 11 Pro can step up to Enterprise when an entitled user signs in, without deploying a new image. An assigned licence alone is insufficient: the device needs an appropriate Windows base, the correct identity state and working subscription verification. This guide covers an ordinary business PC; virtual desktops and other activation models need their own checks.

Four checks before changing the licence

User subscription activation prerequisites
LayerEvidence to collect
WindowsSupported Pro edition with a valid, activated base
DeviceMicrosoft Entra joined or hybrid joined
UserAssigned and enabled Windows Enterprise plan
Sign-inWork identity and access to activation services

The deployment guide requires Enterprise per-user licensing; this mechanism does not use per-device licences. Check the specific person signing in. An administrator account with different entitlements does not demonstrate that an ordinary employee will have the same result.

E3 can mean different products

Microsoft 365 E3 includes Windows Enterprise E3, Office 365 E3 and Enterprise Mobility + Security E3. Standalone Office 365 E3 is not that Windows-containing bundle. Inspect the full product name and the active Windows plan assigned to the actual user. For group-based licensing, also check assignment errors and disabled services.

Assignment eligibility also depends on the offer. The Windows MCA Product Terms require the licensed user of a standalone per-user licence, excluding VDA, to be the primary user of at least one qualifying-OS device that is also their primary work device. The Microsoft 365 terms modify that primary-user requirement, while local Enterprise still requires a qualifying OS. Check the applicable agreement; successful activation does not establish every contractual right.

A valid Pro base and firmware activation

An Enterprise subscription does not supply a missing full Windows licence. Record the underlying entitlement, edition, version and activation status. Home first needs an appropriate path to Pro. We explain the special Business Premium upgrade offer in our Windows Home and Pro guide.

Microsoft documents automatic retrieval of the firmware Pro key and activation of the underlying edition during initial setup, or OOBE. It is therefore inaccurate to say this process can never activate the Pro base. A valid entitlement and supported configuration are still required. On an already configured PC, check activation separately; keep product keys out of tickets and public diagnostic output.

Confirm actual Entra join

Run the read-only command dsregcmd /status in the signed-in user’s context. The diagnostic reference distinguishes device and user state. The table below describes join status, not a licence purchase or successful activation.

Device State in dsregcmd output
AzureAdJoinedDomainJoinedMeaning
YESNOMicrosoft Entra joined
YESYESMicrosoft Entra hybrid joined
NOYESOn-premises domain only; Entra join is not established here

WorkplaceJoined under User State indicates work-account registration. It does not replace the device’s joined state. For hybrid join, also check identity synchronisation. A work mailbox open in Office or an Entra registration alone does not establish these prerequisites.

When the PC stays on Pro

  1. 01

    Check the base

    In Settings → System → Activation, check the Windows edition and activation. Record the supported release and licence source.

  2. 02

    Check identity

    Compare Device State, the signed-in user and tenant. For hybrid join, verify the corresponding synchronised identity.

  3. 03

    Check the plan

    Confirm that Windows Enterprise is assigned to the correct user and that its service is enabled. A purchase order does not prove successful assignment.

  4. 04

    Check account verification

    Investigate connectivity and any request to authenticate the work account again. Record the failure time and corresponding sign-in event.

  5. 05

    Confirm the result

    After the entitled user signs in, check both the Enterprise edition and subscription status. Attach the evidence to a stable device ID.

Our hypothetical pilot has 12 laptops. Ten have activated Pro and Entra join; one has Home and the last is only registered. Assigning the same Microsoft 365 E3 licence does not remove these two different obstacles. Procurement and desktop IT address the Home edition; the identity team addresses the registered device. This makes the result more actionable than a shared ticket saying “E3 does not work”.

Reauthentication and Conditional Access

Older guidance uses an exclusion for the Store application ID 45a330b1-b1ec-4cc1-9161-9f03992aa49f. The current documentation describes an account reauthentication notification on Windows 11 23H2 with KB5034848 or later, removing the need for that exclusion. Before changing policies, check the Windows build and the actual sign-in prompt. Do not disable MFA broadly to resolve one activation failure.

Five devices, fallback to Pro and offline use

User subscription activation supports up to five devices in the Enterprise general availability channel, excluding LTSC. Using a sixth causes the device with the oldest user sign-in to revert to Pro. This is a Windows limit; do not use it to infer Office installation or Shared Computer Activation rules.

If the subscription expires or is transferred, fallback to Pro follows the end of its current validity. Removing the licence does not necessarily cause an immediate edition change. Microsoft describes renewal attempts about every 30 days and the need for internet access. That interval is not a guaranteed fixed grace period for offline devices. On reconnection, check renewal and any authentication request.

Keep other scenarios separate

The activation documentation distinguishes ordinary Azure VMs using Azure KMS: their general activation does not have the same Entra join requirement. Inherited Hyper-V activation requires supported host and guest versions. Assess technical activation and virtualisation rights separately.

Assess shared PCs by the users and exact licence, not just the number of stations. Microsoft 365 F3 has additional eligibility conditions and excludes LTSC; see our F3 eligibility guide. For special clouds, confirm the programme and tenant: the general guide lists Commercial and GCC, while the deployment guide contains additional EA/MPSA restrictions. Do not assume equivalent availability in GCC High or DoD.

Frequently asked questions

Frequently asked questions

Is Microsoft 365 E3 enough?

It includes Windows Enterprise E3, but the base OS, device join and sign-in prerequisites still apply. The relevant plan must be assigned and enabled.

Is Office 365 E3 the same?

No. Confusing Office 365 with Microsoft 365 can explain a missing Windows Enterprise entitlement.

Why did one of six PCs revert to Pro?

User subscription activation supports five devices. When a sixth is used, the device with the oldest user sign-in reverts to Pro.

Is Entra registered sufficient?

Not for the user subscription activation described here. Entra joined or hybrid joined is required; ordinary Azure KMS scenarios have different requirements.

Does successful activation prove correct licensing?

It confirms technical state. Separately document the Windows base, assignment eligibility and rights of the specific product and agreement.