Skip to content

Commit 00c7f37

Browse files
committed
Move delete configuration to Troubleshooting tips
1 parent 7f3f7d4 commit 00c7f37

File tree

1 file changed

+20
-16
lines changed

1 file changed

+20
-16
lines changed

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-configure.md

Lines changed: 20 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -406,22 +406,6 @@ Even though users are being provisioned in the target tenant, they still might b
406406

407407
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).
408408

409-
## Delete a configuration application
410-
411-
![Icon for the source tenant.](./media/common/icon-tenant-source.png)<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-
425409
## Troubleshooting tips
426410

427411
#### Symptom - Test connection fails with AzureDirectoryB2BManagementPolicyCheckFailure
@@ -470,6 +454,26 @@ Restoring a previously soft-deleted user in the target tenant isn't supported.
470454

471455
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).
472456

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+
473477
## Next steps
474478

475479
- [Tutorial: Reporting on automatic user account provisioning](../app-provisioning/check-status-user-account-provisioning.md)

0 commit comments

Comments
 (0)