You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working on various projects across subscriptions and tenants, we end up having a bicepparam file for the 'stacks' or 'deployments'—but I miss the possibility of also being able to specify the subscription and tenant ID in the bicepparam files.
It would be great if we could just use az deployment group create, and it would pick up the subscription ID and tenant ID from the parameter file, rather than needing to run az account set xyz each time.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Working on various projects across subscriptions and tenants, we end up having a bicepparam file for the 'stacks' or 'deployments'—but I miss the possibility of also being able to specify the subscription and tenant ID in the bicepparam files.
It would be great if we could just use az deployment group create, and it would pick up the subscription ID and tenant ID from the parameter file, rather than needing to run az account set xyz each time.
How are people handling this at scale?
Beta Was this translation helpful? Give feedback.
All reactions