If you are like me, you use the application launchers in the Microsoft 365 waffle daily, if not hourly! Then having it as a single pane of glass to access all your applications is a no-brainer!
That includes access to the Azure Virtual Desktop Web client! In addition, Microsoft has given us the ability to add Custom App Launchers for applications that are accessible to a URL to the Launchers in the waffle!
Create custom tiles that will appear in the All apps section of the Office 365 app launcher for all of your users. Users can pin the custom tiles directly to their app launcher for quick access.
You can add much more than the Azure Virtual Desktop web client to help improve your user’s experience, but this quick guide will focus on adding the Azure Virtual Desktop Web Client.
- Open the Microsoft 365 Admin Panel
- Expand Settings
- Click on Org Settings
- Select Organisation Profile
- Click on Custom app launcher tiles
- Click + Add a custom title.
- Please type in the name of your Desktop; in my example, it is Contoso Desktop.
- For the URL of the website, type in: https://rdweb.wvd.microsoft.com/arm/webclient/index.html
- Type in a URL of the icon you want the App Launcher to have (Make sure this is a location that you have access to and can manage (i.e. even sitting on your website or Azure Storage account as long as it’s publically available)).
- Add a description (such as Contoso Desktop, used for Line of Business Applications)
- Click Save
- Log out of your Admin account and log into an account with an Exchange license attached to it. It may take some time for the Custom App Launcher to display.
- Once the Custom App Launcher has displayed, your users can pin it to the launcher, so it is always right on top.
- Click on your Azure Virtual Desktop launcher, and you should be redirected to the Azure Virtual Desktop Web client!
Just some notes on additional testing:
- I attempted copying the Azure Virtual Desktop RDP file (C:\Users\%UserAccount%\AppData\Local\rdclientwpf) to my website to access directly however received an error, even opening up the RDP file directly failed, to test the Remote Desktop client.
- I had some success opening that RDP up with the Remote Desktop application directly using ‘Open With’ C:\Users\%UserAccount%\AppData\Local\Apps\Remote Desktop\msrdcw.exe, instead of the default Remote Desktop Connection client locally.
- This will add it for all M365 users, if you want to restrict it to Users/Groups, I would look at testing and creating an App Registration.
At this stage, having a launcher to the Web Client is the best bet vs a shortcut directly to the RDP file as you don’t have to worry about users having the Remote Desktop agent installed when working remotely.