SOLVED

Possible to prevent creation of new Log Analytics workspaces?

%3CLINGO-SUB%20id%3D%22lingo-sub-1306608%22%20slang%3D%22en-US%22%3EPossible%20to%20prevent%20creation%20of%20new%20Log%20Analytics%20workspaces%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1306608%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20possible%20to%20prevent%20the%20creation%20of%26nbsp%3Bnew%20Log%20Analytics%20workspaces%20and%20instead%20force%20the%20user%20to%20choose%20an%20existing%20log%20analytics%20workspace%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThx%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1306608%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1309100%22%20slang%3D%22en-US%22%3ERe%3A%20Possible%20to%20prevent%20creation%20of%20new%20Log%20Analytics%20workspaces%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1309100%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F173036%22%20target%3D%22_blank%22%3E%40Jeff%20Walzer%3C%2FA%3E%26nbsp%3BDepending%20on%20how%20restrictive%20you%20want%20to%20be%2C%20you%20can%20put%20a%20lock%20on%20the%20resource%20group%20that%20will%20disallow%20any%20new%20resources%20to%20be%20created%2C%20but%20that%20only%20works%20in%20that%20resource%20group.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20could%20create%20a%20policy%20that%20prevents%20LA%20workspaces%20from%20being%20created%20and%20assign%20that%20to%20the%20subscription.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1309151%22%20slang%3D%22en-US%22%3ERe%3A%20Possible%20to%20prevent%20creation%20of%20new%20Log%20Analytics%20workspaces%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1309151%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46875%22%20target%3D%22_blank%22%3E%40Gary%20Bushey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThx%20for%20the%20reply%20and%20information.%20I%20will%20pursue%20setting%20a%20policy%20at%20the%20subscription%20level.%20We're%20trying%20to%20centralize%20any%20and%20all%20logging%20to%20a%20single%20LA%20workspace.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20a%20separate%20note%2C%20is%20there%20a%20way%20to%20see%20what%20Azure%20roles%20(and%20the%20users%20within%20those%20roles)%20have%20access%20to%20creating%20a%20LA%20workspace%3F%20Trying%20to%20see%20who%20has%20right%20to%20create%20a%20LA%20workspace%20and%20having%20issues%20finding%20that%20info%20in%20Azure.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThx%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Is it possible to prevent the creation of new Log Analytics workspaces and instead force the user to choose an existing log analytics workspace?

 

Thx

2 Replies
best response confirmed by Jeff Walzer (Contributor)
Solution

@Jeff Walzer Depending on how restrictive you want to be, you can put a lock on the resource group that will disallow any new resources to be created, but that only works in that resource group.

 

You could create a policy that prevents LA workspaces from being created and assign that to the subscription.

@Gary Bushey 

 

Thx for the reply and information. I will pursue setting a policy at the subscription level. We're trying to centralize any and all logging to a single LA workspace.

 

On a separate note, is there a way to see what Azure roles (and the users within those roles) have access to creating a LA workspace? Trying to see who has right to create a LA workspace and having issues finding that info in Azure.

 

Thx