Microsoft
MicrosoftHi,
I have been pointed to this best-pratice article by my employer (globally present manufacture), that currently is operating in 5 Azure regions and 2 local DC's across 5 continents.
While reading through this I get the impression that Sentinel best-practice was conceived in the context that LA originated at the same time as Sentinel, and hence, customers of Sentinel, would not already have taken LA into production. I base this thought on the recommendation 1. and 2. that are contradictory and can, IMHO, only co-exist if users have few regions in play.
Given the egress charge of Azure, it makes sense to create LA Workspaces' regionally and since LA GA'ed long before Sentinel, this was (backed by recommendation 1.) what was done in our case. "Having a single workspace is technically the best choice to make" ...is probably right, but question is if this is due to Sentinel technical limitations/Sentinel Architectural design flaws/Azure cost metrics/etc.
From an Enterprise perspective I would be interested in learning best-practice for multi-region presence of Azure VM's, local VM's, O365 region and Dynamics365 region.
If my perception of this best-practice (being targeted customer with one region and one LA) is misplaced, please educate me.
Presently I will start consolidating all regional VM's (Azure and local) into one LA - this will be in the region of our O365 tenant. Feedback on this strategy is most welcome.
-René
