SOLVED

Multi Tenant Centralize Log Analytics

%3CLINGO-SUB%20id%3D%22lingo-sub-901413%22%20slang%3D%22en-US%22%3EMulti%20Tenant%20Centralize%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-901413%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20tried%20centralizing%20events%5Cmetric%5Clogs%20from%20other%20tenants%2C%20into%20one%20Log%20Analytics%20workspace%3F%20Or%20using%20other%20Azure%20Services%20like%20Cosmos%2C%20and%20creating%20reports%20or%20alerts%20from%20here%3F%3C%2FP%3E%3CP%3EHaving%20one%20centralized%20%22management%20repository%22%20for%20security%20events%20and%20performance%20counters%2B%2B%20from%20VM's%20will%20be%20pretty%20powerful.%3C%2FP%3E%3CP%3EI've%20tried%20out%20the%20following%20guide%3A%20%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Fplatform%2Factivity-log-collect-tenants%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Fplatform%2Factivity-log-collect-tenants%3C%2FA%3E%3C%2FP%3E%3CP%3Ebut%20as%20a%20CSP%20responsible%20for%20IaaS%2C%20PaaS%20to%20SaaS%20for%20our%20customer%20there%20must%20be%20an%20easier%20way.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-901413%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMulti-tenant%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-901534%22%20slang%3D%22en-US%22%3ERe%3A%20Multi%20Tenant%20Centralize%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-901534%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383177%22%20target%3D%22_blank%22%3E%40AzureSensei%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMy%20experience%20shows%20that%20management%20at%20scale%20should%20be%20done%20by%20tenant.%20This%20means%20that%20resources%20are%20created%20per%20tenant%20otherwise%20you%20will%20have%20problems%20in%20billing%20your%20customers%20correctly%2C%20access%20management%2C%20setup%2C%20etc..%20Azure%20Lighthouse%20can%20you%20bring%20data%20together%20by%20projecting%20customer%20subscriptions%20under%20your%20tenant.%20That%20way%20you%20can%20use%20built-in%20Azure%20Monitor%20features%20where%20you%20can%20query%20information%20from%20multiple%20workspace.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-902023%22%20slang%3D%22en-US%22%3ERe%3A%20Multi%20Tenant%20Centralize%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-902023%22%20slang%3D%22en-US%22%3E%3CP%3Ethanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9172%22%20target%3D%22_blank%22%3E%40Stanislav%20Zhelyazkov%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegarding%20billing%2C%20access%20management%20and%20things%20like%20data%20retention%20will%20be%20managed%20and%20contained%20within%20customer's%20subscriptions%20with%20pre-configured%20policies%20or%20other%20rulesets%20when%20%22built%22.%3C%2FP%3E%3CP%3EAnd%20depending%20on%20which%20way%20data%20is%20exported%20from%20the%20tenant%20will%20depict%20the%20extra%20cost.%3C%2FP%3E%3CP%3E-%20Outbound%20from%20the%20customer%20tenant%20will%20be%20an%20extra%20cost%20for%20the%20customer.%3C%2FP%3E%3CP%3E-%20Initiated%20data%20collection%20from%20our%20tenant%20will%20be%20an%20extra%20cost%20for%20us.%3C%2FP%3E%3CP%3EReferring%20to%20the%20where%20the%20arrows%20are%20pointing%20in%20the%20link%20I%20provided.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20I'm%20over-complicating%20things.%20Is%20it%20possible%20for%20the%20customer's%20Microsoft%20Monitoring%20Agent%20to%20connect%20to%20our%20%22management%22%20tenant%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-902045%22%20slang%3D%22en-US%22%3ERe%3A%20Multi%20Tenant%20Centralize%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-902045%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383177%22%20target%3D%22_blank%22%3E%40AzureSensei%3C%2FA%3E%20For%20me%20this%20is%20just%20not%20the%20right%20way%20and%20I%20think%20it%20is%20a%20road%20that%20is%20filled%20with%20many%20obstacles%20just%20because%20when%20services%20are%20designed%20for%20cross-tenant%20setup.%20Of%20course%20you%20are%20free%20to%20follow%20your%20on%20path.%20I%20cannot%20tell%20if%20every%20single%20integration%20in%20Azure%20will%20work%20in%20such%20scenario%20(%20I%20am%20sure%20it%20will%20not%20work%20in%20some).%20For%20sure%20you%20can%20install%20Log%20Analytics%20agent%20on%20a%20VM%20located%20in%20one%20tenant%20and%20workspace%20in%20another%20tenant.%20That%20is%20possible%20because%20the%20agent%20connects%20to%20the%20workspace%20by%20ID%20and%20key%20so%20it%20works%20even%20for%20on-premises%20setups%20or%20in%20other%20clouds.%3C%2FP%3E%0A%3CP%3EIt%20is%20important%20to%20consider%20in%20such%20scenario%20overall%20management%20of%20these%20resources%20like%20the%20workspace.%20You%20can%20set%20retention%20per%20table%20but%20not%20per%20data.%20So%20if%20one%20of%20your%20customers%20wants%202%20years%20but%20all%20others%20want%20default%2030%20days%3F%20What%20happens%20if%20particular%20customer%20due%20to%20compliance%20reasons%20does%20not%20want%20the%20data%20to%20be%20contained%20in%20the%20same%20resource%3F%20What%20happens%20if%20a%20customer%20leaves%20you%20as%20CSP%20and%20they%20want%20their%20data%20to%20be%20given%20to%20them%3F%20What%20happens%20if%20customer%20asks%20for%20certain%20data%20to%20be%20deleted%20as%20there%20is%20some%20performance%20penalty%20when%20data%20is%20deleted%20that%20will%20affect%20all%20your%20customers%3F%20This%20is%20just%20a%20small%20part%20of%20the%20example%20scenarios%20that%20you%20might%20meet%20if%20you%20take%20such%20decision.%20So%20it%20is%20good%20to%20sit%20down%20and%20consider%20all%20the%20scenarios%20that%20might%20apply%20to%20your%20existing%20or%20future%20customers%20and%20take%20decision%20based%20on%20if%20you%20are%20ready%20with%20solutions%20for%20those%20or%20not.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-902352%22%20slang%3D%22en-US%22%3ERe%3A%20Multi%20Tenant%20Centralize%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-902352%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9172%22%20target%3D%22_blank%22%3E%40Stanislav%20Zhelyazkov%3C%2FA%3E%26nbsp%3Byou%20got%20some%20valid%20points%20there%20mister.%20I'll%20do%20as%20advised%2C%20and%20have%20a%20think%20about%20it..%20Again.%20%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fsmile_40x40.gif%22%20alt%3D%22%3Asmile%3A%22%20title%3D%22%3Asmile%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-905218%22%20slang%3D%22en-US%22%3ERe%3A%20Multi%20Tenant%20Centralize%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-905218%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383177%22%20target%3D%22_blank%22%3E%40AzureSensei%3C%2FA%3E%26nbsp%3BOur%20organization%20doesn't%20do%20this%2C%20but%20we%20have%20taken%20it%20down%20a%20level--we%20have%20a%20single%20Log%20Analytics%20workspace%20for%20multiple%20subscriptions%2C%20and%20so%20far%2C%20it%20has%20worked%20out%20well.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi,

 

Has anyone tried centralizing events\metric\logs from other tenants, into one Log Analytics workspace? Or using other Azure Services like Cosmos, and creating reports or alerts from here?

Having one centralized "management repository" for security events and performance counters++ from VM's will be pretty powerful.

I've tried out the following guide:  https://docs.microsoft.com/en-us/azure/azure-monitor/platform/activity-log-collect-tenants

but as a CSP responsible for IaaS, PaaS to SaaS for our customer there must be an easier way. 

5 Replies
Highlighted

Hi@AzureSensei 

My experience shows that management at scale should be done by tenant. This means that resources are created per tenant otherwise you will have problems in billing your customers correctly, access management, setup, etc.. Azure Lighthouse can you bring data together by projecting customer subscriptions under your tenant. That way you can use built-in Azure Monitor features where you can query information from multiple workspace.

Highlighted

thanks @Stanislav Zhelyazkov,

 

Regarding billing, access management and things like data retention will be managed and contained within customer's subscriptions with pre-configured policies or other rulesets when "built".

And depending on which way data is exported from the tenant will depict the extra cost.

- Outbound from the customer tenant will be an extra cost for the customer.

- Initiated data collection from our tenant will be an extra cost for us.

Referring to the where the arrows are pointing in the link I provided.

 

Maybe I'm over-complicating things. Is it possible for the customer's Microsoft Monitoring Agent to connect to our "management" tenant?

Highlighted
Solution

@AzureSensei For me this is just not the right way and I think it is a road that is filled with many obstacles just because when services are designed for cross-tenant setup. Of course you are free to follow your on path. I cannot tell if every single integration in Azure will work in such scenario ( I am sure it will not work in some). For sure you can install Log Analytics agent on a VM located in one tenant and workspace in another tenant. That is possible because the agent connects to the workspace by ID and key so it works even for on-premises setups or in other clouds.

It is important to consider in such scenario overall management of these resources like the workspace. You can set retention per table but not per data. So if one of your customers wants 2 years but all others want default 30 days? What happens if particular customer due to compliance reasons does not want the data to be contained in the same resource? What happens if a customer leaves you as CSP and they want their data to be given to them? What happens if customer asks for certain data to be deleted as there is some performance penalty when data is deleted that will affect all your customers? This is just a small part of the example scenarios that you might meet if you take such decision. So it is good to sit down and consider all the scenarios that might apply to your existing or future customers and take decision based on if you are ready with solutions for those or not.

Highlighted

@Stanislav Zhelyazkov you got some valid points there mister. I'll do as advised, and have a think about it.. Again. :smile:

Highlighted

@AzureSensei Our organization doesn't do this, but we have taken it down a level--we have a single Log Analytics workspace for multiple subscriptions, and so far, it has worked out well.