Repo sync for protected branch#11336
Merged
learn-build-service-prod[bot] merged 7 commits intoMay 11, 2026
Merged
Conversation
This PR modernizes the Visual Studio cloud subscriptions billing FAQ to improve clarity, accuracy, and alignment with current Azure and Visual Studio subscription guidance. Key updates include: - Updated intro to reflect Azure as the billing model and added pricing comparison link - Clarified supported Azure subscription types and removed outdated or redundant wording - Removed references to the deprecated Azure Enterprise portal and updated guidance to use the Azure portal - Added guidance for contacting subscription admins, including the "Contact my Admin" Learn article - Improved billing and invoice guidance with direct Azure documentation links - Clarified Azure DevTest credit limitations for purchases - Updated annual subscription messaging to reflect current availability (no longer offered for new purchases) - Simplified and modernized cancellation and billing behavior explanations, including removing outdated date examples - Improved consistency, tone, and readability across all FAQ sections (Acrolinx-aligned) - Cleaned up metadata (title typo fix and updated date) - Updated "See also" section to include more relevant resources No changes were made to core billing logic or pricing behavior.
Fix incorrect documentation links in subscriptions/vscloud-billing-faq.yml. Replaced references to the old understand-azure-invoice path with the canonical understand-invoice URL (and added the en-us locale for the See also entry) for the billing/usage and See also sections.
Minor copy edits in subscriptions/vscloud-billing-faq.yml: add terminal periods to bullet items, adjust the ordering/phrasing of subscription names in the NOTE, and remove an extraneous colon after the discount sentence to improve clarity and readability.
Normalize capitalization of 'Cloud Subscriptions' across the billing FAQ file. Updated metadata title, article title, summary, questions, and answers to use 'Visual Studio Cloud Subscriptions'; adjusted a few related resource/link texts and minor phrasing (e.g., 'Visual Studio Subscriptions portal'). No functional changes to content, only editorial/consistency edits.
…-content Modernize Visual Studio cloud subscriptions billing FAQ
Auto Publish – main to live - 2026-05-11 16:00 UTC
Contributor
Author
|
Learn Build status updates of commit d3e6827: ✅ Validation status: passedFor more details, please refer to the build report. |
Contributor
PRMerger Results
|
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
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.
Learn Build Service tried pushing to main, but failed due to branch protection rule in this branch. We create this pull request for manual merge. Please merge this pull request to complete this sync.
If you want to make push successfully without creating such pull requests in future, please follow working with branch protection rule to update your branch protection rule.