You won’t be able to make any changes to the resources that you find within the managed resource. You have Deny permission within a managed resource group, but it’s not just you – it’s everybody. Why Can’t I Change the Managed Resource Group? In this example from a Synapse instance, we can see a master database for Synapse. No it isn’t! Holy moly, calm it down! Take a look again and click, “Show hidden types”. NOTE: Databricks doesn’t give the option to name its managed resource group from the portal. It’s not required to enter that managed resource group name, but it’s a great idea! Synapseworkspace-managedrg-4ff96d80-e464-4512-a577-3d3942041366Īs you can see from this image for creating a synapse workspace, you are provided the opportunity to provide the name for the managed resource group. Here’s an example of an automatically named managed resource group: Microsoft doesn’t provide a naming recommendation for managed resource groups, but it does provide a suggestion for resource group: rg- If you’re following that, then perhaps a simple mrg- will do.Ī managed resource group can be created by default if you don’t or can’t provide a name.

By default, a managed resource group is created for you when your workspace is created. Managed resource group is a container that holds ancillary resources created by Azure Synapse Analytics for your workspace. Those additional resources go into a managed resource group.Īs “Create Synapse workspace” says, providing a good definition for a managed resource group:

This seems reasonable! But sometimes your resource needs other resources to be able to function properly. When you create an Azure resource in your resource group, you may be expecting only that resource to be created.

Microsoft toy box