Connect Install Roadmap
Doc updateThe roadmap now links to download ID 108777 for both the AD FS and AD DS Connect Health agents, replacing download ID 108565.
Daily.Entra.NewsDaily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →
The substantive work on 1 September centers on Global Secure Access TLS inspection. A new guide documents the preview Microsoft-managed certificate route: create a tenant-specific root CA, deploy its public certificate to client devices, and then enable inspection. Related guidance separates that workflow from bringing your own certificate authority. The day's other notable operational change replaces both AD FS and AD DS Connect Health roadmap download ID 108565 with 108777.
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, and MDM such as Intune can be used for deployment.
The updated article focuses on bringing your own certificate authority, including creating a certificate signing request, having it signed by PKI, and uploading the certificate. It also links to the separate Microsoft-managed certificate guidance; the update requires no administrator action for existing users.
The TLS inspection setup guidance for enterprise generative AI prompt-injection protection now explains that administrators can use either a Microsoft-managed certificate or an administrator-provided certificate before configuring TLS inspection policies.
The Connect Install Roadmap now links to download ID 108777 for both the AD FS and AD DS Connect Health agents, replacing download ID 108565.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The roadmap now links to download ID 108777 for both the AD FS and AD DS Connect Health agents, replacing download ID 108565.
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.