About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A vendor saying its software is "not supported on virtual machines" can mean several different things: it has never tested virtual machines, it supports them only on named platforms, it will help but may ask you to reproduce a fault outside your virtual platform, or it genuinely refuses. Ask the vendor for its written support statement naming the hypervisor and version you plan to use, and read exactly what it covers before deciding.
Why it matters
Moving an application to hosted virtual servers without checking support can leave a business stuck when something breaks: the vendor declines the call, and nobody else knows the application. Equally, a vague "we don't support VMs" said on a phone call can stop a sensible move that the vendor's own written policy would allow. The written wording is what counts.
How it works
Unsupported, untested and conditionally supported
These words are not the same:
- Untested means the vendor has not checked the configuration. It may still work, but untested is an absence of validation, not a promise of help; whether the vendor will help depends on its written support policy.
- Conditionally supported means the vendor supports the platform with limits, such as named hypervisors, versions or features.
- Unsupported means the vendor will not accept support cases for that configuration, or will accept them only on its own terms.
The distinctions above are editorial; the vendor's written policy defines what applies to you.
How Microsoft words it
Microsoft's own policies show how layered such statements can be. Its general policy states: "Except as described in this article, Microsoft does not test or support Microsoft software that's run in conjunction with non-Microsoft hardware virtualization software." The same article then describes support for vendors with "Server Virtualization Validation Program (SVVP) validated solutions", adding that "This support will include coordinating with the vendor to jointly investigate support issues."
It also sets limits. Microsoft "may still require the issue to be reproduced independently from the non-Microsoft hardware virtualization software", and features such as "memory over-commitment, moving virtual machines from one host system to another" are not supported by Microsoft under SVVP; the article says "The SVVP vendor is responsible for support of such features and functions."
Where Microsoft asks for a reproduction, "elsewhere" does not have to mean physical hardware. The page says it "can be done on Windows Server 2016 or later versions of the Windows Server operating system product with the Hyper-V role installed, the actual hardware platform with the Windows operating system installed directly upon it, or on both".
So one policy contains a general refusal, a validated-platform exception, a possible requirement to reproduce the fault elsewhere, and a split of responsibility between two vendors. These are Microsoft's policies for Microsoft's own software. They show how one large vendor words its position; other vendors, such as the makers of practice or accounting software, write their own, and SVVP validation is a Microsoft programme that says nothing about another vendor's support. Whether your provider's hypervisor and hardware are SVVP-validated is a question to put to the provider, with the listing to back it up; this article has not checked any platform against the list.
Product-specific rules
Individual products can add their own conditions. Microsoft's SQL Server virtualisation policy lists supported environments including "Configurations that are validated through the Server Virtualization Validation Program (SVVP)." It also notes that "The SVVP solution must be running on hardware that is certified for Windows Server version (currently in support lifecycle) to be considered a valid SVVP configuration." On backups, it states: "Virtual machine snapshots that do not use VSS volume snapshots are not supported by SQL Server."
That last line matters to a hosting decision: the way the host backs up virtual machines can affect database support, not only the hypervisor itself.
What to choose and why
What to ask the vendor
- Send the exact hypervisor name and version, the guest operating system and the database version.
- Ask for the written support statement or policy link, not a verbal answer.
- Ask whether support is full, conditional or "best effort", and what conditions apply.
- Ask whether they may require a fault to be reproduced outside your virtual platform (in Microsoft's case, on its own hypervisor or on physical hardware), and what happens if you cannot.
- Ask about features they exclude, such as live migration, snapshots or memory over-commitment.
- For Microsoft software, ask your hosting provider whether its hypervisor and hardware are SVVP-validated, and for the listing.
- Ask how many of their customers run the product virtualised; their answer is information, not a guarantee.
Reading the answer
| Vendor answer | What it can mean | Next step |
|---|---|---|
| Written support for your hypervisor and version | Supported, with any listed conditions | Record the document and its date |
| Supported only on named platforms | Conditional | Check your host's platform against the list |
| "Untested" or "best effort" | Not validated; any help depends on the written policy | Get the policy in writing; weigh the application's importance; plan a fallback |
| Written refusal | Unsupported | Consider dedicated hardware, another product, or accepting the risk knowingly |
The table is editorial guidance.
Illustrative example
An accounting firm's practice software vendor says on the phone that it does not support virtual machines. The firm asks for the written policy. It states support on two named hypervisors from listed versions, excludes snapshot-based backups without application-aware processing, and asks customers to reproduce suspected platform faults where possible. The firm confirms its host's platform is on the list and that backups are application-aware, then records the policy and date. The example is illustrative.
Read next
Related articles you may want next.
- HostingSupport boundary: your application versus the hosted OS and networkDefine who investigates and fixes faults across your software, hosting and customer systems, including guest OS patching and shared incident ownership.Read article
- Backup & RecoveryDomain Controllers on VMware: Snapshots and RestoresWhat VM-GenerationID protects when a virtual domain controller is reverted or restored, how USN rollback shows up, and when to call a directory specialist.Read article
- Backup & RecoveryVMware Snapshots vs Backups: A Practical Guide to RecoverabilityA practical guide to VMware snapshots, backups and recovery validation, focused on restoring business services and checking recovery dependencies.Read article
Risks and limits
- Policies change. Recheck the written statement before each major upgrade.
- Support is not compatibility. A supported configuration can still perform poorly if sized wrongly.
- Two vendors, two answers. Where faults sit between the application and the platform, agree in advance who leads; our published article Support boundary: your application versus the hosted OS and network covers that split. Our companion article on licences and subscriptions that must move when leaving a host covers a related check.
- This is not legal advice. Support terms sit in contracts; confirm with the vendor or an adviser.
Sources
Opened 15 November 2026; both Microsoft pages and the published article reopened 16 November 2026.
- Microsoft Learn: Support policy for Microsoft software that runs on non-Microsoft hardware virtualization software, KB 897615, page shows last updated 12 February 2026 (page metadata: modified 19 February 2026).
- Microsoft Learn: Support policy for Microsoft SQL Server products that are running in a hardware virtualization environment, page shows last updated 13 June 2024 (page metadata: modified 19 September 2025).
Related articles: Support boundary: your application versus the hosted OS and network; Domain Controllers on VMware: Snapshots and Restores; VMware snapshots vs backups: a practical guide to recoverability.
Related service: Cloud hosting.
Learning notes
- "Not supported on VMs" can mean untested, conditional or a genuine refusal.
- Ask for the written statement naming hypervisor and version.
- Microsoft's policy combines a general refusal with a validated-platform exception and conditions.
- Microsoft may ask for a reproduction on Hyper-V or physical hardware; its SVVP policy covers Microsoft software only.
- SQL Server's policy does not support VM snapshots that do not use VSS.
- Record the policy and its date; recheck before upgrades.
This article was originally published on .