Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Should I create a resource group or subscription?

We are a software company so we setup solutions for the other companies. I guess we are not unique in this regards :) so I would like to know if we should create a new subscription each time or just a resource group.

Requirements:

  • We should be able to bill each customer/project separably
  • They should be able to take control of their resources easily and move to another company
  • Managing them should not be a headache

What we have tried

We've tried adding a subscription for each customer. This way, we could just change the admin profile and they could completely move away from us. The billing is also OK, since we receive a different email for each subscription, but managing them is becoming a real headache.

What I guess could work

From what I read, I guess we could work with resource groups instead of subscriptions and handle the billing part with tags (haven't tried it yet. can we?) but then I'm afraid of not being able to move it to another subscription when they've asked us.

Is it even possible? How easy is that? Does it envolve contacting support?

Has anyone tried it?

like image 960
Ashkan S Avatar asked Jan 02 '18 10:01

Ashkan S


People also ask

What is the difference between subscription and resource Group?

Organizations can use subscriptions to manage costs and the resources created by users, teams, or projects. Resource groups are logical containers where you can deploy and manage Azure resources like web apps, databases, and storage accounts.

Can resource groups be moving between subscriptions?

You can move Azure resources to either another Azure subscription or another resource group under the same subscription. You can use the Azure portal, Azure PowerShell, Azure CLI, or the REST API to move resources. To learn more, see Move resources to a new resource group or subscription.

Can a resource group have resources from different subscriptions?

The resource groups can exist in different subscriptions. You can deploy to 800 resource groups in a single deployment.


1 Answers

I would advise against billing using resource groups and tags. The reports are a real mess and 100% unusable. Also, its a lot of extra work for nothing (seriously, do you care if you have 1 subscription or 10?) and adds no real benefit.

Also, you can move resources across subscriptions of different tenants. Best way of handling this is doing a subscription move. That way you dont have to do anything else. They just link your subscription to another tenant and you are good.

I'm talking from a perspective of administering dozens of subscriptions, and believe me, if you move away from subscriptions to resource groups (as a billing\security boundary) you will get completely devastated by the increased complexity of what you are doing.

like image 151
4c74356b41 Avatar answered Sep 24 '22 20:09

4c74356b41