Skip to main content

SCIM: Phone number provisioning

Updated

For our Smishing (SMS phishing) beta, you will need to provision your users' phone numbers via your SCIM connection.

Prerequisites

Instructions

  1. In the Microsoft Entra admin center, go to previously created SoSafe SCIM enterprise application. There, select Provisioning, open the Mappings dropdown and then select Provision Azure Active Directory Users.

    Microsoft Entra admin center, SoSafe SCIM application Provisioning page, with Provisioning marked in the left navigation. The Mappings section is expanded, highlighting Provision Azure Active Directory Users above Provision Azure Active Directory Groups.

     

     

  2. Here, create a new mapping by selecting Add New Mapping or Edit an existing one. The following attributes need to be mapped. See the screenshots below for more details.
customappsso Attribute Microsoft Entra ID Attribute
phoneNumbers[type eq "work"].value telephoneNumber

Microsoft Entra ID Attribute Mapping page for the customappsso application, with the phoneNumbers[type eq work].value row and its Edit button highlighted among other attribute mappings such as userName, displayName, and address fields.

Microsoft Entra Edit Attribute dialog for the customappsso application, with mapping type set to Direct, source attribute telephoneNumber, and target attribute phoneNumbers[type eq work].value.

  1. Either run a provision on demand or wait until Entra automatically updates the users (which should take less than an hour). To verify whether the changes were successful, go to the SoSafe Manager and navigate to User management / Users.

    SoSafe Manager User management Users list with columns for email, user group, type, language, active status, created on, and phone, showing phone numbers populated for several users after SCIM provisioning.

 

Troubleshooting

If your users' phone numbers do not start appearing, we suggest going through the following points in order:

  • Allow enough time for Microsoft Entra to synchronize the changes. The default provisioning cycle can take up to 40 minutes. You can also manually trigger provisioning to expedite testing.
  • In the Microsoft Entra admin center, review the provisioning logs for your SoSafe SCIM application. Look for any errors or warnings related to the phoneNumbers attribute or the user synchronization process.
  • Make sure the telephoneNumber attribute in Azure AD is correctly populated for the users you expect to have phone numbers.
  • Double-check that the target attribute in your Entra ID mapping is exactly phoneNumbers[type eq "work"].value. Copy/pasting is recommended to avoid typos.
  • In some cases, stopping and restarting the provisioning in Entra ID can help apply new mapping changes.

Related articles