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/how-to-troubleshoot-data-labeling.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.reviewer: vkann
8
8
services: machine-learning
9
9
ms.service: azure-machine-learning
10
10
ms.subservice: mldata
11
-
ms.date: 03/07/2024
11
+
ms.date: 03/10/2025
12
12
ms.topic: troubleshooting
13
13
#customer intent: To troubleshoot and resolve issues that occur when creating your data labeling project.
14
14
---
@@ -80,7 +80,7 @@ When your workspace is secured with a virtual network, use these steps to set th
80
80
81
81
## When data preprocessing fails
82
82
83
-
Another possible issue with creating a data labeling project is when data preprocessing fails. You'll see an error that looks like this:
83
+
Another possible issue with creating a data labeling project is when data preprocessing fails. You see an error that looks like this:
84
84
85
85
:::image type="content" source="media/how-to-troubleshoot-data-labeling/data-error.png" alt-text="Screenshot shows a data preprocessing error.":::
86
86
@@ -103,7 +103,7 @@ When the **Save credentials with the datastore for data access** is **Off**, the
103
103
104
104
Once you have the compute cluster name with a managed identity, assign the Storage Blob Data Contributor role to the compute cluster.
105
105
106
-
Follow the previous steps to [Add Storage Blob Data Contributor access](#add-blob-access). But this time, you'll be selecting the compute resource in the **Select members** section, so that the compute cluster has access to the datastore.
106
+
Follow the previous steps to [Add Storage Blob Data Contributor access](#add-blob-access). But this time, you are selecting the compute resource in the **Select members** section, so that the compute cluster has access to the datastore.
107
107
108
108
* If you're using a system-assigned identity, search for the compute name by using the workspace name, followed by `/computes/` followed by the compute name. For example, if the workspace name is `myworkspace` and the compute name is `mycompute`, search for `myworkspace/computes/mycompute` to select the member.
109
109
* If you're using a user-assigned identity, search for the user-assigned identity name.
0 commit comments