Repository navigation
[docs-vnext] docs: align vNext capability settings guidance - #1050
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
This pull request was automatically closed because it expired on 2026-10-03T19:06:29.382Z.
|
auto-merge was automatically disabled
October 3, 2026 21:42
Pull request was closed
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.
Overview
Aligns the customized vNext Agent Service documentation with the capability-settings terminology introduced by sync commit
c7c2a3e.Changes
docs-vnext/agents/development/capability-hosts.mdxanddocs-vnext/agent-service/capability-hosts.mdx: add a visible note that capability settings supersede capability hosts for declaring agent storage resources while retaining the legacy article as reference.docs-vnext/agents/development/faq.mdxanddocs-vnext/agent-service/faq.mdx: replace legacy capability-host setup guidance with account/project capability settings guidance.docs-vnext/agent-service/migrate-hosted-agent-preview.mdx: clarify where hosted-agent storage resources are now declared.Microsoft Learn comparison
documentStore,vectorStore, andblobStoreas account defaults with project inheritance or overrides. The vNext wording adopts that model without duplicating the full reference.2026-07-15-preview; the vNext migration summary links to the canonical configuration guide for current prerequisites and regional availability.The synced CLI infrastructure page has no vNext counterpart, the condensed limits pages omit the changed storage section, and both vNext quota variants already contain the corrected per-region subscription scope.