Merge pull request #231296 from mbender-ms/ga-sec-admin-breaking-update

virtual network manager - Ga sec admin breaking update

Author: prmerger-automator[bot]

articles/virtual-network-manager/concept-security-admins.md

@@ -74,11 +74,6 @@ Security admin rules are similar to network security group rules in structure an
 | **Security admin rules** | Network admins, central governance team | 	Virtual networks | 	Higher priority | 	Allow, Deny, Always Allow | 	Priority, protocol, action, source, destination |
 | **Network security group rules** | 	Individual teams | 	Subnets, NICs | Lower priority, after security admin rules | Allow, Deny | Priority, protocol, action, source, destination |
 
-## Network intent policies and security admin rules
-
-A network intent policy is applied to some network services to ensure the network traffic is working as needed for these services. By default, a security admin configuration doesn't apply security admin rules to virtual networks with services that use network intent policies such as SQL managed instance service. If you deploy a service using network intent policies in a virtual network with existing security admin rules applied, those security admin rules are removed from those virtual networks. In virtual networks with services that use network intent policies. You can elect for your security admin configuration to act differently and apply security admin rules to those virtual networks unless the security admin rule is of a "deny" action type. With either option, your security admin rules don't block traffic to or from virtual networks with services that use network intent policies. Both options ensure your services continue to function as expected.
-
-If you need to apply security admin rules on virtual networks with services that use network intent policies, contact [email protected] to enable this functionality. Overriding the default behavior described could break the network intent policies created for those services. For example, creating a deny admin rule can block some traffic allowed by the SQL managed instance service, which is defined by their network intent policies. Make sure to review your environment before applying a security admin configuration. For an example of how to allow the traffic of services that use network intent policies, see [How can I explicitly allow SQLMI traffic before having deny rules](faq.md#how-can-i-explicitly-allow-azure-sql-managed-instance-traffic-before-having-deny-rules)
 ## Security admin fields
 
 When you define a security admin rule, there are required and optional fields.