Merge pull request #189279 from dcbrown16/patch-65

Update vnet-service-endpoint-rule-overview.md

Author: PRMerger6

articles/azure-sql/database/vnet-service-endpoint-rule-overview.md

@@ -206,7 +206,7 @@ You must already have a subnet that's tagged with the particular virtual network
 
     :::image type="content" source="../../sql-database/media/sql-database-vnet-service-endpoint-rule-overview/portal-firewall-vnet-firewalls-and-virtual-networks.png" alt-text="Azure SQL logical server properties, Firewalls and Virtual Networks highlighted" lightbox="../../sql-database/media/sql-database-vnet-service-endpoint-rule-overview/portal-firewall-vnet-firewalls-and-virtual-networks.png":::
 
-1. Set **Allow access to Azure services** to **OFF**.
+1. Set **Allow Azure services and resources to access this server** to **No**.
 
     > [!IMPORTANT]
     > If you leave the control set to **ON**, your server accepts communication from any subnet inside the Azure boundary. That is communication that originates from one of the IP addresses that's recognized as those within ranges defined for Azure datacenters. Leaving the control set to **ON** might be excessive access from a security point of view. The Microsoft Azure Virtual Network service endpoint feature in coordination with the virtual network rules feature of SQL Database together can reduce your security surface area.
@@ -298,4 +298,4 @@ Error 40615 is similar, except it relates to *IP address rules* on the firewall.
 - REST API Reference, including JSON
 - Azure CLI
 - ARM templates
--->
+-->