Update note on Daldsv6 VM series naming - #501
Conversation
Clarified naming inconsistency for Daldsv6 VM series.
|
bhumika-dua : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
1 similar comment
|
bhumika-dua : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit ae681c7: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Clarifies the alternate Daldv6 naming used for the Daldsv6 VM family.
Changes:
- Adds a naming inconsistency note.
- Confirms VM capabilities remain unchanged.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| > [!NOTE] | ||
| > This VM series will only work on OS images that support NVMe. If your current OS image doesn't have NVMe support, you'll see an error message. [NVMe](../../../virtual-machines/enable-nvme-interface.md) support is available on the most popular OS images, and we're continuously improving OS image compatibility. | ||
| > | ||
| > Some Azure services may refer to this VM family as **Daldv6** rather than **Daldsv6**. This is a known naming inconsistency and does not affect VM capabilities, including Premium Storage support. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
Clarified naming inconsistency for Daldsv6 VM series.