I'm new to Azure and managing a multi-subscription organization. I'm trying to figure out the best way to implement multi-region resiliency across various workloads and subscriptions. I have two types of vaults, each serving different purposes, but I'm running into some issues. Specifically, I know the vaults need to be in the same region and subscription, and recovery points can't be stored across subscriptions. Additionally, there are assets that have their own backup mechanisms, and it seems like there's no single management policy to create vaults—each subscription has its own policies. I'm really curious about what the experts are doing in these situations!
2 Answers
Before diving into multi-region setups, start with a solid risk assessment and clarify your functional requirements. Understand your budget, expected failure modes, and the needs of the business. Creating a plan is critical! Doing things in the right order can save you future headaches. Tooling comes afterwards — focus on designing your architecture first. It sounds like you might want to build a backup and restore system with cross-region capabilities, especially for critical assets, while keeping an eye on cost.
Managing multi-region resiliency using Azure subscriptions can get tricky since they aren't the best for high availability and disaster recovery. Instead, think of subscriptions as ways to organize billing or separate applications. It’s definitely possible to have multi-region setups within a single subscription. Have you checked out Azure's Well-Architected Framework and Cloud Adoption Framework? Also, are you primarily using IaaS or PaaS? This impacts how you set things up. Regarding management policies, remember that subscriptions can inherit from management groups, and Azure Blueprints can help with consistency, but it’s being deprecated soon, so consider looking into Deployment Stacks instead.
Related Questions
How To Get Your Domain Unblocked From Facebook
How To Find A String In a Directory of Files Using Linux