You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/prompt-flow/get-started-prompt-flow.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,10 +26,6 @@ This article walks you through the main user journey of using Prompt flow in Azu
26
26
> 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.
27
27
>
28
28
>Prompt flow is **not supported** in the project workspace which was created with a workspace hub. The workspace hub is a private preview feature.
29
-
>
30
-
>Prompt flow is **not supported** in workspaces that enable managed VNet. Managed VNet is a private preview feature.
31
-
>
32
-
>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.
33
29
34
30
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.
Copy file name to clipboardExpand all lines: articles/machine-learning/prompt-flow/how-to-create-manage-runtime.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,6 @@ Go to runtime detail page and select update button at the top. You can change ne
108
108
> [!NOTE]
109
109
> If you used a custom environment, you need to rebuild it using latest prompt flow image first, and then update your runtime with the new custom environment.
## Create managed online deployment that can be used as Prompt flow runtime (deprecated)
178
-
179
-
> [!IMPORTANT]
180
-
> Managed online endpoint/deployment as runtime is **deprecated**. Please use [Migrate guide for managed online endpoint/deployment runtime](./migrate-managed-inference-runtime.md).
181
-
182
-
### Create managed online deployment that can be used as Prompt flow runtime via CLI v2
183
-
184
-
Learn more about [deploy and score a machine learning model by using an online endpoint](../how-to-deploy-online-endpoints.md)
185
-
186
-
#### Create managed online endpoint
187
-
188
-
To define a managed online endpoint, you can use the following yaml template. Make sure to replace the `ENDPOINT_NAME` with the desired name for your endpoint.
Use following CLI command `az ml online-endpoint create -f <yaml_file> -g <resource_group> -w <workspace_name>` to create managed online endpoint. To learn more, see [Deploy and score a machine learning model by using an online endpoint](../how-to-deploy-online-endpoints.md).
198
-
199
-
#### Create Prompt flow runtime image config file
200
-
201
-
To configure your Prompt flow runtime, place the following config file in your model folder. This config file provides the necessary information for the runtime to work properly.
202
-
203
-
For the `mt_service_endpoint` parameter, follow this format: `https://<region>.api.azureml.ms`. For example, if your region is eastus, then your service endpoint should be `https://eastus.api.azureml.ms`
You need to replace the following placeholders with your own values:
220
-
221
-
- `ENDPOINT_NAME`: the name of the endpoint you created in the previous step
222
-
- `PRT_CONFIG_FILE`: the name of the config file that contains the port and runtime settings. Include the parent model folder name, for example, if model folder name is `model`, then the config file name should be `model/config.yaml`.
223
-
- `IMAGE_NAME` to name of your own image, for example: `mcr.microsoft.com/azureml/promptflow/promptflow-runtime:<newest_version>`, you can also follow [Customize environment with docker context for runtime](#customize-environment-with-docker-context-for-runtime) to create your own environment.
Use following CLI command `az ml online-deployment create -f <yaml_file> -g <resource_group> -w <workspace_name>` to create managed online deployment that can be used as a Prompt flow runtime.
Copy file name to clipboardExpand all lines: articles/machine-learning/prompt-flow/how-to-deploy-for-real-time-inference.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,11 @@ If you didn't complete the tutorial, you need to build a flow. Testing the flow
45
45
46
46
We'll use the sample flow **Web Classification** as example to show how to deploy the flow. This sample flow is a standard flow. Deploying chat flows is similar. Evaluation flow doesn't support deployment.
47
47
48
+
## Define the environment used by deployment
49
+
When you deploy prompt flow to managed online endpoint in UI. You need define the environment used by this flow. By default, it will use the latest prompt image version. You can specify extra packages you needed in `requirements.txt`. You can find `requirements.txt` in the root folder of your flow folder, which is system generated file.
50
+
51
+
:::image type="content" source="./media/how-to-deploy-for-real-time-inference/requirements-text.png" alt-text="Screenshot of Web requiremnts-text. " lightbox = "./media/how-to-deploy-for-real-time-inference/requirements-text.png":::
52
+
48
53
## Create an online endpoint
49
54
50
55
Now that you have built a flow and tested it properly, it's time to create your online endpoint for real-time inference.
Copy file name to clipboardExpand all lines: articles/machine-learning/prompt-flow/how-to-secure-prompt-flow.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,10 +54,12 @@ Workspace managed virtual network is the recommended way to support network isol
54
54
55
55
:::image type="content" source="./media/how-to-secure-prompt-flow/outbound-rule-non-azure-resources.png" alt-text="Screenshot of user defined outbound rule for non Azure resource." lightbox = "./media/how-to-secure-prompt-flow/outbound-rule-non-azure-resources.png":::
56
56
57
+
4. In workspace which enable managed VNet, you can only deployment to managed online endpoint. You can follow [Secure your managed online endpoints with network isolation](../how-to-secure-kubernetes-inferencing-environment.md) to secure your managed online endpoint.
57
58
## Secure prompt flow use your own virtual network
58
59
59
60
- To set up Azure Machine Learning related resources as private, see [Secure workspace resources](../how-to-secure-workspace-vnet.md).
60
61
- Meanwhile, you can follow [private Azure Cognitive Services](../../ai-services/cognitive-services-virtual-networks.md) to make them as private.
62
+
- If you want to deploy prompt flow in workspace which secured by your own virtual network, you can deploy it to AKS cluster which is in the same virtual network. You can follow [Secure your RAG workflows with network isolation](../how-to-secure-rag-workflows.md) to secure your AKS cluster.
61
63
- You can either create private endpoint to the same virtual network or leverage virtual network peering to make them communicate with each other.
62
64
63
65
## Limitations
@@ -66,15 +68,10 @@ Workspace managed virtual network is the recommended way to support network isol
66
68
- Workspace hub / lean workspace and AI studio don't support bring your own virtual network.
67
69
- Managed online endpoint only supports workspace managed virtual network. If you want to use your own virtual network, you may need one workspace for prompt flow authoring with your virtual network and another workspace for prompt flow deployment using managed online endpoint with workspace managed virtual network.
68
70
69
-
## FAQ
70
-
71
-
### Why I can't create or upgrade my flow when I disable public network access of storage account?
72
-
Prompt flow rely on fileshare to store snapshot of flow. Prompt flow didn't support private storage account now. Here are some workarounds you can try:
73
-
- Make the storage account as public access enabled if there is no security concern.
74
-
- If you are only use UI to authoring promptflow, you can add following flights (flight=PromptFlowCodeFirst=false) to use our old UI.
75
-
- You can use our CLI/SDK to authoring promptflow, CLI/SDK authong didn't rely on fileshare. See [Integrate Prompt Flow with LLM-based application DevOps ](how-to-integrate-with-llm-app-devops.md).
Copy file name to clipboardExpand all lines: articles/machine-learning/prompt-flow/tools-reference/troubleshoot-guidance.md
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,4 +41,21 @@ To resolve the issue, you have two options:
41
41
42
42
-**Option 2**
43
43
- Update your runtime to latest version.
44
-
- Remove the old tool and re-create a new tool.
44
+
- Remove the old tool and re-create a new tool.
45
+
46
+
## Why I can't create or upgrade my flow when I disable public network access of storage account?
47
+
Prompt flow rely on fileshare to store snapshot of flow. Prompt flow didn't support private storage account now. Here are some workarounds you can try:
48
+
- Make the storage account as public access enabled if there is no security concern.
49
+
- If you are only using UI to authoring promptflow, you can add following flights (flight=PromptFlowCodeFirst=false) to use our old UI.
50
+
- You can use our CLI/SDK to authoring promptflow, CLI/SDK authong didn't rely on fileshare. See [Integrate Prompt Flow with LLM-based application DevOps ](../how-to-integrate-with-llm-app-devops.md).
51
+
52
+
53
+
## Why I can't upgrade my old flow?
54
+
Prompt flow rely on fileshare to store snapshot of flow. If fileshare have some issue, you may encounter this issue. Here are some workarounds you can try:
55
+
- If you are using private storage account, please see [Why I can't create or upgrade my flow when I disable public network access of storage account?](#why-i-cant-create-or-upgrade-my-flow-when-i-disable-public-network-access-of-storage-account)
56
+
- If the storage account is enabled public access, please check whether there are datastore named `workspaceworkingdirectory` in your workspace, it should be fileshare type.
- If you didn't get this datastore, you need add it in your workspace.
59
+
- Create fileshare with name `code-391ff5ac-6576-460f-ba4d-7e03433c68b6`
60
+
- Create data store with name `workspaceworkingdirectory` . See [Create datastores](../../how-to-datastore.md)
61
+
- If you have `workspaceworkingdirectory` datastore but its type is `blob` instead of `fileshare`, please create new workspace and use storage didn't enable hierarchical namespaces ADLS Gen2 as workspace default storage account. See [Create workspace](../../how-to-manage-workspace.md#create-a-workspace)
0 commit comments