In development MRC 564617

Microsoft Purview: Information Protection - Rights Management connector – Certificate-based authentication

The Microsoft Rights Management (RMS) connector is moving from shared-secret authentication to certificate-based authentication, improving its security posture. With this update, administrators configure their own Microsoft Entra app registration and certificate, then use the new

Microsoft Purview 03 Horizon04 Security

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure January CY2027
Preview October CY2026
Platforms Web

What it is

Microsoft Purview: Information Protection - Rights Management connector – Certificate-based authentication is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.

What it does

The Microsoft Rights Management (RMS) connector is moving from shared-secret authentication to certificate-based authentication, improving its security posture. With this update, administrators configure their own Microsoft Entra app registration and certificate, then use the new PowerShell module to configure the certificate for each workload (Connector, Exchange, SharePoint, and FCI). New PowerShell cmdlets handle certificate import, registry configuration, private-key permissions, and validation. As part of this change, the connector setup no longer provisions an Entra service principal or issues a shared secret on the customer's behalf. Customers should plan to register an Entra ID application and upload a certificate before installing or upgrading the connector.

Why you should care

Board

Security/compliance control — fund Steady before more seats.

CISO

Prioritise as Steady control; wire into IR and GRC evidence paths.

CFO

Map licence or consumption impact to the frozen value case; avoid seat spray.

Adoption

Pilot with a named cohort and measure changed work, not vanity clicks.

Suggested action

Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Add to Horizon watchlist with an owner. Pilot only after Steady controls for the affected surface are in place.

12 Panes: 03 Horizon · 04 Security

Communication needed

  • Security: Lead review; confirm control mapping before enablement.
  • GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
  • FinOps: Forecast seat or credit impact; align to frozen value case.
  • Adoption: Plan cohort messaging, clinics, and success measures.
  • Comms: One story for board and staff — what changes, what does not, who owns risk.

Benefits

  • May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
  • Roadmap visibility helps Horizon planning without guessing dates.

Risks

  • Status and dates change; treat MRC as directional, not a contract.
  • Enabling without Steady controls can amplify overshare or cost leakage.
  • Preview or rolling features can change behaviour; fence exploration on Pane 12 Frontier.

Source

  • MRC id: 564617
  • Status: In development
  • Products: Microsoft Purview
  • GA / disclosure: January CY2027
  • Preview: October CY2026
  • Platforms: Web
  • Cloud instances: Worldwide (Standard Multi-Tenant)
  • moreInfoUrls: —
  • Open on Microsoft 365 Roadmap

Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.

Back to roadmap intel