SSO is available on Enterprise and Legacy Premium plans, and you must be an Account Owner to configure it. If you don't see the SSO section in your account settings, confirm you're on an eligible plan and signed in as an Account Owner.
Self-serve setup uses a metadata URL. If your identity provider only gives you a metadata XML file, contact our support team or your Customer Success Manager to set it up manually.
Install the Wistia app from the Microsoft Marketplace
With Wistia Enterprise plans, our official SSO integration is available in the Microsoft Marketplace and makes the configuration process super easy.
Install the official Entra-Wistia app.
Under "SAML Certificates," copy the "App Federation Metadata URL" and paste it in the SSO section of your Wistia account settings.
Manually configure Wistia SSO with Entra
While we recommend using the official Wistia app in the Microsoft Marketplace, the manual setup process is documented in Microsoft's comprehensive guide for Entra SSO.
If your IT team is setting up the Wistia app by hand, use these values in Basic SAML Configuration:
Identifier (Entity ID):
urn:amazon:cognito:sp:us-east-1_2sjOZnclhReply URL (ACS):
https://sso-auth.wistia.com/saml2/idpresponseSign on URL:
https://<your-account>.wistia.com/login/sso(use your own Wistia subdomain)
Wistia expects these attributes in the SAML response: firstName (user.givenname), lastName (user.surname), and email (user.mail).
Upon completing the setup of a new SAML app for Wistia, copy the "App Federation Metadata URL" and paste it in the SSO section of your Wistia account settings. To access this section, an Account Owner can navigate to the account menu and select "Settings."
This will take you to your Profile page. From here, scroll down and click "SSO" from the lefthand sidebar.
Here, you can paste your metadata URL and adjust your SSO configuration.
Additional resources
For more information on our SSO functionality and what we currently support, check out our main SSO article and FAQ section.
Troubleshooting Entra ID and FAQs
How do I switch identity providers or update my existing metadata URL?
An Account Owner can do this in the SSO section of your account settings. Simply replace your existing metadata URL with the new one, then re-verify sign-in before enabling for all users. If you're moving to a provider without a self-serve guide, reach out to your CSM.
I'm getting a "No SingleSignOn HTTP redirect binding location" error
Wistia requires your IdP metadata to include an HTTP-Redirect SingleSignOnService binding. Some Entra configurations export HTTP-POST only. If you hit this error, make sure your SAML app exposes the HTTP-Redirect binding.
Rotating your SSO certificate: If Wistia is configured with your App Federation Metadata URL (rather than a static file), rotating the certificate in Entra generally requires no action in Wistia—we read the current certificate from the URL.
Does Wistia support SCIM provisioning or managing Wistia roles/groups from Entra?
Wistia provisions users just-in-time (JIT) on first SSO login. We don't support SCIM provisioning or managing groups from within Entra. SCIM provisioning is currently available with Okta only.
How do my users sign in with SSO?
Users sign in at https://<your-account>.wistia.com/login/sso. Make sure you use your account's exact subdomain. If you're not sure what it is, check the URL when you're signed into Wistia.
Clicking the Wistia tile in My Apps gives me an error
Wistia supports sign in that starts on the Wistia side (SP-initiated), not sign in that starts in your identity provider (IdP-initiated). Make sure the Sign on URL in your Entra app's Basic SAML Configuration is set to https://<your-account>.wistia.com/login/sso. The My Apps tile will then send users to Wistia to start sign in.
Do I need a new certificate from Wistia when I switch to Entra?
No. Wistia doesn't issue SSO certificates. Your identity provider supplies the certificate through its metadata URL. To switch from another provider (like OneLogin or Okta) to Entra, replace the metadata URL in the SSO section of your account settings with your new App Federation Metadata URL.
Some users get a new, separate Wistia user after signing in with SSO
Wistia matches SSO users by email. If the email Entra sends doesn't match the user's existing Wistia email, Wistia creates a new user. Before you turn on SSO for everyone, confirm each user's Entra email (the user.mail attribute) matches their Wistia email. For a smooth rollout, turn on SSO first, have a few users test sign in, then turn on Require single sign-on for all users. Account Owners can always sign in with email and password, so you can't lock yourself out.
Can multiple Wistia accounts use the same Entra app?
Yes. A parent account and its subaccounts can all use the same App Federation Metadata URL, but SSO is set up separately in each account.


