ARM template deployment and "Atlas resource group"

%3CLINGO-SUB%20id%3D%22lingo-sub-2010151%22%20slang%3D%22en-US%22%3EARM%20template%20deployment%20and%20%22Atlas%20resource%20group%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2010151%22%20slang%3D%22en-US%22%3E%3CP%3EWhile%20creating%20a%20Purview%20account%20I%20can%20assign%20it%20to%20any%20resource%20group%2C%20but%20I%20see%20that%20after%20performing%20scans%20a%20new%20resource%20group%20is%20created%20with%20a%20Event%20Hub%20namespace%20and%20a%20Storage%20account.%20These%20seem%20to%20be%20related%20to%20Atlas%20hooks%20and%20entities.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20control%20the%20name%20of%20this%20auto-generated%20resource%20group%3F%20I%20was%20thinking%20I%20may%20be%20able%20to%20control%20this%20via%20an%20ARM%20template-based%20deployment.%20Would%20this%20be%20possible%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20where%20can%20I%20find%20the%20ARM%20template%20reference%20for%20Purview%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

While creating a Purview account I can assign it to any resource group, but I see that after performing scans a new resource group is created with a Event Hub namespace and a Storage account. These seem to be related to Atlas hooks and entities.

 

Is there a way to control the name of this auto-generated resource group? I was thinking I may be able to control this via an ARM template-based deployment. Would this be possible?

 

Also, where can I find the ARM template reference for Purview?

5 Replies
I have the same question. The auto-generated resource group does not meet the tagging policy at my organization, so I can't create the Purview account due to validation failure. Is there a way to use an existing resource group instead? Or specify tags to be applied to the auto-generated resource group?

@dougspadotto We will be exposing a property, in the coming weeks, where the managed resource group name will be configurable at Account create time.
I am tracking down our documentation team to find where we host our ARM template in the meantime here is our swagger documentation, and an example of the create payload. This JSON example can also be used in ARM
azure-rest-api-specs/Accounts_CreateOrUpdate.json at master · Azure/azure-rest-api-specs (github.com...

@WilliamSzostak-LM you can assign tags to your manages resources (the resource group, Storage account, and Eventhub namespace) by setting tags on your Purview account and they will propagate to these resources. You can set these tags both at create time or by updating them using the Azure Portal. This should solve your issue with the offending tagging policy.

Thank you, @annoakes, that worked!

@annoakes Will there be any option to customize the VNET settings on those managed resource groups? As per their policy , many customers wouldn't accept those services to be configured as public.