Seeking clarification on long‑term roadmap for Availability Sets, VMSS Flex adoption for AVD, FSLogix roaming, and AVD platform direction through 2030

Question

Dear Experts,

I’m planning for long‑term Azure Virtual Desktop (AVD) platform stability (looking ahead to 2030+) and want to ensure that our roadmap aligns with Microsoft’s strategic direction.

I understand that Availability Sets are still supported for general Azure VM workloads. However, Microsoft has officially announced the retirement of Availability Sets (VMAS) only for Azure Kubernetes Service (AKS), effective 30 September 2025, and that AS in AKS has been feature‑frozen since 2019.

At the same time, I cannot find any public announcement or roadmap item regarding the long‑term future of Availability Sets for general VM infrastructure or AVD session hosts.

Azure documentation increasingly recommends Virtual Machine Scale Sets (VMSS) with Flexible orchestration as the preferred modern approach for high‑availability VM workloads. Given this trend, I would like to clarify Microsoft’s intended platform direction.

In addition, FSLogix roaming profiles have architectural limitations in multi‑pool roaming scenarios, and I'm interested in understanding whether there are future improvements planned in this area.

I would appreciate clarification on the following points:

• Availability Sets Future - Does Microsoft have any plan to retire or phase out Availability Sets outside of AKS within the next 5 years?
• AVD Architecture Direction (2026–2030+) - For long‑term AVD architecture planning, should customers expect VMSS Flexible to become the primary or recommended compute model for AVD session hosts?
• FSLogix / Profile Roaming Roadmap - As of 2026, FSLogix is not an ideal fit for multi‑pool roaming scenarios. Is there any roadmap update or future solution planned to better support cross‑pool roaming?
• Network Architecture for AVD (Internal vs External Users) - What is Microsoft’s recommended connectivity architecture for internal vs external AVD users? For example, is it still recommended to separate internal-only and external-facing host pools for best security and performance?
• AVD Deprecation Plans - Apart from the retirement of the classic AVD (Fall 2019) platform, is there any known or anticipated deprecation of components or features in the AVD platform over the next 5 years?

Any official clarification or forward‑looking guidance would be greatly appreciated.

Disclaimer: This question is asked in a general architectural context and does not relate to any specific organisation or environment.

Thank you.

Answer 1

InfraSolutions - There is no announced plan to retire Availability Sets for general Azure VMs or Azure Virtual Desktop (AVD). The announced retirement applies only to AKS. Availability Sets remain supported, though Microsoft now recommends newer availability models for new deployments - https://learn.microsoft.com/azure/virtual-machines/availability-set-overview

For long‑term AVD planning, VM Scale Sets with Flexible orchestration are the recommended and future‑aligned compute model. Microsoft documentation explicitly states VMSS Flexible is preferred for high availability and ongoing platform investment.

https://learn.microsoft.com/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes

https://learn.microsoft.com/azure/architecture/guide/technology-choices/compute-decision-tree

FSLogix remains the supported profile solution for AVD, but Microsoft has not published any roadmap for native multi‑pool or cross‑pool roaming improvements. Current limitations still apply. Microsoft docs:

• https://learn.microsoft.com/fslogix/overview
• https://learn.microsoft.com/fslogix/troubleshooting-feature-deprecation

Microsoft does not mandate separate host pools, but recommends designing based on security, identity, and connectivity needs. Many customers separate internal and external access using host pools, network controls, or Conditional Access, but both models are supported.

Docs:

• https://learn.microsoft.com/azure/virtual-desktop/network-connectivity
• https://learn.microsoft.com/azure/virtual-desktop/rdp-shortpath

Other than the already retired AVD (Classic / Fall 2019) platform, there are no announced deprecations of core AVD components in the next five years. All future changes are communicated via official deprecation and “What’s new” channels.

Docs: https://learn.microsoft.com/azure/virtual-desktop/whats-new

Answer 2

The only items covered in the provided material are:

1. Availability Sets vs. VM Scale Sets (general Azure guidance)
   Availability Sets remain a supported high‑availability construct for general Azure VMs. However, newer guidance emphasizes Virtual Machine Scale Sets (VMSS), especially with Flexible orchestration, as the modern approach for high availability:

• VMSS with Flexible orchestration supports spreading instances across availability zones and fault domains and offers a 99.99% SLA when instances are spread across multiple zones.
• Availability Sets provide 99.95% SLA and do not support availability zones.

The comparison table shows that Flexible and Uniform VMSS orchestration modes provide more advanced capabilities than Availability Sets, such as:

• Zone‑aware deployments.
• Explicit zone assignment (Flexible only).
• Maximal fault‑domain spreading.

This indicates a strategic preference toward VMSS (particularly Flexible) for new or modernized workloads, but the context only states a retirement date for Availability Sets in AKS, not for general VM workloads.

2. Availability Sets retirement – AKS only
   For Azure Kubernetes Service (AKS), Availability Sets (VMAS) are explicitly being retired:

• AKS will no longer support Availability Sets starting 30 September 2025.
• AKS clusters using Availability Sets after that date are out of support.
• Customers are instructed to migrate to Virtual Machines node pools.
• Availability Sets in AKS have been feature‑frozen since 2019 and do not support newer AKS features such as AKS Backup.

This retirement notice is scoped specifically to AKS; no broader retirement statement for Availability Sets outside AKS is included in the context.

3. AVD session host high‑availability guidance
   For Azure Virtual Desktop, the guidance in the material focuses on using availability zones and VM scale sets (particularly flexible orchestration) for session hosts:

• Deploy session hosts with redundancy using availability zones or virtual machine scale sets.
• For session host settings, the recommendations include:
  • “Deploy session hosts in an availability zone or a flexible virtual machine scale set” to protect from outages.
  • “Spread session hosts across different availability zones” and also “within availability zones” to improve availability and reduce the chance of environment‑wide outages.

This clearly positions availability zones and flexible VM scale sets as the recommended HA constructs for AVD session hosts going forward, but the context does not state that Availability Sets for AVD are being deprecated.

4. AVD architecture direction (host pools and session hosts)
   The AVD guidance in the context emphasizes:

• Placing session hosts close to users to minimize latency.
• Using availability zones or flexible VM scale sets for resiliency.
• Spreading session hosts across zones and within zones.
• Using IaC (for example, Azure VM Image Builder and the Virtual Desktop Accelerator) and Azure Policy to standardize and harden AVD environments.

This supports a design direction where VMSS Flexible + availability zones are the primary pattern for resilient, scalable AVD host pools, but no explicit long‑term (2026–2030) roadmap statement is provided.

5. FSLogix and storage options for AVD
   The context only covers storage back‑ends for FSLogix containers in AVD and other Azure‑based virtual desktop environments:

• Supported Azure storage options include Azure Files, Azure NetApp Files, Azure Page Blobs, and Storage Spaces Direct.
• It describes these options in terms of use cases (general purpose vs. ultra performance vs. cross‑platform) and whether they are Azure‑native platform services.

There is no roadmap information about FSLogix itself, nor about new profile‑roaming mechanisms or multi‑pool roaming improvements.

6. AVD deprecation plans and network architecture
   The provided material does not include:

• Any deprecation roadmap for AVD components or features beyond the already‑retired “classic” AVD platform.
• Any explicit guidance on separating internal‑only vs. external‑facing host pools or detailed network segmentation patterns for internal vs. external AVD users.

Only general availability and resiliency guidance for session hosts and host pools is present.

Because of the scope of the provided content, the specific questions can be answered only as follows:

• Availability Sets Future (outside AKS): The context only states retirement of Availability Sets for AKS by 30 September 2025 and that they are feature‑frozen in AKS. It does not state any retirement or phase‑out plan for Availability Sets for general VM workloads.
• AVD Architecture Direction (2026–2030+): The context recommends availability zones or flexible VM scale sets for AVD session hosts and shows VMSS Flexible as the more capable HA construct compared to Availability Sets. It does not provide an explicit 2026–2030 roadmap or a statement that VMSS Flexible will become the exclusive or primary required compute model.
• FSLogix / Profile Roaming Roadmap: No roadmap or future enhancement information is provided; only current storage options for FSLogix containers are described.
• Network Architecture for AVD (Internal vs External Users): No explicit guidance is provided on separating internal vs. external host pools or specific connectivity patterns.
• AVD Deprecation Plans (next 5 years): No additional deprecation plans for AVD components or features are described beyond the AKS Availability Sets retirement and general HA guidance.

---

References:

• Migrate from Availability Sets in Azure Kubernetes Service (AKS)
• Application delivery considerations for Azure Virtual Desktop workloads
• Container storage options
• Orchestration modes for Virtual Machine Scale Sets in Azure
• High-availability architecture and scenarios for SAP NetWeaver
• DCsv2-series retirement