📋 Microsoft Entra Documentation Changes

Daily summary for changes since April 12th 2026, 9:51 PM PDT

Report generated on April 13th 2026, 9:51 PM PDT

📊 Summary

36
Total Commits
0
New Files
19
Modified Files
0
Deleted Files
9
Contributors

📝 Modified Documentation Files

+23 / -1 lines changed
Commit: Add DefaultDomain function to expressions reference AB#495931
Changes:
Before
After
 
## List of Functions
 
[Append](#append)      [AppRoleAssignmentsComplex](#approleassignmentscomplex)      [BitAnd](#bitand)      [CBool](#cbool)      [CDate](#cdate)      [Coalesce](#coalesce)      [ConvertToBase64](#converttobase64)      [ConvertToUTF8Hex](#converttoutf8hex)      [Count](#count)      [CStr](#cstr)      [DateAdd](#dateadd)      [DateDiff](#datediff)      [DateFromNum](#datefromnum)  [FormatDateTime](#formatdatetime)      [Guid](#guid)      [IgnoreFlowIfNullOrEmpty](#ignoreflowifnullorempty)     [IIF](#iif)     [InStr](#instr)      [IsNull](#isnull)      [IsNullOrEmpty](#isnullorempty)      [IsPresent](#ispresent)      [IsString](#isstring)      [Item](#item)      [Join](#join)      [Left](#left)      [Len](#len)      [Mid](#mid)      [NormalizeDiacritics](#normalizediacritics)       [Not](#not)      [Now](#now)      [NumFromDate](#numfromdate)      [PCase](#pcase)      [RandomString](#randomstring)      [Redact](#redact)      [RemoveDuplicates](#removeduplicates)      [Replace](#replace)      [SelectUniqueValue](#selectuniquevalue)     [SingleAppRoleAssignment](#singleapproleassignment)     [Split](#split)    [StripSpaces](#stripspaces)      [Switch](#switch)     [ToLower](#tolower)     [ToUpper](#toupper)     [Word](#word)
 
---
### Append
 
Returns a DateTime representing January 1, 2012 at 11:00PM.
 
---
### FormatDateTime
**Function:**
 
 
 
 
 
 
 
 
## List of Functions
 
[Append](#append)      [AppRoleAssignmentsComplex](#approleassignmentscomplex)      [BitAnd](#bitand)      [CBool](#cbool)      [CDate](#cdate)      [Coalesce](#coalesce)      [ConvertToBase64](#converttobase64)      [ConvertToUTF8Hex](#converttoutf8hex)      [Count](#count)      [CStr](#cstr)      [DateAdd](#dateadd)      [DateDiff](#datediff)      [DateFromNum](#datefromnum)  [DefaultDomain](#defaultdomain)      [FormatDateTime](#formatdatetime)      [Guid](#guid)      [IgnoreFlowIfNullOrEmpty](#ignoreflowifnullorempty)     [IIF](#iif)     [InStr](#instr)      [IsNull](#isnull)      [IsNullOrEmpty](#isnullorempty)      [IsPresent](#ispresent)      [IsString](#isstring)      [Item](#item)      [Join](#join)      [Left](#left)      [Len](#len)      [Mid](#mid)      [NormalizeDiacritics](#normalizediacritics)       [Not](#not)      [Now](#now)      [NumFromDate](#numfromdate)      [PCase](#pcase)      [RandomString](#randomstring)      [Redact](#redact)      [RemoveDuplicates](#removeduplicates)      [Replace](#replace)      [SelectUniqueValue](#selectuniquevalue)     [SingleAppRoleAssignment](#singleapproleassignment)     [Split](#split)    [StripSpaces](#stripspaces)      [Switch](#switch)     [ToLower](#tolower)     [ToUpper](#toupper)     [Word](#word)
 
---
### Append
 
Returns a DateTime representing January 1, 2012 at 11:00PM.
 
---
### DefaultDomain
**Function:**
DefaultDomain()
 
**Description:**
Returns the name of the default verified domain for the current Microsoft Entra tenant. The default verified domain is the domain in the tenant's list of verified domains that is marked as the default. If no default verified domain is found, the function returns an error.
 
This function takes no input parameters.
 
Modified by Diana Richards on Apr 13, 2026 3:35 PM
📖 View on learn.microsoft.com
+6 / -6 lines changed
Commit: Alt text and Acrolinx fixes
Changes:
Before
After
 
1. Under **Enterprise portal**, select **Single Sign On**.
 
![Screenshot of the Foodee Enterprise Portal left-pane menu](media/Foodee-provisioning-tutorial/scim.png)
 
1. Copy the value in the **API Token** box for later use. You'll enter it in the **Secret Token** box in the **Provisioning** tab of your Foodee application.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**.
 
![Screenshot of The Enterprise applications pane](common/enterprise-applications.png)
 
1. To add a new application, select **New application** at the top of the pane.
 
![Screenshot of the New application button](common/add-new-app.png)
 
1. In the search box, enter **Foodee**, select **Foodee** in the results pane, and then select **Add** to add the application.
 
![Screenshot of Foodee in the results list](common/search-new-app.png)
 
 
1. Under **Enterprise portal**, select **Single Sign On**.
 
![Screenshot of the Foodee Enterprise Portal left-pane menu.](media/Foodee-provisioning-tutorial/scim.png)
 
1. Copy the value in the **API Token** box for later use. You'll enter it in the **Secret Token** box in the **Provisioning** tab of your Foodee application.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**.
 
![Screenshot of The Enterprise applications pane.](common/enterprise-applications.png)
 
1. To add a new application, select **New application** at the top of the pane.
 
![Screenshot of the New application button.](common/add-new-app.png)
 
1. In the search box, enter **Foodee**, select **Foodee** in the results pane, and then select **Add** to add the application.
 
![Screenshot of Foodee in the results list.](common/search-new-app.png)
 
+5 / -5 lines changed
Commit: worked on comments
Changes:
Before
After
 
1. In the **Tenant URL** field, input your Cisco User Management for Secure Access Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Cisco User Management for Secure Access. If the connection fails, ensure your Cisco User Management for Secure Access account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. In the **Notification Email** field, enter the email address of a person who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
 
![Screenshot of Provisioning properties.](common/provisioning-properties.png)
 
1. Select **Attribute Mapping** in the left panel and select **users**.
 
|name.formatted|String||
|urn:ietf:params:scim:schemas:extension:ciscoumbrella:2.0:User:nativeObjectId|String||
 
> [!NOTE]
> If you have imported the objectGUID attribute for users via Microsoft Entra Connect (refer Step 2), add a mapping from objectGUID to urn:ietf:params:scim:schemas:extension:ciscoumbrella:2.0:User:nativeObjectId.
 
 
1. In the **Tenant URL** field, input your Cisco User Management for Secure Access Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Cisco User Management for Secure Access. If the connection fails, ensure your Cisco User Management for Secure Access account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. In the **Notification Email** field, enter the email address of a person who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
 
![Screenshot of Provisioning properties.](common/provisioning-properties.png)
 
1. Select **Attribute Mapping** in the left panel and select **users**.
 
|name.formatted|String||
|urn:ietf:params:scim:schemas:extension:ciscoumbrella:2.0:User:nativeObjectId|String||
 
> [!NOTE]
> If you have imported the objectGUID attribute for users via Microsoft Entra Connect (refer Step 2), add a mapping from objectGUID to urn:ietf:params:scim:schemas:extension:ciscoumbrella:2.0:User:nativeObjectId.
 
Modified by Colin Cooper on Apr 13, 2026 3:55 PM
📖 View on learn.microsoft.com
+4 / -4 lines changed
Commit: Apply suggestions from code review
Changes:
Before
After
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade](common/enterprise-applications.png)
 
1. In the applications list, select **GoLinks**.
 
![Screenshot of the GoLinks link in the Applications list](common/all-applications.png)
 
1. Select the **Provisioning** tab.
 
![Screenshot of Provisioning tab](common/provisioning.png)
 
1. Select **+ New configuration**.
 
![Screenshot of Provisioning tab automatic](common/application-provisioning.png)
 
1. In the **Tenant URL** field, enter your GoLinks Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to GoLinks. If the connection fails, ensure your GoLinks account has the required admin permissions and try again.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
 
1. In the applications list, select **GoLinks**.
 
![Screenshot of the GoLinks link in the Applications list.](common/all-applications.png)
 
1. Select the **Provisioning** tab.
 
![Screenshot of Provisioning tab.](common/provisioning.png)
 
1. Select **+ New configuration**.
 
![Screenshot of Provisioning tab automatic.](common/application-provisioning.png)
 
1. In the **Tenant URL** field, enter your GoLinks Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to GoLinks. If the connection fails, ensure your GoLinks account has the required admin permissions and try again.
 
Modified by Colin Cooper on Apr 13, 2026 3:55 PM
📖 View on learn.microsoft.com
+4 / -4 lines changed
Commit: Apply suggestions from code review
Changes:
Before
After
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade](common/enterprise-applications.png)
 
1. In the applications list, select **Gong**.
 
![Screenshot of the Gong link in the Applications list](common/all-applications.png)
 
1. Select the **Provisioning** tab.
 
![Screenshot of Provisioning tab](common/provisioning.png)
 
1. Select **+ New configuration**.
 
![Screenshot of Provisioning tab automatic](common/application-provisioning.png)
 
1. In the **Tenant URL** field, enter your Gong Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Gong. If the connection fails, ensure your Gong account has the required admin permissions and try again.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
 
1. In the applications list, select **Gong**.
 
![Screenshot of the Gong link in the Applications list.](common/all-applications.png)
 
1. Select the **Provisioning** tab.
 
![Screenshot of Provisioning tab.](common/provisioning.png)
 
1. Select **+ New configuration**.
 
![Screenshot of Provisioning tab automatic.](common/application-provisioning.png)
 
1. In the **Tenant URL** field, enter your Gong Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Gong. If the connection fails, ensure your Gong account has the required admin permissions and try again.
 
Modified by Diana Richards on Apr 13, 2026 3:35 PM
📖 View on learn.microsoft.com
+4 / -4 lines changed
Commit: Alt text and Acrolinx fixes
Changes:
Before
After
1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
1. In the **Add from the gallery** section, type **Figma**, select **Figma** in the search box.
1. Select **Figma** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
![Screenshot of Figma in the results list](common/search-new-app.png)
 
## Configuring automatic user provisioning to Figma
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade](common/enterprise-applications.png)
 
1. In the applications list, select **Figma**.
 
![Screenshot of the Figma link in the Applications list](common/all-applications.png)
 
1. Select the **Provisioning** tab.
 
 
1. Review the user attributes that are synchronized from Microsoft Entra ID to Figma in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Figma for update operations. Select the **Save** button to commit any changes.
1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
1. In the **Add from the gallery** section, type **Figma**, select **Figma** in the search box.
1. Select **Figma** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
![Screenshot of Figma in the results list.](common/search-new-app.png)
 
## Configuring automatic user provisioning to Figma
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
 
1. In the applications list, select **Figma**.
 
![Screenshot of the Figma link in the Applications list.](common/all-applications.png)
 
1. Select the **Provisioning** tab.
 
 
1. Review the user attributes that are synchronized from Microsoft Entra ID to Figma in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Figma for update operations. Select the **Save** button to commit any changes.
+4 / -4 lines changed
Commit: Alt text and Acrolinx fixes
Changes:
Before
After
1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
1. In the **Add from the gallery** section, type **Federated Directory**, select **Federated Directory** in the results panel.
 
![Screenshot of Federated Directory in the results list](common/search-new-app.png)
 
1. Navigate to the **URL** highlighted below in a separate browser.
 
:::image type="content" source="media/federated-directory-provisioning-tutorial/loginpage3.png" alt-text="Screenshot of the S C I M A D test page on the Federated Directory site. Log in with your Microsoft account is highlighted." border="false":::
1. After a successful authentication, accept the consent prompt for the consent page. The application will then be automatically added to your tenant and you be redirected to your Federated Directory account.
 
## Configuring automatic user provisioning to Federated Directory
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade](common/enterprise-applications.png)
 
1. In the applications list, select **Federated Directory**.
1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
1. In the **Add from the gallery** section, type **Federated Directory**, select **Federated Directory** in the results panel.
 
![Screenshot of Federated Directory in the results list.](common/search-new-app.png)
 
1. Navigate to the **URL** highlighted below in a separate browser.
 
:::image type="content" source="media/federated-directory-provisioning-tutorial/loginpage3.png" alt-text="Screenshot of the S C I M A D test page on the Federated Directory site. Log in with your Microsoft account is highlighted." border="false":::
1. After a successful authentication, accept the consent prompt for the consent page. The application will then be automatically added to your tenant and you'll be redirected to your Federated Directory account.
 
## Configuring automatic user provisioning to Federated Directory
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
 
1. In the applications list, select **Federated Directory**.
Modified by Diana Richards on Apr 13, 2026 3:35 PM
📖 View on learn.microsoft.com
+4 / -4 lines changed
Commit: Alt text and Acrolinx fixes
Changes:
Before
After
1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
1. In the **Add from the gallery** section, type **Flock**, select **Flock** in the search box.
1. Select **Flock** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
![Screenshot of Flock in the results list](common/search-new-app.png)
 
## Configuring automatic user provisioning to Flock
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade](common/enterprise-applications.png)
 
1. In the applications list, select **Flock**.
 
![Screenshot of the Flock link in the Applications list](common/all-applications.png)
 
1. Select the **Provisioning** tab.
 
 
1. Review the user attributes that are synchronized from Microsoft Entra ID to Flock in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Flock for update operations. Select the **Save** button to commit any changes.
1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
1. In the **Add from the gallery** section, type **Flock**, select **Flock** in the search box.
1. Select **Flock** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
![Screenshot of Flock in the results list.](common/search-new-app.png)
 
## Configuring automatic user provisioning to Flock
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps**
 
![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
 
1. In the applications list, select **Flock**.
 
![Screenshot of the Flock link in the Applications list.](common/all-applications.png)
 
1. Select the **Provisioning** tab.
 
 
1. Review the user attributes that are synchronized from Microsoft Entra ID to Flock in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Flock for update operations. Select the **Save** button to commit any changes.
+5 / -1 lines changed
Commit: Enhance formatting of passkeys authentication note
Changes:
Before
After
For more information about passkey authentication, see [Support for FIDO2 authentication with Microsoft Entra ID](~/identity/authentication/concept-fido2-compatibility.md).
 
> [!NOTE]
> Microsoft Entra ID currently supports synced passkeys and device-bound passkeys stored on FIDO2 security keys and in Microsoft Authenticator. Passkeys (FIDO2) are available in all Microsoft Entra ID editions, including Microsoft Entra ID Free. No extra licenses are required. For more information, see [Passkeys (FIDO2) authentication method in Microsoft Entra ID](concept-authentication-passkeys-fido2.md).
 
## Get started
 
 
 
 
 
For more information about passkey authentication, see [Support for FIDO2 authentication with Microsoft Entra ID](~/identity/authentication/concept-fido2-compatibility.md).
 
> [!NOTE]
> Microsoft Entra ID currently supports
> - synced passkeys
> - device-bound passkeys stored on FIDO2 security keys and in Microsoft Authenticator <br>
>
> Passkeys (FIDO2) are available in all Microsoft Entra ID editions, including Microsoft Entra ID Free. No extra licenses are required. For more information, see [Passkeys (FIDO2) authentication method in Microsoft Entra ID](concept-authentication-passkeys-fido2.md).
 
## Get started
 
+4 / -0 lines changed
Commit: Add note about enabling schema editor for Edit attribute list AB#509147
Changes:
Before
After
1. Under **Mappings**, select the object (user or group) for which you'd like to add a custom attribute.
1. At the bottom of the page, select **Show advanced options**.
1. Select **Edit attribute list for AppName**.
1. At the bottom of the attribute list, enter information about the custom attribute in the fields provided. Then select **Add Attribute**.
 
For SCIM applications, the attribute name must follow the pattern shown in the example. The "CustomExtensionName" and "CustomAttribute" can be customized per your application's requirements, for example: urn:ietf:params:scim:schemas:extension:CustomExtensionName:2.0:User:CustomAttribute
 
 
 
 
1. Under **Mappings**, select the object (user or group) for which you'd like to add a custom attribute.
1. At the bottom of the page, select **Show advanced options**.
1. Select **Edit attribute list for AppName**.
 
> [!NOTE]
> If the **Edit attribute list for AppName** option doesn't appear, navigate to your application using the URL `https://portal.azure.com/?Microsoft_AAD_Connect_Provisioning_forceSchemaEditorEnabled=true` to enable the schema editor.
 
1. At the bottom of the attribute list, enter information about the custom attribute in the fields provided. Then select **Add Attribute**.
 
For SCIM applications, the attribute name must follow the pattern shown in the example. The "CustomExtensionName" and "CustomAttribute" can be customized per your application's requirements, for example: urn:ietf:params:scim:schemas:extension:CustomExtensionName:2.0:User:CustomAttribute
Modified by Sudhakaran-S-micro on Apr 13, 2026 8:35 AM
📖 View on learn.microsoft.com
+2 / -2 lines changed
Commit: worked on comments
Changes:
Before
After
 
1. In the **Tenant URL** field, input your Chaos Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Chaos. If the connection fails, ensure your Chaos account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. To configure scoping filters, refer to the instructions provided in the [Scoping filter article](~/identity/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
1. Use [on-demand provisioning](~/identity/app-provisioning/provision-on-demand.md) to validate sync with a small number of users before deploying more broadly in your organization.
 
1. When you're ready to provision, select **Start Provisioning** from the **Overview** page.
 
 
1. In the **Tenant URL** field, input your Chaos Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Chaos. If the connection fails, ensure your Chaos account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. To configure scoping filters, refer to the instructions provided in the [Scoping filter article](~/identity/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
1. Use [on-demand provisioning](~/identity/app-provisioning/provision-on-demand.md) to validate sync with a small number of users before deploying more broadly in your organization.
 
1. When you're ready to provision, select **Start Provisioning** from the **Overview** page.
 
Modified by Sudhakaran-S-micro on Apr 13, 2026 8:35 AM
📖 View on learn.microsoft.com
+2 / -2 lines changed
Commit: worked on comments
Changes:
Before
After
 
1. In the **Tenant URL** field, input your Chatwork Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Chatwork. If the connection fails, ensure your Chatwork account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. To configure scoping filters, refer to the instructions provided in the [Scoping filter article](~/identity/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
1. Use [on-demand provisioning](~/identity/app-provisioning/provision-on-demand.md) to validate sync with a small number of users before deploying more broadly in your organization.
 
1. When you're ready to provision, select **Start Provisioning** from the **Overview** page.
 
 
1. In the **Tenant URL** field, input your Chatwork Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Chatwork. If the connection fails, ensure your Chatwork account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. To configure scoping filters, refer to the instructions provided in the [Scoping filter article](~/identity/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
1. Use [on-demand provisioning](~/identity/app-provisioning/provision-on-demand.md) to validate sync with a small number of users before deploying more broadly in your organization.
 
1. When you're ready to provision, select **Start Provisioning** from the **Overview** page.
 
Modified by Sudhakaran-S-micro on Apr 13, 2026 8:35 AM
📖 View on learn.microsoft.com
+2 / -2 lines changed
Commit: worked on comments
Changes:
Before
After
 
1. In the **Tenant URL** field, input your CheckProof Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to CheckProof. If the connection fails, ensure your CheckProof account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. To configure scoping filters, refer to the instructions provided in the [Scoping filter article](~/identity/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
1. Use [on-demand provisioning](~/identity/app-provisioning/provision-on-demand.md) to validate sync with a small number of users before deploying more broadly in your organization.
 
1. When you're ready to provision, select **Start Provisioning** from the **Overview** page.
 
 
1. In the **Tenant URL** field, input your CheckProof Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to CheckProof. If the connection fails, ensure your CheckProof account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. To configure scoping filters, refer to the instructions provided in the [Scoping filter article](~/identity/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
1. Use [on-demand provisioning](~/identity/app-provisioning/provision-on-demand.md) to validate sync with a small number of users before deploying more broadly in your organization.
 
1. When you're ready to provision, select **Start Provisioning** from the **Overview** page.
 
Modified by Sudhakaran-S-micro on Apr 13, 2026 8:35 AM
📖 View on learn.microsoft.com
+2 / -2 lines changed
Commit: worked on comments
Changes:
Before
After
 
1. In the **Tenant URL** field, input your Cinode Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Cinode. If the connection fails, ensure your Cinode account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. To configure scoping filters, refer to the instructions provided in the [Scoping filter article](~/identity/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
1. Use [on-demand provisioning](~/identity/app-provisioning/provision-on-demand.md) to validate sync with a small number of users before deploying more broadly in your organization.
 
1. When you're ready to provision, select **Start Provisioning** from the **Overview** page.
 
 
1. In the **Tenant URL** field, input your Cinode Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Cinode. If the connection fails, ensure your Cinode account has the required admin permissions and try again.
 
![Screenshot of Provisioning test connection.](common/provisioning-test-connection.png)
 
1. Select **Create** to create your configuration.
 
 
1. To configure scoping filters, refer to the instructions provided in the [Scoping filter article](~/identity/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
1. Use [on-demand provisioning](~/identity/app-provisioning/provision-on-demand.md) to validate sync with a small number of users before deploying more broadly in your organization.
 
1. When you're ready to provision, select **Start Provisioning** from the **Overview** page.
 
+1 / -1 lines changed
Commit: Fix inaccurate SCIM endpoint count in tutorial intro AB#508547
Changes:
Before
After
 
![Provisioning from Microsoft Entra ID to an app with SCIM](media/use-scim-to-provision-users-and-groups/scim-provisioning-overview.png)
 
SCIM 2.0 is a standardized definition of two endpoints: a `/Users` endpoint and a `/Groups` endpoint. It uses common REST API endpoints to create, update, and delete objects. The SCIM consists of a predefined schema for common attributes like group name, username, first name, last name and email.
 
Apps that offer a SCIM 2.0 REST API can reduce or eliminate the pain of working with a proprietary user management API. For example, any compliant SCIM client knows how to make an HTTP POST of a JSON object to the `/Users` endpoint to create a new user entry. Instead of needing a slightly different API for the same basic actions, apps that conform to the SCIM standard can instantly take advantage of pre-existing clients, tools, and code.
 
 
![Provisioning from Microsoft Entra ID to an app with SCIM](media/use-scim-to-provision-users-and-groups/scim-provisioning-overview.png)
 
SCIM 2.0 is a standardized protocol that defines core resource endpoints, including a `/Users` endpoint and a `/Groups` endpoint. It uses common REST API endpoints to create, update, and delete objects. The SCIM consists of a predefined schema for common attributes like group name, username, first name, last name and email.
 
Apps that offer a SCIM 2.0 REST API can reduce or eliminate the pain of working with a proprietary user management API. For example, any compliant SCIM client knows how to make an HTTP POST of a JSON object to the `/Users` endpoint to create a new user entry. Instead of needing a slightly different API for the same basic actions, apps that conform to the SCIM standard can instantly take advantage of pre-existing clients, tools, and code.