Skip to content

Document InformationDisabled feedback group policy for SSMS#47

Closed
cdblake1 wants to merge 1 commit into
MicrosoftDocs:mainfrom
cdblake1:dev/cdblake1/feedback-information-policy
Closed

Document InformationDisabled feedback group policy for SSMS#47
cdblake1 wants to merge 1 commit into
MicrosoftDocs:mainfrom
cdblake1:dev/cdblake1/feedback-information-policy

Conversation

@cdblake1

Copy link
Copy Markdown

Adds the new InformationDisabled feedback group policy to the Configure feedback group policies for SQL Server Management Studio article.

This machine policy lets administrators disable informational announcements shown via info bars. It's read from the shared HKLM\SOFTWARE\Policies\Microsoft\VisualStudio\Feedback\InformationDisabled registry value (same Feedback category as SurveysDisabled / ProductFeedbackDisabled). The matching VS ADMX/ADML entry is in microsoft/Visual-Studio-Administrative-Templates#186 and the VS docs row is in MicrosoftDocs/visualstudio-docs#11382.

For reviewers: the policy gating shipped in the Visual Studio 2026 (18.x) shell, so I noted "SSMS releases based on Visual Studio 2026 or later." Please confirm/adjust the exact minimum SSMS version that includes it, since I don't have the SSMS-to-VS version mapping.

Adds the InformationDisabled policy to the SSMS feedback group policies
table. This machine policy disables informational announcements shown via
info bars, and is read from the shared
HKLM\Software\Policies\Microsoft\VisualStudio\Feedback\InformationDisabled
registry value. The gating shipped in the Visual Studio 2026 (18.x) shell.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@v-regandowner

Copy link
Copy Markdown
Contributor

@rwestMSFT

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds documentation for the new InformationDisabled feedback group policy in the SSMS group policy article so administrators can understand and deploy it alongside existing feedback-related policies.

Changes:

  • Updates the supported policies section intro text.
  • Adds a new table row documenting the InformationDisabled policy and its behavior.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

| --- | --- |
| `SurveysDisabled` | Controls whether the user receives survey links in SSMS. If enabled, SSMS and the Visual Studio Installer don't display any product survey requests or links to surveys to the user. |
| `ProductFeedbackDisabled` | Controls whether the user can submit feedback through SSMS. If enabled, SSMS and the Visual Studio Installer don't allow users to submit feedback to Microsoft. Examples include, but aren't limited to reporting feedback, submitting suggestions, and providing feedback on features via a thumbs up/down control. |
| `InformationDisabled` | Controls whether the user receives informational announcements in SSMS. If enabled, SSMS and the Visual Studio Installer don't display informational announcements via info bars, such as general product announcements or notices. This policy applies to SSMS releases based on Visual Studio 2026 or later. |
@rwestMSFT

Copy link
Copy Markdown
Contributor

Investigating. Thank you for the contribution.

@cdblake1

cdblake1 commented Jul 1, 2026

Copy link
Copy Markdown
Author

Closing this one. Per the docs team, this change belongs in the private MicrosoftDocs/data-tools-pr repo (preferred for employee documentation changes), so I'll recreate it there. Thanks!

@cdblake1 cdblake1 closed this Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants