Update: the change mentioned in this article has been rolled out to all commercial tenants.
Many of you may rely on Exchange Online mobile device access rules to ensure that only approved devices (...
Ross Smith IV well... If Outlook mobile does not use Exchange ActiveSync then you should have introduced different terminology and not refer to the "Set-ActiveSyncOrganizationSettings" commandlet in this original post.
Allow me to share what we are seeing. Outlook mobile may not be using ActiveSync, but it sure looks and smells the same in the portal. This is from just one of our many users / mailboxes:
The first entry with a status of "Access granted" is dated January 18 and shows "Access set by External Mobile Device Management" (recognize that?) The second entry with status "Quarantined" is from February 3 and shows "Access set by Global Permissions". Both of these entries also show "ActiveSync version 1.0"... So if Outlook mobile does not use ActiveSync - then what is it that we are looking at here? Yet another platform bug?
Either way - that "Access granted" entry from January 18 was not approved by our 3rd-party MDM solution - nor was it manually approved, nor is there any log entries we can find that explain this. The second entry showing "quarantined" only came to exist because the user upgraded the Outlook mobile app. This second entry is actually how things should have been all along. But as you can see - the old entry is still there.
So - if Outlook mobile does not use ActiveSync then I think the introduction of new terminology is long overdue. Until then, I will continue to use the same terminology because that sure appears to be what the platform is actually using.