title: Azure AD SSO SingleLogoutService doesn't have POST binding in Federation metadata
body: <p>When tried to integrate a SP(Cognito) with IdP (Azure AD) through SAML federation,</p>
  <p>Azure AD SSO SingleLogoutService doesn't have POST binding in the federation metadata. It does only have <code>urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect</code>.</p>
  <p>What should we do to add <code>urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST</code> in the metadata. I've went through <a href="https://docs.microsoft.com/en-us/azure/active-directory/develop/single-sign-out-saml-protocol" rel="nofollow noreferrer">Azure docs</a> and didn't find one.</p>
  <p>Whereas I've tried to integrate ADFS, ADFS metadata have both HTTP-Redirect and HTTP-POST. The SAML Logout Response from IdP is sent to SP as POST and works perfectly.</p>
  <p>The login flow works pretty straight and has no problems at all. Whereas with Logout, IdP accepts SAML Logout Request and provides the SAML Logout Response through GET endpoint which should be a POST binding endpoint that SP accepts.</p>
  <p>Is the absence of <code>urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST</code> binding in SingleLogoutService disrupts the logout?</p>
  <p>Does Azure support only GET for <code>SingleLogoutService</code>? Azure docs doesn't have any reference regarding the binding it supports for Logout.</p>