Become a Microsoft Intune Mobile Device Management Partner - Microsoft Intune | Microsoft Learn
In brief
Microsoft added guidance describing eligibility criteria and the application process for becoming an Intune compliance MDM partner. Eligible solutions must support MDM, user-based compliance, Microsoft Entra ID, and Android, iOS/iPadOS, or macOS.
What Intune admins need to know
MDM vendors can use the documented process to apply, while organizations using onboarded partners should obtain setup information directly from those partners.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
new file mode 100644
layout: Conceptual title: Become a Microsoft Intune Mobile Device Management Partner - Microsoft Intune | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/intune/device-security/compliance/become-mobile-device-management-compliance-provider author: ilwu-microsoft ms.author: ilwu breadcrumb_path: /intune/breadcrumb/toc.json uhfHeaderId: MSDocsHeader-Intune feedback_system: Standard ms.service: microsoft-intune ms.collection:
- M365-identity-device-management
- compliance
- sub-device-compliance ms.subservice: protect description: Learn the eligibility criteria and application process for becoming a Microsoft Intune mobile device management (MDM) compliance partner. ms.date: 2026-11-03T00:00:00.0000000Z ms.topic: how-to ms.reviewer: ilwu-microsoft ai-usage: ai-assisted locale: en-us document_id: bb0a5a33-7c31-a13c-e573-da1e1e9e7013 document_version_independent_id: bb0a5a33-7c31-a13c-e573-da1e1e9e7013 original_content_git_url: https://github.com/MicrosoftDocs/memdocs-pr/blob/live/intune/device-security/compliance/become-mobile-device-management-compliance-provider.md site_name: Docs depot_name: MSDN.memdocs page_type: conceptual toc_rel: ../../toc.json pdf_url_template: https://learn.microsoft.com/pdfstore/en-us/MSDN.memdocs/{branchName}{pdfName} feedback_product_url: '' feedback_help_link_type: '' feedback_help_link_url: '' asset_id: device-security/compliance/become-mobile-device-management-compliance-provider moniker_range_name: monikers: [] item_type: Content source_path: intune/device-security/compliance/become-mobile-device-management-compliance-provider.md cmProducts:
- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/a72e95ff-4b4f-4cc1-90c6-7dcba67ff05f
- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/57eae307-c3a1-4cac-b645-1a899934bac8 spProducts:
- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/24dc3ccd-591a-4415-a1fe-8759afafcb12
- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/ee561821-1ac7-45a8-9409-6ba5eb7a5b97 platformId: 85b85062-d4b7-739a-1025-c25320ac4938
Become a Microsoft Intune Mobile Device Management Partner - Microsoft Intune | Microsoft Learn
The Third-Party Compliance MDM Partner Program is designed for mobile device management (MDM) solutions that determine and manage compliance for user-associated devices and use Microsoft Entra ID to communicate device compliance status to Microsoft services.
Supported scenarios
To be eligible as an Intune compliance partner, your MDM solution must meet the following criteria:
- Manage devices using MDM protocols.
- Evaluate device compliance for user-based scenarios.
- Use Microsoft Entra ID for user identification.
- Support one or more of the following platforms: Android, iOS/iPadOS, and macOS.
Apply to become an Intune compliance MDM partner
Partners interested in integrating with Microsoft should begin by creating a Microsoft Entra app for their MDM product. For instructions, see Register a Microsoft Entra app and create a service principal.
After you create a Microsoft Entra app and obtain a Microsoft Entra app ID, you can apply to become a partner through the Intune Compliance MDM Partner Application.
Microsoft uses the submitted information to validate that:
- The solution aligns with the intended Intune and Microsoft Entra ID Conditional Access scenario.
- The proposed integration is appropriate for the Intune Device Compliance API.
- The partner is prepared to provide enterprise-grade support to customers after launch.
To protect your organization and customers, do not include detailed implementation information, source code, API payloads, security internals, proprietary design details, or other information not reasonably necessary for Microsoft's evaluation.
If Microsoft accepts your application, an API agreement is sent to the business or legal contact identified by your organization for review and signature. After your organization signs and returns the agreement, Microsoft provides the technical documentation required to begin developing the integration.
Partners are responsible for implementing the integration based on the provided documentation. Microsoft does not guarantee dedicated onboarding assistance, implementation guidance, or engineering support during development.
Submission of an application does not guarantee API documentation access, approval to integrate, public listing, or production availability. Microsoft might request additional information as part of the review process.
Note
For partners onboarded through the new self-service process, Microsoft does not publish partner-specific setup documentation or list each partner by name in the Microsoft Intune admin center. Partners should provide their customers with the setup information required to use their solution.
To configure an MDM integration, a customer adds a custom MDM compliance partner in the Intune admin center by entering the Microsoft Entra application ID provided by their selected third-party MDM provider. Intune uses this application ID to create the connector and enable the partner integration. \ No newline at end of file
@@ -0,0 +1,84 @@+---+layout: Conceptual+title: Become a Microsoft Intune Mobile Device Management Partner - Microsoft Intune | Microsoft Learn+canonicalUrl: https://learn.microsoft.com/en-us/intune/device-security/compliance/become-mobile-device-management-compliance-provider+author: ilwu-microsoft+ms.author: ilwu+breadcrumb_path: /intune/breadcrumb/toc.json+uhfHeaderId: MSDocsHeader-Intune+feedback_system: Standard+ms.service: microsoft-intune+ms.collection:+- M365-identity-device-management+- compliance+- sub-device-compliance+ms.subservice: protect+description: Learn the eligibility criteria and application process for becoming a Microsoft Intune mobile device management (MDM) compliance partner.+ms.date: 2026-11-03T00:00:00.0000000Z+ms.topic: how-to+ms.reviewer: ilwu-microsoft+ai-usage: ai-assisted+locale: en-us+document_id: bb0a5a33-7c31-a13c-e573-da1e1e9e7013+document_version_independent_id: bb0a5a33-7c31-a13c-e573-da1e1e9e7013+original_content_git_url: https://github.com/MicrosoftDocs/memdocs-pr/blob/live/intune/device-security/compliance/become-mobile-device-management-compliance-provider.md+site_name: Docs+depot_name: MSDN.memdocs+page_type: conceptual+toc_rel: ../../toc.json+pdf_url_template: https://learn.microsoft.com/pdfstore/en-us/MSDN.memdocs/{branchName}{pdfName}+feedback_product_url: ''+feedback_help_link_type: ''+feedback_help_link_url: ''+asset_id: device-security/compliance/become-mobile-device-management-compliance-provider+moniker_range_name: +monikers: []+item_type: Content+source_path: intune/device-security/compliance/become-mobile-device-management-compliance-provider.md+cmProducts:+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/a72e95ff-4b4f-4cc1-90c6-7dcba67ff05f+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/57eae307-c3a1-4cac-b645-1a899934bac8+spProducts:+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/24dc3ccd-591a-4415-a1fe-8759afafcb12+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/ee561821-1ac7-45a8-9409-6ba5eb7a5b97+platformId: 85b85062-d4b7-739a-1025-c25320ac4938+---++# Become a Microsoft Intune Mobile Device Management Partner - Microsoft Intune | Microsoft Learn++The Third-Party Compliance MDM Partner Program is designed for mobile device management (MDM) solutions that determine and manage compliance for user-associated devices and use Microsoft Entra ID to communicate device compliance status to Microsoft services.
+
+## Supported scenarios
+
+To be eligible as an Intune compliance partner, your MDM solution must meet the following criteria:
+
+- Manage devices using MDM protocols.
+- Evaluate device compliance for user-based scenarios.
+- Use Microsoft Entra ID for user identification.
+- Support one or more of the following platforms: Android, iOS/iPadOS, and macOS.
+
+## Apply to become an Intune compliance MDM partner
+
+Partners interested in integrating with Microsoft should begin by creating a Microsoft Entra app for their MDM product. For instructions, see [Register a Microsoft Entra app and create a service principal](/en-us/entra/identity-platform/howto-create-service-principal-portal).
+
+After you create a Microsoft Entra app and obtain a Microsoft Entra app ID, you can apply to become a partner through the [Intune Compliance MDM Partner Application](https://forms.cloud.microsoft/r/GKYuFnrSdv).
+
+Microsoft uses the submitted information to validate that:
+
+- The solution aligns with the intended Intune and Microsoft Entra ID Conditional Access scenario.
+- The proposed integration is appropriate for the Intune Device Compliance API.
+- The partner is prepared to provide enterprise-grade support to customers after launch.
+
+To protect your organization and customers, do not include detailed implementation information, source code, API payloads, security internals, proprietary design details, or other information not reasonably necessary for Microsoft's evaluation.
+
+If Microsoft accepts your application, an API agreement is sent to the business or legal contact identified by your organization for review and signature. After your organization signs and returns the agreement, Microsoft provides the technical documentation required to begin developing the integration.
+
+Partners are responsible for implementing the integration based on the provided documentation. Microsoft does not guarantee dedicated onboarding assistance, implementation guidance, or engineering support during development.
+
+Submission of an application does not guarantee API documentation access, approval to integrate, public listing, or production availability. Microsoft might request additional information as part of the review process.
+
+Note
+
+For partners onboarded through the new self-service process, Microsoft does not publish partner-specific setup documentation or list each partner by name in the Microsoft Intune admin center. Partners should provide their customers with the setup information required to use their solution.
+
+To configure an MDM integration, a customer adds a custom MDM compliance partner in the Intune admin center by entering the Microsoft Entra application ID provided by their selected third-party MDM provider. Intune uses this application ID to create the connector and enable the partner integration.\ No newline at end of file