Merge pull request #57743 from ekpgh/avere-doc-updates

add note about internal MS users' role

Author: PRMerger8

articles/avere-vfxt/avere-vfxt-deploy.md

@@ -86,6 +86,7 @@ Under **TERMS AND CONDITIONS**:
   > [!NOTE] 
   > If you are not a subscription owner, have an owner accept the terms for you by following the prerequisite steps in [Accept software terms in advance](avere-vfxt-prereqs.md#accept-software-terms-in-advance). 
 
+
 Click **Purchase** when finished. After five or six minutes, your controller node will be up and running.
 
 Visit the outputs page to gather the controller information that you need to create the cluster. Read [Information needed to create the cluster](#information-needed-to-create-the-cluster) to learn more.
@@ -220,7 +221,9 @@ To do the rest of the deployment steps, you need to connect to the cluster contr
 ## Create the cluster node access role
 
 > [!NOTE] 
-> If you are not a subscription owner, and the role has not already been created, have a subscription owner follow these steps or use the procedure in [Create the Avere vFXT cluster runtime access role without a controller](avere-vfxt-pre-role.md).
+> * If you are not a subscription owner, and the role has not already been created, have a subscription owner follow these steps or use the procedure in [Create the Avere vFXT cluster runtime access role without a controller](avere-vfxt-pre-role.md).
+> 
+> * Microsoft internal users should use the existing role named "Avere Cluster Runtime Operator" instead of attempting to create one. 
 
 [Role-based access control](https://docs.microsoft.com/azure/role-based-access-control/) (RBAC)  gives the vFXT cluster nodes authorization to perform necessary tasks.