Event details
follow up on the Dynamic groups.. For a single tenant shared by two regions (US + EU), what's the recommended way to keep Autopilot deployment profiles, the Enrollment Status Page, and device-naming templates cleanly separated per region? Autopilot profiles assign to groups but there's no scope-tag enforcement on profile assignment — so is the answer group tags + dynamic user groups, Administrative Units, or something else, and how do you keep it from colliding when both regions share one tenant?
I might be reading this question wrong but I think what you'll want to do is create two different autopilot deployment profiles - one for EU, and one for US.
Next you'll create 2 separate dynamic groups - one for Intune Device EU, and one for Intune Device US.
You need to determine how you can programmatically detect the difference between your EU & US devices. You might already have something like this in place.
Then assign your dynamic groups to the matching autopilot deployment profile.
The behavior you'll see is that devices that have the EU identifier will use the EU Autopilot Deployment Profile, and ones with the US identifier will use the US one.
For this specific use case, I don't think you need to worry about group tags or anything else. As long as you can identify which device belongs to which region, Autopilot will apply the correct profile.- Hung_Dang
Microsoft
It's not clear if this is a question about dynamic groups usage or scope tags -- two very different concepts.
