![iOS Build now included in ActiveSyncDeviceAccess rule for Outlook on iOS [MC916298]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-felixmittermeier-956999-1024x683.webp)
Message ID: MC916298
We’re making some changes to the ActiveSyncDeviceAccess rule DeviceOS parameters for Outlook on iOS.
Starting in mid-November, we will start supporting the operating system build number in addition to the operating system version number.
[When this will happen:]
General Availability (Worldwide, GCC, GCC High, DoD) We will roll out this change in mid-November 2024
[How this will affect your organization:]
You are receiving this message because users in your organization may be subject to ActiveSyncDeviceAccess rules on their Exchange mailbox.
Administrations will now be able to specify the iOS operating system build number with the DeviceOS parameter as “iOS X.X.X XXXXX” like “iOS 17.5.1 21F09”, when this change is implemented.
Administrations who have pre-existing ActiveSyncDeviceAccess rules will not be affected by this change. If you want to take advantage of this new capability you will need to update any existing rules.
[What you need to do to prepare:]
When this change takes effect, you will not need to do anything. If you want to take advantage of this functionality you need to update your ActiveSyncDeviceAccess rules or set new ones.
Review:
Source: Microsoft
![New Microsoft Teams and Skype for Business Call Hold Synchronization [MC916294]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-steve-26125330-150x150.webp)
![Outlook for iOS to match Android Authenticator Auto Open Behavior [MC916297]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-266943-150x150.webp)
The upcoming update for Outlook on iOS is set to bring some exciting changes to how ActiveSyncDeviceAccess rules are managed. With the inclusion of the operating system build number, admins will have more precise control over device access parameters.
For administrators, this update means the ability to specify the iOS operating system build number in the DeviceOS parameter, such as “iOS 17.5.1 21F09”. This added granularity will offer better customization options without affecting existing rules. Admins looking to leverage this new feature will need to update their ActiveSyncDeviceAccess rules accordingly.
As for users, the impact of this update will likely be seamless. They may not notice any immediate changes, but behind the scenes, admins will have more tools to ensure a secure and optimized experience for everyone accessing Outlook on iOS devices.
In terms of overall impact, this update seems like a positive step towards enhancing security and management capabilities for organizations using Outlook on iOS. It encourages admins to stay proactive in updating their rules to take advantage of the new functionalities.
What are your thoughts on these changes? Feel free to share your opinions and experiences in the comments below! Let’s start a conversation and learn from each other’s perspectives.