![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 72%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EO%3C/text%3E%3C/svg%3E)
Exchange | Exchange Server | Management
The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 69%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHV%3C/text%3E%3C/svg%3E)
Hi @Omid
Thank you for reaching out.
From my research, this appears to be expected behavior by design, not a regression. Outlook for iOS and Android does not behave like a traditional Exchange ActiveSync (EAS) client. Instead of each mobile device connecting directly to Exchange with its own unique device ID, Outlook Mobile uses a Microsoft cloud-based service layer and modern APIs (REST/Graph) as part of its architecture.
Because of this design, the connection you see (source IP 40.104.x.x) comes from Microsoft cloud infrastructure, not directly from each physical device. Multiple Outlook Mobile installations for the same mailbox can reuse a shared backend service connection or identity rather than creating separate EAS device partnerships. Therefore, after the first device is approved, additional Outlook Mobile installs may not create new MobileDevice objects, may not trigger quarantine, and will not appear in Get-MobileDevice or Get-MobileDeviceStatistics, as observed in your testing.
In contrast, native mail apps (such as iOS Mail or Samsung Mail) use true per-device EAS connections, so each device is able to generate a unique DeviceID, is quarantined independently, and appears in Exchange as expected.
Microsoft documentation also notes architectural differences where Outlook Mobile can use a cloud-backed cache or centralized connection, meaning that multiple devices may not map one-to-one with visible device entries on the Exchange server.
You can refer via: Outlook for iOS and Android | Microsoft Learn
Please note that this summary is based on my own findings and may not fully address your concerns. To help you reach your goal more effectively, I recommend engaging with [GitHub Community Forum] for a deeper technical dive or to connect with individuals who have relevant experience and expertise. Some approaches may behave differently or be restricted depending on your specific environment and configuration. These forums include many experienced developers and Microsoft specialists who can assist with troubleshooting and guidance.
Apologies for redirecting you to the related development team support. As moderators in this community, we do not have access to your specific tenant configuration, and my testing environment is limited. Therefore, my guidance is based on available Microsoft documentation and resources. That said, I’ll do my best to provide additional insight where possible.
I hope this helps.
If you have any additional concerns, feel free to comment below. I would be more than happy to assist.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.