Frequently Asked Questions

AzOps FAQ

This article answers frequently asked questions relating to AzOps.

In this Section

• Subscriptions or resources not showing up in repository?
• Deployments/push fail with deployment already exists in location error

Subscriptions or resources not showing up in your repository?

If there are invalid characters in the resource path, discovery of subscriptions, resource groups or resources will fail during push or pull operations.

To confirm if this applies to you, check the pipeline logs for any of the following messages:

[ConvertTo-AzOpsState] The specified AzOpsState file contains invalid characters (remove any "[" or "]" characters)! <PathToResource>

[New-AzOpsScope] Path not found: <PathToResource>

Remove the invalid resource or character and retry the operation.

Deployments/push fail with deployment already exists in location error

If you have changed "Core.DefaultDeploymentRegion": from the default northeurope post initial setup, subsequent Push/Deployments might fail with an error as below:

Invalid deployment location 'westeurope'. The deployment 'AzOps-microsoft.management_managementgroups-nested' already exists in location 'northeurope'

This happens because because it is unsupported in ARM to create a deployment in one location when there's an existing deployment with the same name in a different location.

To resolve the error, remove the failed deployment(s) from the target scope and re-run the failed Push pipeline. This can be done either under 'Deployments' at the particular scope in the Azure portal or with PowerShell/Azure CLI/REST.