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: src/content/docs/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser.mdx
+12-18Lines changed: 12 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Users can connect to an RDP server without installing an RDP client or the [WARP
14
14
15
15
There are two ways for users to [reach the RDP server in their browser](#4-connect-as-a-user):
16
16
-**App Launcher (recommended)**: Users can log in to the [Access App Launcher](/cloudflare-one/applications/app-launcher/) with their Cloudflare Access credentials and then initiate an RDP connection within the browser to their Windows machine. Users will authenticate to the Windows machine using their pre-configured Windows username and password. Cloudflare does not manage any credentials on the Windows server.
17
-
-**Direct URL**: A user may also navigate directly to the Windows server at `https://<app-domain>/rdp/<vnet-id>/<target-ip>/<port>`. The authentication flow is the same as for the App Launcher; first users must log in to Cloudflare Access and then use their Windows credentials to authenticate to the Windows machine. To learn more about virtual networks, see [this entry](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/).
17
+
-**Direct URL**: A user may also navigate directly to the Windows server at `https://<app-domain>/rdp/<vnet-id>/<target-ip>/<port>`, where `vnet-id` is the <GlossaryTooltipterm="Virtual network">virtual network</GlossaryTooltip> assigned to the Cloudflare Tunnel route. The authentication flow is the same as for the App Launcher; first users must log in to Cloudflare Access and then use their Windows credentials to authenticate to the Windows machine.
18
18
19
19
Browser-based RDP can be used in conjunction with [routing over WARP](/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-warp-to-tunnel/) so that there are multiple ways to connect to the server. You can reuse the same Cloudflare Tunnel when configuring each connection method.
20
20
@@ -144,20 +144,14 @@ To connect to a Windows machine over RDP:
144
144
145
145
The App Launcher tile will launch a URL of the form `https://<app-domain>/rdp/<vnet-id>/<target-ip>/<port>`. You may also navigate directly to this URL.
146
146
147
-
:::note
148
-
`Vnet-id`stands for virtual network identifier. [Virtual networks](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/) (VNET) allow you to connect private networks that have overlapping IP ranges without creating conflicts for users or services.
147
+
:::note[Virtual network ID]
148
+
`vnet-id`refers to the [virtual network](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/) (VNET) that the RDP target is assigned to in your Cloudflare Tunnel configuration. If you did not specify a VNET when routing the target through Cloudflare Tunnel, the target is automatically added to the default VNET.
149
149
150
-
Your organization may not use virtual networks and so all targets will be added to the default VNET automatically.
151
-
152
-
To find the default VNET, you can use [this API endpoint](https://developers.cloudflare.com/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/) to list all virtual networks in your organization. Obtain your default `Vnet-id` by looking for the virtual network with "is_default_network": true.
150
+
To fetch a list of all VNETs and their IDs, make a `GET` request to the [List Virtual Networks](/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/) endpoint. The default VNET will have the parameter `"is_default_network": true`.
153
151
:::
154
152
4. Select the port that you want to connect to. The port selection screen only appears if the Access application allows RDP traffic on multiple ports (for example, port `3389` and port `65321`).
155
153
5. (Optional) In your browser settings, allow the Access application to access the clipboard. Clipboard permissions grant the ability to copy or paste text between the local machine and the remote Windows machine.
156
-
6. Enter your Windows username and password. For more information on supported login credentials, refer to [User identifier formats](#user-identifier-formats).
157
-
158
-
:::note
159
-
Please see [below](#microsoft-entra-id) if you wish to access a Microsoft Entra ID-bound RDP server for further instructions on how to format your username.
160
-
:::
154
+
6. Enter your Windows username and password. For more information on how to format your username, refer to [User identifier formats](#user-identifier-formats).
161
155
162
156
You now have access to the remote Windows desktop.
163
157
@@ -189,7 +183,7 @@ Browser-based RDP supports connecting to Windows machines that run the following
189
183
190
184
### Powershell
191
185
192
-
Please ensure you are running Powershell 7 to mitigate a prior Microsoft issue where keystrokes are not recorded.
186
+
Run Powershell 7 or higher to mitigate a prior Microsoft issue where keystrokes are not recorded.
193
187
194
188
### User identifier formats
195
189
@@ -228,12 +222,13 @@ Cloudflare will not configure user identifiers on the RDP target. Any user ident
228
222
229
223
#### Microsoft Entra ID
230
224
231
-
User identifiers that are bound to Microsoft Entra ID domains must enter their username as AzureAD\[email protected] or as AzureAD\user. The AzureAD\ prefix is case-insensitive.
225
+
User identifiers that are bound to Microsoft Entra ID domains must enter their username as `AzureAD\[email protected]` or `AzureAD\user`. The `AzureAD\` prefix is case-insensitive.
226
+
227
+
The login flow differs slightly when using an Microsoft Entra ID-bound username:
232
228
233
-
The login flow differs slightly when using an Microsoft Entra ID-bound username.
234
229
1. Enter your username in one of the formats outlined above.
235
-
2. Once the username is entered, the password box will disappear, and the RDP connection will initiate.
236
-
3. The RDP server will then prompt for the password before granting you access to your RDP server.
230
+
2. Once the username is entered, the password box will disappear and the RDP connection will initiate.
231
+
3. The RDP server will then prompt for the password before granting access to the RDP server.
237
232
238
233
### Cloudflare products
239
234
@@ -244,7 +239,6 @@ The login flow differs slightly when using an Microsoft Entra ID-bound username.
244
239
-**TLS certificate verification**: Cloudflare uses TLS to connect to the RDP target but does not verify the origin TLS certificate.
245
240
-**WARP authentication**: Since browser-based RDP traffic does not go through the WARP client, users cannot use their [WARP session identity](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-sessions/#configure-warp-sessions-in-access) to authenticate.
246
241
-**Audio over RDP**: Users cannot use their microphone and speaker to interact with the remote machine.
247
-
-**Clipboard size limit**: Data copied to/from your local machine or your browser-based RDP session may not exceed 500 KB.
242
+
-**Clipboard size limit**: Data copied between the local machine and the browser-based RDP session may not exceed 500 KB.
248
243
-**Clipboard controls**: Admins do not have the ability to restrict copy/paste actions between the remote machine and the user's local clipboard.
249
244
-**File transfers**: Users cannot copy/paste files from their local machine to the remote machine and vice versa.
0 commit comments