Skip to content

Conversation

@chiefabel7
Copy link

No description provided.

@prmerger-automator
Copy link
Contributor

@chiefabel7 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit a564820:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/sizes/general-purpose/dldsv6-series.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

Hi @chiefabel7 - Did you intend to open this in the private repo (azure-docs-pr)? This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!


@mattmcinnes

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Dec 18, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Live Migration feature support status for Dldsv6 series virtual machines from "Not Supported" to "Supported", reflecting a change in the capabilities of this VM series.

  • Updates Live Migration support documentation status to "Supported"

@chiefabel7
Copy link
Author

Hi @chiefabel7 - Did you intend to open this in the private repo (azure-docs-pr)? This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

@mattmcinnes

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

Sorry about that I should have double checked. Will keep that in mind

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants