Update how-to-configure-private-link.md

Public doc related to PE/PL configuration should warn customers to recreate clusters and that jobs in progress may fail

Author: meerakurup

articles/machine-learning/how-to-configure-private-link.md

@@ -55,6 +55,7 @@ Azure Private Link enables you to restrict connections to your workspace to an A
 * If you're using Mozilla Firefox, you might encounter problems trying to access the private endpoint for your workspace. This problem might be related to DNS over HTTPS in Mozilla Firefox. We recommend using Microsoft Edge or Google Chrome.
 * Using a private endpoint doesn't affect Azure control plane (management operations) such as deleting the workspace or managing compute resources. For example, creating, updating, or deleting a compute target. These operations are performed over the public Internet as normal. Data plane operations, such as using Azure Machine Learning studio, APIs (including published pipelines), or the SDK use the private endpoint.
 * When you create a compute instance or compute cluster in a workspace with a private endpoint, the compute instance and compute cluster must be in the same Azure region as the workspace.
+* If you enable or disable Private Link for an Azure Machine Learning workspace after creating compute resources, those existing computes will not automatically update to reflect the new Private Link configuration. To ensure proper connectivity and avoid service disruptions, you must recreate the compute resources after making any changes to the workspace’s private link setting.
 * When you attach an Azure Kubernetes Service cluster to a workspace with a private endpoint, the cluster must be in the same region as the workspace.
 * When you use a workspace with multiple private endpoints, one of the private endpoints must be in the same virtual network as the following dependency services: