Federated identity management using Active Directory Federation Services
Escalate the existing Severity A case through your organization’s Microsoft Unified/Premier support channel now, because Microsoft Learn Q&A participants cannot access, assign, or expedite private support cases.
Escalate the support request
- Open Microsoft Engage Center → Support Requests, select the active case, and check:
- State and current owner
- Severity
- Primary contact
- Communications for a missed response
- Whether the case is assigned to the correct workspace
- Add an urgent update stating:
- Production AD FS and WAP are unavailable.
- There is no working authentication path or workaround.
- Your team is available continuously, 24×7.
- Include the affected Windows Server versions, installed KB numbers, outage start time, topology, and callback details.
- Contact your organization’s Microsoft Customer Success Account Manager, Incident Manager, or Unified Support contact and request immediate duty-manager escalation. If that route is unavailable, use Microsoft’s Enterprise support entry point.^2^
- Keep the primary contact continuously reachable. Published Severity A guidance for support services defines critical business impact, an initial response target of less than one hour, and a customer commitment to continuous 24×7 engagement; the exact commitment governing this AD FS case remains the one in your support agreement.^3^
Do not post logs, tenant details, phone numbers, email addresses, or other confidential case data in this public forum.
Parallel AD FS/WAP recovery checks
No public November 2026 Windows Server known issue was identified that specifically documents AD FS/WAP becoming unavailable after the patching reboot.^4^
- Check service state on every AD FS and WAP node.
If either service fails to start, preserve its event details before changing configuration. A stopped AD FS or proxy service can make the federation endpoint return HTTP 503.^5^Get-Service adfssrv, appproxysvc -ErrorAction SilentlyContinue | Format-Table Name, Status, StartType Get-WinEvent -FilterHashtable @{ LogName='AD FS/Admin' StartTime=(Get-Date).AddHours(-6) } -ErrorAction SilentlyContinue | Select-Object -First 30 TimeCreated, Id, LevelDisplayName, Message - On each WAP server, inspect: Event Viewer → Applications and Services Logs → Microsoft → Windows → Web Application Proxy → Admin In particular:
- 12000/12003/12004/12011: test AD FS connectivity and proxy trust.
- 13013/13015: synchronize clocks.
- Trust-certificate or missing-configuration errors: re-establish WAP trust after validating AD FS health.^6^
- Compare the AD FS service-communications certificate with HTTP SSL bindings on every AD FS and WAP server:
Verify the federation hostname, certificate thumbprint/Get-AdfsCertificate -CertificateType Service-Communications | Select-Object Thumbprint, NotAfter netsh http show sslcertcerthash, andAdfsTrustedDevicesCTL binding. Also check clock synchronization and AD FS replication.^7^ - Only if the WAP events identify broken or missing proxy trust, rebuild it on each affected WAP node:
This changes WAP trust configuration; record the current configuration and confirm the federation service name and certificate first. Do not use trust reset as an unconditional first action.^7^Install-WebApplicationProxy ` -FederationServiceName "fs.contoso.com" ` -CertificateThumbprint "<service-communications-thumbprint>"
References
- Support Requests - Microsoft Engage Center
- Microsoft Support
- Support for Microsoft Power Platform and Dynamics 365 apps
- November 10, 2026—KB5131090 (OS Build 20348.5870)
- Active Directory Federated Services (AD FS) server is down or unreachable
- Troubleshoot Web Application Proxy
- Proxy trust between WAP and the AD FS server is broken