# SAML with Azure AD

**URL:** <https://discuss.elastic.co/t/saml-with-azure-ad/183388>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [May 29, 2019, 4:42pm UTC](https://discuss.elastic.co/t/saml-with-azure-ad/183388 "2019-05-29T16:42:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [June 4, 2019, 1:26am UTC](https://discuss.elastic.co/t/saml-with-azure-ad/183388/5 "2019-06-04T01:26:48Z")

</div>

@hmayer This may help in determining what claims are supported by Azure Active Directory, by default:

> [@SAML configuration - Azure Active Directory](https://discuss.elastic.co/t/saml-configuration-azure-active-directory/182314/2):
>
> I see a couple of potential issues: I believe these also must include the port (even though you're using the default HTTPS port of 443). These values do not look like ones that are typically found within the claims that Azure Active Directory supports. If you request the App Federation Metadata URL to retrieve the XML that lists the supported claims, amongst other metadata, it'll look something like \<?xml version="1.0" encoding="ISO-8859-1"?\> \<EntityDescriptor xmlns="urn:oasis:names:tc:SAML…

---

_[View the full topic](https://discuss.elastic.co/t/saml-with-azure-ad/183388)._