VDI Device Not Found (Windows 365)
A Windows 365 connection failure caused by a missing or misregistered Cloud PC state, with the investigation focused on sync, registration, and reprovisioning paths.
Overview
When attempting to connect to a Windows 365 Cloud PC, users may encounter the error "VDI device not found." This usually means the Cloud PC registration or access state is not aligned with the user session.
Problem Statement
Users were unable to connect to their Cloud PC and received "VDI device not found" during connection.
Symptoms
- The Windows 365 session failed before the desktop loaded.
- The error appeared consistently for the affected user or device.
- Account and sync state looked inconsistent in the access work or school area.
Environment
| Component | Value | Why it mattered |
|---|---|---|
| Endpoint | Windows 365 Cloud PC | The issue affected a Cloud PC connection path rather than a local workstation issue. |
| Management plane | Windows 365 + Intune | These services control registration and device state. |
| Recovery path | Sync, verify join state, reprovision if needed | Gives a clear sequence for isolating registration problems. |
Root Cause
The device or Cloud PC registration state was not aligned with the user account state, which caused the Windows 365 connection to fail before session launch.
Troubleshooting Steps
- Go to Settings > Accounts > Access work or school.
- Select the connected work or school account, then click Info.
- Click Sync, then restart the device to apply the changes.
Validation
- Confirm the Cloud PC launches normally after sync and restart.
- Recheck the registration and account state if the error returns.
Notes
If the steps above do not resolve the issue, the Cloud PC may need to be reprovisioned. Reprovisioning rebuilds the device and re-registers it in Azure AD and Intune.