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 (by Azure)

Enterprise-Scale Alternatives

Similar projects and alternatives to Enterprise-Scale based on common topics and language

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Enterprise-Scale alternative or higher similarity.

Suggest an alternative to Enterprise-Scale

Reviews and mentions

Posts with mentions or reviews of Enterprise-Scale. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-30.
  • How are you structuring Hub & Spoke vNets?
    2 projects | reddit.com/r/AZURE | 30 Aug 2021
    Take the example from Cloud Adoption Framework enterprise-scale landing zones hub and spoke architecture https://github.com/Azure/Enterprise-Scale/blob/main/docs/reference/adventureworks/README.md. It should'nt be all about vnets, but how you really design the landscape especially for the services you have listed. If you plan to have multiple hubs in different regions and you want a spoke vnet in a hub communicate with another spoke in a different hub you could run into transitive routing issues which you would need Azure Route Server or Azure Virtual WAN to solve. Start from the landing zone architectures because these examples would mostly fit your requirements and are desinged to scale.
    2 projects | reddit.com/r/AZURE | 30 Aug 2021
    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
  • Real live examples or tours of Azure accounts
    2 projects | reddit.com/r/AZURE | 12 Jun 2021
    Make one for yourself and have a play: https://github.com/Azure/Enterprise-Scale
  • SSL VPN Choice for SMB
    1 project | reddit.com/r/msp | 2 Apr 2021
    Roughly inspired by that. I guess you could go much crazier with Azure Firewall, etc...
  • Azure "sub-tenant" like functionality?
    1 project | reddit.com/r/AZURE | 1 Apr 2021
  • How are you managing resource groups in your organization?
    2 projects | reddit.com/r/AZURE | 12 Mar 2021
    If you are a little larger company, you should look at the enterprise-scale part (https://github.com/Azure/Enterprise-Scale)


Basic Enterprise-Scale repo stats
3 days ago

Azure/Enterprise-Scale is an open source project licensed under MIT License which is an OSI approved license.

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
Find remote jobs at our new job board 99remotejobs.com. There are 34 new remote jobs listed recently.
Are you hiring? Post a new remote job listing for free.