Other Intune-related topics, including unsupported scenarios and platform-specific behaviors
AADSTS53003 means Conditional Access blocked token issuance, so an Entra administrator must inspect the failed Apple Mail sign-in and either keep the intended Outlook-only restriction or modify the policy identified there.^1^
Identify the exact blocking policy
Company Portal enrollment alone does not establish that Apple Mail satisfies every applicable policy. Since Outlook works on the same device, compare its successful event with Apple Mail’s failed event:
- Reproduce the failure in Apple Mail and record the exact time.
- In the Microsoft Entra admin center, go to: Entra ID → Monitoring & health → Sign-in logs.
- Filter by:
- The affected Username
- The recorded Date/time
- Conditional Access: Failure
- Open the failed event and inspect:
- Basic info: application, resource, failure reason, request ID
- Device info: device ID, platform, managed and compliant state
- Conditional Access: failed policy and unsatisfied grant control
- Authentication details and Additional details
- Select the failed Policy Name to review its assignments, conditions, and grant controls. The policy detail view shows which sign-in attributes did or did not satisfy it.^1^
- If the result remains unclear, select Basic info → Troubleshoot Event.
A Reports Reader can inspect the logs; administrator permissions are required to modify the policy.^2^
Apply the matching resolution
The policy requires an approved client app or app protection policy
Apple Mail is then being blocked intentionally. Microsoft documents Conditional Access configurations that allow Outlook for iOS and Android while blocking other Exchange mobile clients.^3^
Choose one outcome:
- Keep the security requirement: continue using Outlook. No iPhone-side Apple Mail reset will override the policy.
- Permit Apple Mail: the Conditional Access administrator must redesign the identified policy so native Mail is not subject to an Outlook/app-protection-only requirement. Test the change in Report-only mode before enabling it. App-based Conditional Access can explicitly block built-in iOS mail while allowing only apps that support Intune app protection policies.^4^
Do not broadly exclude the user or disable Conditional Access merely to make Apple Mail work; adjust only the policy scope and controls required by the organization.
The policy requires a compliant device
Check the failed event’s Device info:
- If the device ID is missing, or managed/compliant is not recognized, investigate device identity rather than reenrolling blindly.
- In Intune, verify that the device and user are compliant with their assigned policies and that the user has the required Intune license.
- If an existing manually configured mail profile conflicts with an Intune-deployed email profile, Company Portal can report noncompliance and prompt for removal. Remove that manual profile only when Company Portal identifies this specific conflict, then allow the managed profile to deploy.^5^
For Apple applications that do not use Microsoft Authentication Library, device-based Conditional Access can also depend on the Microsoft Enterprise SSO plug-in being enabled so the application can participate in device authentication. Have the Intune administrator verify the plug-in configuration if the sign-in log does not recognize the enrolled device.^6^
The policy targets Exchange ActiveSync or legacy clients
Review the policy’s Conditions → Client apps. Native mail access can be evaluated as Exchange ActiveSync or another client category, while Outlook follows a different authentication path. Microsoft notes that legacy clients cannot satisfy controls such as MFA or compliant-device requirements because they do not pass the necessary device-state information.^6^
If native Mail is organizationally required, the administrator must confirm that the account is using a supported modern-authentication path and that the applicable client-app conditions are intentionally scoped. Otherwise, Outlook is the supported result of the current policy.
If escalation is necessary, provide Microsoft Support with the failed event’s request ID, date, and time so the exact Conditional Access evaluation can be located.^1^
References