README: upgrade Public Preview note to GitHub admonition + status badge + link Azure Preview Terms#88
Merged
Conversation
… link to Azure Preview Terms
Three small, README-only changes to make the preview status more
discoverable and legally sourced:
1. Add a 'Status: Public Preview' shields.io badge under the H1
linking to the Azure Preview Supplemental Terms. Matches the
convention used by other Microsoft OSS repos in the same lifecycle
stage and makes the project's pre-GA state visible without scrolling.
2. Upgrade the existing plain blockquote ('> **Public preview.** ...')
into a GitHub [!IMPORTANT] admonition. Renders as a colored callout
on GitHub.com so readers cannot miss it; degrades gracefully to a
plain quote in any markdown renderer that doesn't support
admonitions.
3. Link the admonition body to the canonical Azure Preview
Supplemental Terms page
(https://azure.microsoft.com/support/legal/preview-supplemental-terms/),
which is what Microsoft's Product Terms — Universal License Terms
for Online Services — references for the 'Previews' clause:
provided 'as-is', excluded from SLA and warranties, support not
guaranteed. This way the README's preview claim is sourced rather
than just asserted.
Wording tightened slightly: 'Interfaces, configuration, and tool
behavior may change without notice' becomes 'APIs, configuration,
environment variables, and tool behavior may change in breaking ways
before General Availability' — same intent, but explicit about
'environment variables' (because the server's user-facing surface is
substantially env-driven: AUTH_REQUIRED, TRUST_LOCAL_STDIO, ENABLE_*,
CONNECTION_PROFILES, etc.), and explicit about 'breaking ways before
General Availability' which is the canonical Azure preview-lifecycle
language.
README-only; no source / test / behavior changes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
khelanmodi
approved these changes
May 29, 2026
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.
What
Three small, README-only changes to make the project's Public Preview status more discoverable and legally sourced. No code, test, or behavior changes.
Diff
Why each change
1. Add a
Status: Public Previewbadge under the H1Shields.io badge linking to the Azure Preview Supplemental Terms. Matches the convention used by other Microsoft OSS repos in the same lifecycle stage and makes the project's pre-GA state visible without the reader scrolling past install buttons.
2. Upgrade the blockquote to a GitHub
[!IMPORTANT]admonitionThe existing line:
> **Public preview.** This server is in public preview. Interfaces, configuration, and tool behavior may change without notice. Do not use it in production without your own review.…is a plain blockquote that renders as a thin gray bar with no color emphasis. Wrapping it as
> [!IMPORTANT]makes GitHub.com render a colored callout that readers cannot miss; in any markdown renderer that doesn't support admonitions it degrades cleanly to a plain blockquote.3. Link the canonical legal source
Microsoft Product Terms — Universal License Terms for Online Services — Previews — covers: "Previews are provided 'as-is', 'with all faults' and 'as available' and are excluded from the SLA and all limited warranties… Previews may not be covered by customer support."
That clause is the authoritative source for what "Public Preview" actually obliges (and doesn't oblige) Microsoft to. Linking the Azure Preview Supplemental Terms makes the README's preview claim sourced rather than asserted, so a reader can read the actual terms one click away.
Wording change (small)
Interfaces, configuration, and tool behavior may change without noticeAPIs, configuration, environment variables, and tool behavior may change in breaking ways before General AvailabilitySame intent, but:
environment variables— the server's user-facing surface is substantially env-driven (AUTH_REQUIRED,TRUST_LOCAL_STDIO,ENABLE_*,CONNECTION_PROFILES, etc.), and env-var renames have already happened during preview (e.g., theALLOW_UNAUTHENTICATED_STDIO→TRUST_LOCAL_STDIOrename in add default connection profile and stdio rate limit #83), so calling them out by name as a category that may break is honest;in breaking ways before General Availabilityis the canonical Azure preview-lifecycle phrasing and pairs cleanly with the supplemental-terms link.Also added an explicit "There is no SLA" sentence — implicit in the supplemental terms but worth saying once at the top.
Scope
README-only; no source / test / behavior changes.
git diff --stat:Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com