Skip to content

Commit cfa1622

Browse files
authored
Merge pull request #217225 from cilwerner/patch-1
[msid][content-health] active-directory-saml-protocol-reference.md (AD0-2006082)
2 parents ca01dc8 + 6591a78 commit cfa1622

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

articles/active-directory/develop/active-directory-saml-protocol-reference.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.workload: identity
1111
ms.topic: conceptual
12-
ms.date: 10/27/2021
12+
ms.date: 11/4/2022
1313
ms.author: kenwith
14-
ms.custom: aaddev
14+
ms.custom: aaddev, engagement-fy23
1515
ms.reviewer: paulgarn
1616
---
1717

@@ -23,14 +23,17 @@ The SAML protocol requires the identity provider (Microsoft identity platform) a
2323

2424
When an application is registered with Azure AD, the app developer registers federation-related information with Azure AD. This information includes the **Redirect URI** and **Metadata URI** of the application.
2525

26-
The Microsoft identity platform uses the cloud service's **Metadata URI** to retrieve the signing key and the logout URI. In the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>, you can open the app in **Azure Active Directory -> App registrations**, and then in **Manage -> Authentication**, you can update the Logout URL. This way the Microsoft identity platform can send the response to the correct URL.
26+
The Microsoft identity platform uses the cloud service's **Metadata URI** to retrieve the signing key and the logout URI. This way the Microsoft identity platform can send the response to the correct URL. In the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>;
2727

28-
Azure AD exposes tenant-specific and common (tenant-independent) SSO and single sign-out endpoints. These URLs represent addressable locations--they're not just identifiers--so you can go to the endpoint to read the metadata.
28+
- Open the app in **Azure Active Directory** and select **App registrations**
29+
- Under **Manage**, select **Authentication**. From there you can update the Logout URL.
2930

30-
- The tenant-specific endpoint is located at `https://login.microsoftonline.com/<TenantDomainName>/FederationMetadata/2007-06/FederationMetadata.xml`. The _\<TenantDomainName>_ placeholder represents a registered domain name or TenantID GUID of an Azure AD tenant. For example, the federation metadata of the contoso.com tenant is at: https://login.microsoftonline.com/contoso.com/FederationMetadata/2007-06/FederationMetadata.xml
31+
Azure AD exposes tenant-specific and common (tenant-independent) SSO and single sign-out endpoints. These URLs represent addressable locations, and aren't only identifiers. You can then go to the endpoint to read the metadata.
32+
33+
- The tenant-specific endpoint is located at `https://login.microsoftonline.com/<TenantDomainName>/FederationMetadata/2007-06/FederationMetadata.xml`. The *\<TenantDomainName>* placeholder represents a registered domain name or TenantID GUID of an Azure AD tenant. For example, the federation metadata of the `contoso.com` tenant is at: https://login.microsoftonline.com/contoso.com/FederationMetadata/2007-06/FederationMetadata.xml
3134

3235
- The tenant-independent endpoint is located at
33-
`https://login.microsoftonline.com/common/FederationMetadata/2007-06/FederationMetadata.xml`. In this endpoint address, **common** appears instead of a tenant domain name or ID.
36+
`https://login.microsoftonline.com/common/FederationMetadata/2007-06/FederationMetadata.xml`. In this endpoint address, *common* appears instead of a tenant domain name or ID.
3437

3538
## Next steps
3639

0 commit comments

Comments
 (0)