Document low priority VM retirement and Spot-backed pricing in cost article - #806
Open
rmaziarka wants to merge 1 commit into
Open
Conversation
…rticle Low-priority VMs were retired for Azure Machine Learning on March 31, 2026 and their nodes are now allocated as Spot VMs. Update the cost-optimization guidance to describe variable Spot pricing instead of a fixed discount, add a retirement note, and clarify eviction and max-price behavior. Mirrors the correction made in PR MicrosoftDocs#791 for how-to-use-low-priority-batch.md.
Contributor
|
@rmaziarka : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
@rmaziarka : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit 910a942: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
|
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This is the follow-up to #791, which I mentioned there.
That PR corrected the low priority VM description in
how-to-use-low-priority-batch.md; this one applies the same correction to the related page, Manage and optimize Azure Machine Learning costs (how-to-manage-optimize-cost.md), which described low priority the same (now outdated) way.The Use low-priority virtual machines section still said the allocations "come at a reduced price compared to dedicated VMs." Since low-priority VMs were retired for Azure Machine Learning on March 31, 2026 and their nodes are now allocated as Spot VMs, that fixed-discount framing is no longer accurate.
Changes
[!IMPORTANT]note about the March 31, 2026 retirement and the system-initiated migration to Spot VMs.ms.date.I kept the wording aligned with #791 so the two articles stay consistent.