Skip to content

Commit 0534b71

Browse files
authored
Merge pull request #197557 from wtnlee/refreshpermissions
refresh permissions
2 parents 2aaf6af + bd6db70 commit 0534b71

File tree

1 file changed

+20
-2
lines changed

1 file changed

+20
-2
lines changed

articles/virtual-wan/about-nva-hub.md

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ title: 'About Network Virtual Appliances - Virtual WAN hub'
33
titleSuffix: Azure Virtual WAN
44
description: Learn about Network Virtual Appliances in a Virtual WAN hub.
55
services: virtual-wan
6-
author: cherylmc
6+
author: wtnlee
77
ms.service: virtual-wan
88
ms.topic: conceptual
99
ms.date: 06/02/2021
10-
ms.author: cherylmc
10+
ms.author: wellee
1111
ms.custom: references_regions
1212
# Customer intent: As someone with a networking background, I want to learn about Network Virtual Appliances in a Virtual WAN hub.
1313
---
@@ -84,6 +84,24 @@ NVA Partners may create different resources depending on their appliance deploym
8484

8585
:::image type="content" source="./media/about-nva-hub/managed-app.png" alt-text="Managed Application resource groups":::
8686

87+
88+
### Managed resource group permissions
89+
90+
By default, all managed resource groups have an deny-all Azure Active Directory assignment. Deny-all assignments prevent customers from calling write operations on any resources in the managed resource group, including Network Virtual Appliance resources.
91+
92+
However, partners may create exceptions for specific actions that customers are allowed to perform on resources deployed in managed resource groups.
93+
94+
Permissions on resources in existing managed resource groups are not dynamically updated as new permitted actions are added by partners and require a manual refresh.
95+
96+
To refresh permissions on the managed resource groups, customers can leverage the [Refresh Permissions REST API ](/rest/api/managedapplications/applications/refresh-permissions).
97+
98+
> [!NOTE]
99+
> To properly apply new permissions, refresh permissions API must be called with an additional query parameter **targetVersion**. The value for targetVersion is provider-specific. Please reference your provider's documentation for the latest version number.
100+
101+
```http-interactive
102+
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName}/refreshPermissions?api-version=2019-07-01&targetVersion={targetVersion}
103+
```
104+
87105
### <a name="units"></a>NVA Infrastructure Units
88106

89107
When you create an NVA in a Virtual WAN hub, you must choose the number of NVA Infrastructure Units you want to deploy it with. An **NVA Infrastructure Unit** is a unit of aggregate bandwidth capacity for an NVA in a Virtual WAN hub. An **NVA Infrastructure Unit** is similar to a VPN [Scale Unit](pricing-concepts.md#scale-unit) in terms of the way you think about capacity and sizing.

0 commit comments

Comments
 (0)