Skip to content

Commit 4d241ea

Browse files
Merge pull request #3909 from meerakurup/patch-11
Update how-to-managed-network.md
2 parents 8730201 + 19c9b09 commit 4d241ea

File tree

1 file changed

+26
-1
lines changed

1 file changed

+26
-1
lines changed

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

Lines changed: 26 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -174,7 +174,32 @@ Before following the steps in this article, make sure you have the following pre
174174
---
175175
176176
> [!NOTE]
177-
> If you're using UAI workspace, make sure to add the Azure AI Enterprise Network Connection Approver role to your identity. For more information, see [User-assigned managed identity](how-to-identity-based-service-authentication.md).
177+
> To establish private endpoint connections in managed virtual networks using Azure Machine Learning, the workspace managed identity, whether system-assigned or user-assigned, must have permissions to approve the Private Endpoint connections on the target resources. Previously, this was done through automatic role assignments by the Azure Machine Learning service. However, there are security concerns about the automatic role assignment. To improve security, starting April 30th, 2025, we will discontinue this automatic permission grant logic. We recommend assigning the _Azure AI Enterprise Network Connection Approver_ role or a custom role with the necessary private endpoint connection permissions on the target resource types and grant this role to the Azure Machine Learning workspace's managed identity to allow Azure Machine Learning services to approve Private Endpoint connections to the target Azure resources.
178+
>
179+
> Here's the list of private endpoint target resource types covered by the _Azure AI Enterprise Network Connection Approver_ role:
180+
> * Azure Application Gateway
181+
> * Azure Monitor
182+
> * Azure AI Search
183+
> * Event Hubs
184+
> * Azure SQL Database
185+
> * Azure Storage
186+
> * Azure Machine Learning workspace
187+
> * Azure Machine Learning registry
188+
> * Azure AI Foundry
189+
> * Azure Key Vault
190+
> * Azure CosmosDB
191+
> * Azure Database for MySQL
192+
> * Azure Database for PostgreSQL
193+
> * Azure AI Services
194+
> * Azure Cache for Redis
195+
> * Container Registry
196+
> * API Management
197+
>
198+
> If you would like to create a custom role instead, see [Azure AI Enterprise Network Connection Approver role](/azure/role-based-access-control/built-in-roles/ai-machine-learning#azure-ai-enterprise-network-connection-approver) to add the specific actions for each resource type.
199+
>
200+
> For creating private endpoint outbound rules to target resource types not covered by the _Azure AI Enterprise Network Connection Approver_ role, such as Azure Data Factory, Azure Databricks, and Azure Function Apps, a custom scoped-down role is recommended, defined only by the actions necessary to approve private endpoint connections on the target resource types.
201+
>
202+
> For creating Private Endpoint outbound rules to default workspace resources, the required permissions are automatically covered by the role assignments granted during workspace creation, so no additional action is needed.
178203
179204
## Configure a managed virtual network to allow internet outbound
180205

0 commit comments

Comments
 (0)