Set up single sign-on for microsites
Configure SSO so known subscribers reach your microsites without filling in a separate login. When SSO is enabled, a subscriber who is already authenticated with your identity provider is recognized automatically, and their identity can be used to personalize the page and gate protected content.
Before you begin
- Confirm you have the developer or admin permissions needed to change security settings for the microsite.
- Have your identity provider ready. SSO commonly uses SAML 2.0 or OpenID Connect, and Microsoft Entra ID is a typical provider.
- Gather the provider details you will need: the sign-in (SSO) URL, the issuer/entity ID, and the signing certificate or client credentials.
- Know the microsite (or Folder of microsites) you want to protect, and decide which claim identifies the subscriber (for example, email address).
- (confirm the exact steps in your account)
Steps
- Open the security or authentication settings for the microsite and enable SSO. (confirm the exact label in your account)
- Choose your protocol (SAML 2.0 or OpenID Connect) and register your identity provider by entering the sign-in URL, issuer/entity ID, and signing certificate or client secret.
- Copy the service-provider values shown in the app (such as the reply/redirect URL and entity ID) and register them as an application in your identity provider, for example in Microsoft Entra ID.
- Map the incoming claim that identifies the subscriber (usually email) so the microsite can match visitors and apply personalization.
- Save, then use the preview or test option to run a sign-in round trip before making the microsite live.
Result
An unauthenticated visitor is redirected to your identity provider, signs in once, and returns to the microsite already recognized. Their mapped identity is available for personalization and for gating protected content, with no separate microsite password required.
Related
Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.