-
Notifications
You must be signed in to change notification settings - Fork 978
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment fails to Azure Gov #1687
Comments
Hi @MSBrett thanks for raising this issue. Basically, this means one of the policies in that initiative is not available in Azure Gov cloud. Unfortunately, we currently don't have any way to validate sovereign cloud deployments (and it is a very complicated process to validate if policies are available in each of the sovereign clouds). We are currently in the process of someone in our team getting access to Azure Gov (Fairfax) and hopefully we can improve the quality and reliability for those customers. |
@Springstone +1 for my customer currently attempting to deploy ALZ into Fairfax. Any guidance or a work around? Here is a partial list of initiatives failing for us as of Sept 12
all of these are reported as "could not be found" /cc @brsteph |
Given the deployment is US Gov specific, is it possible to omit or replace these with what IS available? |
Describe the bug
Deployment fails to Azure Gov
Steps to reproduce
{
"status": "Failed",
"error": {
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
"details": [
{
"code": "BadRequest",
"message": "{\r\n "error": {\r\n "code": "PolicyDefinitionNotFound",\r\n "message": "The policy set definition 'Enforce-EncryptTransit' request is invalid. The following policy definition could not be found: '/providers/Microsoft.Authorization/policyDefinitions/0e80e269-43a4-4ae9-b5bc-178126b8a5cb'."\r\n }\r\n}"
}
]
}
}
The same error occurs when deploying from Learn and Github.
The text was updated successfully, but these errors were encountered: