Merge pull request #34368 from MicrosoftDocs/main

6/10/2025 AM Publish

Author: Albertyang0

azure-sql/database/network-security-perimeter.md

@@ -13,7 +13,7 @@ ms.topic: how-to
 
 # Network Security Perimeter for Azure SQL Database and Azure Synapse Analytics
 
-[!INCLUDE [appliesto-sqldb-asa](../includes/appliesto-sqldb-asa-formerly-sqldw.md)]
+[!INCLUDE [appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
 Network Security Perimeter (preview) secures both inbound and outbound network traffic between Azure SQL Database and other Platform as a Service (PaaS) resources (for example, Azure Storage and Azure Key Vault). Any attempts made to communicate with Azure resources that aren't inside the perimeter is blocked.
 

docs/sql-server/azure-arc/troubleshoot-telemetry-endpoint.md

@@ -104,12 +104,12 @@ For DPS:
 ```powershell
 Invoke-WebRequest dataprocessingservice.<region>.arcdataservices.com
 ```
-> [!NOTE]
-> For US Government Virginia, replace `arcdataservices.com` with `arcdataservices.azure.us`. This example would be:
->
-> ```PowerShell
-> Invoke-WebRequest dataprocessingservice.<region>.arcdataservices.azure.us
->  `
+
+For US Government Virginia, replace `arcdataservices.com` with `arcdataservices.azure.us`. This example would be:
+
+```PowerShell
+Invoke-WebRequest dataprocessingservice.<region>.arcdataservices.azure.us
+```
 
 A possible response status code is:
 
@@ -122,9 +122,7 @@ StatusDescription : OK
 200 is expected as there is an unauthenticated route.
 
 ## Probe connectivity to all regions
-> [!NOTE]
-> For US Government Virginia, replace `arcdataservices.com` with `arcdataservices.azure.us`.
-> 
+
 You can probe connectivity to all regions with the [test-connectivity.ps1](https://github.com/microsoft/sql-server-samples/blob/master/samples/features/azure-arc/troubleshooting/test-connectivity.ps1) PowerShell script.
 
 > [!NOTE]
@@ -136,7 +134,6 @@ You can probe connectivity to all regions with the [test-connectivity.ps1](https
 
 The data processing service endpoint supports the following TLS versions: TLS 1.2 and 1.3. Windows Server 2012 and older versions aren't supported.
 
-
 For telemetry endpoints, Windows Server 2012 R2 and older are not supported.
 
 If an unsupported TLS version is being used, you may see an error in the log