Merge pull request #77276 from rolyon/rolyon-users-close-account-2

[Azure AD] [User groups roles] Close your work or school account in an unmanaged directory 2

Author: itechedit

articles/active-directory/users-groups-roles/TOC.yml

@@ -44,6 +44,8 @@
       href: /azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal?context=azure/active-directory/users-groups-roles/context/ugr-context
     - name: Restore a deleted user    
       href: /azure/active-directory/fundamentals/active-directory-users-restore?context=azure/active-directory/users-groups-roles/context/ugr-context
+    - name: Close your account in an unmanaged directory
+      href: users-close-account.md
     - name: Add B2B users  
       href: /azure/active-directory/b2b/what-is-b2b?context=azure/active-directory/users-groups-roles/context/ugr-context
     - name: Assign role to B2B user    

articles/active-directory/users-groups-roles/directory-self-service-signup.md

@@ -18,18 +18,18 @@ ms.custom: it-pro
 
 ms.collection: M365-identity-device-management
 ---
-# What is self-service signup for Azure Active Directory?
+# What is self-service sign-up for Azure Active Directory?
 
-This article explains how to use self-service signup to populate an organization in Azure Active Directory (Azure AD). If you want to take over a domain name from an unmanaged Azure AD organization, see [Take over an unmanaged directory as administrator](domains-admin-takeover.md).
+This article explains how to use self-service sign-up to populate an organization in Azure Active Directory (Azure AD). If you want to take over a domain name from an unmanaged Azure AD organization, see [Take over an unmanaged directory as administrator](domains-admin-takeover.md).
 
-## Why use self-service signup?
+## Why use self-service sign-up?
 * Get customers to services they want faster
 * Create email-based offers for a service
-* Create email-based signup flows that quickly allow users to create identities using their easy-to-remember work email aliases
+* Create email-based sign-up flows that quickly allow users to create identities using their easy-to-remember work email aliases
 * A self-service-created Azure AD directory can be turned into a managed directory that can be used for other services
 
 ## Terms and definitions
-* **Self-service signup**: This is the method by which a user signs up for a cloud service and has an identity automatically created for them in Azure AD based on their email domain.
+* **Self-service sign-up**: This is the method by which a user signs up for a cloud service and has an identity automatically created for them in Azure AD based on their email domain.
 * **Unmanaged Azure AD directory**: This is the directory where that identity is created. An unmanaged directory is a directory that has no global administrator.
 * **Email-verified user**: This is a type of user account in Azure AD. A user who has an identity created automatically after signing up for a self-service offer is known as an email-verified user. An email-verified user is a regular member of a directory tagged with creationmethod=EmailVerified.
 
@@ -43,31 +43,31 @@ Admins have two self-service controls today. They can control whether:
 An admin can configure these capabilities using the following Azure AD cmdlet Set-MsolCompanySettings parameters:
 
 * **AllowEmailVerifiedUsers** controls whether a user can create or join a directory. If you set that parameter to $false, no email-verified user can join the directory.
-* **AllowAdHocSubscriptions** controls the ability for users to perform self-service signup. If you set that parameter to $false, no user can perform self-service signup.
+* **AllowAdHocSubscriptions** controls the ability for users to perform self-service sign-up. If you set that parameter to $false, no user can perform self-service sign-up.
 
-AllowEmailVerifiedUsers and AllowAdHocSubscriptions are directory-wide settings that can be applied to an managed or an unmanaged directory. Here's an example where:
+AllowEmailVerifiedUsers and AllowAdHocSubscriptions are directory-wide settings that can be applied to a managed or unmanaged directory. Here's an example where:
 
 * You administer a directory with a verified domain such as contoso.com
 * You use B2B collaboration from a different directory to invite a user that does not already exist ([email protected]) in the home directory of contoso.com
 * The home directory has the AllowEmailVerifiedUsers turned on
 
 If the preceding conditions are true, then a member user is created in the home directory, and a B2B guest user is created in the inviting directory.
 
-Flow and PowerApps trial signups are not controlled by the **AllowAdHocSubscriptions** setting. For more information, see the following articles:
+Flow and PowerApps trial sign-ups are not controlled by the **AllowAdHocSubscriptions** setting. For more information, see the following articles:
 
 * [How can I prevent my existing users from starting to use Power BI?](https://support.office.com/article/Power-BI-in-your-Organization-d7941332-8aec-4e5e-87e8-92073ce73dc5#bkmk_preventjoining)
 * [Flow in your organization Q&A](https://docs.microsoft.com/flow/organization-q-and-a)
 
 ### How do the controls work together?
-These two parameters can be used in conjunction to define more precise control over self-service signup. For example, the following command will allow users to perform self-service signup, but only if those users already have an account in Azure AD (in other words, users who would need an email-verified account to be created first cannot perform self-service signup):
+These two parameters can be used in conjunction to define more precise control over self-service sign-up. For example, the following command will allow users to perform self-service sign-up, but only if those users already have an account in Azure AD (in other words, users who would need an email-verified account to be created first cannot perform self-service sign-up):
 
 ```powershell
     Set-MsolCompanySettings -AllowEmailVerifiedUsers $false -AllowAdHocSubscriptions $true
 ```
 
-The following flowchart explains the different combinations for these parameters and the resulting conditions for the directory and self-service signup.
+The following flowchart explains the different combinations for these parameters and the resulting conditions for the directory and self-service sign-up.
 
-![flowchart of self service sign-up controls](./media/directory-self-service-signup/SelfServiceSignUpControls.png)
+![flowchart of self-service sign-up controls](./media/directory-self-service-signup/SelfServiceSignUpControls.png)
 
 For more information and examples of how to use these parameters, see [Set-MsolCompanySettings](/powershell/module/msonline/set-msolcompanysettings?view=azureadps-1.0).
 
@@ -78,3 +78,4 @@ For more information and examples of how to use these parameters, see [Set-MsolC
 * [Azure PowerShell](/powershell/azure/overview)
 * [Azure Cmdlet Reference](/powershell/azure/get-started-azureps)
 * [Set-MsolCompanySettings](/powershell/module/msonline/set-msolcompanysettings?view=azureadps-1.0)
+* [Close your work or school account in an unmanaged directory](users-close-account.md)

articles/active-directory/users-groups-roles/media/users-close-account/close-account.png

@@ -0,0 +1,57 @@
+---
+title: Close your work or school account in an unmanaged directory - Azure Active Directory | Microsoft Docs
+description: How to close your work or school account in an unmanaged Azure Active Directory.
+services: active-directory
+author: rolyon
+manager: mtillman
+
+ms.service: active-directory
+ms.subservice: users-groups-roles
+ms.topic: article
+ms.workload: identity
+ms.date: 05/20/2019
+ms.author: rolyon
+ms.reviewer: 
+ms.custom: it-pro
+
+ms.collection: M365-identity-device-management
+---
+
+# Close your work or school account in an unmanaged directory
+
+If you are a user in an unmanaged Azure Active Directory (Azure AD) organization, and you no longer need to use apps from that organization or maintain any association with is, you can close your account at any time. An unmanaged directory does not have a Global administrator. Users in an unmanaged directory can close their accounts on their own, without having to contact an administrator.
+
+Users in an unmanaged directory are often created during self-service sign-up. An example might be an information worker in an organization who signs up for a free service. For more information about self-service sign-up, see [What is self-service sign-up for Azure Active Directory?](directory-self-service-signup.md).
+
+[!INCLUDE [GDPR-related guidance](../../../includes/gdpr-intro-sentence.md)]
+
+## Before you begin
+
+Before you can close your account, you should confirm the following items:
+
+* Make sure you are a user of an unmanaged Azure AD directory. You can't close your account if you belong to a managed directory. If you belong to a managed directory and want to close your account, you must contact your administrator. For information about how to determine whether you belong to an unmanaged directory, see [Delete the user from Unmanaged Tenant](https://docs.microsoft.com/flow/gdpr-dsr-delete#delete-the-user-from-unmanaged-tenant).
+
+* Save any data you want to keep. For information about how to submit an export request, see [Accessing and exporting system-generated logs for Unmanaged Tenants](https://docs.microsoft.com/power-platform/admin/powerapps-gdpr-dsr-guide-systemlogs#accessing-and-exporting-system-generated-logs-for-unmanaged-tenants).
+
+> [!WARNING]
+> Closing your account is irreversible. When you close your account, all personal data will be removed. You will no longer have access to your account and data associated with your account.
+
+## Close your account
+
+To close an unmanaged work or school account, follow these steps:
+
+1. Sign in to [close your account](https://go.microsoft.com/fwlink/?linkid=873123), using the account that you want to close.
+
+1. On **My data requests**, select **Close account**.
+
+    ![My data requests - Close account](./media/users-close-account/close-account.png)
+
+1. Review the confirmation message and then select **Yes**.
+
+    ![My data requests - Confirm close](./media/users-close-account/confirm-close.png)
+
+## Next steps
+
+- [What is self-service sign-up for Azure Active Directory?](directory-self-service-signup.md)
+- [Delete the user from Unmanaged Tenant](https://docs.microsoft.com/flow/gdpr-dsr-delete#delete-the-user-from-unmanaged-tenant)
+- [Accessing and exporting system-generated logs for Unmanaged Tenants](https://docs.microsoft.com/power-platform/admin/powerapps-gdpr-dsr-guide-systemlogs#accessing-and-exporting-system-generated-logs-for-unmanaged-tenants)