Skip to content

Update allowed values and default values to title case to match the p… #296

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.

Sign up for GitHub

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

Closed
jeevanions wants to merge 1 commit into from
Closed

Update allowed values and default values to title case to match the p… #296

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 13 additions & 16 deletions ...alz/policy_set_definitions/Enforce-Encryption-CMK_20250218.alz_policy_set_definition.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,11 +85,11 @@
},
"CosmosCMKEffect": {
"allowedValues": [
"audit",
"deny",
"disabled"
"Audit",
"Deny",
"Disabled"
],
"defaultValue": "deny",
"defaultValue": "Deny",
"metadata": {
"description": "Use customer-managed keys to manage the encryption at rest of your Azure Cosmos DB. By default, the data is encrypted at rest with service-managed keys, but customer-managed keys (CMK) are commonly required to meet regulatory compliance standards. CMKs enable the data to be encrypted with an Azure Key Vault key created and owned by you. You have full control and responsibility for the key lifecycle, including rotation and management. Learn more about CMK encryption at https://aka.ms/cosmosdb-cmk.",
"displayName": "Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest"
Expand Down Expand Up @@ -123,10 +123,10 @@
},
"HealthcareAPIsCMKEffect": {
"allowedValues": [
"audit",
"disabled"
"Audit",
"Disabled"
],
"defaultValue": "audit",
"defaultValue": "Audit",
"metadata": {
"description": "Use a customer-managed key to control the encryption at rest of the data stored in Azure API for FHIR when this is a regulatory or compliance requirement. Customer-managed keys also deliver double encryption by adding a second layer of encryption on top of the default one done with service-managed keys.",
"displayName": "Azure API for FHIR should use a customer-managed key (CMK) to encrypt data at rest"
Expand Down Expand Up @@ -184,11 +184,11 @@
},
"StreamAnalyticsCMKEffect": {
"allowedValues": [
"audit",
"deny",
"disabled"
"Audit",
"Deny",
"Disabled"
],
"defaultValue": "deny",
"defaultValue": "Deny",
"metadata": {
"description": "Use customer-managed keys when you want to securely store any metadata and private data assets of your Stream Analytics jobs in your storage account. This gives you total control over how your Stream Analytics data is encrypted.",
"displayName": "Azure Stream Analytics jobs should use customer-managed keys to encrypt data"
Expand Down Expand Up @@ -242,11 +242,8 @@
"botServiceCmk": {
"allowedValues": [
"Audit",
"audit",
"Deny",
"deny",
"Disabled",
"disabled"
"Disabled"
],
"defaultValue": "Deny",
"type": "string"
Expand Down Expand Up @@ -685,4 +682,4 @@
"policyType": "Custom"
},
"type": "Microsoft.Authorization/policySetDefinitions"
}
}