Skip to main content

May 15, 2026

First-Gen Tenants - Resource Providers That First-Gen Horizon Cloud Requires to Be in Registered Status in the Microsoft Azure Subscription

To provide for creating and managing a first-gen Horizon Cloud pod in your Microsoft Azure subscription, first-gen Horizon Cloud requires the ability to create and manage various resources in that subscription. Therefore, your subscription must have specific resource providers in Registered status so that Horizon Cloud can perform its required operations to initially deploy the pod and to manage and upgrade the pod over its lifetime. This documentation article lists the resource providers that first-gen Horizon Cloud needs in Registered status.

Important: Use this page solely when you have access to a first-gen tenant environment in the first-gen control plane. As described in KB-92424, the first-gen control plane has reached end of availability (EOA). See that article for details.

According to the Microsoft Azure documentation, a resource provider is a service that supplies the Microsoft Azure resources, such as the Microsoft.KeyVault resource provider supplies the key vault type of resource. As described in the Microsoft Azure documentation topic Azure resource providers and types, before a particular resource can be used in a subscription, that subscription must be registered for the resource provider that supplies that type of resource. That Microsoft Azure documentation goes on to state that some resource providers are registered by default while others require explicit manual registration in the subscription.

Most importantly before deploying a pod, verify that the resource providers listed here all show Registered status in the subscription. When deploying a new pod, the pod deployer creates resources in your subscription by issuing commands to the various Microsoft Azure resource providers to request creation of the types of resources that the deployer needs to create. If a resource provider that requires your explicit manual registration is not in Registered status before the pod deployment reaches its Validate & Proceed step, the wizard will block the pod deployment from going forward from that point. In the Validate and Proceed step of the pod deployment wizard, the pod deployer will validate whether its required set of resource providers has the Registered status in the subscription. If a resource provider that the pod deployer requires does not have the Registered status, the wizard displays an error message. The following screenshot is an example of the case where the Microsoft.Security resource provider is not in Registered status in the subscription.

Screenshot that illustrates the pod deployer's validation message when a resource provider required by the deployer does not have Registered status in the subscription.

Horizon Cloud Required Resource Providers

  • Microsoft.Compute
  • microsoft.insights
  • Microsoft.Network
  • Microsoft.Storage
  • Microsoft.KeyVault
  • Microsoft.Authorization
  • Microsoft.Resources
  • Microsoft.ResourceHealth
  • Microsoft.ResourceGraph
  • Microsoft.Security
  • Microsoft.DBforPostgreSQL
  • Microsoft.Sql
  • Microsoft.MarketplaceOrdering

Was this page helpful?

Provide feedback for this topic

Was this topic helpful?

Please do not include any personal or confidential information.

Generating link…