Merge pull request #4596 from kev-out/patch-1

Update troubleshoot-windows-365-boot.md

windows-365/enterprise/troubleshoot-windows-365-boot.md

@@ -40,8 +40,14 @@ If the user can't access the Cloud PC from the Windows 365 Boot physical device,
 1. Check to see if you can sign in to the Cloud PC from either:
     - The browser at windows365.microsoft.com.
     - The Windows 365 app on another (non-Windows 365 Boot) device.
-2. If you can log into the Cloud PC from either method, then there's an issue with the Windows 365 Boot physical device. In this case, confirm that the physical device is correctly configured and has the requisite software versions. For more information, see [Windows 365 Boot physical device requirements](windows-365-boot-physical-device-requirements.md).
-3. Admins can try to manually click on **Device sync** to get the policies delivered faster on the device. Users can try to restart the device.
+2. If a user has more than one Cloud PC, make sure they have selected a default Cloud PC to use each time they sign in. To set this default:
+   - Navigate to https://windows365.microsoft.com.
+   - In the card for the Cloud PC you want to set as default, select the ellipses (...) > Settings.
+   - In the **Integrated experiences** tab, under **Boot to this Cloud PC**, select **Connect while signed into device**.
+   - Select **Save**.
+3. If you can sign into the Cloud PC from the app or web, and a default Cloud PC has been set, then there's an issue with the Windows 365 Boot physical device. In this case, confirm that the physical device is correctly configured and has the requisite software versions. For more information, see [Windows 365 Boot physical device requirements](windows-365-boot-physical-device-requirements.md).
+4. Admins can try to manually click on **Device sync** to get the policies delivered faster on the device. Users can try to restart the device.
+
 
 ## Physical device registry key configuration