EO Mobile Device Quarantine Showing GUID instead of Name

New Contributor

We noticed this morning (it's probably been like this for a little while, we just changed rules to quarantine more than before so we haven't been in here much until today) that the Mobile Device Quarantine pages in both the new Exchange Online Admin Center, and Classic, are showing GUIDs instead of names for the users.

I am aware of this article about the GUID/EDOID change (https://techcommunity.microsoft.com/t5/exchange-team-blog/change-in-naming-convention-of-user-s-name...), and we are in a hybrid environment with accounts syncing from on-prem, but I'm not sure what that has to do with the Exchange Online pages?

It's a bit.. impossible.. to have help desk techs manage quarantined devices when the user's name isn't displaying. How can this be fixed?

3 Replies

Regarding GUIDs vs Names, M365 is in a bit of transition phase. You might still see display names, while GUIDs are becoming more prevalent. The latter is the way, and have support use the Azure AD > Users portal to look people's GUID up before checking quarantined devices, or use PowerShell, e.g. to get all currently blocked devices including user (by dissecting the identity property):

Get-MobileDevice | Select @{n='Id';e={($_.Id -split '\\')[0]}},DeviceId,DeviceAccessStateReason,DeviceAccessControlRule


@Michel de Rooij I don't understand why anone would want to see GUIDs in place of names in 365? I can understand using GUIDs for back-end management for unique identifiers, but no one working the front-end of the system knows their employees by their GUID number. I appreciate you showing how to look that up, but why should there be a need to go an extra step to identify the user? Also that means providing the help desk team even more access to Azure AD that they do not have right now.

How do we get the Mobile Device pages to display names instead of GUID?

Agree it's not pretty, also shows in other places (delegates). Apart from advocating your request, I would suggest upvoting the following on the feedback portal (which is monitored)