Skip to content

Commit 3377c14

Browse files
Merge pull request #3849 from Blackmist/main
Freshness
2 parents f27e4b3 + 314b262 commit 3377c14

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/machine-learning/how-to-troubleshoot-managed-network.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.reviewer: None
99
ms.author: larryfr
1010
author: Blackmist
1111
ms.topic: troubleshooting
12-
ms.date: 04/30/2024
12+
ms.date: 04/01/2025
1313
ms.custom: build-2023
1414
---
1515

@@ -29,11 +29,11 @@ To use an Azure Virtual Network when creating a workspace through the Azure port
2929
1. In the __Workspace Outbound access__ section, select __Use my own virtual network__.
3030
1. Continue to create the workspace as normal.
3131

32-
## Does not have authorization to perform action 'Microsoft.MachineLearningServices<br/> /workspaces/privateEndpointConnections/read'
32+
## Doesn't have authorization to perform action 'Microsoft.MachineLearningServices<br/> /workspaces/privateEndpointConnections/read'
3333

3434
When you create a managed virtual network, the operation can fail with an error similar to the following text:
3535

36-
"The client '\<GUID\>' with object id '\<GUID\>' doesn't have authorization to perform action 'Microsoft.MachineLearningServices/workspaces/privateEndpointConnections/read' over scope '/subscriptions/\<GUID\>/resourceGroups/\<resource-group-name\>/providers/Microsoft.MachineLearningServices/workspaces/\<workspace-name\>' or the scope is invalid."
36+
"The client '\<GUID\>' with object ID '\<GUID\>' doesn't have authorization to perform action 'Microsoft.MachineLearningServices/workspaces/privateEndpointConnections/read' over scope '/subscriptions/\<GUID\>/resourceGroups/\<resource-group-name\>/providers/Microsoft.MachineLearningServices/workspaces/\<workspace-name\>' or the scope is invalid."
3737

3838
This error occurs when the Azure identity used to create the managed virtual network doesn't have the following Azure role-based access control permissions:
3939

0 commit comments

Comments
 (0)