Skip to main content

Setting Up Single Sign-On With Microsoft Entra ID

Learn how your IT team connects Microsoft Entra ID to BidScript for single sign-on and directory sync, including setup, assigning people, testing and what happens when people leave.

T
Written by Tyler McCarthy

This guide covers how your IT team sets up single sign-on (SSO) between Microsoft Entra ID and BidScript, so your team members sign in with their work Microsoft accounts. It also covers directory sync, which keeps BidScript up to date as people join, change roles in your organisation or leave.

Who Does What

  • Your IT administrator: creates the BidScript application in Entra ID, verifies your email domain, chooses which people can sign in and turns on directory sync.

  • Your BidScript contact: sends you secure BidScript setup links and confirms the connection is live once you've finished.

  • Your workspace Admin: manages roles in BidScript as usual. SSO changes how people sign in, not what they can access.

Before You Start

You need permission to create enterprise applications in Entra ID, such as the Application Administrator or Cloud Application Administrator role. You also need access to your organisation's DNS settings to verify your email domain.

Note: Setup usually takes under an hour of IT time. Domain verification can take longer, depending on how quickly your DNS provider publishes changes.

Requesting Your Setup Links

  1. Ask your BidScript contact to start SSO and directory sync setup for your organisation. Tell them the email domain your team members sign in with.

  2. Your BidScript contact sends secure BidScript setup links to your IT administrator: one for SSO and one for directory sync.

  3. Open the SSO link first and keep it open in a browser tab. The setup screens guide you through each step and show the values you need for Entra ID.

Note: Setup links are time-limited. If one expires before you finish, ask your BidScript contact for a new one.

Verifying Your Domain

  1. In the setup screens, enter the email domain your team members use.

  2. Copy the DNS TXT record the setup screens show you.

  3. Add the record to your domain through your DNS provider.

  4. Return to the setup screens and confirm. Verification completes once the record is visible.

Creating the Application in Entra ID

  1. Sign in to the Microsoft Entra admin centre and go to Enterprise applications.

  2. Select New application, then Create your own application. Name it BidScript and choose the option to integrate an application you don't find in the gallery.

  3. Open the new application, select Single sign-on and choose SAML.

  4. In Basic SAML Configuration, paste the Identifier (Entity ID) and Reply URL from the setup screens, then save.

  5. In Attributes & Claims, check that email address, given name, surname and name are still mapped. Entra ID includes these by default, so you only need to change them if they've been removed.

  6. In SAML Certificates, copy the App Federation Metadata Url and paste it into the setup screens.

Assigning People to the Application

  1. In the BidScript application in Entra ID, go to Users and groups.

  2. Select Add user/group and add the people or groups who should use BidScript.

Only people you assign can sign in through SSO. Your workspace Admin still manages each person's role in BidScript.

Turning On Directory Sync

Directory sync uses SCIM to send changes from Entra ID to BidScript automatically, so you don't have to update BidScript by hand when people join or leave.

  1. Open the directory sync setup link from your BidScript contact and choose Microsoft Entra ID.

  2. In the BidScript application in Entra ID, go to Provisioning and set Provisioning Mode to Automatic.

  3. Paste the Tenant URL and Secret Token from the setup screens, then select Test Connection.

  4. Save, keep the default attribute mappings, and set Scope to sync only assigned users and groups.

  5. Set Provisioning Status to On and save.

Note: Entra ID runs provisioning on its own schedule, so the first sync and later changes can take up to about 40 minutes to reach BidScript.

Testing the Connection

  1. Run the connection test in the setup screens. It signs you in through Entra ID and confirms the details are correct.

  2. Ask one team member to go to the BidScript login page and enter their work email address. They should be taken to Microsoft to sign in.

  3. Once they've signed in successfully, tell your BidScript contact so they can confirm the connection is live.

Tip: If the test fails, check that the Identifier and Reply URL in Entra ID exactly match the setup screens, including any trailing slash, and that the person testing is assigned to the application.

How Sign-In Works Once SSO Is Live

  • SSO only: people with an email address on your verified domain sign in through Entra ID. Password, email code, and Google or Microsoft account sign-in are switched off for them.

  • Existing accounts: the first time someone signs in through SSO, BidScript matches them to their existing account by verified email address. After that it uses a fixed ID, so their projects and history stay with them.

  • Name and email changes: with directory sync on, changes you make in Entra ID update in BidScript, as long as the new email address is on a verified domain.

What Happens When Someone Leaves

When you remove someone from the BidScript application in Entra ID, or disable their account, directory sync tells BidScript. Their active sessions end and they can no longer sign in.

Best Practice: keep leavers in your existing Entra ID process, so access to BidScript ends at the same time as access to everything else.

Best Practices

  • Pilot first: test with a small group before you assign everyone.

  • Use groups: assign an Entra ID group rather than individuals, so joiners and leavers are handled by your existing processes.

  • Tell your team: let people know to sign in with their work email address from now on. BidScript sends them to Microsoft automatically.

If you have any questions during setup, contact your BidScript contact or our support team.

Did this answer your question?