Panagiotis Korologos

Have done some work around this topic; feel free to take a look [ESLZcustomRBAC.zip](https://github.com/Azure/Enterprise-Scale/files/6125981/ESLZcustomRBAC.zip)

@Mahesh-MSFT currently the custom role definitions (could) be virtually part of the reference implementation, but this is a parallel discussion going on right now afaik. From my side, I have...

Please see below: a. the fact that now the Policy is called "Auditing on SQL server should be enabled", does not alter the situation that this is _still_ AINE (audit)...

The one referred here "f4c68484-132f-41f9-9b6d-3e4b1cb55036" unfortunately targets storage account as output, not LA workspace.

@mrajess : 1. I will have to partially correct myself (and you), on my (b) statement, a couple of days ago: eventually the _new_ (built-in) policy (**b79fa14e-238a-4c2d-b376-442ce508fc84** for SQL db...

do you know where should we escalate the built-in (b79fa14e-238a-4c2d-b376-442ce508fc8) policy issue to be fixed?

further details: 1. the problematic Policy (actually Initiative) is the "Configure Azure PaaS services to use private DNS zones"; I tested _only_ with storage accounts, not other PaaS Services, but...

Hello @jtracey93 Indeed, some months back when I was doing some testing, the custom initiative then called "Configure Azure PaaS services to use private DNS zones" (definition: /providers/Microsoft.Management/managementGroups//providers/Microsoft.Authorization/policySetDefinitions/Deploy-Private-DNS-Zones ), which...

Closing - fixed via PR mentioned above.

As is, the documented process for restoring System State from local path, does not work.