A secure cloud platform distributes applications to connected computers and data centers across two locations.
Microsoft has put VM Applications for Azure Arc-enabled servers into Public Preview. VM Applications for Arc is described as a way to package third-party and internal apps, agents and middleware, store them centrally with versioning, and deploy them to Azure VMs and Arc servers without rebuilding images. If you already run Azure VMs, the idea is familiar. The change is that Arc-connected servers can now use the same model. Those servers might be on-premises, at the edge, or in other clouds.

A secure cloud platform distributes applications to connected computers and data centers across two locations. What Microsoft announced​

Microsoft's Azure Arc blog announced the preview on November 17, 2026. VM Applications already let organizations package, version, share, deploy and manage applications on VMs through Azure Compute Gallery. The preview extends that to servers outside Azure. Teams can publish custom or third-party applications to Azure Compute Gallery and deploy them to both Azure VMs and Arc-enabled servers.

Microsoft's pitch is "publish once, deploy everywhere", which it expects to reduce tooling sprawl in hybrid estates. The post lists these benefits:

  • One management plane across Azure, hybrid and multicloud servers.
  • A private gallery for line-of-business and third-party applications.
  • Access and version control. Galleries can be shared with RBAC. Administrators can control which versions are approved. Azure Policy can enforce required applications and versions. Security patches can be published quickly.
  • Resilience. Microsoft cites automatic regional replication to reduce CDN-failure risk. It also cites gradual rollouts and fast rollback to limit the damage from a bad release.
  • Flexible operations. You can deploy declaratively with templates and policies, manage single servers with PowerShell or CLI, or manage a fleet in the portal.
  • Governance and visibility through Azure Policy and Azure Resource Graph.

These are Microsoft's own claims. The post gives no figures for rollout speed, rollback timing or supported scale.

What you need to get started​

Microsoft gives two prerequisites:

  1. Servers that are connected to Azure Arc.
  2. A compatible VM Application published in Azure Compute Gallery. Its version must be replicated to the region of the target servers.

The post also points to prerequisites for supported agent versions, networking and permissions. It does not state the actual values. That means no minimum Connected Machine agent version, no supported operating system list, no region list and no preview limitations. I haven't found Arc-specific documentation that fills those gaps, so check the current Microsoft Learn pages before you plan a pilot.

Background: how VM Applications work on Azure VMs​

Microsoft Learn describes the existing Azure VM model. The following is documented for Azure VMs. It is not confirmed for Arc.

  • A gallery is the repository. An application definition holds common metadata. Each application version holds the actual package plus its install, remove and optional update commands.
  • Packages are uploaded to a storage account first. The gallery then pulls them in and replicates them.
  • Packages can be in many formats, including .zip, .msi, .exe, .tar.gz, .deb, .rpm and .sh.
  • Windows commands run under cmd.exe by default, and Linux commands under /bin/bash. You can call PowerShell explicitly.
  • By default, a failed application script still lets the extension report success. Setting treatFailureAsDeploymentFailure to true changes that on Azure VMs.
  • Documented Azure VM limits include 2 GB per package, 25 applications per VM, 300 versions per region, and up to 10 replicas per region.
  • Retrying a failed install currently means removing the application from the profile and adding it back.
  • There's no extra charge for the feature itself. You pay for storage and for network egress when replicating the first version.

An Ignite 2026 roundup on WindowsForum.com adds one Arc-related detail. Extension or VM Application packages, which can be as large as 2 GB, download from Microsoft's CDN on install or upgrade. That is a reasonable cue to check your outbound network rules.

Analysis: why this matters, and what to verify​

Many mixed estates run a patchwork of tools for software distribution, such as configuration management, scripts and endpoint tools. A single versioned gallery governed by Azure Policy is attractive. The security-patch angle may matter most. A fix could be published as a new version and enforced across Azure and Arc servers through policy.

Treat it as a preview, though. Several questions remain open:

  • Which Arc agent versions and operating systems are supported?
  • Do the Azure VM limits above apply to Arc servers?
  • How do application state and install errors show up for Arc machines?
  • Is there a cost for Arc servers beyond storage and egress?
  • Does a server behind a restrictive firewall or proxy reach the gallery content?

A sensible pilot approach​

  1. Pick a small group of non-critical Arc servers.
  2. Confirm their agent version, network access and permissions against the current prerequisites.
  3. Publish a simple application version, with install and remove commands you have tested.
  4. Replicate it to the target servers' region.
  5. Deploy it and confirm the result. Don't rely on the extension's success status alone, given how application failures are reported on Azure VMs.
  6. Test an update and a rollback before you use Azure Policy to enforce anything.

Bottom line​

The preview brings the Azure VM Applications workflow to Arc-enabled servers, with a private gallery, RBAC, policy enforcement and Resource Graph visibility. The headline is sound, but the details that decide production use aren't in the announcement. Those are supported agent versions, operating systems, limits and Arc-specific behavior. Pilot it, and verify them first.

 

References

  1. Azure VM Applications for Azure Arc-enabled servers now in Public Preview Azure Arc Blog 2026-11-17T18:45:00+00:00
  2. Azure VM Applications for Azure Arc-enabled servers now in Public Preview | Microsoft Community Hub techcommunity.microsoft.com
  3. Overview of Azure VM Applications in the Azure Compute Gallery - Azure Virtual Machines | Microsoft Learn learn.microsoft.com