A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
Hello Stefan Geisler, we understand that you're experiencing a failure when trying to install the "Microsoft.AdminCenter.AdminCenter" extension on your server. The error includes issues with DNS records, metadata retrieval from Azure, certificate access from Key Vault, and connectivity to required services for the extension setup. Despite multiple attempts, including re-registering and re-onboarding the server from Azure Arc, the same error persists.
This issue might occur because the Azure Arc treats the machine’s managed identity like any other principal. Even though it’s “itself,” the identity does not automatically inherit permissions to read its own metadata or Key Vault entries. RBAC in Azure is explicit you must grant the identity the necessary roles. Without them, certificate retrieval and metadata queries fail.
The server uses its System-Assigned Managed Identity to ask Azure for a certificate. If the identity doesn't have the "Reader" role on the Arc Machine resource, the request is rejected.
Verify Managed Identity Permissions: The most common issue is missing RBAC roles.
- Go to the Azure Portal > Arc-enabled servers > Select your machine
- Select Access Control (IAM) > Add role assignment.
- Assign the Reader role to the Managed Identity of this specific Arc machine.
- Additionally, ensure your own user account has the Windows Admin Center Administrator Login role.
Manage Azure Arc-enabled Servers using Windows Admin Center in Azure | Microsoft Learn
Note: Even though it’s "itself," the identity needs explicit permission to read its own metadata.
Validate Network & Proxy: The extension must reach the Identity Endpoint locally and the WAC Service globally.
- Local Endpoint: The extension calls http://localhost:40342 (the local Arc identity service). Ensure no local firewall or "Loopback" restriction is blocking this.
- Global Endpoints: Ensure your firewall/proxy allows:
*.wac.azure.com,pas.windows.net,*.servicebus.windows.net - SSL Inspection: Crucial.Microsoft docs state that if your proxy performs SSL/TLS inspection (intercepting and re-signing certificates), the WAC extension will fail because it uses certificate pinning for security. You must bypass inspection for the URLs above.
Hope this helps. and please feel free to reach out if you have any further questions. Thanks