Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cross-Tenant managed disk copy doesn't keep NVMe

Open
#9,127 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
azure
Domain
cloud

Research direction

Start by locating the cross-tenant managed disk copy entry point and tracing how disk attributes are transferred, especially the NVMe setting. Check for existing managed-disk copy tests; done means a copied disk preserves NVMe attributes and allows an NVMe-enabled VM to be created in the destination tenant.

Written by the indexing model from the issue text.

Description

Problem

Cross-Tenant managed disk copy doesn't keep NVMe. So, NVMe-enabled VMs cannot be created on the destination tenant's disk.

Desired Solution

I'd like to keep NVMe attributes even when copying between tenants.

Alternatives and Workarounds

No response

Additional Context

No response

Dominant language
No language data
Stars
452
Forks
92
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/AzureStorageExplorer

All issues in microsoft/AzureStorageExplorer

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.