Azure-docs: Azure Policy Regulatory Compliance controls for Azure Data Lake Storage Gen2 - not working

Created on 13 Oct 2020  Â·  9Comments  Â·  Source: MicrosoftDocs/azure-docs

Hi, i am CSS dev support engineer working for a cx case.

Cx is following the below documentation - https://docs.microsoft.com/en-us/azure/storage/blobs/security-controls-policy#hipaa-hitrust-92 for setting diagnostic logs audit policy on ADLS gen2 storage account.

while using the below template , it is working for gen1 account only for the Cx, but the public documentation states that it is for Gen2 - "Azure Policy Regulatory Compliance controls for Azure Data Lake Storage Gen2"

https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/Data%20Lake/DataLakeStore_AuditDiagnosticLog_Audit.json

Cx - " When we applied the built in policy mentioned in the json ,the policy is only showing compliance checkup for Gen1 resource.
The json file contains the policy rule as below. Here resource showing as "Microsoft.DataLakeStore/accounts" but for gen2 it is a storage account. Please clarify."

"policyRule": {
  "if": {
  "field": "type",
  "equals": "Microsoft.DataLakeStore/accounts"
  },


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri2 assigned-to-author data-lake-storage-gensubsvc doc-bug in-progress storagsvc triaged

All 9 comments

@vsriram-binary Thanks for the question! We are investigating and will update you shortly.

@DCtheGeek can you help with this? I'm unfamiliar with these controls.

@normesta The list is everything that maps to Azure Policy Regulatory Compliance for the Microsoft.DataLakeStore RP. If that RP covers both "Gen1 and Gen2" or "only Gen1" we should probably update both the title of the page itself to properly reflect that as well as enhance the description of the definition itself. I'll start an internal email and add you to it.

Ok thank you @DCtheGeek! I'll await final confirmation. @vsriram-binary - we will keep you updated with what we learn. Thank you for raising this to our attention!

@vsriram-binary We've confirmed that Microsoft.DataLakeStore RP is for Gen1, so this is both in the wrong TOC and has the wrong title. I've submitted a PR to fix both issues. Once that PR is merged, this issue will automatically close. Publish to live will occur later. Thank you for pointing this out!

@MicrosoftDocs/azure-cxp-triage Please remove label 'product-issue' and add label 'doc-bug'. #in-progress

Thank you @DCtheGeek for the update. So for Customer's ask on diagnostic logs audit template for ADLS gen2 storage accounts - is it available?

@v-albemi Hi, can i know why this request is closed ? i was expecting a response from @DCtheGeek . Please advise.

@vsriram-binary

It appears that I merged the pull request, but it’s actually the commit that was merged in a different pull request. My understanding is that the commit exists in at 2 least PRs, and it was merged in one of the PRs that was signed off. (In MicrosoftDocs/azure-docs-pr#134207)

This is a GitHub technical issue and not something that PR reviewers can manually watch for or prevent, unfortunately. And I don't have a complete grasp of the situation. The solution might be to be careful to work on an article in only one working branch, one level down from master. If you need more technical help with this, the best place to go is the Docs Support channel in Teams

Thanks

@vsriram-binary Sorry! I didn't see your follow-up question and the PR I created was set to automatically close this GitHub Issue. @v-albemi _appears_ to have closed it, but that's because he merged my commit. :)

This issue should be closed as the incorrect page was updated, moved, and clarified to be specific to Gen1. If a built-in policy definition for Azure Storage does exist, it'll be documented in one of these places:

If the built-in doesn't exist, the recommendation is to build a custom definition. This tutorial is the best place to start. Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ianpowell2017 picture ianpowell2017  Â·  3Comments

Ponant picture Ponant  Â·  3Comments

monteledwards picture monteledwards  Â·  3Comments

AronT-TLV picture AronT-TLV  Â·  3Comments

JeffLoo-ong picture JeffLoo-ong  Â·  3Comments