fix: Add CredScan suppression for DeviceManagement.Administration v1.0 example#3630
Merged
ramsessanchez merged 1 commit intoJun 2, 2026
Merged
Conversation
…0 example The Update-MgDeviceManagementVirtualEndpointOnPremiseConnectionAdDomainPassword.md example file contains a placeholder password that triggers CredScan. Added it to the suppressions list to match the existing pattern for similar example files. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
peombwa
approved these changes
Jun 1, 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
2 participants
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.
Summary
Adds a CredScan suppression entry for the v1.0 example file:
This file contains a placeholder password (\AdDomainPassword_XXXX) in its code snippet, which is not a real credential. The suppression follows the existing pattern used for similar example files (e.g., the beta counterpart under DeviceManagement.Actions).
Changes