Description of the issue.
Custom policies definition inside custom initiative seem to not work as excepted.
We have seen this problem since the 03/22/2021 release of Azure Security Center including the Recommendations page enhancements feature.
Since this date, custom recommendations have disappeared from ASC and they do not trigger workflow automation anymore. Also, ASC always shows zero affected resources for custom policies in the regulatory compliance dashboard.
I haven't found any documentation that mentions this change in behavior. Is it normal ?
To Reproduce
Steps to reproduce the behavior (mostly from the documentation):
1. Enable Azure Defender plan to enable custom initiative in ASC Regulatory Compliance
2. Duplicate one built-in policy in order to create a custom policy from a "validated" rule logic.
3. Create a policy initiative that includes the created policy.
4. Assign the policy initiative in ASC or add the metadata property with the value {"ASC": "true"} in the initiative assignement.
5. Create a non-compliant resource affected by your policy.
After more than 24h, in the ASC Regulatory compliance dashboard, ASC still found 0 affected resources for the policy.

On the over side, the Azure Policy compliance dashboard indicates that a non-compliant resource indeed exists for this custom initiative.
Expected behavior
Non compliant resources for custom initiatives appear in the ASC Regulatory compliance and Recommendation dashboard as custom Security Center recommendations.
Additional context
Documentation linked to this feature: https://docs.microsoft.com/en-us/azure/security-center/custom-security-policies?pivots=azure-portal
On-boarding process followed during deployment: https://github.com/Azure/Azure-Security-Center/blob/onboarding/Onboarding/Modules/3-Policy-Management.md#step-6---assign-custom-policies-optional