Windows 365 Enterprise known issues
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/SupportArticles-docs · commit 947701d · +22 −12 lines · also on GitHub
⋯ 45 unchanged lines
4646
Find and manage the Cloud PC in Microsoft Intune by using the unchanged Intune device name, either through the **Devices** > **All devices** list or the **Devices** > **Windows 365** > **All Cloud PCs** list.
4747
4848
## Windows 365 provisioning fails<!--38483005-->
49
−
50
−Windows 365 provisioning might fail if both of the following conditions are met:
51
−
52
−- The Desired State Configuration (DSC) extension isn't signed.
53
−- The PowerShell Execution policy is set to **AllSigned** in the GPO.
54
−
55
−### Solution
56
−
57
−1. Check if the Azure network connection (ANC) fails with the error "An internal error occurred. The virtual machine deployment timed out." If yes, review the related GPO.
58
−1. Check if the PowerShell Execution policy is set to **AllSigned**. If it is, either remove the GPO or reset the PowerShell Execution policy to **Unrestricted**.
59
−1. Retry the ANC health check. If the check succeeds, retry provisioning.
60
−
49
+
50
+ Windows 365 provisioning might fail if the Desired State Configuration (DSC) extension is used and the PowerShell
51
+ execution policy is set to **AllSigned** through Group Policy.
52
+
53
+ Windows 365 sets the PowerShell execution policy to `RemoteSigned` at the `LocalMachine` scope during provisioning.
54
+ This policy allows locally created scripts and scripts run through the Custom Script Extension (CSE), while requiring
55
+ downloaded scripts to be digitally signed. If a customer-configured GPO sets the execution policy to `AllSigned` at the
56
+ `MachinePolicy` scope, it overrides the default configuration and blocks unsigned scripts.
57
+
58
+ You might see either of the following errors:
59
+
60
+ - **Custom Script Extension authorization manager validation failed.** Script execution was blocked by an authorization
61
+ manager validation failure in the Custom Script Extension.
62
+ - "An internal error occurred. The virtual machine deployment timed out."
63
+
64
+ ### Solution
65
+
66
+ 1. Ensure that the execution policy and App Control for Business policies allow required scripts to run.
67
+ 1. Review any applied GPOs that set the PowerShell execution policy to **AllSigned**.
68
+ 1. Remove the GPO or change the policy to **RemoteSigned**.
69
+ 1. Retry the ANC health check. If the check succeeds, retry provisioning.
70
+
6171
## Cloud PC reports as not compliant with the compliance policy
6272
6373
The following device compliance settings report as **Not applicable** when being evaluated for a Cloud PC:
⋯ 296 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/SupportArticles-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 00:39 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.