Unable to Activate Azure Benefits on Windows Server 2025 Datacenter Azure Edition VM

Question

Unable to Activate Azure Benefits on Windows Server 2025 Datacenter Azure Edition VM

Priyanka 0

Hello Azure Support Team,

We are encountering an issue while attempting to activate Azure benefits on a Windows Server 2025 Datacenter Azure Edition virtual machine.
The VM displays the following message:

"Your Windows Server 2025 Datacenter Azure Edition VM has been deactivated because you are not running on Azure or a supported Azure Stack hypervisor, or that you have not enabled Azure benefits on the supported Azure Stack. To enable Azure benefits, go to your cluster settings in Windows Admin Center > Enable Azure benefits."
Details:

Operating System: Windows Server 2025 Datacenter Azure Edition

Issue: VM appears to be deactivated and Azure benefits cannot be activated.

We would like to understand:

Why the VM is detecting that it is not running on a supported Azure/Azure Stack environment.

Whether any additional configuration is required to enable Azure benefits.

How to reactivate the VM and restore the Azure Edition licensing status.

Any diagnostic steps we can perform to verify the current licensing and activation state. Please let us know if you require any additional information.

Subscription ID: a094c85c-f60d-4f02-b40d-a5b42c4bfdc8
VM name : ArtlockerAutomationVM

Thank you for your assistance. Best regards,
Priyanka

VarunTha 15,090 Reputation points Microsoft External Staff Moderator

2026-07-25T16:57:02.04+00:00
Hi Priyanka,

sorry you’re running into this. That deactivated message for Windows Server 2025 Datacenter: Azure Edition generally means the VM’s OS licensing/attestation check can’t validate that it’s running in a supported Azure / supported Azure Stack hypervisor scenario, or that Azure benefits aren’t enabled / attested correctly on the supported host side.

Below are the practical things to check and the likely remediation approach based on the guidance we have.

Why the VM is detecting “not running on a supported Azure/Azure Stack environment”

For Azure Edition licensing/benefits to activate, the VM needs to pass the appropriate verification path. The troubleshooting guidance calls out two big families of root causes:

IMDS connectivity/attestation problems If the VM can’t communicate with the Azure Instance Metadata Service (IMDS) (or IMDS-related certificates/validation aren’t up to date), activation can fail and the VM can become deactivated.

Network / routing / KMS connectivity or network restrictions (more common in Azure VM activation flows) While your message specifically references Azure benefits + supported hypervisor, the same theme applies: outbound connectivity required for licensing/activation needs to work reliably (for example, connectivity through NSGs/firewalls, and in more complex cases “forced tunneling” scenarios).

Additional configuration required to enable Azure benefits

The message you posted already hints at the key step: enable Azure benefits on the supported “cluster settings” side via Windows Admin Center.

So, confirm the following:

You are enabling Azure benefits in the supported management plane (Windows Admin Center → cluster settings → Enable Azure benefits).

Ensure the environment that the VM is running on matches the supported Azure / supported Azure Stack hypervisor requirement for Azure Edition.

Reactivating the VM and restoring Azure Edition licensing status

In the provided documentation, the remediation path typically looks like this (in order):

1) Check IMDS connectivity from the VM

Run the IMDS test from the VM. If this fails, licensing/attestation can fail:

Invoke-WebRequest -Uri "http://169.254.169.254/metadata/instance?api-version=2021-02-01" -Headers @{Metadata="true"} -UseBasicParsing

If it fails: check NSGs and firewalls to ensure traffic to the IMDS endpoint (169.254.169.254) is allowed.

2) Ensure the guest has the required updates and certificates

The guidance specifically recommends:

Install required cumulative updates for your Windows Server version.

Ensure IMDS certificates used for verification aren’t expired/missing.

Validate the Azure VM Agent is installed and up-to-date (an outdated agent can block activation in some cases).

3) If the VM is on an environment with forced routing / custom routing, verify KMS connectivity (Azure activation pattern)

If your environment uses custom routing, the documentation emphasizes ensuring Azure KMS endpoints are reachable (otherwise activation can fail).

Diagnostic steps to verify licensing / activation state

From the relevant troubleshooting materials, these are the two most useful diagnostics you can run:

A) Check the activation/licensing error code

On the VM:

Run:

slmgr /dlv

Look at the returned error details (examples in the provided guidance include codes like 0xc004f074 / 0xc004FD03 / hr=0x80004005, which indicate KMS/service availability or certificate/network issues).

B) Check network connectivity to required endpoints (if applicable)

If you suspect network restrictions (NSG/firewall/route), the guidance for Azure VM activation includes checking KMS endpoint connectivity and next-hop behavior. (The exact endpoint checks depend on your region/environment.)

Please let us know if you have any further queries.

1 answer

Your answer

Answer 1

That message does not necessarily mean the VM uses an unsupported hypervisor. On Windows Server 2025 Datacenter: Azure Edition, it can appear when the guest cannot obtain its activation token from Azure Instance Metadata Service (IMDS), or cannot validate the token's certificate chain.

In an elevated session, run slmgr.vbs /dlv and slmgr.vbs /ato to capture the licensing channel and error. Query IMDS at 169.254.169.254 using the Metadata header and bypassing proxies. Check route print to confirm that address uses the primary Azure NIC, and verify the guest MAC and private IP match the primary NIC in Azure.

If IMDS responds, validate the attested-document certificate chain. Permit certificate and revocation-list downloads, install missing certificates in Local Machine, run C:\Windows\System32\fclip.exe, then restart. The Windows Admin Center Azure-benefits setting applies to Azure Local, not an Azure-hosted VM. If all checks pass but activation remains failed, open an Azure VM support request with outputs.

Unable to Activate Azure Benefits on Windows Server 2025 Datacenter Azure Edition VM

Why the VM is detecting “not running on a supported Azure/Azure Stack environment”

Additional configuration required to enable Azure benefits

Reactivating the VM and restoring Azure Edition licensing status

1) Check IMDS connectivity from the VM

2) Ensure the guest has the required updates and certificates

3) If the VM is on an environment with forced routing / custom routing, verify KMS connectivity (Azure activation pattern)

Diagnostic steps to verify licensing / activation state

A) Check the activation/licensing error code

B) Check network connectivity to required endpoints (if applicable)

1 answer

Your answer