Could you please share the YAML file in private message for further debugging
Meanwhile follow the below steps:
- Use
dependsOn in
n your Bicep modules, explicitly define dependencies using thedependsOn
property to ensure that resources are provisioned in the correct order. - Use a
deploymentScript
resource in Bicep to poll for readiness of fabrics and containers before proceeding to the next module. - Use multiple Azure DevOps pipeline stages or jobs to sequence ASR resource creation and verification.
- You can mix Bicep for initial resource provisioning and Azure CLI or REST API for:
- Checking
fabricState
- Creating container mapping
- Associating replication policies
az recoveryservices fabric container mapping create \ --resource-group $rg \ --vault-name $vault \ --fabric-name $fabric \ --container-name $container \ --name $mappingName \ --policy-id $policyId
- Checking
Hope this helps!
Please Let me know if you have any queries.