Merge pull request #247238 from cloga/lochen/pf-VNet

Explicitly call out VNet not support

Author: prmerger-automator[bot]

articles/machine-learning/prompt-flow/get-started-prompt-flow.md

@@ -28,6 +28,10 @@ A quick video tutorial can be found here: [Prompt flow get started video tutoria
 > Prompt flow is **not supported** in the workspace which has data isolation enabled. The enableDataIsolation flag can only be set at the workspace creation phase and can't be updated.
 >
 >Prompt flow is **not supported** in the project workspace which was created with a workspace hub. The workspace hub is a private preview feature.
+>
+>Prompt flow is **not supported** in workspaces that enable managed VNet. Managed VNet is a private preview feature.
+>
+>Prompt flow is **not supported** if you secure your Azure AI services account(Azure openAI, Azure cognitive search, Azure content safety) with virtual networks. If you want to use these as connection in prompt flow please allow access from all networks.
 
 In your Azure Machine Learning workspace, you can enable Prompt flow by turning on **Build AI solutions with Prompt flow** in the **Manage preview features** panel.
 

articles/machine-learning/prompt-flow/how-to-create-manage-runtime.md

@@ -52,6 +52,10 @@ You need to assign enough permission to use runtime in Prompt flow. To assign a
 > Prompt flow is **not supported** in the workspace which has data isolation enabled. The enableDataIsolation flag can only be set at the workspace creation phase and can't be updated.
 >
 >Prompt flow is **not supported** in the project workspace which was created with a workspace hub. The workspace hub is a private preview feature.
+>
+> Prompt flow is **not supported** in workspaces that enable managed VNet. Managed VNet is a private preview feature.
+>
+>Prompt flow is **not supported** if you secure your Azure AI services account (Azure openAI, Azure cognitive search, Azure content safety) with virtual networks. If you want to use these as connection in prompt flow please allow access from all networks.
 
 ### Create compute instance runtime in UI
 
@@ -299,6 +303,9 @@ If your compute instance is behind a VNet, you need to make the following change
 - If your storage account also behind vnet, see [Secure Azure storage accounts](../how-to-secure-workspace-vnet.md#secure-azure-storage-accounts) to create private endpoints for both table and blob.
 - Make sure the managed identity of workspace have `Storage Blob Data Contributor`, `Storage Table Data Contributor` roles on the workspace default storage account.
 
+> [!NOTE] 
+> This only works if your AOAI and other cognitive services allow access from all networks.
+
 ### Managed endpoint runtime related
 
 #### Managed endpoint failed with an internal server error. Endpoint creation was successful, but failed to create deployment for the newly created workspace.