How to configure Site Recovery on-premises VMware on Cosmos DB

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

Why this matters

Configure site recovery on-premises vmware on a Cosmos DB device is one of the highest-volume how-to searches for the Azure Enterprise category. Most users find the menu path inconsistent across Cosmos DB model revisions, so this guide gives a generalised path plus model-specific notes.

Pre-requisites

• A Cosmos DB device that's powered on and on the latest stable service version / OS.
• The Cosmos DB companion app or management tool installed and signed in.
• 5-15 minutes uninterrupted.

Step-by-step

1. Locate the setting. Open settings on your Cosmos DB device. For "configure Site Recovery on-premises VMware", the option lives under one of: General, Advanced, Connectivity, Accessibility, or a Cosmos DB-specific menu. Check the Cosmos DB user manual for your exact model if you can't find it.
2. Toggle the feature on. Confirm the on-screen prompt.
3. Configure sub-options. Most features have 2-3 sub-options (mode, schedule, paired device). Pick values that match your real-world usage pattern.
4. Save / apply. Some Cosmos DB models auto-save, others require an explicit Done / Save tap.
5. Test live. Trigger the feature in a real scenario to confirm the configuration is correct.

Tips that save time

• Pair this feature with a Cosmos DB automation / routine if the device supports it.
• If the feature relies on cloud sync, give it 1-2 minutes after enabling to propagate.
• For multi-user households / multi-admin teams, set per-user profiles so each user sees their preferred state.

Common gotchas

• Feature greyed out. usually service version too old. Update + retry.
• Feature works once then stops, battery saver / power saver mode is killing the Cosmos DB app process. Whitelist it.
• Feature works but with delay: usually cloud-sync latency; check internet speed and Cosmos DB service status.

Region / variant notes

Some Cosmos DB features are region-locked or only available on higher-tier SKUs. If your variant doesn't show "configure Site Recovery on-premises VMware" at all, check the Cosmos DB model spec sheet to confirm support.

Frequently asked questions

How long should the recovery / setup take?

For most Cosmos DB Azure Enterprise cases, allow 15-45 minutes the first time. Repeats are usually under 10 minutes once you know the menu path.

Will this exact procedure work on every Cosmos DB model?

The procedure reflects current Cosmos DB behaviour. Menu paths shift between service version generations; verify against the manual for your specific model + revision.

Is the procedure safe in production / live use?

Apply during a maintenance window where possible. Capture pre-change state. Cosmos DB doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my Cosmos DB support coverage?

Standard operation per the user manual + applying official service version updates does NOT void support coverage. Opening managed services, third-party repair, or unauthorised modifications can void support coverage, check before going further.

Related guides

• All Azure Enterprise guides → /microsoft/section/azure_enterprise.html
• All Microsoft guides → /microsoft/

Related fixes

Related guides worth a look while you sort this one out:

• How to configure Site Recovery on-premises VMware on AKS
• How to configure Site Recovery on-premises VMware on Application Gateway
• How to configure Site Recovery on-premises VMware on Azure AI Search
• How to configure Site Recovery on-premises VMware on Azure Arc
• How to configure Site Recovery on-premises VMware on Azure Backup
• How to configure Site Recovery on-premises VMware on Azure Firewall

References

• Cosmos DB official support portal for your model.
• Cosmos DB community forum + Reddit threads.
• Vendor PSIRT / advisory page (where applicable).

Reference material, not professional advice. Validate with your vendor manual and follow local regulations.

What changed recently?

Fault diagnosis on this hardware goes faster when you map the symptom to a recent change:

• Did service version update in the last 7 days?
• Did the network (router, ISP, VPN) change?
• Was the device moved physically?
• Did paired devices (phone, hub, app) update?
• Were any accessories swapped in or out?

The answer narrows the root cause to a manageable subset.

Before you start

A few things to confirm so the affected device fix goes cleanly:

• Latest service version downloaded if you're going to update.
• support coverage + support contract status checked. opening managed parts may void it.
• Backup of current configuration (where applicable) taken.
• Spare parts on hand if you anticipate replacement.
• Adequate workspace, lighting, and time, rushing causes regressions.

How to confirm it's actually fixed

On the device in front of you, the test is rarely "reboot and see". Use this list:

• Active reproduction: trigger the original failure path on purpose.
• Indirect reproduction: do an activity that would expose the same subsystem.
• Status indicator review: every service health indicator / display / app status should be green.
• 24-hour soak: leave the device under normal load overnight; check the next morning.
• Telemetry check: review the device or app's diagnostic log for new error entries.

When to call How support instead

Escalate if:

• The same symptom returns within 24 hours of a clean fix.
• You see physical damage (burn marks, swollen battery, cracked PCB).
• The device is in support coverage and a hardware replacement is the cheaper outcome.
• Repair requires specialised tools you don't own (alignment jigs, calibration software).
• Following the official path keeps the support coverage intact, which matters more than the time spent.

More frequently asked questions

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Are there safer alternatives for non-technical users?

Yes: the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major service version generations sometimes shift the menu path; the option is usually under a similarly-named section.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent service version update (rollback).

How long does this fix usually take?

Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.

Field notes from real Azure Enterprise incidents

When I work on configure Site Recovery on-premises VMware on Cosmos DB the rhythm I lean on is the one I have built over years of these tickets. I have lost more hours to Azure Resource Graph queries than I would like to admit, but the alternative, clicking through the portal hoping the right blade loads. is worse. Activity Log is the first place I open on any Azure regression because the operation that flipped the state is usually right there at the top of the list. When a customer says 'Azure broke', the answer is almost always either RBAC propagation lag or a quota that quietly tightened on a region they did not check.

Tools I actually reach for

For configure Site Recovery on-premises VMware on Cosmos DB on Cosmos DB the cheapest signal I can land usually comes from Azure Portal Resource Explorer, then Azure Activity Log, Azure Advisor when Azure Portal Resource Explorer cannot see the layer the fault sits in, and kubectl (for AKS) for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.

Verification I run before I close the ticket

Before I mark configure Site Recovery on-premises VMware on Cosmos DB resolved on a Cosmos DB unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.

az resource list --resource-group RG --query "[].{name:name,type:type}" -o table

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

az network watcher test-connectivity --source-resource VM1 --dest-resource VM2

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

az account show --query '{sub:id,tenant:tenantId}' -o table

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

az aks browse --resource-group RG --name CLUSTER  # verify dashboard reachable

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Azure Enterprise detail, the disambiguation order I lean on is stable. I usually start at learn.microsoft.com/azure for the ground-truth view on Azure Enterprise. I usually start at azurecharts.com for the ground-truth view on Azure Enterprise. I usually start at github.com/Azure for the ground-truth view on Azure Enterprise. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on configure Site Recovery on-premises VMware on Cosmos DB have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Cosmos DB unit, not things I read about. When a customer says 'Azure broke', the answer is almost always either RBAC propagation lag or a quota that quietly tightened on a region they did not check. I have lost more hours to Azure Resource Graph queries than I would like to admit, but the alternative, clicking through the portal hoping the right blade loads: is worse. Network Watcher's connectivity check has saved me from blaming Azure when the problem turned out to be a stale NSG rule someone left behind from a pilot. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand configure Site Recovery on-premises VMware on Cosmos DB off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Cosmos DB on the Azure Enterprise family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For configure Site Recovery on-premises VMware on Cosmos DB on a Cosmos DB unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.