Windows 365 Enterprise known issues

This page's changes and edits · All guidance changes

Microsoft's edit · 13 Nov 2025 22:22 UTC

Acrolinx fixes

Microsoft's commit message in MicrosoftDocs/SupportArticles-docs · commit cc7a283 · +10 −8 lines · also on GitHub

⋯ 181 unchanged lines

182182

183183 ## Windows 365 Authentication Issues in Government Environments Using Windows App on macOS

184184

185 +- Government customers (GCC, GCC High) using **Windows 365** on macOS might encounter authentication failures when adding a **Work or School Account** via the **Windows App**.

186 +- **Web browser access** to Windows 365 remains unaffected.

187 +- The Windows App on macOS doesn't properly detect the GCC High Windows 365 environment during discovery.

188 +- Required workspace URL (`https://rdweb.wvd.azure.us/api/arm/feeddiscovery`) isn't automatically identified during authentication.

189 +

185190 ### Possible Cause

186191

187 −- Government customers (GCC, GCC High) using **Windows 365** on macOS may encounter authentication failures when adding a **Work or School Account** via the **Windows App**.

188 −- **Web browser access** to Windows 365 remains unaffected.

189 −- The Windows App on macOS does not properly detect the GCC High Windows 365 environment during discovery.

190 −- Required workspace URL (`https://rdweb.wvd.azure.us/api/arm/feeddiscovery`) is not automatically identified during authentication.

191 −- This is by design and requires to choose **Add workspace** instead of **Work or School Account** for government customers.

192 +This behavior is by design and requires to choose **Add workspace** instead of **Work or School Account** for government customers.

192193

193194 ### Solution

194 −- Instead of selecting **Add Account**, choose **Add Workspace**.

195 +

196 +- Instead of selecting **Add Account**, select **Add Workspace**.

195197 - Manually enter the following URL: `https://rdweb.wvd.azure.us/api/arm/feeddiscovery`.

196198 - The Windows 365 devices should now be discovered and added.

197199

⋯ 125 unchanged lines

323325

324326 ### Autopilot Device Preparation (DPP) initially shows as failed if timeout limit is reached

325327

326 −Once you create the provisioning policy and you receive the error code `DevicePreparationProfileTimeout`, then the time-out limit has been reached and the Cloud PCs are provisioned without applying the Autopilot Device Preparation successfully.

328 +Once you create the provisioning policy and you receive the error code `DevicePreparationProfileTimeout`, then the timeout limit has been reached and the Cloud PCs are provisioned without applying the Autopilot Device Preparation successfully.

327329

328330 #### Solution

329331

⋯ 1 unchanged line

331333

332334 ### Cloud PC serial numbers don't show immediately in Windows Autopilot Device Preparation deployment status

333335

334 −When monitoring the status of the Autopilot Device Preparation profile immediately after provisioning, the Cloud PC serial numbers are not available.

336 +When monitoring the status of the Autopilot Device Preparation profile immediately after provisioning, the Cloud PC serial numbers aren't available.

335337

336338 #### Solution

337339

⋯ 5 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.