Merge pull request #8552 from ChristianMontoya/patch-2

Removing references to "email" since we don't do that

Author: prmerger-automator[bot]

windows-365/enterprise/provisioning.md

@@ -42,8 +42,8 @@ Admins need only provide a few configuration details to set up the provisioning
 At a high level, the full provisioning process looks like this:
 
 1. You [create a provisioning policy](create-provisioning-policy.md) to manage who gets access to Cloud PCs. The provisioning policies are the engines that build, configure, and make Cloud PCs available to end users. Within a policy, you’ll provide details for the network, the [image](device-images.md) used to create each Cloud PC, and an Azure Active Directory (Azure AD) user group.
-2. When a user in the Azure AD user group is assigned a Windows 365 license, Windows 365 automatically provisions a Cloud PC and sends access information to the user. This automation has three stages, which are invisible to the administrator. For more information on this automated process, see the [Details of the automated provisioning process article](automated-provisioning-steps.md).
-3. The end user receives the access information and can then sign in to the Windows Cloud PC from anywhere.
+2. When a user in the Azure AD user group is assigned a Windows 365 license, Windows 365 automatically provisions a Cloud PC for the user. This automation has three stages, which are invisible to the administrator. For more information on this automated process, see the [Details of the automated provisioning process article](automated-provisioning-steps.md).
+3. Once provisioned, the end user can then sign in to the Windows Cloud PC from anywhere.
 
 ## Provisioning policy objects