A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
Hi Baldwin,
This behavior looks like an Azure portal blade/UI failure rather than a service-principal permissions issue. I found another report describing this exact Azure Arc behavior from August 4, 2026, but there is currently no published response confirming a widespread outage or known issue. [learn.microsoft.com]
Recommended checks
- Check Azure Service Health for active or emerging issues affecting Azure Arc, Azure Resource Manager, or the Azure portal in the affected tenant and region.
- Reproduce the issue in an InPrivate/Incognito window.
- Test with another supported browser and temporarily disable browser extensions.
- Clear the browser cache and site data for
portal.azure.com, then sign in again. - Confirm whether the problem affects:
- All users or only one user
- All subscriptions or one subscription
- Multiple tenants
- Multiple browsers and networks
- Multiple tenants
- All subscriptions or one subscription
- All users or only one user
Workaround
You can create the Azure Arc onboarding service principal through Azure CLI instead of the affected portal blade. Microsoft documents Azure CLI, Azure PowerShell, and Azure portal as supported creation methods. The identity should receive the Azure Connected Machine Onboarding role at the required subscription or resource-group scope. [learn.microsoft.com]
az login
az account set --subscription "<subscription-id>"
az ad sp create-for-rbac </span>
--name "<service-principal-name>" </span>
--role "Azure Connected Machine Onboarding" </span>
--scopes "/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>"
Store the returned appId, password, and tenant securely because the secret is displayed only when created.