Running Microsoft Teams in a Virtual Environment

Nowadays security and compliance are at the forefront of many companies concerns. For organizations with these issues they typically look to virtualize some of their environment. To cater to those needs, Microsoft has recently made VDI available for Microsoft Teams. In this article I will be discussing some of the key features, limitations, and offerings for this up and coming solution for Microsoft Teams if your organization chooses to go this route. One important thing to consider that as of the time of this writing Teams has not been optimized to access or use the audio or video devices on the user’s local devices (without additional software).

Note: Working in a VDI environment will usually have challenges related to multimedia scenarios such as calling, video calling, screen sharing, app sharing, co-authoring, and more.

Your organization can choose to run Teams fully in VDI (using either the Web App or Desktop Client) but it is recommended that the following policies be turned off, so users don’t have a poor experience in a virtualized environment.

• Policies recommended to be disabled:
  • Calling – Controls whether the Calling app is available in the left rail on the Teams client or not. Also control whether users see Calling and Video Call options in private chat.
    • It is recommended to set this to FALSE to remove the Calling app from the left rail and to remove Calling and Video Call options in private chat.
  • Meetings – The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users.
    • For the specific policy names and recommended values, please check out the list here.

Known Limitations

Other than the audio and video limitations that we mentioned earlier, there are some additional limitations your organization may face:

• Joining meetings created by others. Even though the above policies restrict users from creating meetings, they will still be able to join meetings sent out by other users. Within these meetings, their ability to share video, use WhiteBoard and other features will depend on whether the admin disabled them or not.
• Issues related to cached content. If the virtual environment that Teams is running in is not persisted (data is cleaned up at the end of each user session), users might notice performance degradation due to the client having to re-download all content again, regardless of whether the given user accessed the same content in a previous session. This performance impact can be mitigated by using roaming cache solutions, such as those provided by FSLogix.

Unleash the Potential of Power Platform With a Center of Excellence

Business innovation often comes from within. Discover how to empower innovation from non-traditional developers with the Microsoft Power Platform.

Learn More

Once Teams has been optimized for use within Virtual Desktop environments, admins can revert these policies and allow users to use Teams as they normally would.

Similar to the HDX RealTime Optimization Pack offered for Skype for Business Server 2015, Citrix is currently working on a similar plugin for Teams desktop app. As Citrix mentions, this virtualization plugin will be very similar to the one offered for Skype for Business Server 2015. The currently layout for the Citirix HDX RealTime Optimization pack is as follows:

1.  A VDA-side HDX component will interface with the Teams hosted app and receive commands,
2. Then it will open a control virtual channel to a Citrix Workspace app-side media engine and let the multimedia be rendered locally by the endpoint
3. Reverse seamless will snap-in the local Citrix Workspace App window back into the hosted Teams app
4. Authentication and signalling will happen natively on the Teams-hosted app, just like the other Teams services (e.g. chat or collaboration). They will not be affected by the audio/video redirection.
5. As always, client-fetch/client-render and server-fetch/client-render (in case your endpoints don’t have internet access, thanks to a media relay virtual channel) are going to be available. And of course, there will be support for HID Devices and any endpoint (Windows, Mac and Linux).

In terms of the Teams Web App on VDI, you can expect it to support audio, video, and desktop sharing using WebRTC for multimedia (so that means no browser plugins required!). Citrix has stated they also intend on supporting BCR (Browser Content Redirection). This will allow you to redirect an entire website to the endpoint for local rendering. This feature is intended to be released sometime this quarter (Q3 2018) for XenApp and XenDesktop by enhancing BCR to support WebRTC redirection. For the full blog post on this check it out here. I hope you have found this quick overview of what Microsoft VDI brings to the table useful. Stay tuned, as I have more exciting news on Teams and Skype for Business coming out shortly!