Sacha Narinx

We've tried multiple paths to ask engineering to improve this experience and provide additional features/mechanisms to enable the scenario you've highlighted, but unfortunately our feedback is not being prioritized. We'll...

@baartch just a heads up, the new policies might be delayed by a few weeks due to some issues with resources not fully supporting diag settings (as per your screenshot,...

Closing this as we've deprecated all our diagnostic settings policies and shifted to the PG owned initiative to do the same. Please review https://aka.ms/alz/whatsnew for details. If you find gaps...

@teemukom thank you for raising and putting together this detailed issue. As per the original issue, we don't own/manage built-in policies, but given the importance of services like OpenAI we'll...

@teemukom following up. Just thinking on what you're trying to achieve above, have you considered using the generic Private DNS Zone policy we published to support services that don't have...

Hi @SebastianClaesson, the reason this was using two different effect parameters was because the effect value is case sensitive. But I see that the policies have been updated to support...

@MikaelJcSoderberg thanks for raising the issue, we'll add to our backlog to review.

Tracking in AB#37540

@mlomat and @hlokensgard This is a valid ask but requires quite a bit of engineering on our end across all the reference architectures. We'll add this for review and prioritization...

@lodrantl and @anttonalkio just to let you know, a bug has been detected in policy enforcement that is impacting this specific policy. Engineering is working on addressing the issue and...