Skip to main content
This walkthrough uses Microsoft Entra as the identity provider. It configures Entra’s generic (non-gallery) SAML application, the same generic setup any SAML 2.0 provider uses, so the steps map directly onto SAML and SCIM settings. Connectly has run it end to end both ways, with a setup link and manually.
Create an Enterprise application with SAML single sign-on. An App registration does not work with Connectly.

Before you start in Entra

Where a step differs between the two ways Connectly hands over the values, it says Setup link or Manual. With a setup link, keep the wizard open next to Entra: its Single Sign-On part belongs to Step 1 and its Provisioning part to Step 3.
1

Create the Entra application and set up sign-in

  1. In the Microsoft Entra admin center (or the Azure portal), open Enterprise applications and click New application.
  2. Click Create your own application, name it (for example Connectly), choose Integrate any other application you don’t find in the gallery (Non-gallery) and click Create.
  3. Open Single sign-on and choose SAML.
  4. In Basic SAML Configuration, click Edit and enter the Identifier (Entity ID), Reply URL and Sign on URL. Leave Relay State and Logout URL empty, then Save.
  5. In Attributes & Claims, keep Unique User Identifier (Name ID) as user.userprincipalname. The emailaddress claim defaults to user.mail: keep it if every person has an Email in Entra, otherwise change its source attribute to user.userprincipalname.
  6. In SAML Certificates, give Connectly your application’s metadata (below).
  7. In Properties, set Assignment required to Yes, so only people you assign can sign in. With Visible to users set to Yes, people also get a Connectly tile in My Apps that opens the Sign on URL.
2

Assign people and confirm your domain

  1. In the application, open Users and groups, click Add user/group, select the people who will use Connectly and click Assign. Only assigned people can sign in, and only assigned people are provisioned.
  2. If you prove your domain by DNS, publish the TXT record Connectly sent you at your DNS provider and tell Connectly when it is live. Connectly looks it up itself; nothing needs to be uploaded.
  3. Connectly verifies the domain and links your connection to your Connectly business. You hear back when sign-in is switched on.
3

Set up provisioning (SCIM)

Skip this step if you do not use SCIM; see SSO without SCIM.
  1. In the application, open Provisioning. In the classic view, click Get started and set Provisioning Mode to Automatic; in the new view, open Connectivity.
  2. Under Admin Credentials, choose Bearer authentication. Paste the SCIM endpoint into Tenant URL and add ?aadOptscim062020 at its end, which turns on Microsoft’s SCIM 2.0 compliance fixes. Paste the SCIM token into Secret Token. Click Test Connection, wait for Entra to confirm the credentials are authorized, then Save.
  3. Open Attribute mapping (classic view: Provision Microsoft Entra ID Users; new view: the Users tab) and check the mappings against the table below. If you assign groups, turn off provisioning of the groups themselves (classic view: Provision Microsoft Entra ID Groups, Enabled No). Their members are still provisioned.
  4. Under Settings, set Scope to Sync only assigned users and groups.
  5. Do not start provisioning yet. Test with one person first (Step 4).
4

Test with one person, then turn provisioning on

  1. In Provisioning, open Provision on demand, pick one assigned person and click Provision. Entra should report that the user was created, and list the values it sent.
  2. Tell Connectly. We confirm the person is in your Connectly business with the agreed role.
  3. That person opens the Sign on URL in a private browser window and signs in with their Microsoft account. They land in your Connectly business. A first Microsoft sign-in may ask them to change a temporary password or register MFA.
  4. When the test works, open the provisioning Overview and click Start provisioning. Entra provisions everyone assigned, then repeats on its own schedule (Microsoft runs an incremental cycle roughly every 40 minutes). Provision on demand stays available for anyone who cannot wait.
Test sign-ins from a browser that is not already signed in to Microsoft as someone else. Microsoft reuses the session it has, often the admin’s own, and Connectly then refuses that account with error=jit_disabled.