Forum Discussion
can dedicated host be shared between different subscriptions created for the same tenant?
A dedicated host can be shared between different subscriptions created for the same tenant.
In your example, if subscription A creates a dedicated host group A, subscription B can also create IaaS resources on the dedicated host group A, as long as the necessary permissions are granted.
In your case, if subscription A creates a dedicated host group A, subscription B can also create IaaS resources on the dedicated host group A, as long as the necessary permissions are granted.
To allow subscription B to use the dedicated host group A, subscription A (or the Azure AD tenant administrator) needs to grant the necessary permissions to subscription B. This can be done by adding subscription B as a contributor or owner to the resource group that contains the dedicated host group A, or by creating a custom role with the required permissions and assigning it to subscription B.
- When you are referring to "adding subscription B as a contributor or owner to the resource group that contains the dedicated host group A" are you meaning to add a user or group in Azure AD to the RG? As far as I know subscriptions are not associated with azure roles like contributor or owner.
You are correct that subscriptions in Azure are not associated with Azure roles like contributor or owner. However, when I mentioned "adding subscription B as a contributor or owner to the resource group that contains the dedicated host group A," I was referring to adding a user or group in Azure AD to the resource group and assigning them the contributor or owner role.
In Azure, resource groups are used to organize and manage Azure resources, and you can assign users or groups in Azure AD to roles like contributor or owner at the resource group level. By adding subscription B as a contributor or owner to the resource group that contains the dedicated host group A, you would be granting users or groups in subscription B permissions to manage resources within the dedicated host group A.
So to clarify, you would not be adding subscription B itself as a contributor or owner to the resource group, but rather users or groups from subscription B that you want to grant those permissions to.
