0% found this document useful (0 votes)
8 views

ISE 3.2 Multi-MDM Authorization Notes

Uploaded by

Ndahimana Emmy
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views

ISE 3.2 Multi-MDM Authorization Notes

Uploaded by

Ndahimana Emmy
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Without “Query Multiple MDM / UEM Integrations” feature, this is how it works..

Considering you have multiple MDM integrations with ISE,

Requirement: if specific group/location users are being managed by specific MDM server, then you
can define policies in ISE to get compliance info and give access accordingly. In below snapshot, I
was making use of AD groups to differentiate MDM users managed by MDM server.

Problems: If there is no differentiation of users/devices being managed by MDM server, then how do
you write policies? Or If an un-enrolled device comes into network and the device/user doesn’t belong
to any of the groups/location, then to which MDM server ISE has to query with?

Solution: enable “Query Multiple MDM/UEM Integrations


Case1: if MobileIron user comes with a device which is not yet enrolled against MobileIron into the
network, then you can write policies like below,

ISE will first query against MobileIron and falls back to Intune policy to query against multiple MDM
vendors.

You might also like