为客户部署方案：选择Resource Group还是Subscription？

Hey there! Let's break down your dilemma between using separate Subscriptions vs. Resource Groups for each client, based on your specific requirements and questions.

1. Comparing Both Options Against Your Needs #

Requirement 1: Independent Billing per Client/Project #

• Subscription Approach: This is the most straightforward fit. Each subscription natively supports isolated billing—you can link different payment methods, send separate invoices to each client via their dedicated email, and track costs without cross-contamination. You’ve already seen this benefit firsthand.
• Resource Group Approach: Using tags for billing split is 100% feasible. Azure’s Cost Management tool lets you filter and generate bills by tags. Just add a tag like Customer=ClientName to each client’s Resource Group, and you can easily export a standalone cost report for them. The caveat: bills are tied to the parent subscription, so if you want clients to receive direct invoices, you’ll need to set up shared cost views or export bill data to share with them—less direct than subscriptions, but totally doable.

Requirement 2: Client Control & Resource Transfer #

• Subscription Approach: Transferring ownership is seamless—you can update the admin profile to hand full control to the client, letting them manage everything independently without any resource movement. This is the gold standard for full client autonomy.
• Resource Group Approach: Here’s the key: Resource Groups can be moved across Subscriptions, no technical support required. You can do this directly in the Azure Portal, or via Azure CLI/PowerShell. A few notes:
  • Make sure the target subscription is in the same Azure AD tenant (if the client wants to move to their own tenant, you’ll first need to migrate the resource group to their tenant’s subscription, which is also possible).
  • Some resource types don’t support cross-subscription migration (e.g., classic resources, certain database instances)—check Azure’s official list for your specific resources first.

Requirement 3: Low Resource Management Overhead #

• Subscription Approach: This is where it falls short. Managing dozens/hundreds of subscriptions adds significant overhead—you’ll have to handle individual permissions, compliance policies, monitoring, and lifecycle tasks (like renewals) for each one. It scales poorly with more clients.
• Resource Group Approach: Far more lightweight. All client resources live under one (or a small number of) parent subscriptions, so you can apply Azure Policies, RBAC roles, and monitoring rules once across all clients. This cuts down on repetitive work drastically.

2. Answering Your Specific Questions #

• Is tag-based billing feasible? Yes! Azure’s tagging system is designed exactly for this use case. You can even set up tag inheritance at the subscription level to ensure all resources in a client’s Resource Group automatically get the right tag, making cost tracking effortless.
• Can Resource Groups be migrated to other Subscriptions? Absolutely, and it’s not difficult. For example, using Azure CLI to move an entire Resource Group:

  az group move --destination-subscription-id <target-subscription-ID> --destination-resource-group <target-RG-name> --name <source-RG-name>
  

  In the Portal, just navigate to the Resource Group > Overview > Move > Move to another subscription, and follow the prompts.
• Do I need to contact support for migration? No. Most migrations can be done self-service. If you hit errors, Azure will provide specific troubleshooting messages (e.g., unsupported resource types) that you can resolve on your own.
• Are there real-world practices for this? Definitely. Many SaaS providers and system integrators use the "Resource Group + Tags" model for small-to-medium client bases. It balances billing isolation, client flexibility, and manageable overhead. When a client grows and needs full independence, they simply migrate their Resource Group to their own subscription.

3. Final Recommendation #

• If you have a small number of high-value clients who demand fully isolated billing and instant ownership transfer, stick with separate Subscriptions.
• If you serve many clients and want to keep management overhead low while still meeting billing and transfer needs, Resource Groups + tag-based billing is the better choice. It’s flexible enough to handle client requests to move resources later, without the hassle of managing dozens of subscriptions.

内容的提问来源于stack exchange，提问作者Ashkan S