You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-wan/about-nva-hub.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,10 @@
2
2
title: 'About Network Virtual Appliances - Virtual WAN hub'
3
3
titleSuffix: Azure Virtual WAN
4
4
description: Learn about Network Virtual Appliances in a Virtual WAN hub.
5
-
services: virtual-wan
6
5
author: wtnlee
7
6
ms.service: virtual-wan
8
7
ms.topic: conceptual
9
-
ms.date: 06/02/2021
8
+
ms.date: 09/14/2022
10
9
ms.author: wellee
11
10
ms.custom: references_regions
12
11
# Customer intent: As someone with a networking background, I want to learn about Network Virtual Appliances in a Virtual WAN hub.
@@ -32,7 +31,7 @@ Deploying NVAs into a Virtual WAN hub provides the following benefits:
32
31
> [!IMPORTANT]
33
32
> To ensure you get the best support for this integrated solution, make sure you have similar levels of support entitlement with both Microsoft and your Network Virtual Appliance provider.
@@ -87,11 +86,11 @@ NVA Partners may create different resources depending on their appliance deploym
87
86
88
87
### Managed resource group permissions
89
88
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.
89
+
By default, all managed resource groups have a 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
90
92
91
However, partners may create exceptions for specific actions that customers are allowed to perform on resources deployed in managed resource groups.
93
92
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.
93
+
Permissions on resources in existing managed resource groups aren't dynamically updated as new permitted actions are added by partners and require a manual refresh.
95
94
96
95
To refresh permissions on the managed resource groups, customers can leverage the [Refresh Permissions REST API ](/rest/api/managedapplications/applications/refresh-permissions).
0 commit comments