Skip to main content
Version: Next

Phase 02: Resource Providers

Runbook Azure

DOCUMENT CATEGORY: Runbook SCOPE: Azure resource provider registration PURPOSE: Register required providers for Azure Local MASTER REFERENCE: Microsoft Learn — Resource Providers

Status: Active

Overview​

Azure Local requires specific resource providers to be registered in your Azure subscription before deployment. This phase ensures all required providers are registered and validated.

What This Accomplishes​

  • Provider registration — registers all Azure resource providers required for Azure Local
  • Validation — verifies all providers are in "Registered" state
  • Foundation ready — prepares subscription for subsequent RBAC and deployment phases

Prerequisites​

Azure Authentication Required

Before running any scripts in this phase, ensure you have an authenticated Azure session. See Authentication for options including Azure PowerShell, Azure CLI, and service principal authentication.

Run AsDescription
⚡ Elevated AdminContributor or Owner role at subscription level
  • Landing Zones Complete — Phase 01: Landing Zones completed
  • Subscription Access — Contributor or Owner role at subscription level
  • variables.yml — Configured with target subscription ID
Subscription-Level Permission Required

Resource provider registration requires Contributor or Owner role at the subscription level. Users with only resource group-level permissions cannot register providers.

Required Resource Providers​

Azure Local requires the following 12 resource providers:

Provider NamespacePurposeCritical
Microsoft.HybridComputeAzure Arc-enabled servers✅
Microsoft.GuestConfigurationAzure Policy guest configuration✅
Microsoft.HybridConnectivityAzure Arc connectivity✅
Microsoft.AzureStackHCIAzure Local cluster management (core)✅
Microsoft.KubernetesAzure Arc-enabled Kubernetes✅
Microsoft.KubernetesConfigurationKubernetes configuration✅
Microsoft.ExtendedLocationCustom locations for Arc✅
Microsoft.ResourceConnectorAzure Arc Resource Bridge✅
Microsoft.HybridContainerServiceHybrid container workloads✅
Microsoft.AttestationSecurity attestation✅
Microsoft.StorageStorage accounts for deployment✅
Microsoft.InsightsMonitoring and logging (Key Vault audit)✅
Microsoft.Insights is Critical

The Microsoft.Insights provider is required for Key Vault diagnostic logging. Deployment will fail without this provider registered, as it breaks diagnostic account creation and Key Vault audit logging.

Tasks​

TaskDescriptionDuration
Task 01: Register Resource ProvidersRegister all required providers in target subscription5–15 min
Task 02: Verify Provider RegistrationValidate all providers show "Registered" status2–5 min

Configuration Reference​

Config PathDescription
variables.yml → azure.subscriptions.lab.idTarget subscription for provider registration

IIC Example​

Subscription: iic-lz-azurelocal-001 (azure.subscriptions.lab.name)

All 12 providers are registered against this single subscription. In the full deployment model, providers must be registered in each subscription that hosts Azure Local resources.

Validation​

After completing this phase, verify:

  • All 12 resource providers show "Registered" status
  • No providers show "NotRegistered", "Unregistered", or "Registering" status
  • Azure Activity Log shows successful registration events

Next Steps​

After resource providers are registered, proceed to Phase 03: RBAC & Permissions to configure role-based access control.

References​

PreviousUpNext
Phase 01 — Landing ZonesAzure FoundationPhase 03 — RBAC Permissions

Version Control

  • Created: 2026-01-15 by Azure Local Cloudnology Team
  • Last Updated: 2026-03-02 by Azure Local Cloudnology Team
  • Version: 2.0.0
  • Tags: azure-local, phase-02, resource-providers
  • Keywords: resource providers, provider registration, Azure Local requirements
  • Author: Azure Local Cloudnology Team