Forum Discussion
Mult-subscription Terraform deployment and Azure DevOps Service Connections
While it is understood that Terraform templates can facilitate multi-subscription deployment through the 'alias' concept, as outlined in the documentation https://registry.terraform.io/providers/hash...
Hi, for multi-subscription Terraform from Azure DevOps, I would usually avoid relying on only one classic service connection if the deployment needs access across several subscriptions. A cleaner approach is to use one identity with RBAC assigned at the right management group or subscription scopes, then configure provider aliases in Terraform. If separate service connections are required, the pipeline has to authenticate each context explicitly before the matching provider is used.