Facing 530003 issue with intune

Shrishail, Lata 0 Reputation points
2026-11-17T10:23:26.9333333+00:00

Please help me to resolve 530003 issue with android 16

Microsoft Security | Intune | Enrollment
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-17T10:25:30.0066667+00:00

    Confirm the complete AADSTS code and use the matching Microsoft Entra sign-in event to identify and correct the Conditional Access policy blocking Android enrollment; AADSTS53003 means BlockedByConditionalAccess, while Microsoft documents AADSTS530003 separately in a device-related, SharePoint-specific scenario. ^1^ ^2^

    1. Identify the exact blocking policy

    An administrator with at least Reports Reader access should:

    1. On the error page, select More details and record:
      • Complete AADSTS code and error text
      • Request ID and correlation ID
      • Timestamp
      • Application and resource being accessed
    2. Open Microsoft Entra admin center → Entra ID → Monitoring & health → Sign-in logs.
    3. Filter by the affected username, timestamp, correlation ID, and failed Conditional Access status.
    4. Open the matching event and select Conditional Access.
    5. Open each failed policy and review Troubleshooting and support, Device Info, and the failed grant or session control. The Troubleshoot Event option can run the sign-in diagnostic. ^3^

    If administrative access is unavailable, send all details above to the Intune/Entra administrator. An end user cannot change the policy producing this error.

    2. Correct only the condition shown as failed

    A Conditional Access Administrator or Security Administrator should edit the named policy under Entra ID → Protection → Conditional Access → Policies. Test changes with a pilot user before broad deployment and preserve emergency-access account exclusions.

    • Microsoft Intune Enrollment is blocked: Review Target resources. Microsoft Intune Enrollment controls the enrollment workflow, while Microsoft Intune controls the admin center and its data sources. Do not apply a control to the enrollment application that requires the device to be enrolled or compliant before enrollment can finish. ^4^
    • Device platform, client app, or device filter failed: Review:
      • Conditions → Device platforms
      • Conditions → Client apps
      • Conditions → Filter for devices
      Microsoft documents these checks for literal AADSTS530003 in a SharePoint Document Grid scenario; they are not proof of the cause here. Apply them only if the Intune enrollment sign-in event shows the same failed conditions. ^2^
    • Compliant network location failed: This condition supports MDM-enrolled devices. A not-yet-enrolled Android device can fail it, so exclude the affected enrollment population or use an appropriate enrollment-compatible control. ^5^
    • Policy targets all users/resources: Avoid configurations that require compliance for every user and resource without appropriate exclusions, because unenrolled users can also be blocked from Intune. ^3^

    3. Run the Android enrollment diagnostic

    An administrator can open the Intune Android enrollment diagnostic, enter the affected user, and select Run tests. Alternatively:

    Microsoft 365 admin center → Show all → Support → Help & support, then describe the Android enrollment failure and run the suggested diagnostic. The test detects configuration problems but does not modify the tenant. It is unavailable in GCC High, DoD, and Microsoft 365 operated by 21Vianet. ^6^

    On the device, also:

    1. Restart it.
    2. Enable automatic date and time and verify the time zone.
    3. Update or reinstall Company Portal if that enrollment method is being used.
    4. Retry using Chrome, Edge, or Samsung Browser for web-based enrollment. ^6^ ^7^

    For a BYOD personally owned work profile only, confirm that Android Enterprise is allowed and that the tenant is connected to Managed Google Play. Other modes—fully managed, corporate-owned work profile, and dedicated—have different enrollment requirements. ^7^

    Do not remove an existing work profile without IT approval: removal deletes its work apps, accounts, settings, and locally stored work data. Ensure work data is synchronized first.

    Android 16 status and escalation

    The public Intune known-issues list does not currently document an Android 16 enrollment issue specifically associated with 530003. That does not exclude a tenant-specific configuration problem or an unpublished Service Health advisory. ^8^

    Open a Microsoft support request if the matching sign-in event and Android diagnostic do not expose a tenant-remediable cause. Include the full error, request ID, correlation ID, timestamp, enrollment mode, device model, Android build, and collected Company Portal logs. If every administrator is blocked by Conditional Access, Microsoft Support is required unless an unaffected administrator can disable the offending policy. ^3^


    References

    1. Microsoft Entra authentication and authorization error codes
    2. Troubleshooting conditional access authentication
    3. Troubleshoot sign-in problems with Conditional Access
    4. Common ways to use Conditional Access with Intune
    5. Learn about Conditional Access and Intune
    6. Troubleshoot device enrollment in Intune - Intune | Microsoft Learn
    7. Set up enrollment of Android Enterprise personally owned work profile devices
    8. Known issues with Microsoft Intune - Intune | Microsoft Learn
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.