Sev A ticket no response for 4 hours

Lara Gumasing 0 Reputation points
2026-11-14T20:27:49.29+00:00

Case 2611140030001196. Anyone can assist?
AD FS and Web Application Proxy unavailable after patching reboot

Microsoft Security | Active Directory Federation Services
0 comments No comments

1 answer

Sort by: Oldest
  1. AI answer

    2026-11-14T20:28:55.9266667+00:00

    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

    1. 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
      Engage Center exposes these case details and identifies older active cases as candidates for follow-up.^1^
    2. 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.
    3. 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^
    4. 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^

    1. Check service state on every AD FS and WAP node.
         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
      
      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^
    2. 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^
    3. Compare the AD FS service-communications certificate with HTTP SSL bindings on every AD FS and WAP server:
         Get-AdfsCertificate -CertificateType Service-Communications |
             Select-Object Thumbprint, NotAfter
      
         netsh http show sslcert
      
      Verify the federation hostname, certificate thumbprint/certhash, and AdfsTrustedDevices CTL binding. Also check clock synchronization and AD FS replication.^7^
    4. Only if the WAP events identify broken or missing proxy trust, rebuild it on each affected WAP node:
         Install-WebApplicationProxy `
           -FederationServiceName "fs.contoso.com" `
           -CertificateThumbprint "<service-communications-thumbprint>"
      
      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^

    References

    1. Support Requests - Microsoft Engage Center
    2. Microsoft Support
    3. Support for Microsoft Power Platform and Dynamics 365 apps
    4. November 10, 2026—KB5131090 (OS Build 20348.5870)
    5. Active Directory Federated Services (AD FS) server is down or unreachable
    6. Troubleshoot Web Application Proxy
    7. Proxy trust between WAP and the AD FS server is broken
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.