Skip to content

Commit efd6b53

Browse files
committed
added caveat
1 parent 90a256f commit efd6b53

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/virtual-wan/how-to-nva-hub.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,10 @@ To deploy a Network Virtual Appliance in a Virtual WAN Hub, the user or service
4444

4545
These permissions need to be granted to the Azure Marketplace Managed Application to ensure deployments succeed. Additional permissions may be required based on the implementation of the deployment workflow developed by your NVA partner.
4646

47-
## Assigning Permissions to Managed Application
47+
## Assigning Permissions to Azure Managed Application
48+
49+
>[!NOTE]
50+
> At this time, assigning additional permisisons to faciliate Azure Managed Application deployments of Network Virtual Appliances in Virtual WAN is not required for all NVA deployments but will be in the future. Reference provider documentation to determine whether or not user-assigned identities are applicable to your enviornment.
4851
4952
Network Virtual Appliances that are deployed via Azure Marketplace Managed Application are deployed in a special resource group in your Azure tenant called the **managed resource group**. When you create a Managed Application in your subscription, a corresponding and separate **managed resource group** is created in your subscription. All Azure resources created by the Managed Application (including the Network Virtual Appliance) are deployed into the **managed resource group**.
5053

0 commit comments

Comments
 (0)