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
Working on a startup, trying to figure out how to layout initial setup...
1 project | reddit.com/r/AZURE | 15 Jan 2022
Real live examples or tours of Azure accounts
2 projects | reddit.com/r/AZURE | 12 Jun 2021
SSL VPN Choice for SMB
1 project | reddit.com/r/msp | 2 Apr 2021
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