SOLVED

Azure Monitor - Centralized or per-subscription

%3CLINGO-SUB%20id%3D%22lingo-sub-898705%22%20slang%3D%22en-US%22%3EAzure%20Monitor%20-%20Centralized%20or%20per-subscription%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-898705%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20looking%20into%20cleaning%20up%20log%20analytics%2Fapp%20insights%20etc.%20for%20our%20subscriptions%2C%20and%20I%20want%20to%20configure%20Azure%20Monitor%20(preferably%20with%20policies).%3C%2FP%3E%3CP%3EWe%20have%20a%20few%20subscriptions%20each%20for%20prod%2C%20dev%2Ftest%20and%20QA%20environments.%3C%2FP%3E%3CP%3EI'm%20not%20sure%20whether%20it%20would%20be%20better%20to%20create%20a%20separate%20subscription%20only%20to%20host%20Azure%20Monitor%20for%20all%20subscriptions%2C%20or%20if%20we%20should%20have%20a%20workspace%20in%20each%20subscription%20requiring%20monitoring.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20would%20be%20the%20pros%20and%20cons%20for%20each%20approach%3F%3C%2FP%3E%3CP%3EIs%20cross-subscription%20monitoring%20supported%20for%20all%20workloads%2C%20or%20would%20some%20require%20a%20Monitor%20workspace%20in%20it's%20home%20subscription%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-914483%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Monitor%20-%20Centralized%20or%20per-subscription%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-914483%22%20slang%3D%22en-US%22%3E%3CP%3EAdding%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F84435%22%20target%3D%22_blank%22%3E%40Meir%20Mendelovich%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915120%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Monitor%20-%20Centralized%20or%20per-subscription%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915120%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EOur%20recommendation%20is%20to%20have%20as%20few%20workspaces%20as%20needed.%20The%20needs%20depands%20on%20your%20business%20constrains%2C%20mainly%20around%20regulation.%20You%20can%20see%20all%20pros%20and%20cons%20in%20this%20article%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Flogsdesign%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Flogsdesign%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20be%20more%20than%20happy%20to%20get%20feedback%20on%20it.%20%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%2C%3CBR%20%2F%3EMeir%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-921698%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Monitor%20-%20Centralized%20or%20per-subscription%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-921698%22%20slang%3D%22en-US%22%3EThank%20you!%20Just%20what%20I%20needed.%3C%2FLINGO-BODY%3E
New Contributor

Hi,

 

I'm looking into cleaning up log analytics/app insights etc. for our subscriptions, and I want to configure Azure Monitor (preferably with policies).

We have a few subscriptions each for prod, dev/test and QA environments.

I'm not sure whether it would be better to create a separate subscription only to host Azure Monitor for all subscriptions, or if we should have a workspace in each subscription requiring monitoring.

 

What would be the pros and cons for each approach?

Is cross-subscription monitoring supported for all workloads, or would some require a Monitor workspace in it's home subscription?

3 Replies
Best Response confirmed by OlveJA (New Contributor)
Solution
Hi,

Our recommendation is to have as few workspaces as needed. The needs depands on your business constrains, mainly around regulation. You can see all pros and cons in this article: http://aka.ms/logsdesign

I would be more than happy to get feedback on it.

Thanks,
Meir
Thank you! Just what I needed.