| IT549491 | Microsoft Intune | Admins may experience issues within Microsoft Intune with Rapid Security Response version of iOS/iPadOS and macOS |
|---|
| Status | serviceDegradation |
|---|---|
| Classification | advisory |
| User Impact | Admins may experience issues within Microsoft Intune with Rapid Security Response version of iOS/iPadOS and macOS. |
| Last Updated | 05/04/2023 22:51:42 |
| Start Time | 05/02/2023 22:37:58 |
| End Time | |
| Latest Message | Title: Admins may experience issues within Microsoft Intune with Rapid Security Response version of iOS/iPadOS and macOS
User impact: Admins may experience issues within Microsoft Intune with Rapid Security Response version of iOS/iPadOS and macOS. More info: Impact in specific scenarios are limited to Apple devices that take the Rapid Security Responses update iOS: 16.4.1 (a) and macOS: 13.3.1 (a) with an alpha “(a)” character in the OS. Examples of impact may include: – Admins can’t create new compliance policies to check for the new iOS update which has an “(a)” added to the version string. Existing policy checks are unaffected. – Admins can’t create a policy to block conditional launches based on OS version with the character “(a)” for Mobile Application Management (MAM), is unable to check for the new version and can’t validate whether an application can launch or not. – Enrollment restriction policies may not work as intended with non-numerical character versions for Apple products. – Reports with build-specific values will report OS without the “(a)”. – For Mobile Device Management (MDM) admins can use Intune update controls to set the required version to latest to get the security update. For more details on the Rapid Security Response update mentioned above, please read the following article: support.apple.com/en-ca/guide/deployment/dep93ff7ea78/web Specifics for MDM Update controls – learn.microsoft.com/mem/intune/protect/software-updates-ios Current status: The validation of our Rapid Security Response guidelines compliance update is ongoing, while in parallel we’re developing two code changes to work in tandem with our compliance update to resolve the issue. Our current expectation is these should complete by our next scheduled update, after which we’ll conduct further testing to confirm the efficacy of our fixes before initiating our broader deployment. Scope of impact: This issue affects any admin attempting to perform the actions outlined in the More info section of this update. Start time: Monday, May 1, 2023, at 12:00 AM UTC Root cause: Apple recently introduced a change to how their versions are specified, causing a need to change how our originally supported processes work in relation to iOS/iPadOS, and macOS. Next update by: Friday, May 5, 2023, at 7:30 PM UTC |