dataCollectionRuleResourceId

[arrerezai]

Recent update (from two days ago) for the ALZ-Root-Default file now requires dataCollectionRuleResourceId. There is a description followed by a link, indicating there must be a DCR in place in Azure Monitor in order to fetch the resource ID from it. Since I had no DCR in place, I created a test DCR in my lab environment, whereas I didn't find the dcrResourceId from anywhere in the Portal.

Running the following command:

> Get-AzDataCollectionRule -Name <NameoftheDataCollectionRule> -ResourceGroupName <NameoftheResourceGroup> -SubscriptionId <SubscriptionId>

led me to believe that the ID shown in the output was the right one. However, while inserting that ID into the parameter and running the Deploy-PolicyPlan script gives me the following error:

Assignment error 400 -- {   "error": {     "code": "MissingPolicyParameter",     "message": "The policy assignment 'Deploy-VMSS-Monitoring' is missing the parameter(s) 'dcrResourceId' as
     | defined in the policy definition 'f5bf694c-cca7-4033-b883-3a23327d5485'."   } }

What am I missing here? Do I even need to create a DCR or are these created automatically whenever I configure something to monitor? As VM Insights is to-be retired from Log Analytics and moved to Monitor, is it safe to believe that you will in the following days remove the soon to be deprecated policies from epac? (I believe this has to do with the Deploy diagnostic settings policy).

[anwather]

Fixed in v9.1.3 - thanks for your contribution @arretesting

[arrerezai]

Thanks yourself for the continuous development of epac. As v9.1.3 didn't fix things for me, I have proposed a new change to be looked over that now works fine for me. You may check the pull request and see if it fits the expected behavior on your end too :-)

[anwather]

As explained on the other issue you can run Sync-ALZPolicies after updating the module to get the updated assignment. I can't see a PR you have raised apart from the one the other day to fix the typo (thanks)

[arrerezai]

And I am experiencing the same thing even after running the Sync-ALZPolicies and updating the ALZ-Root-Default file (or in my case ALZ-Root-Default-epac-DEV, ALZ-Root-Default-epac-TST, and ALZ-Root-Default-epac-PRD).

However, what solves it for me is to replace dataCollectionRuleResourceId with dcrResourceId and also removing the quotation marks while setting the bringYourOwnUserAssignedManagedIdentity to false. I'll raise a PR yet again for you to review.