A glowing cloud-computing network connects virtual machines to a secure database beneath a data management dashboard.
Microsoft has declared Azure Native Commvault Cloud generally available as an Azure Native ISV service. It's a backup option for people who want Commvault's recovery tooling without leaving the Azure portal for every task. The scope at launch is narrower than some of the pre-launch chatter suggested, so the details matter.

A glowing cloud-computing network connects virtual machines to a secure database beneath a data management dashboard. What Microsoft announced​

According to Microsoft's Azure Storage blog, the service is jointly built by Microsoft and Commvault. It brings Commvault backup and recovery for Azure virtual machines into the Azure portal. Data-protection resources are managed as Azure resources, and applicable Commvault charges appear on the Azure bill. Microsoft frames it as another option for protecting business-critical workloads in Azure. It does not present it as a replacement for Azure Backup.

The announcement says this goes beyond a Marketplace purchase and deployment. From Azure, administrators can configure backup storage, define protection policies, and run supported backup and recovery operations.

The scope: Azure VMs only, for now​

Microsoft Learn's management guide says Commvault Cloud currently supports protection and recovery for Azure virtual machines only. Support for more workloads is planned in future releases, including Azure Kubernetes Service (AKS). No delivery date is given.

That matters because third-party coverage of the June 2026 partnership announcement has been inconsistent. Some write-ups on other sites claimed AKS, Azure VMware Solution, SQL Managed Instance, Windows endpoint coverage and specific regions. They also gave conflicting availability dates, from September to December 2026. None of that appears in Microsoft's launch post or documentation. Microsoft's documentation is the safer guide. Treat anything beyond VM protection as unconfirmed until it shows up in Microsoft Learn.

The launch post does not mention these items either:

  • Pricing.
  • Regional availability.
  • Service-level commitments.
  • A feature-by-feature comparison with Azure Backup.

Check these with Microsoft and Commvault before you plan a rollout.

Setup: more than a click in Marketplace​

Onboarding still has real prerequisites. They are documented in Microsoft Learn's configuration guide:

  • Subscription: You need an active Azure subscription that can purchase the Commvault Azure Marketplace offer.
  • Tenant consent: A tenant administrator must grant admin consent to the Commvault single sign-on enterprise application.
  • Managed identity role: You download CVBackupRole-VMs-LIFTR.json, create the approved custom Azure role from it, and assign it to the managed identity at a supported scope. The identity uses it to discover selected VMs, read their configuration and perform supported backup and recovery operations.
  • Entra groups: Prepare Microsoft Entra security groups to map to Commvault roles during account creation, with at least one mapped to Commvault Backup Administrator. After the account exists, assign the Commvault Contributor Azure role to those groups.
  • Resource access: Users who configure protection must also have access to the Azure resources being protected.

The documented role split is useful for separating duties:

Commvault roleWhat it can do
Backup AdministratorManages the service, creates and deletes resources, grants access to others
Backup OperatorManages resources but can't delete storage or backup plans
Backup UserCreates protection groups and adds Azure resources to them

Two checks apply to every operation. The mapped Commvault role decides whether Commvault authorizes it. The Commvault Contributor Azure role decides whether Azure Resource Manager allows it. Both must succeed. If a user's backup action fails, check both layers.

How protection is organized​

The workflow has four steps: prepare identity and access, create the Commvault Cloud account, then configure storage, a backup plan and a protection group.

  • Storage defines where backup data lives. Documented classes are Hot for frequent access and Cool for infrequent access. Creating storage requires the Backup Operator or Backup Administrator role.
  • A backup plan sets primary storage, the schedule and recovery-point retention. Extra storage copies can be added if supported. Microsoft's blog describes plans as controlling full or incremental backup frequency and retention.
  • A protection group ties Azure resources to a plan and runs scheduled and on-demand backups.

For resource selection, you can pick VMs manually or define include and exclude rules. Microsoft says you can preview the rule results before applying them. Each time the group runs, it picks up newly matching VMs. In a fast-changing subscription, that helps prevent a new VM from sitting unprotected.

A new group shows To Be Protected until its first scheduled backup finishes. That label is not proof of a recovery point. If you need confidence on day one, use Backup now and then confirm the job outcome.

Recovery options​

From an available recovery point, you can recover one or several VMs from a group. Microsoft's blog lists two options:

  • Restore to a disk attached to an existing VM.
  • Recover a full VM, either in place or to a new VM.

Group-level actions in the portal are:

  • Recover: Restore from an available recovery point.
  • Backup now: Start an on-demand backup using the plan's storage and retention settings.
  • Stop backup: Halt future scheduled backups. This doesn't delete the group or its configuration, and existing recovery points stay available.
  • Resume backup: Restart scheduled backups on the plan's schedule.

The documentation covers VM-level protection and recovery. It doesn't establish file or folder restore, so don't assume it.

For detailed job information and failure troubleshooting, Microsoft points to Commvault Command Center. The Azure portal handles supported actions, but it's not the whole Commvault console. Expect to switch between the two when a job misbehaves.

Compliance Lock: the trade-off to understand​

Microsoft says the service offers immutable, air-gapped backup protection against ransomware, accidental deletion and malicious modification. The Learn documentation adds a concrete control: Compliance Lock is enabled by default on storage created through Azure Native Commvault Cloud.

While it's on:

  • Backup copies are immutable.
  • You can't delete the storage resource.
  • You can't reduce retention on an associated plan, though you can increase it.
  • You can't delete an associated plan.
  • You can't delete a protection group linked to a plan that uses the locked storage.

Disabling it requires multi-person authorization:

  • An administrator opens the storage resource, selects Manage Compliance Lock, gives a reason and submits the request.
  • The status becomes Disablement pending.
  • Authorized approvers get an email and a Commvault notification. They approve or deny the request in Command Center.
  • Approval changes the status to Disabled. Denial leaves it Enabled.

This is good ransomware hygiene, because an attacker with stolen admin credentials can't quietly shorten retention or wipe backups. It also means mistakes are sticky. A badly chosen storage or retention design can't be tidied up on a Friday afternoon. Set retention and plan structure deliberately before you create locked storage. Make sure the approvers who can lift the lock are named and reachable.

Analysis: who should care​

This looks most relevant for organizations that already use Commvault, or that want Commvault's controls while keeping Azure-native resource management and consolidated billing. Whether it beats Azure Backup depends on your needs, and Microsoft doesn't offer a comparison. This is my own reading, not a Microsoft claim. The VM-only scope, the multi-step identity setup and the split between portal and Command Center are the main limits. Another point favors it. Using managed identity and Entra group mapping fits existing Azure governance, rather than adding a separate credential model.

Microsoft says it has worked with Commvault for more than 25 years. It ties this launch to its 2026 Azure Storage outlook, which described co-engineered partner solutions. The quote from Commvault's Chief Product Officer, Rajiv Kottomtharayil, is a vendor statement. It isn't independent evidence of recovery speed or reliability.

Practical checklist before piloting​

  • Confirm your subscription can buy the Commvault Marketplace offer.
  • Line up tenant admin consent for the Commvault SSO app.
  • Create and assign the CVBackupRole-VMs-LIFTR.json custom role to the managed identity.
  • Define Entra groups for Backup Administrator, Operator and User.
  • Decide storage class, retention and Compliance Lock policy up front.
  • Run Backup now on a test group, and rehearse a restore to a new VM.
  • Ask Commvault and Microsoft about pricing, regions and the AKS timeline.

In short, this is a real, documented option for Azure VM backup, with sensible identity design and strong immutability defaults. It isn't yet a broad Azure workload protection platform. Test restores before you rely on it.


Correction (November 18, 2026): The setup steps named the role-definition file CVbackup.json. The file Commvault documents is CVBackupRole-VMs-LIFTR.json. Both references have been corrected.

 

References

  1. Azure Native Commvault Cloud is now generally available Azure Storage Blog 2026-11-18T13:00:00+00:00
  2. Azure Native Commvault Cloud is now generally available | Microsoft Community Hub techcommunity.microsoft.com
  3. Configure Azure Native Commvault Cloud service - Azure Native Integrations | Microsoft Learn learn.microsoft.com