Skip to content

Commit da310db

Browse files
committed
remove preview
1 parent 82238b7 commit da310db

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

articles/active-directory-b2c/connect-with-saml-service-providers.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 03/20/2020
12+
ms.date: 05/18/2020
1313
ms.author: mimart
1414
ms.subservice: B2C
1515
ms.custom: fasttrack-edit
@@ -19,8 +19,6 @@ ms.custom: fasttrack-edit
1919

2020
In this article, you learn how to configure Azure Active Directory B2C (Azure AD B2C) to act as a Security Assertion Markup Language (SAML) identity provider (IdP) to your applications.
2121

22-
[!INCLUDE [active-directory-b2c-public-preview](../../includes/active-directory-b2c-public-preview.md)]
23-
2422
## Scenario overview
2523

2624
Organizations that use Azure AD B2C as their customer identity and access management solution might require interaction with identity providers or applications that are configured to authenticate using the SAML protocol.
@@ -367,7 +365,6 @@ The following SAML relying party (RP) scenarios are supported via your own metad
367365
* Multiple logout URLs or POST binding for logout URL in application/service principal object.
368366
* Specify signing key to verify RP requests in application/service principal object.
369367
* Specify token encryption key in application/service principal object.
370-
* Identity provider-initiated logins are not currently supported in the preview release.
371368

372369
## Next steps
373370

0 commit comments

Comments
 (0)