Daily.Entra.NewsDaily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →
The most substantive addition is a new troubleshooting article for intermittent HR-to-Active Directory provisioning timeouts. Cloud Sync prerequisites now call out DNS and Active Directory site-mapping failure modes, while three Global Secure Access pages align their documented Explicit Forward Proxy route under Connect rather than Session management.
Entra ID · TroubleshootingA new Entra ID article covers slow or intermittent provisioning from Workday, SAP SuccessFactors, and API-driven HR integrations to on-premises Active Directory. It provides checks for job status, provisioning agents, matching attributes, domain controllers, DNS, connectivity, logs, and required roles.
Entra ID · GeneralThe prerequisites now explain that incorrect DNS, subnet-to-site mappings, or site configuration can cause synchronization failures, performance problems, and intermittent connectivity. They direct administrators to map agent-server subnets correctly in Active Directory Sites and Services.
Global Secure Access · GeneralThe configuration, header, and custom file-hosting instructions now direct administrators to Global Secure Access > Connect > Explicit Forward Proxy, replacing the former Session management route and, for custom hosting, the previous tab-selection procedure.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The prerequisites now explain how incorrect DNS, subnet-to-site mappings, or site configuration can cause provisioning synchronization failures, performance issues, and intermittent connectivity. It directs administrators to correctly map agent server subnets in Active Directory Sites and Services.
A new article explains how to diagnose intermittent timeouts and slow provisioning from Workday, SAP SuccessFactors, and API-driven HR integrations to on-premises Active Directory. It covers job status, provisioning agents, matching attributes, domain controllers, DNS, connectivity, and relevant logs.
The configuration instructions now direct administrators to Global Secure Access > Connect > Explicit Forward Proxy instead of Session management.
The documented path changed from Global Secure Access > Session management > Explicit Forward Proxy to Global Secure Access > Connect > Explicit Forward Proxy.
The instructions now direct administrators to Global Secure Access > Connect > Explicit Forward Proxy, replacing the previous Session Management path and tab selection.
