Windows 365 topics

MS designer is NOT WORKING!

dj0ker — Tue, 10 Mar 2026 10:10:21 GMT

It only makes 1 image not 4, it takes way too long time,. and it doesnt follow prompting,. and it makes imegs in 3:2 not 16:9... thsi has been goign on for over 2 weeks,... alsmot 3.. i have been in contact with support many times woith zero help.. HOW can you have a product in your office bunlde ant it not workign an zero supprot on it? I need teh application to make my videos,. im just abptu to cancel all subscritopons to micrposft an switch to apple..

Azure Default Outbound Access Changes: Guidance for Windows 365 ANC Customers

Kathryn_Jakubek — Wed, 11 Feb 2026 23:01:03 GMT

After March 31, 2026, newly created Azure Virtual Networks (VNets) will no longer have default outbound internet access enabled by default. Windows 365 customers choosing Azure Network Connection as a deployment option must configure outbound connectivity explicitly when setting up new VNets. This post explains what’s changing, who’s impacted, and the recommended actions, including Azure Private Subnets and Microsoft Hosted Network.

What is Default Outbound Access (DOA)?

Default Outbound Access is Azure’s legacy behavior that allowed all resources in a virtual network to reach the public internet without configuring a specific internet egress path. This allowed telemetry, Windows activation, and other service dependencies to reach external endpoints even when no explicit outbound connectivity method was configured.

What’s changing?

After March 31, 2026, as detailed in Azure’s communications, Azure will no longer enable DOA by default for new virtual networks, instead the VNet will be configured for Private Subnet option, allowing you to designate subnets without internet access for improved isolation and compliance. These changes encourage more intentional, secure network configurations while offering flexibility for different workload needs. Disabling Private Subnet option will allow administrators to restore DOA capabilities to the VNet, although Microsoft strongly recommends using Azure NAT Gateway.

Impact on Windows 365 Azure Network Connection Customers

For Windows 365 Azure Network Connection (ANC) deployments using virtual networks created after March 31, 2026, new VNets will default to private subnets. Outbound internet access must be explicitly configured for the VNet; otherwise, Cloud PC provisioning will fail. Existing virtual networks are not affected and will continue using their current internet access configuration.

Note on Microsoft-hosted network: For Microsoft-hosted network deployments, which is the Microsoft recommended deployment model for Windows 365, Microsoft fully provides and manages the underlying connectivity in Azure on your behalf. There is no impact or change needed for those deployments.

What You Should Do

To prepare for Azure’s Default Outbound Access changes and ensure your Windows 365 ANC deployments remain secure and functional:

Recommendations

Transition to Microsoft-hosted network (MHN) if possible. MHN provides secure, cost-effective connectivity with outbound internet access by default, reducing operational overhead and ensuring compliance with Azure’s updated standards.
Update deployment plans to ensure either an explicit NAT, such as a NAT Gateway or Default Outbound access (not recommended) is enabled by disabling the Private Subnet option.
Test connectivity to ensure all services dependent on outbound access continue to function as expected, and that the ANC does not enter a failed state.

Supported Outbound Access Methods

To maintain connectivity, choose one of these supported methods:

NAT Gateway (recommended)

Note: Direct RDP Shortpath (UDP over STUN) cannot be established through a NAT Gateway because its symmetric NAT policy prevents direct UDP connectivity over public networks.

Azure Standard Load Balancer

Azure Firewall or third-party Network Virtual Appliance (NVA). Note, it is not recommended to route RDP or other long-lived connections through Azure Firewall or any other network virtual appliance which allows for automatic scale-in. A direct method such as NAT Gateway should be used.

More information about the pros and cons for each method can be found at Default Outbound Access.

Resources:

Quick FAQ

Does this affect existing VNets? No. Only new VNets created after March 31, 2026, are affected. Existing VNets will continue to operate as normal.

Do Microsoft Hosted Network deployments require changes? No. MHN already includes managed egress.

What if I do nothing on a new VNet? ANC checks will fail because the VNet does not have internet access. Configure NAT Gateway or another supported method.

What are the required endpoints? Please see here for a list of the endpoints required.

Why might peer-to-peer connectivity using STUN-based UDP hole punching not work when using NAT Gateway? NAT Gateway uses a type of network address translation that does not support STUN (Simple Traversal Underneath NAT) based connections. This will prevent STUN-based UDP hole punching, commonly used for establishing peer-to-peer connections, from working as expected. If your application relies on reliable UDP connectivity between peers, STUN may revert to TURN (Traversal Using Relays around NAT) in some instances. TURN relays traffic between endpoints, ensuring consistent connectivity even when direct peer-to-peer paths are blocked. This helps maintain smooth real-time experiences for your users.

What explicit outbound options support STUN? Azure Standard Load Balancer supports UDP over STUN.

How do I configure Azure Firewall? For additional security you can configure Azure Firewall using these instructions https://learn.microsoft.com/en-us/azure/firewall/protect-azure-virtual-desktop?context=/azure/virtual-desktop/context/context

. It is strongly recommended that a direct method of access is used for RDP and other long-lived connections such as VPN or Secure Web Gateway tunnels. This is due to devices such as Azure firewall scaling in when load is low which can disrupt connectivity.

Wrap-up

Azure’s change reinforces intentional networking for better security. By planning explicit egress (or choosing MHN), Windows 365 ANC customers can stay compliant and keep Cloud PCs reliably connected.

OneNote - Location, Name, Resolving Backup (& Search dropdown)

roninkansas — Wed, 11 Feb 2026 17:46:53 GMT

I recently had a problem with the Search function in OneNote - where Search was not finding words in recently created Notes. And I fixed that problem, eventually, by deleting all of the files in the OneNote cache. But after that, when restarting OneNote, it came up Empty (with Errors). After jacking around with copying the old OneNote folder and renaming it, Opening Backups, etc. - I finally got my OneNote back up and working (sort of - see paragraph at the end).

My problem now is the "Info" is showing 2 Notebooks - "OneNote Notebooks 4" and "OneNote Notebooks 2" - and even worse, the location shown for Notebooks 4 is: https://onedrive.live.com/view.aspx?resid=562C6E59%21s0bcbd9618347485ca665bf8f3012d298&id=documents&end=()&end.

I created Notebooks 4 on the advice for another post to get things running again - but, WHERE AM I? - which Notebook am I using?

How do I get back to a single notebook at a reasonable location instead of the ridiculous link above.

I also have a question about the OneNote locations shown in the "Save & Backup" option - I don't understand a couple of things there.

[And a side note - even though OneNote Search is now working, the dropdown list is now showing the full path name for the Note location instead of the Page/Tab name for the location of the Note. Is there some option that I reset while trying to get OneNote working again.]

I obviously need help with this one - and am afraid to mess around experimenting since OneNote is back up and working well (except for the dropdown).

ron in shawnee

26 ноября

L_DM3 — Wed, 26 Nov 2025 17:13:00 GMT

Здравствуйте!
Хочу обратиться в службу поддержки с целью продвинуть компанию Microsoft. Дело в том, что мой друг сегодня активировал Windows, чему предшествовало огромное количество шуток на эту тему. Я создал google-форму, а точнее петицию, в которой призываю граждан любой страны утвердить 26 ноября как праздник "Активации Windows". Я бы хотел, чтобы вы рассмотрели мою идею и, как основная сторона, согласились на это, а также расширили этот опрос в больших кругах.
Прикрепляю ссылку на google-формы:
https://docs.google.com/forms/d/e/1FAIpQLSfrlFcap22IUJhrLBeRp4C8tAcxlGRY_AMPVqxcQJjwxPB4Tg/viewform?usp=publish-editor
С уважение, Дмитрий

Translation:

Hello!
I want to contact support in order to promote Microsoft. The thing is, my friend activated Windows today, which was preceded by a huge number of jokes about it. I created a Google form, or rather a petition, in which I urge citizens of any country to establish November 26 as "Windows Activation" Day. I would like you to consider my idea and, as the main party, agree to it, as well as help spread this survey more widely.
I am attaching the link to the Google form:
https://docs.google.com/forms/d/e/1FAIpQLSfrlFcap22IUJhrLBeRp4C8tAcxlGRY_AMPVqxcQJjwxPB4Tg/viewform?usp=publish-editor
Sincerely, Dmitry

Map only local drives and default printer from clients computer when logging into 365 Desktop?

tylderlurden — Mon, 24 Nov 2025 19:54:49 GMT

Hello, I have gone into Intune and created a new config profile and have set Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer Redirection \ Device and resource redirection to let the users map drives and printers that are on their laptop into Windows 365 Desktop.

However, how can we set it so that:

1. The only printers that are mapped to the 365 desktops from the client's device is the clients default printer and not any network printers that are installed on the laptop.

2. The only drives it maps into 365Desktop are the clients local drives like their SSD drive, and usb drives pluged in and not any network drives that are on the laptop.

Windows 365 Enterprise Cloud PC Connection Fails - VM Unavailable (Code 10012)

Pratishtha16 — Fri, 21 Nov 2025 15:13:50 GMT

We are facing a critical and persistent connection failure for a Windows 365 Enterprise Cloud PC that appears to be stuck in a state where the VM is not available to the RDP client.

Provisioning Policy Configuration:
- Cloud PC Type: Windows 365 Enterprise
- Experience: Access a full Cloud PC desktop
- Use Microsoft Entra single sign-on: Yes
- Join type: Microsoft Entra Join
- Geography: Canada
- Region: Automatic (Recommended)
- Network: Microsoft hosted network
- Current MDM -Microsoft Intune

Checked logs and found that the RDP client connection attempts consistently failing with same error, 
Disconnected: reason = 10012
[Telemetry :: Event] Type: RDPClient Details: DisconnectReason
Subdetails: SessionHostResourceNotAvailable Code: 10012

Troubleshooting steps taken so far:
- Restarted the Cloud PC.
- Initiated a Reprovision action.
- Tried web version but that didn't help either.

Since simple restarts and reprovisions have failed to resolve the SessionHostResourceNotAvailable (10012) error, the current VM instance is unusable. Any guidance on resolving this definitive Code 10012 error is highly appreciated.

Save the date: Windows 365 AMA - What’s new from Microsoft Ignite

Pearl-Angeles — Fri, 14 Nov 2025 00:05:17 GMT

Tune in on December 3 for a special Windows 365 AMA. Catch up on the latest capabilities for Windows 365 announced at Microsoft Ignite! Host Christian Montoya and members of the product team will answer your questions live and offer insights to help you configure, deploy, and manage Windows in the cloud with ease.

Save the date and post your questions early at aka.ms/Windows365AMA!

How to begin using Windows 365?

Ken_Ekholm — Fri, 07 Nov 2025 09:41:33 GMT

If I wan't to learn more about Windows 365 and Cloud PC, where is the best place to begin?
Are there any good links?

Microsoft Word - recover a document

Chris_X — Mon, 03 Nov 2025 12:36:25 GMT

Is this OK to post here re Microsoft Word? (I couldn't find a section for Word specifically).

I want to try and recover a situation with a Word doc... I think it is probably unrecoverable... but here goes.

Somehow... and i was typing fast and the screen froze so i cant be sure what happened...i deleted the contents of a word document and then save it.... so it is now blank... i do not have a backup of it...

Is there any way to roll it back or recover a cached version?

This happened an hour ago.

Many thanks!

Loss of apps after MS outage

Alamo44 — Fri, 10 Oct 2025 11:48:44 GMT

HI
Since the MS outage yesterday (9th October), although MS 365 Business Premium is licensed in Admin Portal and assigned to my one User, it does not appear in the User account, so I cannot access apps.
As a charity, we have a non-profit account.
Please help

Multimedia Redirection and WebRTC Redirector plug-in updates for Windows 365 & Azure Virtual Desktop

Donna_Ryan — Mon, 06 Oct 2025 14:59:22 GMT

Automating plug-in maintenance with GitHub Scripts

Keeping your Windows 365 and Azure Virtual Desktop environment up to date is crucial for optimal performance and security. Two essential plug-ins, Multimedia Redirection service and WebRTC (Web Real-Time Communication) redirector service, require periodic updates. However, these plug-ins do not update automatically, which can lead to compatibility or performance issues if left unattended.

Understanding the Challenge

Unlike most of the components of Windows 365 and Azure Virtual Desktop, both the Multimedia Redirection and WebRTC plug-ins must be updated manually. This manual process can be time-consuming for IT administrators and disruptive if not managed properly, especially in enterprise environments where user experience and uptime are top priorities.

Cloud PCs that are provisioned or reprovisioned with Gallery images do have the latest plug-ins installed and Azure Virtual Desktop session hosts deployed with Azure Marketplace images have the latest WebRTC plug-in installed. But as these Cloud PCs and Session Hosts age, these plug-ins will become outdated over time.

Note: Windows 365 Gallery images that include the latest Multimedia Redirection and WebRTC plug-ins are only the Windows Enterprise + Microsoft 365 Apps images. For Azure Marketplace images, only the Windows multi-session + Microsoft 365 Apps images include the latest WebRTC plug-in.

Features dependent on WebRTC and Multimedia Redirection

WebRTC: Microsoft Teams media optimizations

Users connect from non-Windows physical endpoints
Users connect from Windows endpoints and SlimCore fails

Multimedia Redirection: Video playback and call redirection on Edge or Chrome browsers

Users who visit websites with embedded videos
Users who use Contact Center as a Service (CCaaS) solutions

Manually Updating

Administrators can update these binaries by deploying their respective MSI installers to users’ Cloud PCs and personal Session Hosts either through Intune or their management engine of choice. This may be the simplest way of upgrading endpoints, but there is a chance that end users would be disrupted during their work because WebRTC installer will forcefully stop Teams processes while installing, and Multimedia Redirection could break video streams or calls while the binaries are upgraded. If choosing this method, administrators should leverage maintenance windows to minimize disruptions. The MSI installers can be manually downloaded from the links below:

Automating Updates with GitHub Scripts

To address this challenge, our team has developed a series of PowerShell scripts available in our GitHub repository. These scripts automate the update process for both Multimedia Redirection and WebRTC plug-ins, ensuring that the latest versions are installed without the need for direct user intervention. The benefits of these scripts are:

No End User Impact: The scripts are designed to run silently in the background, so end users experience no downtime or interruptions.
Consistent Plugin Versions: Automated updates help maintain consistency across all Windows 365 instances, reducing troubleshooting time and compatibility issues.
Easy Integration: The scripts can be deployed with Intune via Remediations, or as a standalone script. Remediations provides the best admin experience as it will report back on compliance and any errors encountered during deployment.

Getting Started

To begin using the automated update scripts:

Visit our GitHub repository and download the latest versions of the update scripts.
- WebRTC Updater
- Multimedia Redirector Updater
Review the step-by-step setup and configuration instructions.
Deploy the scripts to your Windows 365 or Azure Virtual Desktop environment, either in standalone mode or with Remediations.

IMPORTANT: The scripts currently do not support Windows Multi-Session hosts.

Updating Azure Virtual Desktop Multi-Session Hosts

Updating these plugins should be done during the build process of the golden image or the Session Hosts. This can be achieved by using an automated building solution, like Azure Image Builder, to install the latest versions. The URLs for these plugins are static, meaning that administrators can use the same URL without having to be concerned about the version that is being downloaded. For reference, the URLs are below:

WebRTC - https://aka.ms/msrdcwebrtcsvc/msi
Multimedia Redirection - https://aka.ms/avdmmr/msi

More information on WebRTC and Multimedia Redirection plug-ins

Microsoft updates these binaries periodically for functional and security enhancements. To stay current on the latest releases and what they contain, please visit the following links:

Conclusion

Regularly updating the Multimedia Redirection and WebRTC plugins is essential for a secure and efficient Windows 365 environment. By leveraging the automation scripts from our GitHub repository, IT administrators can ensure plugins remain current, all while eliminating manual effort and minimizing any impact on end users. For more details and to access the scripts, check out our GitHub page.

Windows 365 Watermarking - QR Codes Missing in Screenshots/Teams from Within Session?

Durrante — Mon, 22 Sep 2025 10:01:23 GMT

Hi all,

I've implemented watermarking on our Windows 365 setup using the official Microsoft guide, and I'm seeing behaviour that I'd like to confirm is expected.

Current Situation:

Watermarking is enabled and working (QR codes appear when I screenshot from my local client PC)
However, when taking screenshots FROM WITHIN the Cloud PC session itself, no QR codes appear
Similarly, when screen sharing via Teams from within the Cloud PC session, participants don't see the QR codes

My Question: Is this the intended behaviour? Should QR codes only appear when capturing externally (from the client device) but not when capturing internally (from within the Windows 365 session itself)?

I've read through the Microsoft documentation but can't find explicit clarification on whether internal screenshots should show watermarks or if the protection is specifically designed for external capture attempts.

Can anyone confirm this behaviour or point me to official documentation that explains the internal vs external capture distinction?

Thanks in advance!

Microphone & camera passthrough to Cloud PC from MacBook

apollon — Thu, 11 Sep 2025 16:20:21 GMT

I have a M1 MacBook Pro that I use to connect to my Cloud PC for work via the Microsoft App.

I try to use the Teams app installed locally on the Cloud PC for making and accepting calls but I am having a lot of audio issues. First of all, the person I am calling sounds very tinny (kinda like a chipmunk!) and they cannot hear me. Video doesn't seem to work properly either. I have had very little luck with my external webcam (some Logitech one, don't actually know the model but I don't think it makes a difference? but it has a microphone). There has the very odd few times that a call is working fine but then after a few seconds or so, or when I start sharing my screen on the Cloud PC after a minute of the call starting, I start to experience the same issues with audio as explained above.

I am running Sequoia 15.6, the Mac Windows App is version 11.1.5 (2585). Admittedly I've mostly tried in clamshell mode and connected to external earphones (AirPods Pro).

I used to use my earphones via the Citrix app on VDI with no issues previously.

Any solutions would be gratefully received.

Thank you

Windows App on Mac "Send feedback" link not found

jschuster — Thu, 21 Aug 2025 19:58:04 GMT

I went to file feedback on the Windows App for Mac, and the link it opened (https://techcommunity.microsoft.com/t5/forums/postpage/board-id/AzureVirtualDesktop) was not found. Is this the right place to file feedback?

Enable FIDO Token (RSA DS100) passthrough to W365 Machine via Windows App

britestonedev — Fri, 08 Aug 2025 04:02:31 GMT

Hi There,

Working with Enterprise license, trying to establish the approach to allow FIDO Token, specifically the RSA DS100, to redirect from the Host device. The users can only connect via the Windows application, not via the RDP client.

I have the Device Class/Driver ID of the token.

It is key that removable storage is not enabled as a result of this, for obvious reasons. Ideally the allowance would be scoped to only include the token.

Thanks in advance.

What is one must-have intune policy you always deploy to windows 365 Cloud PCs ?

Tovar — Thu, 07 Aug 2025 12:24:24 GMT

I'm getting deeper into managing Windows 365 Cloud PCs with intune and I'm trying to build out a solid baseline for policy deployment. I know there's a lot that can be configured via intune, from security baselines to user experience tweaks.

Do you use for hardening security, streamlining login times, restricting certains apps, enabling Bitlocker or enforcing windows updates ? Have you had any conflict with other policies ? Does it differ from what you push to physical endpionts ?

365 stuck at "Setting Up" after license reassignment, is there a way to force reprovisioning?

Barlow — Thu, 07 Aug 2025 11:45:23 GMT

I am fairly new to managing Windows 365, and I've run into an issue that seems like it should have a simple fix, but hasn't been so straightforward in practice.

I have a 365 Business cloud PC under one user (admin). After testing a few things, I removed the license from that user and reassigned it to a new employee. The portal now shows " Setting up Cloud Pc" for that user, and it's been stuck there for several hours with no sign of progress.

I have tried :

Unassigned and reassigned the license again.
Restarted the cloud PC from the portal ( though it's not active).

is there a way to manually trigger or force reprovisioning of the Cloud PC after a license reassignment ?

Getting Started with Windows 365 Benefits, Use Cases, and Setup Guide

JohnNaguib — Thu, 24 Jul 2025 14:26:19 GMT

In today’s hybrid work environment, flexibility, security, and scalability are more critical than ever. Windows 365, Microsoft’s Cloud PC solution, addresses these demands by bringing the Windows experience to the cloud — enabling users to securely access their personalized desktop from any device, anywhere. Whether you’re an enterprise IT architect, an SMB owner, or an individual professional, Windows 365 has a lot to offer.

Let’s dive into the key benefits, common use cases, and how you can get started with Windows 365.

https://dellenny.com/getting-started-with-windows-365-benefits-use-cases-and-setup-guide/

Cannot Access Windows Hardware Developer Program in Partner Center — How to Sign Drivers in 2025?

ykryvosheiev — Mon, 07 Jul 2025 12:58:44 GMT

Hi all,

I'm trying to sign a Windows driver and need access to the Microsoft Windows Hardware Developer Program.

**What I'm trying to achieve:**
- Sign a driver for Windows using the standard Microsoft hardware signing process.

**The issue:**
- When I try to register for the Windows Hardware Developer Program, I get a message saying "Hardware Program is already in Active state".
- However, when I go to Programs > Settings in Microsoft Partner Center, the Hardware Developer Program is NOT visible/available.
- I have Global Admin permissions, and I’ve also tried using an account with Owner permissions — no difference, the Hardware Program is missing from the list.

**My question:**
- How do I get access to the Windows Hardware Developer Program if it's "Active" but not visible in the Partner Center?
- Is there any way to manage or join the Hardware Program in 2025 if it's not listed?
- Is there an alternative process for signing Windows drivers now? Any up-to-date guidance for 2025 would be super helpful.

Any advice or escalation contacts would be highly appreciated!

Thanks in advance.

Expanded TURN relay regions for Windows 365 and Azure Virtual Desktop

Rinku_Dalwani — Mon, 10 Nov 2025 20:11:02 GMT

We’re excited to share that the rollout of expanded TURN relay regions for Windows 365 and Azure Virtual Desktop is now complete. TURN relay is available in all regions listed below. This new range—51.5.0.0/16—enhances RDP Shortpath connectivity and delivers faster, more reliable performance for Azure Virtual Desktop and Windows 365 users in 39 regions worldwide.

What is TURN?

TURN (Traversal Using Relays around NAT) enables devices behind firewalls to establish reliable UDP connections. With RDP Shortpath for public networks, TURN acts as a fallback when a direct UDP-based connection isn’t possible—ensuring low-latency, high-reliability remote desktop sessions.

This new TURN relay range is part of the ‘WindowsVirtualDesktop’ service tag in Azure, making it easier for you to manage access and security configurations at scale.

Benefits of the new TURN relay

This change isn’t just a technical update—it’s a regional expansion. We’re scaling from 14 to 39 regions globally, bringing the TURN relay infrastructure closer to users, reducing latency, and improving connection reliability. Combined with a dedicated IP range for Azure Virtual Desktop and Windows 365 traffic, this initiative offers you more control, optimized routing, and a higher success rate for UDP-based communications. Here are the benefits in more detail:

Expanding regional coverage

By expanding from 14 to 39 regions globally, organizations will benefit from:

Lower latency: Data travels shorter distances, resulting in faster connections and reduced lag.
Improved reliability: Fewer dropped connections and more stable sessions, especially for real-time applications.
Higher UDP success rates: Better performance for voice, video, and real-time data—even under variable network conditions.

Dedicated IP Range for Azure Virtual Desktop and Windows 365 traffic

This rollout introduces a dedicated IP range tailored for Azure Virtual Desktop and Windows 365 traffic, distinct from the ACS TURN relay. Benefits of this improvement include:

Optimized traffic flow for Azure Virtual Desktop and Windows 365.
Improved control over network security configurations.
Customers can navigate restrictive security setups without compromising performance.
Enhanced quality and speed for traffic, free from generic filtering

Supported regions

Here is a list of supported regions with the new TURN relay. A TURN relay is selected based on the physical endpoints, not the Cloud PC or session host. For example, a user physically located in the UK will use a relay in the UK South or the UK West regions. If the user is far from a supported region, the connection may fall back to TCP, potentially impacting performance. For example, a user physically located in the UK will use a relay in the UK South or the UK West regions. If the client is far from a supported region, the connection may fall back to TCP, potentially impacting performance.

Accessible

Your environment should have this subnet accessible from all networks used for Windows 365 or Azure Virtual Desktop connectivity, both on the physical network and cloud side. For Microsoft Hosted Network deployments in Windows 365 this underlying connectivity is already in place. For Azure Virtual Desktop and Windows 365 – Azure network connection ANC deployments, the ‘WindowsVirtualDesktop’ service tag contains this subnet so connectivity may already be in place.

Optimized

The subnet should also be optimized to ensure this critical, latency sensitive traffic has the most performant path available, this means:

No TLS inspection on the traffic. This traffic is TLS encrypted transport with a nested TLS encrypted tunnel. TLS inspection yields no benefit but carries high risk of performance and reliability impact and puts significant additional load on the inspecting device.
Locally egressed, meaning traffic is sent to Microsoft via the most direct and efficient path. In Azure this means directly routed onto Microsoft’ backbone and for customer side networks, directly to the internet where it will be picked up by Microsoft’s infrastructure locally.
Bypassed from VPN, Proxy and Secure Web Gateway (SWG) tunnels and sent directly to the service as demonstrated in the example here.
On the Cloud side this may involve using a User Defined Route (UDR) to send the Windows Virtual Desktop traffic direct to ‘internet’ instead of traversing a virtual firewall as can be seen in the example here.

Learn more

To learn more about RDP Shortpath and how to configure it for public networks, see our documentation on RDP Shortpath for Azure Virtual Desktop.