Skip to content

Commit 8f44d71

Browse files
authored
Merge pull request #88642 from KumudD/patch-21
Fixed typo
2 parents 3800241 + 77d6a49 commit 8f44d71

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/private-link/private-link-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Azure Private Link provides the following benefits:
2626

2727
- **On-premises and peered networks**: Access services running in Azure from on-premises over ExpressRoute private peering/VPN tunnels (from on-premises) and peered virtual networks using private endpoints. There is no need to set up public peering or traverse the internet to reach the service. This ability provides a secure way to migrate workloads to Azure.
2828

29-
- **Protection against data exfilteration**: With Azure Private Link, the private endpoint in the VNet is mapped to a specific instance of the customer's PaaS resource as opposed to the entire service. Using the private endpoint consumers can only connect to the specific resource and not to any other resource in the service. This in built mechanism provides protection against data exfilteration risks.
29+
- **Protection against data exfiltration**: With Azure Private Link, the private endpoint in the VNet is mapped to a specific instance of the customer's PaaS resource as opposed to the entire service. Using the private endpoint consumers can only connect to the specific resource and not to any other resource in the service. This in built mechanism provides protection against data exfiltration risks.
3030

3131
- **Global reach**: Connect privately to services running in other regions. This means that the consumer's virtual network could be in region A and it can connect to services behind Private Link in region B.
3232

0 commit comments

Comments
 (0)