Merge pull request #94366 from bengimblett/patch-9

Clarification RE az network traffic

Author: Court72

articles/event-grid/consume-private-endpoints.md

@@ -17,7 +17,7 @@ Then, you can use a private link configured in Azure Functions or your webhook d
 :::image type="content" source="./media/consume-private-endpoints/deliver-private-link-service.svg" alt-text="Deliver via private link service":::
 
 
-Under this configuration, the traffic goes over the public IP/internet from Event Grid to Event Hubs, Service Bus, or Azure Storage, but the channel can be encrypted and a managed identity of Event Grid is used. If you configure your Azure Functions or webhook deployed to your virtual network to use an Event Hubs, Service Bus, or Azure Storage via private link, that section of the traffic will evidently stay within Azure.
+Under this configuration, the secured traffic from Event Grid to Event Hubs, Service Bus, or Azure Storage, [stays on the Microsoft backbone](../networking/microsoft-global-network.md#get-the-premium-cloud-network) and a managed identity of Event Grid is used. Configuring your Azure Function or webhook from within your virtual network to use an Event Hubs, Service Bus, or Azure Storage via private link ensures the traffic between those services and your function or webhook stays within your virtual network perimeter.
 
 ## Deliver events to Event Hubs using managed identity
 To deliver events to event hubs in your Event Hubs namespace using managed identity, follow these steps:
@@ -44,4 +44,4 @@ To deliver events to Storage queues using managed identity, follow these steps:
 
 
 ## Next steps
-For more information about delivering events using a managed identity, see [Event delivery using a managed identity](managed-service-identity.md).
+For more information about delivering events using a managed identity, see [Event delivery using a managed identity](managed-service-identity.md).