Azure DNS Private Zones is in Public Preview, which supports split-horizon scenarios.
We will support non-empty Vnets very soon. Stay tuned !
Private Zones look good, but currently, they cannot be added to an existing (production) VNET. Please make this possible! (Don't need the auto registration, just need to manually add local DNS entries for existing VMs.)
Thanks for your feedback. This is planned as a new supported RuleSet.
Also, rules that are flagged with a severity of "WARNING" in the specs are being completely blocked by the WAF. There should be a way to log but allow any with a severity of "warning".
Also, rules that are flagged with a severity of "WARNING" in the specs are being completely blocked by the WAF.
2 votes0 comments · Azure Monitor-Application Insights » Service monitoring and diagnostics · Flag idea as inappropriate… · Admin →