Skip to content

Commit 42739c2

Browse files
author
Ken Withee
committed
Fixes number.
1 parent c7c8556 commit 42739c2

File tree

1 file changed

+15
-19
lines changed

1 file changed

+15
-19
lines changed

articles/active-directory/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md

Lines changed: 15 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -72,31 +72,27 @@ Scoping filters are configured as part of the attribute mappings for each Azure
7272
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Application Administrator](../roles/permissions-reference.md#application-administrator).
7373

7474
::: zone pivot="app-provisioning"
75-
1. Browse to **Identity** > **Applications** > **Enterprise applications** > **All applications**.
76-
1. Select the application for which you have configured automatic provisioning: for example, "ServiceNow".
75+
2. Browse to **Identity** > **Applications** > **Enterprise applications** > **All applications**.
76+
3. Select the application for which you have configured automatic provisioning: for example, "ServiceNow".
7777
::: zone-end
7878

7979
::: zone pivot="cross-tenant-synchronization"
80-
1. Browse to **Identity** > **External Identities** > **Cross-tenant Synchronization** > **Configurations**
81-
82-
3. Select your configuration.
80+
4. Browse to **Identity** > **External Identities** > **Cross-tenant Synchronization** > **Configurations**
81+
5. Select your configuration.
8382
::: zone-end
8483

85-
4. Select the **Provisioning** tab.
84+
6. Select the **Provisioning** tab.
8685

8786
::: zone pivot="app-provisioning"
88-
5. In the **Mappings** section, select the mapping that you want to configure a scoping filter for: for example, "Synchronize Azure Active Directory Users to ServiceNow".
87+
7. In the **Mappings** section, select the mapping that you want to configure a scoping filter for: for example, "Synchronize Azure Active Directory Users to ServiceNow".
8988
::: zone-end
9089

9190
::: zone pivot="cross-tenant-synchronization"
92-
5. In the **Mappings** section, select the mapping that you want to configure a scoping filter for: for example, "Provision Azure Active Directory Users".
91+
8. In the **Mappings** section, select the mapping that you want to configure a scoping filter for: for example, "Provision Azure Active Directory Users".
9392
::: zone-end
94-
95-
6. Select the **Source object scope** menu.
96-
97-
7. Select **Add scoping filter**.
98-
99-
8. Define a clause by selecting a source **Attribute Name**, an **Operator**, and an **Attribute Value** to match against. The following operators are supported:
93+
9. Select the **Source object scope** menu.
94+
10. Select **Add scoping filter**.
95+
11. Define a clause by selecting a source **Attribute Name**, an **Operator**, and an **Attribute Value** to match against. The following operators are supported:
10096

10197
a. **EQUALS**. Clause returns "true" if the evaluated attribute matches the input string value exactly (case sensitive).
10298

@@ -127,15 +123,15 @@ Scoping filters are configured as part of the attribute mappings for each Azure
127123
> - Filtering is not supported for multi-valued attributes.
128124
> - Scoping filters will return "false" if the value is null / empty.
129125
130-
9. Optionally, repeat steps 7-8 to add more scoping clauses.
126+
12. Optionally, repeat steps 7-8 to add more scoping clauses.
131127

132-
10. In **Scoping Filter Title**, add a name for your scoping filter.
128+
13. In **Scoping Filter Title**, add a name for your scoping filter.
133129

134-
11. Select **OK**.
130+
14. Select **OK**.
135131

136-
12. Select **OK** again on the **Scoping Filters** screen. Optionally, repeat steps 6-11 to add another scoping filter.
132+
15. Select **OK** again on the **Scoping Filters** screen. Optionally, repeat steps 6-11 to add another scoping filter.
137133

138-
13. Select **Save** on the **Attribute Mapping** screen.
134+
16. Select **Save** on the **Attribute Mapping** screen.
139135

140136
>[!IMPORTANT]
141137
> Saving a new scoping filter triggers a new full sync for the application, where all users in the source system are evaluated again against the new scoping filter. If a user in the application was previously in scope for provisioning, but falls out of scope, their account is disabled or deprovisioned in the application. To override this default behavior, refer to [Skip deletion for user accounts that go out of scope](../app-provisioning/skip-out-of-scope-deletions.md).

0 commit comments

Comments
 (0)