Skip to content

Single sign-on with Microsoft Entra ID

This guide connects Microsoft Entra ID to CloudRepo with OpenID Connect (OIDC), so the people in your directory sign in to CloudRepo through Entra ID. Each step says what you should see before you go on.

  1. Sign in to CloudRepo as your organization’s owner, with a second factor set up. If you have not set one up yet, do the steps in Before you change anything first: they keep your builds working.

    Expected: your sign-in asks for a code from your authenticator app.

  2. Check that you can sign in to the Microsoft Entra admin center with a role that can register applications.

    Expected: you can open App registrations under Entra ID.

  1. In the sidebar, click Security, then Single sign-on. Under Which identity provider do you use?, choose Microsoft Entra ID.

    Expected: a box headed For your identity provider shows a Redirect URI and the line In Microsoft Entra ID, add this as a Redirect URI on the Web platform. Below it is the form you fill in later.

  2. Copy the Redirect URI. Leave this page open.

    Expected: you have an address that ends in a long ID. That address belongs to your organization alone, so paste it exactly, with nothing added.

  1. In the Microsoft Entra admin center, go to Entra ID, then App registrations, and select New registration. Set Name to CloudRepo. Under Supported account types, choose Single tenant only. Select Register.

    Expected: the app’s Overview page, with an Application (client) ID.

  2. Under Manage, select Authentication, then Add Redirect URI. Choose the Web tile, paste the Redirect URI you copied as its Redirect URI, and select Configure.

    Expected: the Web platform lists one redirect URI, the same as the Redirect URI in CloudRepo, character for character.

  3. Select Certificates & secrets, then Client secrets, then New client secret. Add a description, choose when it expires, and select Add. Copy the secret’s Value now: Entra ID never shows it again.

    Expected: you have the secret’s value.

  4. Copy the Application (client) ID from the app’s Overview page, and your Tenant ID from Entra ID, then Overview, then Properties.

    Expected: you have the client ID and the tenant ID.

  1. Back on SSO Settings in CloudRepo, fill in the form:

    • Issuer URL: https://login.microsoftonline.com/{tenant-id}/v2.0, with your tenant ID in place of {tenant-id}.
    • Client ID: the application (client) ID.
    • Client Secret: the secret’s value.
    • Verified Domains: the email domains your people sign in with, such as example.com. Only addresses at these exact domains can sign in with SSO.
    • Scopes: leave it empty.

    Click Save. In Confirm Your Identity, enter the code from your authenticator app under Authenticator Code and click Confirm.

    Expected: the Identity Provider card shows your settings and the Disabled badge. Saving does not turn SSO on.

  2. Click Enable SSO, and confirm your identity the same way.

    Expected: a banner reads SSO enabled., and the badge reads Enabled.

  1. Pick one person in your directory whose address is at one of your verified domains, and who has no CloudRepo account or invitation yet. Ask them to go to https://admin.cloudrepo.io/login, enter your organization ID, click Continue, and sign in with Microsoft.

    Expected: they land in the admin portal, signed in as themselves. CloudRepo made their account at this first sign-in.

Then finish the rollout in the SSO guide:

  • People you invited to CloudRepo, and people who already have a CloudRepo account, need you to allow SSO sign-in for them before their first sign-in through Entra ID works. With Entra ID this holds for invited people too: see If your identity provider is Microsoft Entra ID, and allow them as in step 10. Read that step before you click: it says what changes for them.
  • Each member then creates new repository tokens after signing in through Entra ID, as in step 11.
  • When you are ready to enforce SSO, steps 12 to 14 say what to check first.
  • Microsoft shows its own error page instead of sending you back to CloudRepo: open the app’s Authentication page in Entra ID and compare its Web redirect URI with the Redirect URI on SSO Settings. They must match character for character. Fix the Entra ID side: you do not need to change anything in CloudRepo.
  • CloudRepo says Your organization has to make a change before you can sign in with SSO: that person was invited, or already has a CloudRepo account. Allow SSO sign-in for them, as sso_link_required shows.

Every other refusal, and how to fix it, is in Refusals, and how to fix each one.

To have Entra ID add and remove your members for you, connect SCIM as SCIM provisioning with Okta or Entra ID shows. Members still sign in through the app you registered here.

View as Markdown