Skip to content

Commit bb6ec80

Browse files
committed
latest permissions
1 parent d8785a2 commit bb6ec80

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -87,21 +87,21 @@ NVA Partners may create different resources depending on their appliance deploym
8787

8888
### Managed resource group permissions
8989

90-
By default, all managed resource groups have an deny-all Azure Active Directory assignment. These deny-all assignments prevent customers from calling write operations on any resources in the managed resource group, including the Network Virtual Appliance resource.
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.
9191

92-
However, partners may create exceptions and whitelist specific actions that customers are allowed to perform on resources deployed in managed resource groups.
92+
However, partners may create exceptions for specific actions that customers are allowed to perform on resources deployed in managed resource groups.
9393

94-
Permissions on resources in managed resource groups are not dynamically updated as new permitted actions are added by partners and require manual intervention.
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.
9595

96-
To refresh permissions on the managed resource groups, customers can leverage the [Refresh Permissions REST API ](/rest/api/managedapplications/applications/refresh-permissions).
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.
97100
98101
```http-interactive
99-
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName}/refreshPermissions?api-version=2019-07-01
102+
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName}/refreshPermissions?api-version=2019-07-01&targetVersion={targetVersion}
100103
```
101104

102-
103-
104-
105105
### <a name="units"></a>NVA Infrastructure Units
106106

107107
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)