The Scribe browser extension signs users in through your organization's single sign-on (SSO) connection. Before any of the browser extension guides, SSO must be set up for your Scribe organization. This guide covers Microsoft Entra ID as the identity provider.
What you need from Scribe
Your Scribe contact sets up the SSO connection for your organization and gives you two values for the Entra side:
- an Identifier (Entity ID)
- a Reply URL (Assertion Consumer Service URL)
They will also need the App Federation Metadata URL from your Entra application once it is configured (step 4 below).
In Microsoft Entra
- Entra admin center → Enterprise applications → New application → Create your own application → name it (for example, Scribe SSO) → Integrate any other application you don't find in the gallery → Create.
- Single sign-on → SAML → Basic SAML Configuration → Edit: Identifier (Entity ID) = the value from Scribe, Reply URL = the value from Scribe → Save.
- Attributes & Claims: The defaults are correct. The email claim comes from
user.userprincipalname, so users' sign-in names must be the emails they have in Scribe. - SAML Certificates → Copy the App Federation Metadata URL and send it to your Scribe contact.
- Users and groups → assign every user who will sign in to Scribe. Unassigned users cannot sign in through SSO.
Verify
Once Scribe confirms the connection is active, in a browser, go to scribehow.com and sign in with one of the assigned users. The sign-in should redirect to Microsoft and complete without asking for a Scribe password.
Identity provider changes can take time to propagate. If SSO fails immediately after setup with an "application not configured" message, retry later before changing anything.