Improve Tags/deny-resource-without-tag: add empty-value check, excludedResourceTypes param, and description#538
Merged
neiichango merged 2 commits intoJul 16, 2026
Conversation
…, excludedResourceTypes param
Contributor
Author
|
@microsoft-github-policy-service agree |
Joshua-Donovan
requested changes
Jul 15, 2026
hendersonandrade
left a comment
Contributor
Author
There was a problem hiding this comment.
fix implemented as suggested
Collaborator
|
Reviewed to confirm correct policy design. |
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.
Summary
Improves the existing
Tags/deny-resource-without-tagpolicy definition. This is an in-place update (same policynameGUID12dc4dea-6097-4a18-b24e-a9a3e00dd456), not a new policy, so existing assignments continue to work.What changed
"need to add description"with a meaningful description of the policy behavior.equals ""), in addition to the previous "tag does not exist" check. Previously a resource with an empty tag value passed compliance.excludedResourceTypesparameter (Array,strongType: ResourceType, default[]): allows excluding resource types that don't support tags, without editing the policy. More flexible than hardcoding exclusions.allof→allOfcasing in the policy rule.1.0.0→1.1.0(added functionality, backward compatible — the new parameter defaults to an empty array).Backward compatibility
excludedResourceTypesparameter has a default value ([]), so existing assignments are unaffected.effectdefault remainsAudit.Validation
Validated with the repository's own script: