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/ai-foundry/how-to/troubleshoot-deploy-and-monitor.md
+33-26Lines changed: 33 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,23 @@
1
1
---
2
2
title: How to troubleshoot your deployments and monitors in Azure AI Foundry portal
3
3
titleSuffix: Azure AI Foundry
4
-
description: This article provides instructions on how to troubleshoot your deployments and monitors in Azure AI Foundry portal.
4
+
description: Learn how to troubleshoot and monitor model deployments in Azure AI Foundry portal to quickly resolve errors and optimize performance.
5
5
ms.service: azure-ai-foundry
6
6
ms.custom:
7
7
- ignite-2023
8
8
- build-2024
9
9
- ignite-2024
10
10
- hub-only
11
+
ai-usage: ai-assisted
11
12
ms.topic: how-to
12
-
ms.date: 04/23/2025
13
+
ms.date: 08/26/2025
13
14
ms.reviewer: fasantia
14
15
reviewer: santiagxf
15
16
ms.author: mopeakande
16
17
manager: nitinme
17
18
author: msakande
19
+
20
+
#CustomerIntent: As a developer or data scientist, I want to troubleshoot and monitor model deployments in Azure AI Foundry so that I can quickly resolve errors, optimize performance, and ensure my AI solutions run smoothly.
18
21
---
19
22
20
23
# How to troubleshoot your deployments and monitors in Azure AI Foundry portal
@@ -25,7 +28,7 @@ This article provides instructions on how to troubleshoot your deployments and m
25
28
26
29
## Deployment issues
27
30
28
-
For the general deployment error code reference, see [Troubleshooting online endpoints deployment and scoring](/azure/machine-learning/how-to-troubleshoot-online-endpoints) in the Azure Machine Learning documentation. Much of the information there also apply to Azure AI Foundry deployments.
31
+
For general deployment error code reference, see [Troubleshooting online endpoints deployment and scoring](/azure/machine-learning/how-to-troubleshoot-online-endpoints) in the Azure Machine Learning documentation. Much of the information there also applies to Azure AI Foundry deployments.
29
32
30
33
31
34
### Error: Use of Azure OpenAI models in Azure Machine Learning requires Azure OpenAI in Azure AI Foundry Models resources
@@ -44,26 +47,27 @@ For more information about managing quota, see:
44
47
45
48
### Error: `ToolLoadError`
46
49
47
-
After you deployed a prompt flow, you got the error message: "Tool load failed in 'search_question_from_indexed_docs': (ToolLoadError) Failed to load package tool 'Vector Index Lookup': (HttpResponseError) (AuthorizationFailed)."
50
+
After you deploy a prompt flow, you might get the error message: "Tool load failed in 'search_question_from_indexed_docs': (ToolLoadError) Failed to load package tool 'Vector Index Lookup': (HttpResponseError) (AuthorizationFailed)."
48
51
49
-
To fix this error, take the following steps to manually assign the ML Data scientist role to your endpoint. It might take several minutes for the new role to take effect.
52
+
To fix this error, manually assign the **Azure ML Data Scientist** role to your endpoint by following these steps. It might take several minutes for the new role to take effect.
1. Go to your project in [Azure AI Foundry](https://ai.azure.com/?cid=learnDocs) and select **Management center** from the left pane to open the settings page.
54
57
1. Under the **Project** heading, select **Overview**.
55
-
1. Under **Quick reference**, select the link to your resource group to open it in the Azure portal.
58
+
1. Under **Project properties**, select the link to your resource group to open it in the Azure portal.
56
59
1. Select **Access control (IAM)** from the left pane in the Azure portal.
57
60
1. Select **Add role assignment**.
58
-
1. Select **Azure ML Data Scientist**, and select __Next__.
59
-
1. Select **Managed Identity**.
60
-
1. Select **+ Select members**.
61
-
1. Select **Machine Learning Online Endpoints** in the Managed Identity dropdown field.
62
-
1. Select your endpoint's name.
63
-
1. Select **Select**.
64
-
1. Select **Review + Assign**.
65
-
1. Return to your project in Azure AI Foundry portal and select **Deployments** from the left pane.
66
-
1. Select your deployment.
61
+
1. Select the **Azure ML Data Scientist** role. You might have to search for it in the search box.
62
+
1. Select **Next** to go to the **Members** page.
63
+
1. For **Assign access to**, select **Managed Identity**.
64
+
1. For **Members**, select **+ Select members**. This action opens up the right pane where you can select managed identities.
65
+
1. Select **Machine learning online endpoint** in the Managed identity dropdown field.
66
+
1. Select your endpoint's name.
67
+
1. Select **Select** to choose the endpoint and close the right pane.
68
+
1. Select **Review + assign**. Then select **Review + assign** again to confirm the role assignment.
69
+
1. Return to your project in Azure AI Foundry portal and select **Models + endpoints** from the left pane.
70
+
1. On the **Model deployments** page, select your deployment.
67
71
1. Test the prompt flow deployment.
68
72
69
73
### Error: Deployment failure
@@ -72,17 +76,19 @@ The full error message is as follows:
72
76
73
77
"ResourceNotFound: Deployment failed due to timeout while waiting for Environment Image to become available. Check Environment Build Log in ML Studio Workspace or Workspace storage for potential failures. Image build summary: [N/A]. Environment info: Name: CliV2AnonymousEnvironment, Version: 'Ver', you might be able to find the build log under the storage account 'NAME' in the container 'CONTAINER_NAME' at the Path 'PATH/PATH/image_build_aggregate_log.txt'."
74
78
75
-
You might have come across an `ImageBuildFailure` error: This error happens when the environment (docker image) is being built. For more information about the error, you can check the build log for your `<CONTAINER NAME>` environment.
79
+
You might come across an `ImageBuildFailure` error. This error happens when the environment (docker image) is being built. For more information about the error, you can check the build log for your `<CONTAINER NAME>` environment.
76
80
77
81
This error message refers to a situation where the deployment build failed. You want to read the build log to troubleshoot further. There are two ways to access the build log.
78
82
79
83
__Option 1: Find the build log for the Azure default blob storage.__
1. Go to your project in [Azure AI Foundry](https://ai.azure.com/?cid=learnDocs) and select **Management center** from the left pane to open the settings page.
84
-
1. Under the **Hub** heading, select **Overview**.
85
-
1. In the section for **Connected resources**, select the link to your storage account name. This name should be the name of the storage account listed in the error message you received. You'll be taken to the storage account page in the [Azure portal](https://portal.azure.com).
87
+
1. Go to your project in [Azure AI Foundry](https://ai.azure.com/?cid=learnDocs) and select **Management center** from the left pane to open the overview page of your hub.
88
+
1. In the section for **Connected resources**, select the link to your storage account name. This name should be the name of the storage account listed in the error message you received.
89
+
1. On the details page of the storage account, select **View in Azure Portal** to open up the storage account page in the [Azure portal](https://portal.azure.com).
90
+
1. Alternatively, go to the Azure portal, and from the home page, select **Storage accounts** from the list of Azure services.
91
+
1. Select your storage account from the list. You might want to search for it in the search box to find it quickly.
86
92
1. On the storage account page, select **Data Storage** > **Containers** from the left pane.
87
93
1. Select the container name that's listed in the error message you received.
88
94
1. Select through folders to find the build logs.
@@ -93,24 +99,25 @@ __Option 2: Find the build log within Azure Machine Learning studio.__
93
99
> This option to access the build log uses [Azure Machine Learning studio](https://ml.azure.com), which is a different portal than [Azure AI Foundry](https://ai.azure.com/?cid=learnDocs).
94
100
95
101
1. Go to [Azure Machine Learning studio](https://ml.azure.com).
96
-
2. Select **Endpoints** from the left pane.
97
-
3. Select your endpoint name. It might be identical to your deployment name.
98
-
4. Select the link to **Environment** from the deployment section.
99
-
5. Select **Build log** at the top of the environment details page.
102
+
1. Go to your workspace or hub.
103
+
1. Select **Endpoints** from the left pane.
104
+
1. Select your endpoint name. It might be identical to your deployment name.
105
+
1. Select the link to **Environment** from the deployment section.
106
+
1. Select **Build log** at the top of the environment details page.
100
107
101
108
### Error: `UserErrorFromQuotaService`
102
109
103
110
The full error message is: "UserErrorFromQuotaService: Simultaneous count exceeded for subscription."
104
111
105
-
This error message means that the shared quota pool has reached the maximum number of requests it can handle. Try again at a later time when the shared quota is freed up for use.
112
+
This error message means that the shared quota pool reached the maximum number of requests it can handle. Try again later when the shared quota is freed up for use.
106
113
107
114
### Question: I deployed a web app but I don't see a way to launch it or find it
108
115
109
-
We're working on improving the user experience of web app deployment at this time. In the meantime, here's a tip: if your web app launch button doesn't become active after a while, try to deploy it again, using the __update an existing app__ option. If the web app was properly deployed, it should show up on the dropdown list of your existing web apps.
116
+
We're working on improving the user experience of web app deployment. In the meantime, here's a tip: if your web app launch button doesn't become active after a while, try to deploy it again, using the **update an existing app** option. If you properly deploy the web app, it appears on the dropdown list of your existing web apps.
110
117
111
118
### Question: I deployed a model but I don't see it in the playground
112
119
113
-
Playground only supports select models, such as Azure OpenAI models and Llama-2. If playground support is available, you see the **Open in playground** button on the model deployment's **Details** page.
120
+
The playground only supports select models, such as Azure OpenAI models and Llama-2. If the playground supports a model, you see the **Open in playground** button on the model deployment's **Details** page.
Copy file name to clipboardExpand all lines: articles/ai-foundry/includes/uses-hub-only.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,4 +11,4 @@ ms.custom: include
11
11
---
12
12
13
13
> [!NOTE]
14
-
> You must use a **[!INCLUDE [hub](hub-project-name.md)]** for this feature. A**[!INCLUDE [fdp](fdp-project-name.md)]** isn't supported. See [How do I know which type of project I have?](../what-is-azure-ai-foundry.md#how-do-i-know) and [Create a hub-based project](../how-to/create-projects.md?pivots="hub-project").
14
+
> You must use a **[!INCLUDE [hub](hub-project-name.md)]** for this feature. An**[!INCLUDE [fdp](fdp-project-name.md)]** isn't supported. See [How do I know which type of project I have?](../what-is-azure-ai-foundry.md#how-do-i-know) and [Create a hub-based project](../how-to/create-projects.md?pivots="hub-project").
0 commit comments