Skip to content

Commit 6f4b119

Browse files
authored
Merge pull request #111953 from srdan-bozovic-msft/patch-1
Remove MS peering recommendation
2 parents 6acd128 + e92de34 commit 6f4b119

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sql-database/sql-database-managed-instance-public-endpoint-securely.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Although not mandatory, the common deployment model for a managed instance with
2929

3030
## Secure data in motion
3131

32-
Managed instance data traffic is always encrypted if the client driver supports encryption. Data sent between the managed instance and other Azure virtual machines or Azure services never leaves Azure's backbone. If there's a connection between the managed instance and an on-premises network, we recommend you use Azure ExpressRoute with Microsoft peering. ExpressRoute helps you avoid moving data over the public internet. For managed instance private connectivity, only private peering can be used.
32+
Managed instance data traffic is always encrypted if the client driver supports encryption. Data sent between the managed instance and other Azure virtual machines or Azure services never leaves Azure's backbone. If there's a connection between the managed instance and an on-premises network, we recommend you use Azure ExpressRoute. ExpressRoute helps you avoid moving data over the public internet. For managed instance private connectivity, only private peering can be used.
3333

3434
## Lock down inbound and outbound connectivity
3535

0 commit comments

Comments
 (0)