Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
The following are examples of errors that might be encountered and their solution.
General troubleshooting
The general troubleshooting steps that aren't specific to an Azure Enclave resource.
Portal Links don't work in the Air Gapped Azure environments
Azure Enclave portal links (for example, Learn More) don't work in some Azure air-gapped environments.
Solution: Those documentation links work on the low side so you can navigate to the same URL from a computer with access to github.io.
Community Troubleshooting
The community troubleshooting steps that are specific to the Azure Enclave community resource.
API error when creating first community
Scenario: Create a community for the first time in a new subscription, the following error message blocks the deployment
"The resource type could not be found in the namespace 'Microsoft.Mission' for api version '<api-version>'."
Solution: Ensure Microsoft.Mission is registered in your subscription. Follow Get started with Azure Enclave to verify resource provider registration and required permissions, and then retry the deployment.
Workloads
User has permissions to write but not permissions to do something else
If the permission that was denied is one of the permissions included in the actions protected by maintenance mode like Microsoft.Network/virtualNetwork/subnets/join/action this is a good indicator that maintenance mode should be enabled and then you can try again.