How are you structuring Hub & Spoke vNets?

This page summarizes the projects mentioned and recommended in the original post on reddit.com/r/AZURE

Our great sponsors
  • Scout APM - Less time debugging, more time building
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
  • OPS - Build and Run Open Source Unikernels
  • GitHub repo Enterprise-Scale

    The Enterprise-Scale architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture

    The example is for a single region deployment. You are mentioning the potential of more services to be in Azure. Where do you get your subscriptions from? Do you have Enterprise Agreement? If so, then it really doesn't matter and you could reference the example desing. Based on the service you determine the destination subscription. If you have multiple teams/partners working on different services then this design is excellent for RBAC. If you have a small team then you could have a maximum of three subscriptions, from the example desing you could put together the management, connectivity and identity subscription and seperate the resources based on resource groups for RBAC. Each new service that you are offering is in the corp or online subscription and you create your services and vnets and peer them on the basis that should the vnet be corp connected or is exposed to the outside. Something like this https://github.com/Azure/Enterprise-Scale/blob/main/docs/reference/treyresearch/README.md

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts