Purview Extensibility Catalog

These are surfaces partners and developers commonly ask about, but which are NOT currently buildable on a documented public API. Listed here so you can rule them out quickly and find the right substitute.

There is no formal "Microsoft Purview Partner Program" today. Below are the actual paths that exist for partners, customers, and developers building on Purview — with their real entry points. Most surfaces in this catalog need only a standard Entra app registration; only the items below need a separate program track.

1. MISA — Microsoft Intelligent Security Association. Nomination-only (no application form). Purview products qualify under Data security, governance, and compliance, but there is no Purview-specific track. Requirements: Microsoft AI Cloud Partner Program enrollment + a commercial marketplace listing + integration with ≥ 2 MISA-qualifying Microsoft Security products (a single Purview integration alone does not qualify). Entry point: nomination through your Microsoft contact. MISA overview →
2. IPIA — Information Protection Integration Agreement (MIP SDK). Required before any public release of an app built on the MIP SDK family (`mip-file`, `mip-policy`, `mip-protection`). Not required for internal-only apps. Email-based contract — not Partner Center, not an aka.ms form. Entry point: email IPIA@microsoft.com with subject "Requesting IPIA for [Company Name]". Microsoft returns a Word agreement; you complete it with your legal entity, Tenant ID, and App ID; sign via DocuSign. Approximately 72-hour turnaround. IPIA process docs →
3. Microsoft commercial marketplace (AppSource / Azure Marketplace). Standard listing path via Partner Center. The canonical category for Purview-integrated solutions is Security → Information Protection and Governance. A marketplace listing is a prerequisite for MISA eligibility. No Purview-specific certification tier or badge exists beyond the generic "Microsoft preferred solutions" badge (earned via Azure IP co-sell eligibility). Marketplace categories →
4. Co-sell. Generic Microsoft co-sell framework applies to Purview-integrated solutions. No Purview-specific co-sell motion, incentive tier, or field alignment exists in public partner documentation as of the verified date. Any Purview-integrated solution competes for attention within the broader Security/Compliance co-sell motion. Co-sell overview →
5. Featured-partner listings on the Purview extensibility Learn page. Not an open program — a curated featuring opportunity. Partners who build integrations on the Purview public APIs can apply to be listed on learn.microsoft.com/en-us/purview/purview-extensibility under Software Developer Partner Integrations. Two active categories with their own application forms:
   • Network Data Security (NDS). For SASE / network-provider integrations using graph-process + graph-scopes (the same surfaces behind dlp-sase-store). Currently featured: [SSE vendor], [SSE vendor]. Apply: aka.ms/PurviewNetworkPartnerOnboardRequest (Microsoft Form: "Microsoft Purview Network Data Security partner integration checklist").
   • Generative AI apps. For 3P AI agents / Gen AI apps integrating with the Purview SDK for AI / processContent / protectionScopes / contentActivities. Currently featured: a Frontier 3P AI partner. Apply: forms.office.com/r/ekg1sxKhkP (Microsoft Form: "Microsoft Purview for Generative AI apps partner integration checklist").
   The same Learn page also points MIP partners to the MISA partner catalog filtered to Purview Information Protection rather than listing them inline.

Programs that do NOT have a public landing page (verified May 2026, no Microsoft Learn / Partner Center URL found): a "Purview Partner Program," a Purview Data Map connector certification, a Purview Security Store / SASE registration distinct from the NDS featuring path above, and a dedicated Purview co-sell tier. If you encounter a reference to one of these, ask for the canonical Microsoft Learn or Partner Center URL before treating it as a publicly available program.