Outlook Mobile Access
Enable Outlook Mobile (Outlook for iOS and Android) access to mailbox.
Adding a baselineConfigure it
This baseline applies per user, through a user-level scheme or an Azure group, rather than to the tenant as a whole.
-
Add it directly to a user or an Azure group (Adding a baseline), or bundle it into a user-level scheme and deploy that to many users or groups at once (Deploying a scheme). See Groups and priority for how Octiga resolves which value a user gets when a Direct value, a scheme and a group all supply one.
-
Leave Outlook Mobile access set to On; it’s the only setting on this baseline. It controls whether the official Outlook for iOS and Android app can sync this mailbox, and it’s separate from ActiveSync access: a phone’s built-in mail app can be blocked while Outlook Mobile stays allowed, or the other way round.
-
Microsoft exposes this setting only through Exchange Online PowerShell (
Get-CASMailbox/Set-CASMailbox), with no admin-centre toggle. That’s where Octiga reads and writes it for you. -
Save. Turn on Auto-remediation and Octiga switches Outlook Mobile access back on automatically if it’s disabled for a user it applies to. Their app starts syncing again on its own the next time it checks in.
Check it worked
Passing means the mailbox’s Outlook Mobile access reports as enabled. There’s no
admin-centre page for it; to see it directly, run
Get-CASMailbox -Identity <user> | Format-List OutlookMobileEnabled in Exchange Online
PowerShell. On the user roster or a group’s member list, Passing shows as a green dot
for this baseline; Deviated (red) means it’s currently off; Excluded (grey) means the
user or tenant isn’t licensed for Exchange Online. With access off, the Outlook for iOS or
Android app stops syncing the user’s mail, contacts and calendar.
Doing this for every tenant?
Step through the deploy wizard to apply a scheme to a tenant, groups or users, and see what Managed and Direct do at deploy time.