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/external-identities/leave-the-organization.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ services: active-directory
7
7
ms.service: active-directory
8
8
ms.subservice: B2B
9
9
ms.topic: how-to
10
-
ms.date: 09/10/2021
10
+
ms.date: 03/21/2022
11
11
12
12
ms.author: mimart
13
13
author: msmimart
@@ -17,12 +17,16 @@ ms.reviewer: mal
17
17
ms.collection: M365-identity-device-management
18
18
---
19
19
20
-
# Leave an organization as a guest user
20
+
# Leave an organization as a B2B collaboration user
21
21
22
-
An Azure Active Directory (Azure AD) B2B guest user can decide to leave an organization at any time if they no longer need to use apps from that organization or maintain any association. A user can leave an organization on their own, without having to contact an administrator.
22
+
An Azure Active Directory (Azure AD) B2B collaboration user can decide to leave an organization at any time if they no longer need to use apps from that organization or maintain any association. A B2B collaboration user can leave an organization on their own, without having to contact an administrator.
23
+
24
+
-**B2B collaboration users** can leave external organizations they're collaborating with. However, you can't leave an organization if your B2B collaboration account is disabled (either in your home organization or in the external organization). If your account is disabled, contact the tenant admin so they can either delete your B2B collaboration account or enable it so you can leave the organization yourself.
25
+
26
+
-**B2B direct connect users** don't currently have the option to leave the external organization. If you're a B2B direct connect user at an organization, you can contact your IT admin to submit a Data Subject Request, which is a request to remove the personal data associated with your B2B direct connect user account from the organization.
> A guest user can't leave an organization if their account is disabled in either the home tenant or the resource tenant. If their account is disabled, the guest user will need to contact the tenant admin, who can either delete the guest account or enable the guest account so the user can leave the organization.
26
30
27
31
## Leave an organization
28
32
@@ -44,7 +48,7 @@ To leave an organization, follow these steps.
44
48
45
49
## Account removal
46
50
47
-
When a user leaves an organization, the user account is "soft deleted" in the directory. By default, the user object moves to the **Deleted users** area in Azure AD but isn't permanently deleted for 30 days. This soft deletion enables the administrator to restore the user account (including groups and permissions), if the user makes a request to restore the account within the 30-day period.
51
+
When a B2B collaboration user leaves an organization, the B2B collaboration user account is "soft deleted" in the directory. By default, the user object moves to the **Deleted users** area in Azure AD but isn't permanently deleted for 30 days. This soft deletion enables the administrator to restore the B2B collaboration user account (including groups and permissions), if the user makes a request to restore the account within the 30-day period.
48
52
49
53
If desired, a tenant administrator can permanently delete the account at any time during the 30-day period. To do this:
50
54
@@ -53,9 +57,7 @@ If desired, a tenant administrator can permanently delete the account at any tim
53
57
3. Select **Deleted users**.
54
58
4. Select the check box next to a deleted user, and then select **Delete permanently**.
55
59
56
-
If you permanently delete a user, this action is irrevocable.
0 commit comments