If you’re keeping track, we’re at the halfway mark already in 2019. Wow, time flies when you’re busy building new features based on customer feedback.
In the March release of Horizon Cloud on Microsoft Azure, we came out with vGPU support for Windows 10 virtual desktops using Microsoft Azure NV Series VMs, the ability to redirect end users to Workspace ONE when accessing their Horizon virtual desktops, and support for Microsoft Windows 10 1809 for VDI desktops.
Today, we are excited to announce the July release of Horizon Cloud on Microsoft Azure. Our latest release includes a number of key capabilities that give organizations more choice, enhance the administrator’s user experience, and provide more metrics to optimize deployments.
Support for additional Microsoft Azure VM types and sizes
We are excited to announce additional support for Microsoft Azure VM types and sizes for added flexibility.
Customers can now pick from over 200 VM sizes that best meets their use case for both VDI and RDSH along with the ability to filter the VM sizes based on Type, Series, CPU, Memory and Tag when creating a Desktop Assignment or RDSH Farm.
- The VM sizes that will be available are determined by the customers’ Azure subscription and the Azure region.
*Note: VMware will restrict access to specific VM sizes that we deem not acceptable to use with the service (Standard A series, B series).
Updated UI for Login Screen and Horizon Cloud Administrator Console
Our team has been listening to your feedback and we’ve made updates to our user interface. We have a new UI for the login screen. We have also made it easier for you to navigate Horizon Cloud Management Console with UI updates. You can easily see the health of your deployment, VM utilization, the number of active sessions and much more.
To help you better manage the health of your Horizon Cloud on Microsoft Azure deployment, we are providing a number of pre-built reports covering VDI and RDSH desktop usage, VDI applications usage, and user usage.
Support for a custom role when creating the Microsoft Azure Service Principal
Customers are no longer required to use the “Contributor” role when creating the Service Principal and can now create a custom role with the appropriate permissions.
The custom role that is created for the Service Principal will require specific permissions to be set in order to deploy and operate the service.
For more information on the latest release of Horizon Cloud on Microsoft Azure, please check out the Release Notes.