-
We have a subscription only containing Azure DevOps organization, for billing invoice reasons. Which be a better placement option?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi @mthemark I work with a customer in Financial Services, and we recently had a very similar requirements. They have identified a number of use-cases, where a subscription is required solely for commercial/billing purposes. We've made the decision to add a new Management Group at the same level as Platform, LZ, Sandbox for Billing Only purposes. We've assigned a policy which restricts deploying any Azure resources to the MG, and a PIM request will need to be approved to the subscription, when linking to a service such as ADO, or making a purchase via the Marketplace etc. A decision was made to create a separate subscription under the new MG for each requirement, as they may have different teams approving the purchase, and for simplifying the cross-charge capabilities. This might be overkill for other organisations, but this gives them a very good separation between workloads and billing only options. Just an idea, and interested to see what others are doing |
Beta Was this translation helpful? Give feedback.
Hey both @chrisking81 & @mthemark,
Great question and conversation here.
Whilst nothing wrong with you approach @chrisking81 at all, I think I'd follow the ALZ Tailoring Guidance and make this another child MG of the Landing Zones MG.
As theres nothing but positives from inheriting most of the policies from the LZ MG and above and then assigning some more specific ones on top of that 👍