Built in Policy is Not working as expected. Policy Name is 'Require encryption on Data Lake Store accounts' with Deny effect

Manikanta 1 Reputation point
2020-11-12T06:24:40.873+00:00

Policy is not working as expected because if we already creates a data lake storage accounts but the resource showing in compliant state even the encryption and firewall properties are not enabled. even i created and tried with Audit and AINE effect but then also not working as expected.

Azure Data Lake Storage
Azure Data Lake Storage
An Azure service that provides an enterprise-wide hyper-scale repository for big data analytic workloads and is integrated with Azure Blob Storage.
1,374 questions
Azure Policy
Azure Policy
An Azure service that is used to implement corporate governance and standards at scale for Azure resources.
807 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SwathiDhanwada-MSFT 18,031 Reputation points
    2020-11-26T13:00:36.003+00:00

    Generally, for the deny or audit evaluation, Azure policy will trigger the List Collection REST API to detect current status of resources. If we check the response body of the List API, the object does not contain any property like firewallState or encryptionState so that the Policy Rule will not be evaluated ever.

    According to the confirmation of ADLS Gen 1 product group, this is by design. Considering that the ADLS Gen 1 is sunsetting, there is currently no plan to fix the gap(with GET REST API).

    Workaround : We may consider using ADLS Gen2(latest version of Storage Account) for the long term. ADLS Gen2 REST API which is actually the latest version of Azure Storage Service can be evaluated by following policy rule:

    "policyRule": {  
        "if": {  
            "allOf": [{  
                    "field": "type",  
                    "equals": "Microsoft.Storage/StorageAccounts"  
                }, {  
                    "field": "Microsoft.Storage/storageAccounts/encryption.services.blob.enabled",  
                    "equals": "true"  
                }  
            ]  
        },  
        "then": {  
            "effect": "audit"  
        }  
    }  
    }  
    

    Thanks @Manikanta for the sharing the support ticket number. Sharing the resolution for the benefit of broader community.

    0 comments No comments