Skip to content

Clarify tenant ID requirement in get-token documentation#640

Merged
nchapagain001 merged 2 commits intousers/nchapagain/Feature_Enable_KV_AccessTokenfrom
copilot/sub-pr-613-another-one
Feb 13, 2026
Merged

Clarify tenant ID requirement in get-token documentation#640
nchapagain001 merged 2 commits intousers/nchapagain/Feature_Enable_KV_AccessTokenfrom
copilot/sub-pr-613-another-one

Conversation

Copy link

Copilot AI commented Feb 13, 2026

The get-token command documentation stated "VC will extract key vault uri and tenant ID", implying automatic discovery. The tenant ID must be explicitly provided by the user as a URI query parameter.

Changes

  • Updated note to clarify tenant ID must be included in Key Vault URI as query parameter (?tid=<tenant-id>)
  • Changed "extract" to "parse" to accurately describe VC's behavior

Before

* Note: VC will extract key vault uri and tenant ID to authenticate and retrieve a token for the current user.

After

* Note: The tenant ID must be included in the Key Vault URI as a query parameter (e.g., `?tid=<tenant-id>`). VC will parse the URI to authenticate and retrieve a token for the current user.

This aligns the documentation with the examples showing ?tid=... in the URI.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: nchapagain001 <165215502+nchapagain001@users.noreply.github.com>
Copilot AI changed the title [WIP] Update to address feedback on enabling get-token and bootstrap features Clarify tenant ID requirement in get-token documentation Feb 13, 2026
Copilot AI requested a review from nchapagain001 February 13, 2026 18:15
@nchapagain001 nchapagain001 marked this pull request as ready for review February 13, 2026 18:16
@nchapagain001 nchapagain001 merged commit e54ecff into users/nchapagain/Feature_Enable_KV_AccessToken Feb 13, 2026
1 check passed
@nchapagain001 nchapagain001 deleted the copilot/sub-pr-613-another-one branch February 13, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants