microsoft / microsoft/AzureStorageExplorer
Cross-Tenant managed disk copy doesn't keep NVMe
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100