Merge pull request #387 from J-Silvestre/patch-8

Update how-to-assign-roles.md

Author: v-dirichards

articles/machine-learning/how-to-assign-roles.md

@@ -269,7 +269,7 @@ If you anticipate that you need to recreate complex role assignments, an Azure R
 The following table is a summary of Azure Machine Learning activities and the permissions required to perform them at the least scope. For example, if an activity can be performed with a workspace scope (Column 4), then all higher scope with that permission also work automatically. For certain activities, the permissions differ between V1 and V2 APIs.
 
 > [!IMPORTANT]
-> All paths in this table that start with `/` are *relative paths* to `Microsoft.MachineLearningServices/` :
+> All paths in this table that start with `/` are *relative paths* to `Microsoft.MachineLearningServices/`
 
 | Activity | Subscription-level scope | Resource group-level scope | Workspace-level scope |
 | ----- | ----- | ----- | ----- |
@@ -293,6 +293,8 @@ The following table is a summary of Azure Machine Learning activities and the pe
 
 2. When attaching an AKS cluster, you also need to have the [Azure Kubernetes Service Cluster Admin Role](/azure/role-based-access-control/built-in-roles#azure-kubernetes-service-cluster-admin-role) on the cluster.
 
+3. These scenarios don't include the permissions needed to create workspace dependent resources. For more information, see the write permissions for [Storage](https://learn.microsoft.com/azure/role-based-access-control/permissions/storage#microsoftstorage), [OperationalInsights](https://learn.microsoft.com/azure/role-based-access-control/permissions/monitor#microsoftoperationalinsights), [Key Vault](https://learn.microsoft.com/azure/role-based-access-control/permissions/security#microsoftkeyvault) and [Container Registry](https://learn.microsoft.com/azure/role-based-access-control/permissions/containers#microsoftcontainerregistry).
+
 ###  Deploy into a virtual network or subnet
 
 [!INCLUDE [network-rbac](includes/network-rbac.md)]