Ensure that the Microsoft.Maintenance resource provider is registered in your subscription:
az provider show --namespace Microsoft.Maintenance --query "resourceTypes[?resourceType=='configurationAssignments'].apiVersions" --output json
az provider show --namespace Microsoft.Maintenance \ --query "resourceTypes[?resourceType=='configurationAssignments'].locations[]" \ --output json | jq '.[] | select(startswith("G"))'
Fix: Ensure that both the configurationAssignment and the target resource (e.g., VM) are in Germany West Central.
Even though the region is listed, preview features may not be fully rolled out in all listed regions.
Fix: Try deploying the same template in a more established region like East US or West Europe to confirm if the issue is region-specific.
You're setting:
resourceId: subscriptionId
But resourceId in this context expects the fully qualified Azure Resource ID of the target resource (like a VM or a resource group), not just the subscription ID.
Since you're using targetScope = 'subscription', and trying to apply a dynamic scope assignment, you should use the subscription resource ID in the correct format
If subscription-level dynamic scoping is unstable, consider scoping to a resource group
Even though while checking the api version it is not visible, there are older api versions available. Please try using older api version.
Hope this helps!
let us know if any help, we will always help as you needed.!
Please do not forget to "Accept the answer” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.