Question: Why is the deny/block public access policy for Cognitive services deprecated?

[odee79]

When investigating policies for Cognitive Services I saw this policy that had a deny effect as option was deprecated and is replaced by this modify policy.
As a platform team we don't want to interfere with our customer DevOps teams in their development and deployment flow, we prefer a deny policy so the deployment of an incompliant instance is directly stopped at the beginning of the flow.
Can someone explain why the deny policy is replaced with a modify policy?
Thank you in advance for your answer!