Azure Landing Zones - How many subscriptions should I use in Azure?
HTML-код
- Опубликовано: 8 июл 2024
- Ever wondered how many Azure Subscriptions you should be using in your organization?
Ever wondered how to make the Azure Landing Zones design principal of Subscription Democratization (docs.microsoft.com/azure/clou...) real?
Ever wondered whether you should have one big Subscription or lots of smaller Subscriptions per application/service?
Then this is the video for you! Join Jack Tracey, Matt White & Kevin Rowlandson from the Microsoft Customer Architecture & Engineering team (the team that are responsible for Azure Landing Zones) as they talk through the criteria you should use to decide how many Azure Subscriptions you need and how to achieve Subscription Democratization!
Useful Links:
- Azure Landing Zones - aka.ms/ALZ
Chapters:
0:00 Introduction
0:45 Azure Landing Zone Conceptual Architecture
1:19 Benefits of adoption Azure Landing Zones - "myth busting"
2:41 Subscription Democratization Decision Criteria Guidance
6:06 Common scenarios we see for Subscription Democratization conversations
10:53 Key Takeaways
14:30 Closing & Stay Tuned
![Skilla Baby - Misfit (Feat. Polo G) [Official Video]](http://i.ytimg.com/vi/IjsylSnNMyw/mqdefault.jpg)
Awesome vid, great content and key areas covered in 15 mins. Good work.
Thanks for the videos guys. I've just shared this with my client as they're at a critical juncture with their journey. Hopefully, this will help them design a subscription model which is aligned with the organisation's operating model and industry regulations.
Amazing! I need to learn more about how to democratize the platform, but this video was an excellent start. Studying for the AZ-305 has me wondering if I have just been going rogue with some migrations.
Love the content and can't wait to check out the rest of your stuff!
Good informative stuff.. let us have next deep dive sessions
good stuff gents
Good idea for content
more Subscriptions = longer it takes to view combined cost analysis. We can't view costs are MGMT group scope, only Sub scope.
Very informative video on subscriptions. Just one thing when you say 'overlapping ip assignments within an address space...' could you clarify what you mean by 'ip assignments'. I understand we can't have overlapping ip address with a subnet so was wondering what you meant by overlapping ip assignments?
@Jack Tracey why would Cloud Networking Team would object to different subscriptions?
What about Secure Hub-spoke landing zone with different subscription? Any idea
Great Knowledge Base Info. Please keep coming with videos with your advisory about what to use not use as well.
Thanks for the video.
Would be great to make a end to end "demo" of a say Contoso cloud deployment using IaC after this one.
Funny you should ask, as we're currrently working on recording some epsiodes for the Azure Enablement Show which will include demos using our Bicep and Terraform implementations. I'll try to remember to post links here once they go live!
Ivory tower discussion.. All the points mentioned are pro multiple subscription and nothing to the contrary. We are a 50 person organization with an IT team of 5 people. Why should we create a management group hierarchy and multiple subscriptions and increase the complexity from the get go ?
Hey Duraid, thanks for the feedback. I think the point of ALZ is to set you up for long-term success and growth. We know that migrating resources out of single subscription environments can be painful, depending on the services you have within it.
Also having a single subscription approach can cause:
- Running into Resources/Quota limits faster and when you do, you dont have a scalable way to handle this.
- Apps can be impacted by noisy neighbours, using quota they may need etc.
- Complex RBAC assignments - hard to give higher level of control to app/workload teams in shared single subscription model
- Larger blast radius should a single subscription become compromised
Management groups help you enable, operate and govern and multi-subscription environment at scale.
Hope that helps
@@MicrosoftCAE Thanks for the response. The advantages were mentioned in the video. Thanks for re-iterating them. Non of the trade-offs were mentioned however which an unbalanced design decision. So now we build skyscrapers for everybody even if they need a couple of rooms just in case you need them in the future?
@@duraidh7299 I think CAE's response was valid, and I'll ask. How does having multiple subscriptions increase complexity? If anything, it allows you to reduce complexity as your company's cloud adoption goes.
As architects, we should design environments that scale well. As outlined in the video, a single subscription can run into very painful scalability issues. A multi-subscription environment on the other hand might avoid those. If the complexity is not large (and there is no additional cost involved), why not create the more scalable solution?
One final question that I'll ask that probably could have summarized my entire response. What about multiple subscriptions do you find more complex than a single subscription? The requirement for additional VNet Peering perhaps?
@@tharagz08Complexity