MCT - Visual Studio Enterprise Subscription - Cannot create AVD host pool

Question

Hi,

I am using MCT sponored subscription VSES - Whereas I can create VMs workload and other functionalities. I cannot create Azure Virtual Desktop pools either Entra ID based or Active directory joined.

Any limitation in the subscription on any fine tune requires?

Answer 1

Hi Selvakumar,

Thanks for posting this is a pretty common scenario when working with MCT-sponsored Visual Studio Enterprise subscriptions, and the good news is it's usually fixable with a couple of checks.

The most likely root cause here is that the Microsoft.DesktopVirtualization resource provider hasn't been registered on your subscription. Even though you can create VMs just fine, AVD host pools depend on this provider being explicitly enabled — and it's not registered by default on all subscription types.

Step 1 – Register the Resource Provider

1. Go to the Azure Portal → Subscriptions → select your VSES subscription
2. In the left menu, click Resource providers
3. Search for Microsoft.DesktopVirtualization
4. If the status shows NotRegistered, select it and click Register
5. Wait a minute or two, refresh, and confirm the status is Registered

You can also do this via PowerShell

Register-AzResourceProvider -ProviderNamespace Microsoft.DesktopVirtualization

https://learn.microsoft.com/en-us/azure/virtual-desktop/prerequisites?tabs=portal

Step 2 – Confirm your RBAC permissions

To create host pools, your account needs at least the Contributor role at the subscription or resource group level. MCT-sponsored subscriptions sometimes have tightened IAM policies. Double-check under:

Subscriptions → Access control (IAM) → View my access

https://learn.microsoft.com/en-us/azure/virtual-desktop/faq

Step 3 – Check for any policy restrictions

Some sponsored/dev-test subscriptions have Azure Policy assignments that block specific resource types or regions. Go to:

Policy → Compliance and look for any denied assignments targeting Microsoft.DesktopVirtualization or the region you're deploying to.

Step 4 – What the error message says

Could you share the exact error you're seeing when the host pool creation fails? That'll help narrow it down further. You can find detailed deployment logs under:

Resource Groups → [your RG] → Deployments → [failed deployment] → Operation details

https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-desktop/troubleshoot-set-up-issues

Regarding your question about whether there are hard AVD restrictions on VSES/MCT subscriptions specifically there's no official documented block, and Visual Studio subscribers are supported for AVD usage as noted in Microsoft's documentation. The Azure credits are intended for dev/test workloads, which AVD qualifies as.

https://learn.microsoft.com/en-us/visualstudio/subscriptions/vs-windows-virtual-desktop

Thanks,
Manish.

Answer 2

The behavior is consistent with subscription-type limitations for Azure Virtual Desktop in certain sponsored or special offer subscriptions.

From the documented setup and troubleshooting guidance for Azure Virtual Desktop:

• Some subscription types (for example MSDN, Free, Education) cannot access required features in specific regions when deploying Azure Virtual Desktop resources via the Azure portal or ARM templates. In these cases, host pool creation or session host deployment can fail even though regular VMs work.
• The documented resolution for this class of issue is to change either:
  • The subscription type, or
  • The deployment region to one that supports the required Azure Virtual Desktop features.

In an MCT-sponsored Visual Studio Enterprise subscription (VSES), Azure Virtual Desktop host pool creation can be blocked in the same way as other restricted offer types. Regular VM workloads are allowed, but AVD control-plane or dependent features may not be.

Actionable steps:

1. Try deploying the host pool in a different Azure region that is supported for Azure Virtual Desktop.
2. If deployment still fails, use or create a different subscription type (for example a standard Pay-As-You-Go subscription) and deploy the AVD host pool there.
3. If the subscription must be used, open a support request with Azure support to confirm whether the specific MCT-sponsored VSES offer ID supports Azure Virtual Desktop and, if not, what upgrade or conversion path is available.

---

References:

• Troubleshoot host pool creation
• Deploy Azure Virtual Desktop (host-pool-standard)
• Use Azure Virtual Desktop with your Visual Studio Subscriptions