Microsoft Entra Integration
All DocumentationsSupport
  • First Steps
    • Getting started
  • Authentification
    • Single Sign On (SSO) via SAML2
    • Sign In via Microsoft 365
  • Data-Synchronization
    • SCIM Provisioning
Powered by GitBook
On this page
  • Application Setup
  • Mapping Settings
  1. Data-Synchronization

SCIM Provisioning

Becard enables automatic data synchronization from Microsoft Entra using SCIM provisioning.

PreviousSign In via Microsoft 365

Last updated 9 months ago

Application Setup

Before we proceed, it is important to ensure that the "" preparations are completed.

We open our Enterprise application in Microsoft Entra, then navigate to the "Provisioning" menu:

Next, we select "Provisioning" again and choose "Automatic" for the Provisioning Mode. Under "Admin Credentials," enter the Tenant URL and the Secret Token, which can be found in Becard under "SCIM Provisioning via Microsoft AD" in your User Directory. Then, test the connection. If an authentication error appears, the Access Secret Token should be regenerated.

Before testing the connection, it is important to ensure that "Enable SCIM Provisioning via Microsoft Entra ID Enterprise application" is activated in Becard. Additionally, "Activate Microsoft Entra" must also be enabled under "Interface Settings."

Mapping Settings

Before starting the provisioning, it is important to check the mappings. Specifically, we need to adjust two parameters in the default settings. To do this, open the mapping for "Provision Azure Active Directory Users":

Adjustment necessary

customappsso Attribute
Microsoft Entra ID Attribute

userName

objectId

externalId

userPrincipalName

Becard uses the standard user mapping with the following values:

Attributes that should not be synchronized can be removed from the mapping.

Getting Started