Loading...

Introducing Azure Virtual Desktop workload in Azure Stack HCI Sizer!

Introducing Azure Virtual Desktop workload in Azure Stack HCI Sizer!

Earlier in February 2024, we announced the general availability of Azure Virtual Desktop for Azure Stack HCI which extends the capabilities of the Microsoft Cloud to your datacenters and edge locations . Today, we are happy to announce that ‘Azure Virtual Desktop’ is now available as a new workload category in Azure Stack HCI sizer! It enables customers to efficiently plan and size Azure Virtual Desktop deployments on Azure Stack HCI by calculating no. of VM required, suggest per VM configuration and what hardware to purchase.

Azure Stack HCI Sizer

Azure Stack HCI Sizer is a web-based comprehensive tool to assist organizations in accurately estimating hardware requirements for their Azure Stack HCI deployments.

Azure Virtual Desktop for Azure Stack HCI

Bringing the benefits of Azure Virtual Desktop and Azure Stack HCI together, Azure Virtual Desktop for Azure Stack HCI lets organizations securely run virtualized desktops and apps on-premises at the edge or in their datacenter. For organizations with data residency requirements, latency-sensitive workloads, or those with data proximity requirements.

Getting Started

The sizer allows you to create multiple projects, thus reflecting your various business needs.
To plan your Azure Virtual Desktop workload on Azure Stack HCI, first go to the sizer tool and create a new project.

Step 1 of the sizer asks you for Environmental preferences that will stay consistent across your projects, for example, Preferred system type, CPU family etc.

Step 1: Set Environmental PreferencesStep 1: Set Environmental Preferences

 

 

Step 2 of the sizer asks for your workloads. You can now select ‘Azure Virtual Desktop’ as a Workload category when you click on ‘Add workload’.
As soon as you select workload category as ‘Azure Virtual Desktop’, you can now provide information about your environment like:

  • Max. concurrency percentage i.e., maximum no. of users who will login concurrently
  • Session type i.e. Multi-session or Single session
  • Workload type i.e. Light, Medium, Heavy or Power workload.
    (Learn more about session host sizing guidelines here)

Optionally, you can also plan a file share to manage user profiles.

Step 2: Add Azure Virtual Desktop WorkloadStep 2: Add Azure Virtual Desktop Workload

 

Based on the above input parameters, Azure Virtual Desktop workload will calculate number of virtual machines required and will also minimum recommended VM configuration.
We strongly recommend that each customer to perform stress testing based on the apps required and update per VM configuration as needed. 

Add the workload to the project and click on ‘Next’ to see what hardware has been suggested by the sizer based on HCI catalog.
At this stage, you’ve completed all the steps and can check out the results and see what hardware we recommend for your workloads. If you notice anything odd about your results, you can go back and edit your environmental preferences as well as your workloads from the results page. Our suggestion tells you the exact model, number of nodes and node level recommendations that would satisfy your needs. We also include utilization bars for CPU, memory and storage which show you resource consumption and help you understand how we arrived at our recommendation.

Result PageResult Page

 

Conclusion

We are excited for the future of Azure Virtual Desktop for Azure Stack HCI as we keep building and transforming with our customers. We would love to hear your feedback and suggestions on this form

Thank you! 

 

 

Published on:

Learn more
Azure Stack Blog articles
Azure Stack Blog articles

Azure Stack Blog articles

Share post:

Related posts

Accelerate Your Growth: Azure Cosmos DB Partner Acceleration Program

Accelerate Your Growth: Azure Cosmos DB Partner Acceleration Program Unlock 360° Success with the Cosmos DB Engineering Team Are you ready to ...

16 hours ago

Transforming Field Operations with AI, Azure Maps & Dynamics 365

Efficient field operations are the backbone of successful, data-driven organizations. Yet, many businesses continue to struggle with scattered...

2 days ago

Failures Happen in Cloud, but how Azure Cosmos DB keeps your Applications Online

The only thing that’s constant in distributed systems is failures. No cloud platform is immune to failures — from regional outages and transie...

4 days ago

The `azd` extension to configure GitHub Copilot coding agent integration with Azure

This post shares how to set up the GitHub Copilot coding agent integration with Azure resources and services by using the Azure Developer CLI ...

4 days ago

Announcing Azure MCP Server 1.0.0 Stable Release – A New Era for Agentic Workflows

Today marks a major milestone for agentic development on Azure: the stable release of the Azure MCP Server 1.0! The post Announcing Azure MCP ...

6 days ago

From Backup to Discovery: Veeam’s Search Engine Powered by Azure Cosmos DB

This article was co-authored by Zack Rossman, Staff Software Engineer, Veeam; Ashlie Martinez, Staff Software Engineer, Veeam; and James Nguye...

6 days ago

Azure SDK Release (October 2025)

Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (October 2025)...

7 days ago

Microsoft Copilot (Microsoft 365): [Copilot Extensibility] No-Code Publishing for Azure AI Foundry Agents to Microsoft 365 Copilot Agent Store

Developers can now publish Azure AI Foundry Agents directly to the Microsoft 365 Copilot Agent Store with a simplified, no-code experience. Pr...

7 days ago

Azure Marketplace and AppSource: A Unified AI Apps and Agents Marketplace

The Microsoft AI Apps and Agents Marketplace is set to transform how businesses discover, purchase, and deploy AI-powered solutions. This new ...

10 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy