Pinned Posts
Forum Widgets
Latest Discussions
Optimizing RDP Connectivity for Windows 365
Updated with RDP & Zscaler connectivity improvements August 2025 The use of VPN or Secure Web Gateway (SWG) client software or agents to provide tunneled access to on-premises resources in addition to providing protected internet access via a cloud based Secure Web Gateway (SWG) or a legacy VPN & on-premises proxy path is very commonly seen in Windows 365 and AVD deployments. This is especially the case when deployed in the recommended Windows 365 with Microsoft Hosted Network (MHN) model where the Cloud PC is located on a network with direct, open high-speed internet available. The more modern, cloud based SWG solutions fit perfectly with this modern Zero-Trust approach and generally perform at a higher level than traditional VPN software, where internet browsing is hairpinned through on-premises proxies and back out to the internet. As we have many Windows 365 customers using such solutions as part of their deployment, there are some specific configuration guidelines which are outlined in this post which Microsoft recommends are applied to optimize key traffic and provide the highest levels of user experience. What is the Problem? Many of these VPN/SWG solutions build a tunnel in the user context, which means that when a user logs in to their device, the service starts and creates the tunnels required to provide both internet and private access as defined for that user. With a physical device the tunnel is normally up and running before or shortly after the user sees their desktop on screen, meaning they can then quickly get on with their work without noticing its presence. However, as with any virtualized device which needs a remote connection to access, the above model poses several challenges: 1. Additional Latency Firstly, the remote desktop traffic is latency sensitive, in that delay to the traffic reaching its destination can easily translate into a poor user experience, with lag on actions and desktop display. Routing this traffic through a tunnel to an intermediary device to reach its destination adds latency and can restrict throughput regardless of how well configured or performing said device is. Modern SWG solutions tend to perform at a much higher levels than a traditional VPN/Proxy approach, but the highest level of experience is always achieved through a direct connection and avoiding any inspection or intermediary devices. Much like Teams media traffic, the RDP traffic in the Windows 365 case should be routed via the most optimal path between the two endpoints so as to deliver the very highest levels of performance, this is almost always the direct path via the nearest network egress. From a Cloud PC side this also means the traffic never leaves Microsoft’s managed network if directly egressed. 2. RDP Connection Drops An additional challenge comes from the use of user-based tunnels. As the user initiates a connection to the Cloud PC, the connection reaches the session host without issue and the user successfully sees the initial logon screen. However, once the user login starts, and the client software then builds the tunnels to the SWG/VPN for the user, the user then experiences a freeze of the login screen. The connection then drops, and we have to go through the reconnection process to re-establish the connection to the Cloud PC. Once this is complete, the user can successfully use the Cloud PC without further issue. Users however may also experience disconnects of the remote session if there is any issue with the tunnel, for example if the tunnel temporarily drops for some reason. Overall, this doesn’t provide a great user experience with the Cloud PC, especially on initial login. Why does this occur? It occurs because the tunnels built to route internet traffic to the SWG generally capture all internet bound traffic unless configured not to do so, a forced tunnel or ‘Inverse split tunnel’. This means the initial login works without issue but as soon as this tunnel is established upon user logon, the RDP traffic gets transferred into it and as it’s a new path, requires reconnecting. Equally, as the traffic is inside this tunnel, if the tunnel drops momentarily and needs to reconnect, this also causes the RDP session to require reconnecting inside the re-established tunnel. In the diagram below, you can see a simplified representation of this indirect connectivity approach with a forced tunnel in place. RDP traffic has to traverse the VPN/SWG resources before hitting the gateway handling the traffic. Whilst this is not a problem for less sensitive traffic and general web browsing, for latency critical traffic such as Teams and the RDP traffic, it is non-optimal. What’s the Solution? Microsoft strongly recommends implementing a forced tunnel exception for the critical RDP traffic which means that it does not enter the tunnel to the SWG or VPN gateway and is instead directly routed to its destination. This solves both of the above problems by providing a direct path for the RDP traffic and also ensuring it isn’t impacted by changes in the tunnel state. This is the same model as used by specific ‘Optimize’ marked Office 365 traffic such as Teams media traffic. On the Cloud PC side this also means this traffic never leaves Microsoft’s managed network. What exactly do I need to bypass from these tunnels? Previously, solving this problem meant significant complexity due to the large number of IP addresses required to configure optimization for this RDP traffic, we provided a script as part of this blog to assist with collecting and formatting these IPs. I'm pleased to share that Microsoft has invested in an extensive and complex piece of work to solve this challenge by building a new, upgraded global gateway infrastructure to allow it to be addressed from a single subnet. In addition to that simplification that we have planned so that this subnet should not see any regular change, abstracting customers from change as we scale the infrastructure and add new regions in future. As of February 2025, this work has now been completed and the old infrastructure decommissioned, this was all completed with zero downtime for our customers. This now allows RDP based traffic to now be covered by two single subnets rather than many hundred as previously was the case. There are further improvement works due to be delivered in the coming months for UDP based RDP to provide new dedicated and globally scaled TURN infrastructure. This post will be updated when this is complete and RDP connectivity is therefore in its final and complete, simplified and secured state. These temporary elements are: The WindowsVirtualDesktop service tag Is now up to date as of 19th March 2025 with all decommissioned IPs removed. 2. UDP based RDP via TURN now exclusively uses 51.5.0.0/16 as of August 2025. The new, dedicated subnet is in the WindowsVirtualDesktop service tag. More on this can be found in this post. This work will also vastly expand our global TURN relay availability. RDP based Connectivity bypass: As of August 2025, the critical traffic which carries RDP is contained within the following simplified endpoints: RDP Endpoints for Optimization Row Endpoint Protocol Port Purpose 1 *.wvd.microsoft.com TCP 443 Core TCP based RDP and other critical service traffic 2 40.64.144.0/20 TCP 443 Core TCP based RDP 3 51.5.0.0/16 UDP 3478 Core UDP based RDP via TURN Please see this article for more information on row 3 In some network equipment/software we can configure bypass using FQDNs and wildcard FQDNs alone, and we’d recommend that this method (row 1) is used in addition to the IP based rules if possible. However, some solutions do not allow the use of wildcard FQDNs so it’s common to see only IP addresses used for this bypass configuration. In this case you can use the newly simplified rows 2 & 3 in the table above, making sure row 1 is still accessible via the SWG/Proxy. There are also a small number of other endpoints which should be bypassed on the Cloud PC side: Other required VPN/SWG bypass requirements: Other endpoints for Optimization Row Endpoint Protocol Port Purpose 4 azkms.core.windows.net TCP 1688 Azure KMS - Traffic Needs to arrive from Azure public IPs 5 169.254.169.254 TCP 80 Azure Fabric communication 6 168.63.129.16 TCP 80 Azure Fabric communication These additional bypass requirements (4-6) are not RDP related but are required for the following reasons: Row 4 – This is Azure KMS activation which is a required endpoint for a Cloud PC and AVD Session Hosts. The traffic for this needs to arrive from an Azure public IP, if not then the connection will not be successful. Therefore it should not be sent via a 3 rd party internet egress such as via an SWG or proxy. IP addresses corresponding to the FQDN can be found via the link above if required. Rows 5 & 6 – These are critical IP addresses used to communicate to the Azure Fabric to operate the VM. We need to ensure these are not inadvertently sent in any VPN/SWG tunnel where they will not be then able to reach their destination in Azure. How do I implement the RDP bypass in common VPN/SWG solutions? Microsoft is working with several partners in this space to provide bespoke guidance and we’ll add detailed guidance for other solutions here as we get them confirmed. Already available however is Zscaler ZIA. Zscaler Client Connector The changes outlined above should make configuration in all scenarios vastly simpler moving forward. Due to some fantastic work to assist our mutual customers by our friends at Zscaler, as of February 2025 and version 4.3.2 of the Zscaler Client Connector, the majority of the mentioned Windows 365 and AVD traffic which requires optimization, including RDP can be bypassed with a single click configuration within a predefined IP based bypass! Zscaler ZIA Configuration Version 4.3.2 (Released Feb 2025) of the Zscaler Connector Client portal enables this feature. Ensure a recent version of the Client Connector is installed on both the Cloud PC (And Physical device if Zscaler is used there) to take advantage. In the Zscaler Client Connector Portal, select the new IP-Based, Predefined Application Bypass for Windows 365 & Azure Virtual Desktop. This contains preconfigured bypass for RDP and KMS traffic. 3. Add the following endpoints to the bypass configuration manually as they are not included in the automatic bypass. Endpoint Protocol Port Purpose 169.254.169.254 TCP 80 Azure Fabric communication 168.63.129.16 TCP 80 Azure Fabric communication Other VPN/SWG solutions Microsoft is currently working with other partners in this space to provide detailed guidance for other VPN/SWG solutions and will list them here as they are complete. Please let us know in the comments if you’d like us to list a particular solution and we’ll aim to prioritize based on feedback. In the interim, use rows 1-6 in the tables above to create manual bypasses from VPN/SWG/Proxy tunnels. This should be significantly simpler and have much lower change rates than previously due to the IP consolidation. FAQs: Q: In a Microsoft Hosted Network deployment, is there anything else I need to do? A: Unless the local Windows firewall is configured to block access to the endpoints noted, there should be nothing else required, the network the virtual NIC sits in has direct, high speed connectivity Microsoft’s backbone and the internet. Q: In an Azure Network Connection scenario, is there anything further I need to do? A: In this scenario, the recommended path for the traffic is directly out of the VNet into Microsoft’s backbone. Depending on the configuration it may require allowing the endpoints noted in this article through a firewall or NSG. The WindowsVirtualDesktop service tag or FQDN tag may help with automating rules in firewalls or configuring User Defined Routing. RDP traffic specifically should be sent direct into Microsoft’s backbone via a NAT Gateway or similar with no TLS inspection, avoiding putting load on NVAs such as Firewalls. Q: Do I need to configure the bypass on just the Cloud PC? A: RDP connectivity (Rows 1-3) is used identically on both the physical and cloud sides. It is strongly advised that the bypass is applied to both the Cloud PC and the connecting client if that also uses the SWG/VPN to connect. If both are using the same configuration profile then this should happen automatically. Rows 4-6 are only required on the cloud side. Q: How often do the IP addresses Change? A: Now the improvement work is complete we don’t anticipate regular change. You can monitor the WindowsVirtualDesktop service tag for changes if desired and we’re working on getting these requirements into the M365 Web Service longer term for monitoring and automation. Q: Can I add more than the RDP traffic to the bypass. A: Microsoft only provides IP addresses for the RDP connectivity at present. However if your solution is capable of configuration by FQDN alone, then you can add other service endpoints to your optimized path, these can be found on this Microsoft docs page. Q: Im using a true split tunnel, does this impact me? A: The above advice is for a forced tunnel scenario (inverse split tunnel) where the default path is via the tunnel and only defined exceptions are sent direct, which is often referred to as a split tunnel in common parlance and is the most commonly seen deployment model of such solutions. However a split tunnel in the technically accurate sense of the words, where the default path is the internet and only defined endpoints (such as corp server ranges/names) are sent down the tunnel, shouldn’t need such configuration as the RDP traffic should follow the default path to the internet. Q: Does this also optimize RDP shortpath? A: RDP Shortpath for Public Networks works to provide a UDP based RDP connection between the client and Cloud PC if enabled and achievable. This connection is in addition to the TCP based connection described above and the dynamic virtual channels such as graphics, input etc are switched into the UDP connection if deemed optimal. Row 3 above covers this traffic for connectivity via TURN relays. Please see this article for more information on this connectivity model. Q: Is this advice also shared in Microsoft’s official documentation? A: We’re currently working on uplifting the entire connectivity documentation for Windows 365 and the above will form part of this work in the coming months. We’ll share the official link in this blog when available. Q: Does this advice apply equally to AVD? A: Yes, both Windows 365 and AVD have exactly the same requirements in terms of the connectivity discussed in this blog.How To Learn about Windows 365 Cloud PC in 2022 to jumpstart your implementation
With the increased demand and interest in Windows 365 Cloud PC, this might be a good moment to summarize all the resources available online that can help ramp you up on the technical and business aspects to get started. " With Windows 365, we’re bringing the operating system to the cloud and creating a new category: the cloud PC, providing organizations with greater flexibility and a secure way to empower their workforce, regardless of location.” – Satya Nadella, CEO of Microsoft Let’s get started and show you all the resources that are freely available on the internet to kick the tires with Windows 365 Cloud PC as part of your journey to SaaS-based Cloud PCs. Microsoft certification course Learning about Windows 365 will soon be something you can get rewarded on as well. We are working on an official Modern Desktop Administrator. You can already follow the instructor-led training courses to get trained on Windows 365 today! Stay tuned, more news coming soon! Microsoft 365 Certified: Modern Desktop Administrator Associate - Learn | Microsoft Docs What's new in Windows 365 Learn what new features are available in Windows 365. What's new in Windows 365 Enterprise | Microsoft Docs Windows 365 for Partners Grow your Microsoft 365 cloud services business with Windows 365, the following resources will help you establish maximum benefit from the Microsoft cloud as a Partner. Windows 365 Official Partner Portal Page Windows 365 Partner FAQ Windows 365 Partner PowerPoint deck Windows 365 Official Training material Windows 365 Product Brochure Technical deployment guide Upcoming partner (free) sales training March 31, 2022, 8:00-9:00 AM, Pacific time Register here: https://aka.ms/W365Salestraining1 April 5, 2022, 5:00-6:00 PM, Pacific time Register here: https://aka.ms/W365Salestraining2 April 7, 2022, 8:00-9:00 AM, Pacific time Register here: https://aka.ms/w365technicaltraining1 April 12, 2022, 5:00-6:00 PM, Pacific time Register here: https://aka.ms/w365technicaltraining2 Windows 365 PowerPoint presentations We know like no other that content is sometimes more important than the technology itself to share the benefits for business before starting a proof-of-concept implementation. Therefore, we made our official Microsoft presentation material publicly available for anyone. L100 overview deck of Windows 365 Enterprise L100 overview deck of Windows 365 Business Windows 365 Business vs Enterprise comparison deck L300 technical deep-dive deck of Windows 365 Enterprise Paperback book: Mastering Microsoft Endpoint Manager and Windows 365 One of the main reasons for the slow adoption of Modern Workplace solutions designed to simplify the management layer of your environment is the lack of understanding and knowledge of the product. With this book, you'll learn everything you need to know to make the shift to Modern Workplace, running Windows 10, Windows 11, or Windows 365. You can order it here: Amazon.com: Mastering Microsoft Endpoint Manager: Deploy and manage Windows 10, Windows 11, and Windows 365 on both physical and cloud PCs: 9781801078993: Brinkhoff, Christiaan, Larsen, Per, Pan, Ken, Manchester, Scott: Books Windows in the Cloud – YouTube webcast series This free live Microsoft Teams webcast series highlights new features, best practices from both Microsoft Engineering and the community, and Windows 365 success stories. We hope you’ll join us right here as we explore technology-focused topics alongside members of the community, Microsoft Engineering, customers, and users. Episode 6: Windows 365 Enterprise and Azure AD join support with Christian Montoya Episode 5: Monitoring, endpoint analytics, and alerting for Windows 365 with Navnith Ramkrishnan Episode 4: Windows 365 Business deep dive with Joydeep Mukherjee Episode 3: Learn from the Experts – MVPs with MVP Anoop Nair Episode 2: Windows 365 at Microsoft Ignite with Scott Manchester Episode 1: Welcome to the Show with Jen Gentleman Demo bytes Create Windows 365 Enterprise Azure AD Join Cloud PCs on your own network How to use the Windows 365 Web Portal the best way possible How to make your Windows 365 Cloud PC users a local administrator How to proactively monitor your Windows 365 Cloud PCs with Endpoint Analytics Windows 365 Business – deep dive technical walkthrough Windows 365 Business is a version of Windows 365 made specifically for use in smaller companies (up to 300 seats). It offers an easy, streamlined way of providing Cloud PCs to your users. Learn in this blog how to configure it. Get started with Windows 365 Business - Microsoft Tech Community Windows 365 Enterprise – deep dive technical walkthrough Find out what you need to know to jump into this new service and make it even easier for your users to connect to Windows running in the Microsoft cloud. Learn in this blog how to configure it. Get started with Windows 365 Enterprise - Microsoft Tech Community How to configure Windows 365 Enterprise Azure AD join (mindcore.dk) Universal Print, Defender, and OneDrive with Windows 365 Learn about how to use Windows 365 with other Microsoft 365 Cloud services such as Universal Print and Defender! Get started with Universal Print and Windows 365 Cloud PC - Microsoft Tech Community Learn how to configure Microsoft Defender for Endpoint for your Windows 365 cloud PCs and physical endpoints via Microsoft Endpoint Manager Learn how to exclude files and extensions in Windows 365 cloud PCs from syncing in to OneDrive via both GPOs and Microsoft Endpoint Manager Linkedin Learning – Deploy, Provision and Manage Windows 365 Cloud PCs by Brian Posey Learn more about how to configure and enable supporting infrastructure in Azure to create a virtual remote network. Get the skills you need to deploy a secure, manageable network, setting up your organization for success. Brian shows you why Windows 365 is so appealing, as it combines the simplicity of the PC with the security and power of the cloud. Welcome to Windows 365 | Linkedin Learning (linkedin.com) Puralsight online training – Windows 365 In this course, Windows 365 Cloud PC, we explore the value of Windows 365 and walk through accessing your cloud PC from both a browser and through an app called Remote Desktop. Windows 365 Cloud PC | Pluralsight Microsoft Endpoint Manager: Windows Autopilot, Windows 365 | Pluralsight Ask Microsoft Anything – Windows 365 New series! Join us every month with your questions about Windows 365 features, deployment, customization, and best practices. During these one-hour Ask Microsoft Anything (AMA) events, we'll have members of the Microsoft engineering and product teams ready to help and provide answers. Not sure where to start? Watch our Windows in the Cloud web series to catch up on the latest. Upcoming AMAs: Ask Microsoft Anything: Windows 365 - February 2022 Ask Microsoft Anything: Windows 365 - March 2022 Ask Microsoft Anything: Windows 365 - April 2022 Ask Microsoft Anything: Windows 365 - May 2022 Ask Microsoft Anything: Windows 365 - June 2022 Microsoft Mechanics Watch as Microsoft engineers show you how to get the most from the software, service, and hardware they built. Through in-product demos, recommendations, how-to's, and tips, they simplify complex topics so you can share them with clients, peers, and your management team. Windows 365, your Cloud PC | What it is, how it works, and how to set it up - YouTube Windows 365 admin setup and management tutorial for Cloud PCs - YouTube Microsoft Docs Official product documentation for Windows 365 Business Windows 365 Enterprise documentation | Microsoft Docs Windows 365 Business documentation | Microsoft Docs Windows 365 Feedback portal Share your ideas for future features and functionality for Windows 365—and vote on your favorites! Windows 365 feature requests - Microsoft Tech Community Windows 365 Roadmap To help in your readiness and planning, this page lists Windows 365 updates and features that are in development but not yet released. In development - Windows 365 Enterprise | Microsoft Docs Become a Microsoft MVP for Windows 365 Do you aspire to be a Microsoft Most Valuable Professional (MVP) for Windows 365? We just announced our new program. If you're interested in becoming an MVP, please reach out to me on social media! Join our Windows 365 Community – led by MVPs! We are a group of EUC, Enterprise Mobility and Azure specialists, sharing their knowledge actively with the wider virtual desktop communities. Our community is open to everyone, and several Microsoft MVPs will keep you posted every week on the latest news and announcements of Windows 365! Welcome to the brand new Windows 365 Community! - Windows 365 Community (w365community.com)Initial ISV solutions for Windows 365
Today we announced Windows 365, a cloud service that introduces a new way to experience Windows 10 or Windows 11. Windows 365 takes the operating system to the Microsoft cloud, streaming the full Windows experience—including your apps, content, and settings—to any device. Windows 365 also creates a new hybrid personal computing category called cloud PC, which uses both the power of the cloud and the capabilities of the device to provide a full, personalized Windows experience. As Partner Director with over 20 years of experience at Microsoft, I've worked on many projects and built many different products and services. For the last two years I've been leading the team of engineers to develop Windows 365. Through the process, I've spoken with customers, relied on the inputs of colleagues and applied all my industry knowledge to build this solution. I'm excited about the many features and capabilities we've put into Windows 365. Although we've built an end-to-end solution with Windows 365, we know that our partners are always able to find new ways to expand and extend Microsoft services. To support our partners, extensibility via Graph APIs is a core design principle of Windows 365. Over the last 12 months, we began working with four different ISVs during a private service preview. These companies were chosen because of the consistent innovations they've developed and because of their own unique perspectives. We gave them an overview of our product strategy, provided access to the preview service and Graph APIs, and then watched them get to work. Here's a look at the four ISVs and what they've built: Nerdio Nerdio provides deployment, management, and optimization services that simplify Azure deployments and empower Managed Services Providers and IT Professionals to be successful with Windows 365. Microsoft has worked closely with Nerdio to expand their Nerdio Manager for MSP and Nerdio Manager for Enterprise products to make it even easier for MSPs and IT professionals to deploy and manage Windows 365 with ease. With Nerdio, MSPs and enterprises of all sizes can facilitate the pricing, design, deployment, and management of cloud PCs from a central console. MSPs and enterprise organizations can use Nerdio Manager to roll out Windows 365 environments to individual customers or across multiple tenants. UKG UKG is a leading global provider of Human Capital Management (HCM), payroll, HR service delivery, and workforce management solutions that help companies create great work experiences for all employees. UKG has now expanded their signature UKG Pro solution to make the process of delivering Windows 365 to employees even simpler. Through the service, when HR enters the new hire's information in UKG Pro, a workflow is launched that results in a fully provisioned cloud PC delivered directly to the employee. Similarly, when employees leave the company and their credentials are revoked, UKG Pro and Windows 365 return that cloud PC to inventory, ready for the next person. ServiceNow ServiceNow enables organizations to create digital workflows that optimize how business gets done. Working with Microsoft, the ServiceNow team has integrated Windows 365 and Microsoft Teams with their ServiceNow IT Service Management (ITSM) solution. Through this integration, end users themselves can request cloud PCs through the familiar interface of Microsoft Teams. The platform automates the workflow to collect the necessary approvals, provision the machines, and deliver the cloud PCs to the end users. Through this automation, IT saves time and end users get access to the resources they need, all through a system that provides regular status updates. NetApp NetApp is a Microsoft Partner that gives managed services providers (MSPs) the tools they need to provision, deploy, manage, and troubleshoot virtual infrastructure. Spot PC by NetApp gives MSPs a powerful, single-pane-of-glass through which they can manage Windows 365 instances. This software as a service (SaaS) offering blends the power of Windows 365 with NetApp's enterprise-class infrastructure management so that MSPs can deliver highly available, scalable, and performant cloud PCs that meet their clients' needs—in minutes. MSPs can manage their entire customer base of cloud PCs through a single partner dashboard with full multi-tenant security, from which they can drill down into any given tenant to correct performance issues, troubleshoot problems, and allocate new cloud PC instances. Excitement for what's to come I'm excited about the great work these partners have done. They've helped Windows 365 integrate with popular tools and solutions to meet customers where they are. Now that we've launched Windows 365, the same Graph APIs used by these partners are available to everyone. You can find these resources here on Microsoft Docs. I look forward to seeing the next set of services that will be built by our partner ecosystem.
Windows 365'e ve yeni Bulut PC'nize hoş geldiniz (tr-TR)
Windows işletim sistemi ailesinin yeni üyesini Microsoft bulutuna taşıyan hizmetini geçtiğimiz hafta tanıtıldığını duyurdu. Sizlere Windows 365 ve bunun için oluşturulan yeni teknoloji ile tanıştırmak isterim. Windows 365, uygulamaları, içerikleri ve ayarları dahil olmak üzere son kullanıcılara, herhangi bir cihaza eksiksiz, kişiselleştirilmiş Windows deneyimi aktarır. Geleneksel sanal masaüstü altyapısının (VDI) aksine bunu, fiziksel PC'leri dağıtmak ve yönetmek için halihazırda kullandığınız beceri ve araçlardan yararlanarak, kullanıcı başına aylık bir fiyatla sahip olabilirsiniz. Windows 365, Microsoft 365 ile tamamen tümleşik bir Windows 10 veya Windows 11 (genel kullanıma sunulduğunda) kişiselleştirilmiş bir masaüstü deneyimi sunar. Windows 365, son kullanıcı deneyimi ve yönetici deneyimindeki geleneksel çözümlerden belirgin bir şekilde farklı olduğu için Bulut PC dediğimiz yeni bir hibrit kişisel bilgi işlem çözümü sunar. Bu hizmet için belirlenen kriter, kullanıcıların geleneksel PC'lerle sahip olduğu deneyime ve yöneticilerin bugün kullandığı yönetim deneyimine ve araçlarından esinlenilmiş. Windows 365 Enterprise, uç nokta yöneticilerinin bugün geleneksel bilgisayarlarla kullandıkları iş akışlarını ve araçları kullanarak Bulut bilgisayarları yönetmesini sağlamak için Microsoft Endpoint Manager üzerine kurulmuştur. Windows 365 Business, arka uç altyapısına gerek olmadığından ve yerel Azure Active Directory (Azure AD) Join'i desteklediğinden sanallaştırmadan yararlanmanız için yeni bir fırsat sunar. Bu, genel giderleri önemli ölçüde azaltır ve en küçük kuruluşlara ölçeklenebilen uygun maliyetli çözümler sağlar. Önümüzdeki haftalarda, bugün fiziksel bilgisayarlar için kullandığınız becerileri ve teknikleri kullanarak hem Windows 365 web portalından hem de doğrudan Microsoft Endpoint Manager yönetim merkezinden Bulut PC'leri nasıl dağıtabileceğinizi anlatacağım. Ayrıca, İnternet'e nasıl bağlı olduklarından bağımsız olarak son kullanıcılara benzersiz ağ performansı ve güvenliği sağlamak için Azure ağının nasıl hızlı bir şekilde kurulacağına ilişkin yönergeleri de paylaşacağız. Yeni Watchdog hizmetimizde size yol göstereceğiz ve kurulum, sorun giderme ve sorun uyarılarını nasıl büyük ölçüde basitleştirdiğini göstereceğim. Ayrıca, Endpoint analytics ile entegrasyonun, tıpkı fiziksel PC'lerde olduğu gibi Bulut PC'lerinizde de size nasıl eyleme geçirilebilir öngörüler sağladığını göstereceğim. Ve bu sadece başlangıç. Öyleyse başlayalım. Hepsi Windows 365 ve Bulut PC'leri daha iyi anlamanıza yardımcı olmak için Microsoft Mechanics serisinin yeni videosu olan “ Windows 365, your Cloud PC | What it is, how it works, and how to set it up “ isimli videoyu youtubedan izleminizi öneririm. Son kullanıcı yönetiminde ve kullnımında bir devrim niteliği taşıyacağını düşündüğüm Windows 365 oyunun kurallarını fazlasıyla değiştireceğini düşünüyorum. Önümüzdeki aylarda ve yıllarda bunu sizlerle paylaşıyor olacağım. Windows 365'e ve yeni Bulut PC'nize hoş geldiniz : )365 stuck at "Setting Up" after license reassignment, is there a way to force reprovisioning?
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 ?Application Deployment in Windows 365 – Recommended Practices
(This post was jointly written with Aleksandar Bozadzhiev) Overview As more companies are using Windows 365 to enable their employees, reduce their costs, or reimagine how to provide a managed Windows experience, we’re hearing some consistent feedback. A common challenge we hear is “How can I ensure that all my required applications are installed before my users can access their Cloud PCs?” Common statements we’ve heard include: “I need to ensure all security tools are installed before users can logon to reduce risk.” “I need to ensure my people are immediately productive when they 1 st logon.” This article will provide some recommended approaches to help you meet this need; providing both technical and process recommendations. Technical Recommendations Use Intune to assign applications to devices rather than users. By targeting devices you can better ensure your applications get installed as soon as possible. When a Cloud PC is provisioned, it immediately is enrolled with Intune. After enrollment, the Cloud PC will sync with Intune to determine what applications, policies and profiles are required for the device. Assigning to user groups will result in the Intune sync occurring after the user 1 st logs, potentially delaying the installation of required apps for several minutes after logon. Additionally, using Configuration Manager or a third-party solution to install applications will result in additional delays, as Intune will need to install the 3 rd party agent/client, which will then do its own scan/sync to determine what needs to install on the Cloud PC. Of course, there may be exceptions where applications are more appropriate to be targeted to users rather than devices; such as software that has specific license requirements, or applications require a user to be logged on to perform the installation. Use “All Devices” group and device filters (rather than dynamic groups) Our Windows 365 documentation provides details on how to use both dynamic groups and device filters for targeting applications. The challenge with using Azure AD dynamic groups is that a newly provisioned Cloud PC may not be in a dynamic group for some time, potentially for several minutes up to several hours. This is due to the nature of how dynamic groups are processed and synced to Intune. When a Cloud PC is provisioned and enrolled into Intune, the following actions occur: A device object in both Azure AD and Intune are created. Azure AD Dynamic group membership is periodically calculated for new members. Dynamic group membership is synced with Intune. The Cloud PC checks-in with Intune to determine what applications, policies, and profiles are applicable. The above actions occur sequentially and run on a periodic schedule which results in a potentially significant delay in installing applications. Using the “All devices” Intune virtual group and device filters when assigning applications will result in your applications being installed as fast as possible. Why? Device filters are evaluated by Intune immediately upon enrollment and the All Devices Intune group does not require any synchronization activity. Device filters that can be used with Cloud PCs include: All Cloud PCs All Cloud PCs within a specific provisioning policy All Cloud PCs with a specific configuration Also, note that if you’d like to use an Enrollment Status Page (ESP), a device filter that represents a specific provisioning policy is the only filter that is supported with an ESP. More details in the section below. The above links describe how to create a device filter. The below images shows an example of creating a device filter, and then using a device filter when assigning applications. Check out the Common Questions and Answers in our Intune documentation for more details on the challenge of using dynamic groups to deploy applications at enrollment. Also, note our performance recommendations in our Intune documentation when using groups for application targeting. Recommendation: To reiterate, using the “All Devices” group AND a device filter that represents some or all Cloud PCs will provide the best possible performance, installing your applications as fast as possible post provisioning. Using a device filter that represents a specific provisioning policy or a specific configuration will provide granular targeting. What about using an Enrollment Status Page (ESP)? An ESP is commonly used to display the provisioning status when enrolling with Intune. It’s a detailed progress indicator. An ESP is designed to be displayed while the user is waiting for their device to be ready. When using Windows Autopilot to provision new physical Windows devices, the ESP runs in two phases: the device ESP and the user ESP. The device ESP runs only during the default out-of-box experience (OOBE). When provisioning Cloud PCs the device ESP is not used – as there’s no OOBE phase - only the user ESP. Since a Cloud PC is provisioned without a user present, an ESP may add complexity to the overall provisioning process. Further, while there is a setting “Block device use until all apps and profiles are installed” this is only used during the user ESP phase, and this setting is not used during Cloud PC provisioning when targeting apps to devices. Thus, if you’re targeting applications to device groups, we recommend not to use an ESP for Cloud PCs. If you’d like to use an ESP for user targeted applications and policies, make sure to follow the guidance here. Specifically, note that a custom ESP is only supported when you use a device filter that targets a specific provisioning policy. Using dynamic device groups with an ESP is not supported. Process Recommendations - Planning for onboarding users to Cloud PCs Without using the “Block device use until all apps and profiles are installed” setting, how can we ensure all the apps are installed prior to the 1 st logon? This is when it’s important to consider the onboarding process. Meaning, when testing/evaluating Windows 365, you might assign a license to yourself or your coworker, ensure you’re in a group that is assigned a provisioning policy, and then check the Intune admin console to see when you’re Cloud PC status changes from “provisioning” to “provisioned.” If you then immediately connect to your Cloud PC, you may find that not all of your applications installed, and then think “Well I can’t give this to my users until I know all my apps will be there!” Surprisingly, this statement holds the key to managing this challenge. Think about how you’re going to provide Cloud PCs to users. How many will you provision at a time? One? One hundred? One thousand? What’s your communication plan? How will users know when (and how) to use their Cloud PCs? What we find is that it is uncommon for users to login to their Cloud PCs shortly after they’re provisioned. Below is a chart that shows some of our internal telemetry from the last 28 days (based on time of this writing). Some takeaways from this data: Less than 30% of users sign-in to a Cloud PC less than 1 hour after it’s been provisioned. Over 50% of users sign-in to their Cloud PC 4 hours or more after it’s been provisioned. Additionally, we found that the average time until 1 st login is just over 32.4 hours and the median is 4.2 hours as there is a lot of variation in the results. What we can infer from the above is that most companies have users that do not sign-in immediately after provisioning and wait several hours before doing so. Sometimes this is done unintentionally, while sometimes this is planned during a deployment project. For example, a deployment plan may look like the following: Day 1 - Provision 50/500/5000* Cloud PCs Day 2 – Review the results Day 3 – Send out end user communications * Earlier this year, we worked with a company who followed this model and successfully provisioned over 10,000 Cloud PCs in less than 24 hours. The above deployment plan can definitely be compressed to build in a 2-3 hour buffer (for example) to ensure all apps are installed. Consider how a user will know to log on to their Cloud PC for the 1 st time. As an IT admin, you can control when to notify people that their Cloud PC is ready. During your notifications, you can optionally provide a link to download the Windows 365 app through the Microsoft Store, or a link to the Intune Company Portal to install the app. Lastly, make sure to test your application installation prior to onboarding your Cloud PC users in a production environment. While this may sound obvious, such testing helps eliminate potential onboarding challenges. What can be done to verify application installation? The Intune Admin portal can be used to review the results and ensure that all device targeted apps are installed. Administrators can select a Cloud PC and view the “Managed Apps” list that are targeted to the device. Using the Intune admin portal is a great way to review the results of a few Cloud PCs. Additionally, the Graph API can be used to help you automate this process. Check out our documentation that explicitly mentions how to get the application installation status on a user’s device. The Microsoft Hosted Network (MHN) can help If you’re concerned about having a Cloud PC connected to your network without immediately having your required security applications, consider using the Microsoft Hosted Network when planning your network deployment of the Windows 365 service. Using the MHN is the simplest option and aligns with the Zero Trust framework model and is the Microsoft recommended deployment model for Azure AD joined Cloud PCs. Additionally, a Cloud PC is not connected to your network until a VPN connection is explicitly established, further reducing risk. Summary When it comes to the Windows 365 provisioning process, the process used by IT admins to perform testing and evaluation can be vastly different than the process to deliver Cloud PCs to end users. In most environments, people 1 st sign-in to Cloud PCs several hours after they are provisioned. Acknowledging this human behavior and building a waiting period buffer is a means to ensure all your applications are installed and provide IT admins a way to verify prior to providing the Cloud PC to end users. The technical guidance above will also help you provide the best provisioning and onboarding experience to your users.
Windows 365 Cloud PC Self-Service Automated Request Process
How to automate Windows 365 Cloud PC self-service requests (Windows 365, Azure Active Directory, Microsoft Forms, Power Automate, MS Graph) Contributors: Juan José Guirola Sr. (Next Generation Endpoint GBB for Americas) Bobby Chang (Power Platform GBB for Americas) Azim Manjee (Cloud Endpoint Technical Specialist) Windows 365 simplifies how organizations offer Cloud PCs to their employees. As a cloud-based service from Microsoft, Windows 365 provides a personal, secure streamed experience from any supported device. It comes with all the productivity, security, and collaboration benefits of Microsoft 365. Windows 365 removes the need to manage a complex infrastructure and it integrates with existing cloud-based networking investments such as Azure Active Directory, Microsoft Endpoint Manager, and more. As the workplace continues to shift toward hybrid work, Windows 365 gives more organizations the ability to issue a cloud-native, persistent Cloud PC that is available 24 hours a day, 7 days a week, all with the ease of assigning a license. This simplified approach to provisioning Cloud PCs opens up the potential for automation and self-service scenarios. With Windows 365, you can provide your employees with Cloud PCs on demand, and here, we’ll show you how. Prerequisites The following items are required to provide automated, self-service Cloud PC request of Windows 365 deployment in a production environment: (For personal development and sandbox/testing scenario, you can use the Microsoft 365 Developer Plan and Power Apps Developer Plan). Windows 365 Enterprise Licenses Windows 10 Enterprise or Windows 11 Enterprise Azure Active Directory (Azure AD) Premium (P1/P2) Azure AD native group (must NOT be a synced group) Microsoft Intune (previously known as Microsoft Endpoint Manager) Microsoft Forms Power Automate per flow plan Microsoft Graph (Windows 365 Cloud PC MS Graph API in beta) Working with Windows 365 Cloud PCs using the Microsoft Graph API Azure App Registration with the following permissions: CloudPC.Read.All. For enterprise production scenarios, we would recommend leveraging the Application Lifecycle Management (ALM) capabilities in Power Platform, in order to safely adopt future changes to your processes. However, this is outside of the scope of this blog post. Before you begin Before you set up automation and a self-service Cloud PC request process, identify and assign the target Azure AD group(s) for the Windows 365 Cloud PC license assignment and provisioning policy. In our scenario, we have three Azure AD Groups (one Azure AD group for each of our three business segments), for both license and provisioning policy assignments. To configure group license assignments, see Assign licenses to users by group membership in Azure Active Directory. For information about how to target the groups for provisioning policies, see Create Windows 365 Cloud PC provisioning policies. Once you have the group assignment, set up the self-service process starting with Microsoft Forms. Create the request intake form Establishing an intake process will not only allow your employees to request the Windows 365 Cloud PC on-demand, but also allow you to build in an approval process and a feedback loop once the license is provisioned and ready for access. For our scenario, we are using Microsoft Forms as the intake form for requesting a Cloud PC. If your organization needs additional requirements around data validations and user experience in the form, we recommend leveraging Power Apps instead. To create a form with Microsoft Forms, see the Microsoft Forms help and learning home page or Create a form with Microsoft Forms. The following are the key components of our example form: Purpose-specific title “Windows 365 Cloud PC Request Form” Four questions to identify the requesting employee’s business segment, the type of Cloud PC they require, their region, and their contact number (aka mobile number) Shared to people in the organization only, for security, tracking, and notification purposes Alt text: Example Windows 365 Cloud PC Request Form in Microsoft Forms. Register MS Graph in Azure AD Once the request form is complete, register MS Graph as an Enterprise application in Azure Active Directory. Log into the Azure portal with appropriate permissions for making application registrations. Global Administrator privileges will provide the permissions to make application registrations; there are other options by following the custom role details in this documentation Custom role permissions for app registration - Azure AD - Microsoft Entra | Microsoft Docs. In the Azure services portal, click Azure Active Directory > Azure Active Directory. Alt text: A screenshot of the Azure Active Directory blade in the Azure services portal. Select App registrations in the left navigation menu. Click New registration. Give the application a name, select Single Tenant for the supported account type, and then click Register. Alt text: A screenshot of the Register an application screen, showing the details that need to be identified for the new application. Note. Alt text: A screenshot of the recently created application overview with the Application (client) ID and Directory (tenant) ID details highlighted. Click API permissions in the left navigation menu. . Select Microsoft.Graph and choose Application permissions. Ensure the following permissions are added: CloudPC.Read.All User.Read User.Read.All Group.Read.All Mail.Send (optional for sending messages via Graph ) Alt text: A screenshot of the Select permissions setup. Once the permissions have been added, click Grant consent. Click Certificates & secrets in the left navigation menu, and then click New client secret. Important! Note this key and store it somewhere safe, like a key vault. This key will only be visible upon creation. Once you navigate away, you will be unable to expose the key again and will have to generate a new key. Create the Cloud PC provisioning process automation In this section, we will build the Power Automate flows that will orchestrate the self-service process. This decision flow illustrates the end-to-end process of adding the requestor to proper AD security group, prompting an approval process, and then notifying requestor of their Cloud PC readiness. Alt text: A flowchart depicting the process for the automated provisioning process. To begin, sign into Microsoft Power Automate with your Microsoft 365 organization credentials. From the left navigation menu, click + Create then: Click Automated cloud flow. Name the flow and choose the flow trigger, “When a new response is submitted” (Microsoft Forms) from list. Click Create. Alt text: A screenshot that shows the flow name and trigger selection options. In When a new response is submitted, select your form from the Form Id drop down, then: Click + New step. Search for “forms” in Choose an operation and select Get response details (Microsoft Forms) from Actions. For Get response details, select your form from the Form Id drop down and then select Response Id as Dynamic content. Alt text: A screenshot of the criteria for the Get response details step. Click on + New step (To add variable for the Object ID of the targeted group in Azure AD). In Choose an operation, type variable. Select Initialize variable from Actions. Type VARGroup ID details screen. Give it a name, e.g., VARGroupID and select “String” as Type. Click + New step (To add variable for the “id” attribute value of the Cloud PC). Choose an operation, type variable. Select Initialize variable from Actions. Give it a name, e.g. VARCloudPCID and select “String” as Type. Click on + New step (To add variable for the “status” provisioning value of the Cloud PC). Search for VAR in Choose an operation. Select Initialize variable. Give it a name (e.g. VARProvisioningStatus) and select “String” as Type. Click on + New step (To add variable for your tenant ID). Choose an operation, type variable. Select Initialize variable from Actions. Give it a name (e.g., VARTenantGUID) and select “String” as Type. Tenant ID/Tenant GUID is required for authentication against the CloudPC Microsoft.Graph API. For information on getting your tenent ID, see How to find your Azure Active Directory tenent ID.For information on getting your tenent ID, see How to find your Azure Active Directory tenant ID. In the Value field, enter your Tenant ID. Click on + New step (To add variable for your Choose an operation, type variable. Select Initialize variable from Actions. Give it a name (e.g., VARAppID) and select “String” as Type. (This AppID represents the App Registration Client GUID, which is required for authentication against the CloudPC Microsoft.Graph API). In the Value field, enter your App Registration Client ID. Click on + New step (To add variable for the “Secret,” which is your . Choose an operation, type variable. Select Initialize variable from Actions. Give it a name (e.g., VARSecretID) and select “String” as Type. This is required for authentication against the CloudPC Microsoft.Graph API. Refer to Step 6 in the “Register MS Graph in Azure AD” section of this document. For additional protection, use Azure KeyVault to store and retrieve this client secret. Refer to Defining inputs and outputs for this variable action to obfuscate the secret during run time and from the logs. In the Value field, enter your Client Secret. At this point, we need to determine the automated actions, based on the “Business Segment” value provided by requestor. This can be accomplished by applying a Switch action. : Click on + New step. Search for “Switch” in Choose an operation and select Switch (Control). Next to On, select What Business Segment are you part of? from Dynamics content. Add as many “Cases” as needed to meet your specific needs. In our example, we have 3 Cases, which represent the 3 business segments: South Enterprise, LATAM, and Microsoft Federal. Within each Case, click Add an action Search for “variable” and select Set variable. Select VARGroupID from the Name drop down. Insert the Object ID of the desired targeted group for each “Case.” Note: The Object ID can be retrieved by viewing the group properties in Azure AD. Alt text: A screenshot of options for setting the Case variables. Click on + New step (This step will initiate the approval process) Search for “approval” in Choose an operation and select Start and wait for an approval. Select Approve/Reject – Everyone must approve from the Approval type drop down. Enter the email addresses for approvers in the Assigned to field. Fill in the remaining fields as desired. In our example, we elected to use values gathered from the requestor. Alt text: A screenshot of the available settings for the approval process in Start and wait for an approval. Click on + New step. This step will set up the execution process determined by approval outcome. Search for “Condition” in Choose an operation and select Condition control. Select Outcome under Dynamic content as the value. Choose is equal to and type “Approve” for the value. You will be presented with two sub processes, If yes and If no. Add necessary flows for each. Alt text: A screenshot of the If yes and If no sub-process flow setup options. For the If yes process: Click Add an action. Search for “Azure AD” in Choose an operation and select Get User. Select Responders’ Email for the User Id or Principal Name value. Click Add an action. Search for “Azure AD” in Choose an operation and select Add user to group. Select VARGroupID for Group Id and Id for User Id. Click Add an action. Search for “Send email” in Choose an operation and select Send an email (V2) Office 365 Outlook. Select VARGroupID for Group Id and Id for User Id. Rename to “Send an approved email.” Fill in all fields, as desired. Alt text: A screenshot of the Send an approval email setup. [Optional] If you want to added notification, click Add an action. You can add notification to your flow. In our example we are using Twilio, but you can choose to use other services. Follow your SMS provider’s instructions to properly configure in Power Automate Flow. Click Add an action. To pause the flow and allow the provisioning process to kick off in the backend, select Delay and configure the desired time. In our example, we’ve elected to delay the flow for 1 minute. Search for Delay in Choose an operation. Click Add an action. Important! To add the control to perform Graph API calls against tenant to monitor requestors Cloud PC provisioning status, search. In the Method field, select GET. Under URI, set it up exactly as illustrated below, placing the UserPrincipalName dynamic content inside the string: https://graph.microsoft.com/beta/deviceManagement/virtualEndpoint/cloudPCs?$filter=userPrincipalName eq '@{outputs('Get_user')?['body/userPrincipalName']}' and status eq 'Provisioning'&$count=true For Authentication, select Active Directory OAuth. Leave the authority as default. Enter your TenantID variable under Tenant, https://graph.microsoft.com under Audience, the AppID under Client ID, and the Secret in the Secret section. Alt text: Example setup for Graph API controls to monitor requestor Cloud PC provisioning status. Click Add an action, and search for “Parse JSON.” Under (note in the UI you will also see Parse User CPCs), select Body for the Content field and insert the body of the HTTP request response into the Schema field. Use the following schema: Alt text: A screenshot of completed content and schema details for Parse JSON. { "type": "object", "properties": { "@@odata.context": { "type": "string" }, "@@odata.count": { "type": "integer" }, "value": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string" }, "displayName": { "type": "string" }, "imageDisplayName": {}, "provisioningPolicyId": { "type": "string" }, "provisioningPolicyName": { "type": "string" }, "onPremisesConnectionName": { "type": "string" }, "servicePlanId": { "type": "string" }, "servicePlanName": { "type": "string" }, "status": { "type": "string" }, "userPrincipalName": { "type": "string" }, "lastModifiedDateTime": { "type": "string" }, "managedDeviceId": {}, "managedDeviceName": {}, "aadDeviceId": {}, "gracePeriodEndDateTime": {}, "servicePlanType": { "type": "string" }, "statusDetails": {} }, "required": [ "id", "displayName", "imageDisplayName", "provisioningPolicyId", "provisioningPolicyName", "onPremisesConnectionName", "servicePlanId", "servicePlanName", "status", "userPrincipalName", "lastModifiedDateTime", "managedDeviceId", "managedDeviceName", "aadDeviceId", "gracePeriodEndDateTime", "servicePlanType", "statusDetails" ] } } } } Note: You can also get this schema by using the Graph explorer to request from the same endpoint. Use the Generate from example button to generate the schema: Click Add action and search for “Apply to each.” In the Output field, select Value from our Parse JSON step. A Do until step should appear., If it doesn’t, click Add an action and search for “Do until.” Alt text: A screenshot of the Do until setup. In the Do until step, select the ProvisioningStatus variable is equal to string(‘provisioned’). Click and search for “Set Variable.” Configure the CPC-ID Variable to the ID of the item from the Parse JSON. Click Add an action and search for “HTTP.” Configure the HTTP using the same variables for TenantID, APpID, and Secret, as in the previous HTTP action, but using the following URI: https://graph.microsoft.com/beta/deviceManagement/virtualEndpoint/cloudPCs/@{variables('CPC-ID')} Example: Alt text: Example setup for monitoring Cloud PC. Click Add an action, search for “Parse JSON.” Select Body for the Content field and insert the following into the Schema field: { "type": "object", "properties": { "@@odata.context": { "type": "string" }, "id": { "type": "string" }, "displayName": { "type": "string" }, "imageDisplayName": { "type": "string" }, "provisioningPolicyId": { "type": "string" }, "provisioningPolicyName": { "type": "string" }, "onPremisesConnectionName": { "type": "string" }, "servicePlanId": { "type": "string" }, "servicePlanName": { "type": "string" }, "status": { "type": "string" }, "userPrincipalName": { "type": "string" }, "lastModifiedDateTime": { "type": "string" }, "managedDeviceId": { "type": "string" }, "managedDeviceName": { "type": "string" }, "aadDeviceId": { "type": "string" }, "gracePeriodEndDateTime": {}, "servicePlanType": { "type": "string" }, "statusDetails": {} } } Alt text: A screenshot of the Parse JSON schema. Click Add an action and search for “Set Variable.” Select ProvisioningStatus for the Name and configure the provisioning status variable to the status of the item from the Parse JSON. Click Add an action and search for “Delay.” Set a delay in an appropriate increment to recheck the status based on your typical Cloud PC provisioning time (e.g., 30 minutes is a normal time increment). In our example, we selected an increment of every 15 seconds. Consider throttling concerns to not overwhelm the API and cause timeouts. Once you’re past the Do Until scope, Click Add an action and search for “Send an Email.” Create your “successful” provisioning email. In our example, we use several variables and dynamic content to ensure clarity. You can also embed links to the different clients available to the employee for accessing their Cloud PC. Alt text: An example of a “successful” provisioning email setup. Click Add an action and search for “Send Text Message.” Create your “successful” provisioning SMS. In our example, we use several variables and dynamic content for clarity. Alt text: An example “successful” provisioning SMS message setup. Once you’re past the Apply to Each scope, Click Add an action, and search for “Terminate.” Set the Status to Successful. Return to the Approval Conditon to setup the rejection or If no process. Scroll up in the workflow to access this setup. Click Add an action and search for “Send Email.” Create and carefully word the rejection email. Alt text: An example of a rejection email setup. Click Add an action and search for Terminate. Set the Status as Cancelled. The entire Power Automate flow should look like the image below. Alt text: A Power Automatic flow diagram depicting the process described in this document. Once you’ve completed adding in steps to your automation flow, you’re ready to test the solution. Select Test and execute the steps described in the User experience section of this document. User experience Once the self-service experience is configured, the employee or requestor should be able to generate a request. The following is an example of what the user can expect during their request experience. The requestor completes the Self-service user request form. Alt text: An example of a completed self-service request form filled in by an employee. The flow kicks off based on information entered in the form by the requestor. The approval process begins. Alt text: An illustration of the approval process flow. The Approver gets an email and Microsoft Teams notification to approve, reject, or reassign the request. Alt text: An example of an approval request. Once approved or rejected, the flow continues to add the user to the proper Azure AD Group, which in turn will assign the proper Windows 365 license and the correct provisioning policy. Alt text: An illustration of the If yes and If no process flows. If the request is approved, the approval email and SMS text will be sent to the requestor informing them that the request was approved. If the request is rejected, the rejection email will be sent. Alt text: An example of an approval email. Alt text: An example of an approval text message. Power Automate will monitor the provisioning status as it changes from “provisioning” to “provisioned.” Once the Cloud PC status changes to “provisioned,” the requestor will receive an email and SMS text message informing them that their Cloud PC has been provisioned and is ready to access. Alt text: An example email message informing the requestor that their Cloud PC has been provisioned. Alt text: An example text message informing the requestor that their Cloud PC has been provisioned. Continue the conversation by joining us in the Microsoft 365 Tech Community! Whether you have product questions or just want to stay informed with updates on new releases, tools, and blogs, Microsoft 365 Tech Community is your go-to resource to stay connected.
