You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/windows-365/connection-error-interactive-window-not-shown.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,9 @@ ms.custom:
11
11
---
12
12
# Windows 365 Link connection fails with error "an interactive window could not be shown"
13
13
14
+
>[!NOTE]
15
+
>With the release of Windows 365 Link October Quality Update version 26100.6899, users should no longer encounter this error message for the reasons stated below. If such an error is encountered first check that Windows 365 Link is on version 26100.6899 or greater. For more information on updating the device, see [Windows 365 Link update behavior and control](/windows-365/link/update-behavior-control).
16
+
14
17
This article helps resolve the connection error "an interactive window could not be shown."
15
18
16
19
After you authenticate on the sign-in screen, you might encounter the following error message when connecting to your Cloud PC:
Copy file name to clipboardExpand all lines: support/windows-365/connection-fails-with-failed-to-open-a-microsoft-entra-id-credential-prompt.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,9 @@ ms.custom:
12
12
---
13
13
# Windows 365 Link connection fails with "Failed to open a Microsoft Entra ID credential prompt"
14
14
15
+
>[!NOTE]
16
+
>With the release of Windows 365 Link October Quality Update version 26100.6899, users should no longer encounter this error message for the reasons stated below. If such an error is encountered first check that Windows 365 Link is on version 26100.6899 or greater. For more information on updating the device, see [Windows 365 Link update behavior and control](/windows-365/link/update-behavior-control).
17
+
15
18
After a user authenticates on the sign-in page, when the user tries to connect to the Cloud PC, the user might encounter the following message:
Copy file name to clipboardExpand all lines: support/windows-365/known-issues-enterprise.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -179,6 +179,21 @@ Allow third-party cookies from `microsoft.us` in your Web client settings, Safar
179
179
180
180
This change lets the web client or Safari browser store and use the `microsoft.us` cookies to connect to your Cloud PC session.
181
181
182
+
## Windows 365 Authentication Issues in Government Environments Using Windows App on macOS
183
+
184
+
### Possible Cause
185
+
186
+
- 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**.
187
+
- **Web browser access** to Windows 365 remains unaffected.
188
+
- The Windows App on macOS does not properly detect the GCC High Windows 365 environment during discovery.
189
+
- Required workspace URL (`https://rdweb.wvd.azure.us/api/arm/feeddiscovery`) is not automatically identified during authentication.
190
+
- This is by design and requires to choose **Add workspace** instead of **Work or School Account** for government customers.
191
+
192
+
### Solution
193
+
- Instead of selecting **Add Account**, choose **Add Workspace**.
194
+
- Manually enter the following URL: `https://rdweb.wvd.azure.us/api/arm/feeddiscovery`.
195
+
- The Windows 365 devices should now be discovered and added.
196
+
182
197
## Windows Security reports "Memory Integrity is off. Your device may be vulnerable." <!--48643259-->
183
198
184
199
Windows Security reports "Memory Integrity is off. Your device may be vulnerable."
@@ -251,7 +266,7 @@ For newly provisioned Cloud PCs, verify that WebRTC is available. If it's not, y
251
266
252
267
- To add the WebRTC Redirector Service app to the list of apps to install by default onto Cloud PCs, follow the steps in [Add Microsoft 365 Apps to Windows 10/11 devices with Microsoft Intune](/mem/intune/apps/apps-add-office365).
253
268
254
-
- To add the WebRTC Redirector Service app to an individual Cloud PC, follow the steps in [Install the Remote Desktop WebRTC Redirector Service](/azure/virtual-desktop/teams-on-avd#install-the-remote-desktop-webrtc-redirector-service). To get the most up-to-date installer, use this link: [https://aka.ms/msrdcwebrtcsvc/msi](https://aka.ms/msrdcwebrtcsvc/msi).
269
+
- To add the WebRTC Redirector Service app to an individual Cloud PC, follow the steps in [Install the Remote Desktop WebRTC Redirector Service](/azure/virtual-desktop/teams-on-avd#install-the-remote-desktop-webrtc-redirector-service). To get the most up-to-date installer, use this link: [https://aka.ms/msrdcwebrtcsvc/msi](https://aka.ms/msrdcwebrtcsvc/msi).
0 commit comments