Troubleshooting - Deployment and Operations
This topic explains how to identify, diagnose, and fix issues that you might encounter when attempting to deploy and perform operations with Azure Sphere.
Azure Portal
This topic provides troubleshooting steps for the Azure Portal > Azure Sphere service.
Errors
| Error | Solution |
|---|---|
| Resource provider(s): microsoft.azuresphere are not registered for subscription <subscription-name> and you don’t have permissions to register a resource provider for subscription <subscription-name> | Verify that Azure Sphere service is registered for the subscription and the user has the required permissions. |
| You don't have sufficient permissions to create a resource on the resource group level. If the access has been recently granted, it may take sometime to be reflected. | Verify that the user has required permissions at the resource group level. |
Integrate Azure Sphere (Legacy) tenants into (Integrated) catalogs
Cannot see the option to integrate my Azure Sphere tenant to Azure Sphere catalog
Users should have the "Administrator" role in the Azure Sphere tenant.
Cannot integrate the users in the tenant to the catalog
To integrate a tenant and the users in the tenant, the user integrating the tenant should:
- Have "Administrator" role on the tenant
- Have Owner privileges on a catalog
User that are being integrated, should:
- Exist in the AAD
- Have Azure Sphere contributor/owner privileges on a Resource Group where they are integrating.
To gain access to the Microsoft Azure management portal, you must have an Azure subscription and a Microsoft account associated with that subscription. If you're using federation authentication and the user doesn't already exist in Azure Active Directory, the user can't be invited. To resolve this issue, the external user’s admin must synchronize the user’s account to Azure Active Directory.
Known issues
Pagination is currently not supported for list commands. This will be supported in future releases.