What is changing
The roadmap description says Outlook for Android will support multiple MAM (Mobile Application Management) accounts. Only one MDM (Mobile Device Management) account will be supported on a device at a time.
For anyone who has hit the old wall, this is a real change. Admins and users have long reported that apps like Teams and Outlook are multi-identity, but only one managed account can carry MAM policies. One Microsoft Q&A thread describes a user whose Authenticator app removed the second account when he tried to add it. The workaround was usually a shared mailbox, a separate work profile, or a second device.
MAM versus MDM
The two terms are easy to blur, and the distinction matters here.
- MAM protects organizational data inside supported apps. It doesn't require the device to be enrolled. Microsoft's app protection overview says these policies can be used independent of any MDM solution, so they work with or without enrollment.
- MDM manages the whole device, or on Android, the work profile.
The roadmap item expands MAM only. It does not promise that a device can be enrolled in several management systems.
Microsoft's Multiple Managed Accounts (MMA) documentation describes the supported configurations. Either one account is MDM plus MAM managed and the rest are MAM-only, or all accounts are MAM-only. The same page states that multiple MDM isn't supported. The roadmap's "one MDM account" language fits that model.
Who benefits
Microsoft's MMA documentation lists these scenarios:
- Consultants with managed accounts in two organizations.
- Employees in transition during mergers.
- Help desk or shared-mailbox users who manage several accounts in one tenant.
Each account is governed by its own app protection policy. Don't read that as unrestricted freedom. See the next section.
The mixed-view catch
Outlook is what Microsoft calls a "mixed view" app. It can show several accounts together, for example in a combined inbox or calendar. Microsoft's MMA page warns that mixed views always enforce full lockdown, the most restrictive behavior, whatever each account's policy says. Its examples are:
- Cut, copy and paste are blocked, including inside the app.
- Screen capture and screenshots are blocked.
- Other data protection controls default to the most restrictive setting.
A security reviewer would call this sensible. If data from two organizations can sit in one view, the more permissive policy would create a path for data to leak between them. A user who loves screenshots may disagree.
Caveat: That documentation currently covers iOS/iPadOS Outlook. Microsoft hasn't published Android-specific MMA details that I could verify. It is reasonable to plan for the same behavior on Android, but it is not confirmed.
What is not yet confirmed for Android
Microsoft's MMA page was last updated on June 11, 2026. It lists Outlook only for iOS/iPadOS, with a minimum version of 5.2626.0, and says support for more apps and platforms is coming. That fits an Android expansion, but nothing I found confirms Android specifics. Specifically, I could not verify:
- A minimum Outlook for Android build. Do not reuse the iOS version number.
- A minimum Android version.
- A setup workflow or tenant rollout schedule.
- Whether the accounts must come from different tenants. The roadmap text doesn't say so.
The documentation also says rollout is gradual and the feature may not yet be in your tenant. That is general MMA guidance. It doesn't confirm the Android date.
Admin planning notes
These points come from Microsoft's general MMA and Outlook management documentation. They are not Android-specific announcements.
- There is no on/off switch. Microsoft says MMA isn't a standalone policy setting and has no first-class admin control to enable or disable it. It depends on app participation. Wrapped apps aren't supported, and only apps integrated with the Intune SDK are in scope. The MMA page names one indirect brake on iOS, the IntuneMAMAllowedAccountsOnly setting. It says the setting effectively disables MMA there. Android behavior for that setting isn't documented in the material I reviewed.
- Keep Conditional Access in the plan. Microsoft's Outlook guidance pairs Conditional Access, which requires an approved client app or app protection policy, with Intune app protection policies. For Android devices, the Intune Company Portal app is required for app-based Conditional Access. The same page says unenrolled Android devices need Company Portal for app protection policies to apply.
- Check mobile threat defense. Microsoft says MTD threat level is evaluated at the device level, tied to the Entra device record. Accounts from one tenant may share a threat level, while cross-tenant behavior depends on the MTD vendor. Ask your vendor before relying on it.
- Brief your help desk. The documentation tells admins that if policies look stricter than expected, they should check whether the user is in a mixed view. That is likely to become a common ticket.
- Log tickets from the right tenant. For issues on a managed device, Microsoft says support tickets must be logged from the tenant that manages the device.
Bottom line
This is a modest roadmap line with a useful payoff for people who work across organizations. Plan around three facts. The feature is still in development. Microsoft's documented behavior shows one MDM account per device. And Outlook's combined views will probably apply the strictest policy. Until Microsoft publishes Android-specific guidance, test in a pilot group rather than promising users a date or a copy-and-paste experience.