Transport Layer Security
Doc updateThe TLS inspection documentation now explains how to configure either a Microsoft-managed certificate or your own certificate authority.
Daily.Entra.NewsDaily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →
Global Secure Access was the sole focus of the period, centered on TLS inspection. A new preview guide covers a tenant-specific Microsoft-managed root CA for Microsoft Entra Internet Access TLS inspection, while related guidance separates managed-certificate and customer-provided certificate procedures. The remaining custom-header update only standardized spacing in domain lists.
The new guide explains how to create a tenant-specific Microsoft-managed root CA, deploy its public certificate to client devices, and enable it for Microsoft Entra Internet Access TLS inspection. The private key remains protected by Microsoft.
The main TLS inspection page now explains how to configure TLS inspection with either a Microsoft-managed certificate or an administrator-provided certificate.
The updated guide focuses on creating a certificate signing request, having it signed by the organization’s PKI, and uploading the resulting certificate, while linking to the separate Microsoft-managed certificate guidance.
The guidance now explains that TLS inspection for enterprise generative AI app prompt-injection protection can use either a Microsoft-managed certificate or an administrator-provided certificate before TLS inspection policies are configured.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The TLS inspection documentation now explains how to configure either a Microsoft-managed certificate or your own certificate authority.
The guide explains how to create a tenant-specific Microsoft-managed root CA, deploy its public certificate to client devices, and enable it for Microsoft Entra Internet Access TLS inspection. The capability is in preview, and the private key remains protected by Microsoft.
The article now focuses on bringing your own certificate authority for TLS inspection, including CSR creation, PKI signing, and certificate upload. It also links to separate Microsoft-managed certificate guidance.
The AI prompt injection protection documentation now explains that TLS inspection can use either a Microsoft-managed certificate or an administrator-provided certificate before configuring TLS inspection policies.
The documentation now provides separate links for configuring TLS inspection with a Microsoft-managed certificate and with your own certificate.
Consistent spacing was added to domain lists for Claude, GitHub, Slack, Dropbox, and YouTube entries. Header names and descriptions are unchanged.
The troubleshooting page now links to separate guides for Microsoft-managed certificates and customer-provided certificates, and its publication date was updated.