Skip to content
English
  • There are no suggestions because the search field is empty.

Entra ID single sign-on and provisioning

Connect TelluCare to your organisation's Microsoft Entra ID so that personnel can sign in with their work account (single sign-on), and so that personnel are created and kept up to date in TelluCare automatically (provisioning).

For / Required Role: Administrator

Before you start

  • Entra ID single sign-on (SSO), and Entra ID provisioning if you use it, must be turned on in Account settings under Security and access. Administrators can see these settings but cannot turn them on. Contact Support to have them turned on.
  • When they are on, an administrator in TelluCare does the rest of the setup.
  • In Entra ID, you need permission to create enterprise applications and to grant admin consent.
  • Follow the steps in order. Some values are created in Entra ID and entered in TelluCare, and some go the other way.
Step Where What you do
1 Entra ID Create an enterprise application.
2 Entra ID Add a permission and a client secret, and copy the IDs.
3 TelluCare Create the Entra ID account, test the configuration and copy the redirect URL.
4 Entra ID Add the redirect URL and grant admin consent.
5 TelluCare and Entra ID Set up provisioning.
6 Entra ID and TelluCare Add groups and assign roles.

Steps 1–4 set up single sign-on. Steps 5–6 set up provisioning.

1. Create the enterprise application in Entra ID

  1. In the Microsoft Entra admin center, go to Enterprise applications and select New application.
  2. Select Create your own application and enter a name, for example TelluCare. You can change the name later.

2. Prepare the application for single sign-on

Add the User.Read permission

Personnel need it to sign in with Entra ID.

  1. In the enterprise application, open Properties.
  2. Go to the application registration, open API permissions and select Add a permission.
  3. Add User.Read from Microsoft Graph.

Add a client secret

  1. In the application registration, open Certificates & secrets and select New client secret.
  2. Enter a name for the secret and choose when it expires.
  3. Copy the secret's Value right away. It is not shown again.

Copy the IDs

  1. Open Overview and copy the Application (client) ID and the Directory (tenant) ID.

3. Connect TelluCare

  1. In TelluCare, go to Account settings.
  2. Under Entra ID accounts, select Create. The card shows when Entra ID single sign-on (SSO) is on.
  3. Enter the Tenant ID (the Directory (tenant) ID), the Client ID (the Application (client) ID), the Client Secret (the secret's Value) and a Display name. All four are required. Select Save.
  4. On the Entra ID account page, select Test configuration to check that the saved values are valid.
  5. Copy the Redirect URL that TelluCare shows.

4. Finish single sign-on in Entra ID

  1. In the application registration, open Authentication, select Add a platform and choose Web.
  2. Paste the redirect URL from TelluCare.
  3. Go back to the enterprise application. Under Security, open Permissions and select Grant admin consent for your organisation.

Single sign-on is now set up.

5. Set up provisioning

In TelluCare

  1. In Account settings, open the Entra ID account under Entra ID accounts and select Activate provisioning. The button shows when Entra ID provisioning is on.
  2. A dialog shows the generated Secret token and the Tenant URL. Copy both.
  3. The tenant URL stays visible on the Entra ID account page under Provisioning admin credentials.

In Entra ID

  1. In the enterprise application, open Provisioning and select Get started.
  2. Set Provisioning mode to Automatic.
  3. Enter the Tenant URL and the Secret token from TelluCare.
  4. Under Mappings, turn on provisioning for both groups and users, and check the attribute mapping. The username is usually mapped from userPrincipalName.

6. Add groups and assign roles

Provisioning needs both groups and personnel. The group decides which role personnel get and turns on single sign-on for them. Personnel provisioned without a group get no role, and single sign-on is not turned on for them.

  1. In the enterprise application in Entra ID, add the groups whose members should have access to TelluCare.
  2. After the first provisioning cycle, TelluCare shows the provisioned groups and how many personnel are in each.
  3. In TelluCare, assign a role to each provisioned group, so everyone in the group gets that role. Each role is given in an organisation unit and shown as Organisation unit | Role. You can also set roles for individual personnel. New members of a group get the group's role in the next provisioning cycle.

Personnel who already exist in TelluCare

If a person already has a profile in TelluCare when provisioning starts, TelluCare tries to link the profile to the person in Entra ID. The link is made only if all three rules are met:

Rule What must be true
Same username and email The username and email are the same in Entra ID and in TelluCare. Check that the attribute mapping uses the same source for the username as TelluCare, usually userPrincipalName.
Not provisioned from another source TelluCare stores the Entra ID object ID on a profile when it is provisioned. If the profile already has an object ID, it must match.
Single sign-on already on The person already has single sign-on turned on in TelluCare. This rule is skipped if the profile was already provisioned from this Entra ID.

When all three are met, the profile is linked and its other fields are updated to match Entra ID. If any rule is not met, provisioning returns a conflict for that person and the profile is not changed.

Good to know

  • The client secret expires. Before it does, create a new secret in Entra ID and enter its value in TelluCare. Sign-in with Entra ID stops working when the secret has expired.
  • If you change the Client ID or the Tenant ID, you must enter a new client secret too. If you leave Client Secret empty when you change other fields, the saved secret is kept.
  • Reset secret token on the Entra ID account page creates a new secret token for provisioning. The old token stops working.
  • Personnel provisioned without a group get no role and no single sign-on.