Skip to content

Commit 63eb647

Browse files
Update provision-on-demand.md
1 parent d7d34a5 commit 63eb647

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/active-directory/app-provisioning/provision-on-demand.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -163,9 +163,12 @@ There are currently a few known limitations to on-demand provisioning. Post your
163163
::: zone pivot="app-provisioning"
164164
> [!NOTE]
165165
> The following limitations are specific to the on-demand provisioning capability. For information about whether an application supports provisioning groups, deletions, or other capabilities, check the tutorial for that application.
166-
* On-demand provisioning supports provisioning one user at a time through the Microsoft Entra portal.
167166
* On-demand provisioning of groups supports updating up to five members at a time. Connectors for cross-tenant synchronization, Workday, etc. do not support group provisioning and as a result do not support on-demand provisioning of groups.
168167
::: zone-end
168+
::: zone pivot="cross-tenant-synchronization"
169+
* On-demand provisioning of groups is not supported for cross-tenant synchronization.
170+
* ::: zone-end
171+
* On-demand provisioning supports provisioning one user at a time through the Microsoft Entra portal.
169172
* Restoring a previously soft-deleted user in the target tenant with on-demand provisioning isn't supported. If you try to soft-delete a user with on-demand provisioning and then restore the user, it can result in duplicate users.
170173
* On-demand provisioning of roles isn't supported.
171174
* On-demand provisioning supports disabling users that have been unassigned from the application. However, it doesn't support disabling or deleting users that have been disabled or deleted from Azure AD. Those users don't appear when you search for a user.

0 commit comments

Comments
 (0)