A cloud-based identity and access management service for securing user authentication and resource access
Conditional Access can identify device platform from information provided by the device, such as the user agent string, and that information is not verified because user agent strings can be modified. That is why an iOS sign-in can appear as macOS in sign-in evaluation and trigger the wrong policy.
To validate whether Conditional Access is the reason for the block and which policy matched:
- Open the failed sign-in in Microsoft Entra ID sign-in logs.
- Select the failed request.
- Check Basic info for the failure reason.
- Open the Conditional Access tab to see which policy caused the block.
For policy design, Microsoft recommends using device platform as part of a block statement or together with Intune device compliance policies, because platform detection alone is based on unverified device-provided data.
If the current policy blocks macOS broadly, review whether the block is relying only on platform detection. A more reliable approach is to combine platform targeting with device compliance requirements, or test changes in Report-only mode before enforcing them.
If a policy requires device compliance, note these iOS/macOS behaviors:
- On iOS, Android, macOS, and some non-Microsoft browsers, device identification can use a client certificate provisioned during Microsoft Entra registration.
- When users first sign in through the browser, they can be prompted to select that certificate before continuing.
- In report-only mode, policies that require a compliant device can still prompt users on macOS, iOS, and Android to select a device certificate even though compliance is not enforced.
If the immediate goal is to find the exact blocking rule, start with the sign-in log’s Conditional Access tab for the failed event and confirm whether the macOS block policy was applied to that session.