Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Azure Policy] - Update to Policy Definition breaks Enforce-Encryption-CMK Policy Set #959

Open
2 tasks done
tulpy opened this issue Feb 18, 2025 · 1 comment · May be fixed by #957
Open
2 tasks done

[Azure Policy] - Update to Policy Definition breaks Enforce-Encryption-CMK Policy Set #959

tulpy opened this issue Feb 18, 2025 · 1 comment · May be fixed by #957
Labels
Area: Policy 📝 Issues / PR's related to Policy Needs: Upstream Policy Changes 🔃 Upstream ESLZ repo policy changes required Status: In PR 👉 This is when an issue is due to be fixed in an open PR

Comments

@tulpy
Copy link

tulpy commented Feb 18, 2025

What happened? Provide a clear and concise description of the bug, including deployment details.

Looks like there was a major version update to Policy Definition Azure AI Search services should use customer-managed keys to encrypt data at rest (76a56461-9dc0-40f0-82f5-2453283afa2f) from 1.0.0 to 2.0.0

https://www.azadvertizer.net/azpolicyadvertizer/76a56461-9dc0-40f0-82f5-2453283afa2f.html

Image

There is a change to the default value and allowed values for the definition that now breaks the PolicySet definition.

Line 227 - https://github.com/Azure/ALZ-Bicep/blob/main/infra-as-code/bicep/modules/policy/definitions/lib/policy_set_definitions/policy_set_definition_es_Enforce-Encryption-CMK.json

Image

Please provide the correlation id associated with your error or bug.

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

What was the expected outcome?

The policy set definition should deploy but fails as the "Deny" default value isn't an allowed value.

Relevant log output

Check previous GitHub issues

  • I have searched the issues for this item and found no duplicate

Code of Conduct

  • I agree to follow this project's Code of Conduct
@oZakari
Copy link
Contributor

oZakari commented Feb 18, 2025

Hi @tulpy, thanks for calling this out and for including all of the details! I have included the update in #957

FYI: @Springstone

@oZakari oZakari added Area: Policy 📝 Issues / PR's related to Policy Needs: Upstream Policy Changes 🔃 Upstream ESLZ repo policy changes required labels Feb 18, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the Status: In PR 👉 This is when an issue is due to be fixed in an open PR label Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Policy 📝 Issues / PR's related to Policy Needs: Upstream Policy Changes 🔃 Upstream ESLZ repo policy changes required Status: In PR 👉 This is when an issue is due to be fixed in an open PR
Projects
None yet
2 participants