38483005

Author: ErikjeMS

windows-365/enterprise/known-issues-enterprise.md

@@ -6,7 +6,7 @@ f1.keywords:
 ms.author: erikje
 author: ErikjeMS
 manager: dougeby
-ms.date: 03/03/2022
+ms.date: 03/23/2022
 audience: Admin
 ms.topic: troubleshooting
 ms.service: cloudpc
@@ -40,10 +40,24 @@ A [resize](resize-cloud-pc.md) of a Cloud PC eliminates all existing [restore](r
 
 ## Windows doesn’t scan for software updates until the first time a user signs in<!--38212344-->
 
- While a Windows PC (physical or Cloud PC) sits idle before the first user signs in, Windows Update doesn’t scan for or install monthly quality patches. This means that the PC might miss important security updates. Without the latest security updates, the device is exposed to security vulnerabilities. 
+ While a Windows PC (physical or Cloud PC) sits idle before the first user signs in, Windows Update doesn’t scan for or install monthly quality patches. This means that the PC might miss important security updates. Without the latest security updates, the device is exposed to security vulnerabilities.
 
  **Troubleshooting steps**: Make sure that a user signs in to new Cloud PCs as soon as possible.
 
+## Windows 365 provisioning fails<!--38483005-->
+
+Windows 365 provisioning failures may occur because both:
+
+- the Desired State Configuration (DSC) extension isn't signed and
+- the PowerShell Execution policy is set to Allsigned in the Group Policy Object (GPO)
+
+**Troubleshooting steps**: Follow these steps:
+
+1. Did the on-premises network connection (OPNC) fail with the following error: ```"An internal error occurred. The virtual machine deployment timed out."```
+2. If yes, review the related GPO. Is PowerShell Execution set to AllSigned?
+3. If it is, either remove the GPO or reset the PowerShell Execution to RemoteSigned/ByPass.
+4. Retry the OPNC health check. If this succeeds, retry provisioning.
+
 ## Next steps
 
 [Troubleshoot Windows 365 Enterprise Cloud PC](troubleshooting.md)