You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-configure.md
+20-16Lines changed: 20 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -406,22 +406,6 @@ Even though users are being provisioned in the target tenant, they still might b
406
406
407
407
This setting also applies to B2B collaboration and B2B direct connect, so if you set **External user leave settings** to **No**, B2B collaboration users and B2B direct connect users can't leave your organization themselves. For more information, see [Leave an organization as an external user](../external-identities/leave-the-organization.md#more-information-for-administrators).
408
408
409
-
## Delete a configuration application
410
-
411
-
<br/>**Source tenant**
412
-
413
-
If you no longer need to synchronize users, you can stop provisioning and delete the configuration application in the source tenant. Currently, you must delete the configuration in Enterprise applications.
414
-
415
-
1. In the source tenant, select **Azure Active Directory** > **Enterprise applications**.
416
-
417
-
1. In the list of all applications, find the name of your configuration. If necessary, you can search by the configuration name.
418
-
419
-
1. Select the configuration and then select **Properties**.
420
-
421
-
1. Select **Delete** and then **Yes** to delete the configuration.
422
-
423
-
:::image type="content" source="./media/cross-tenant-synchronization-configure/enterprise-applications-configuration-delete.png" alt-text="Screenshot of the Enterprise applications Properties page showing how to delete a configuration." lightbox="./media/cross-tenant-synchronization-configure/enterprise-applications-configuration-delete.png":::
424
-
425
409
## Troubleshooting tips
426
410
427
411
#### Symptom - Test connection fails with AzureDirectoryB2BManagementPolicyCheckFailure
@@ -470,6 +454,26 @@ Restoring a previously soft-deleted user in the target tenant isn't supported.
470
454
471
455
Manually restore the soft-deleted user in the target tenant. For more information, see [Restore or remove a recently deleted user using Azure Active Directory](../fundamentals/active-directory-users-restore.md).
472
456
457
+
#### Symptom - Unable to delete a configuration application
458
+
459
+
On the **Configurations** page, there isn't a way to delete a configuration application.
460
+
461
+
**Cause**
462
+
463
+
Currently, there isn't a way to delete a configuration on the **Configurations** page. Instead, you must delete the configuration in **Enterprise applications**.
464
+
465
+
**Solution**
466
+
467
+
1. In the source tenant, select **Azure Active Directory** > **Enterprise applications**.
468
+
469
+
1. In the list of all applications, find the name of your configuration. If necessary, you can search by the configuration name.
470
+
471
+
1. Select the configuration and then select **Properties**.
472
+
473
+
1. Select **Delete** and then **Yes** to delete the configuration.
474
+
475
+
:::image type="content" source="./media/cross-tenant-synchronization-configure/enterprise-applications-configuration-delete.png" alt-text="Screenshot of the Enterprise applications Properties page showing how to delete a configuration." lightbox="./media/cross-tenant-synchronization-configure/enterprise-applications-configuration-delete.png":::
476
+
473
477
## Next steps
474
478
475
479
-[Tutorial: Reporting on automatic user account provisioning](../app-provisioning/check-status-user-account-provisioning.md)
0 commit comments