Skip to content

Commit aa52eeb

Browse files
committed
Update about-nva-hub.md
1 parent 6fd17c3 commit aa52eeb

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

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

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,10 @@
22
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.
5-
services: virtual-wan
65
author: wtnlee
76
ms.service: virtual-wan
87
ms.topic: conceptual
9-
ms.date: 06/02/2021
8+
ms.date: 09/14/2022
109
ms.author: wellee
1110
ms.custom: references_regions
1211
# 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:
3231
> [!IMPORTANT]
3332
> 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.
3433
35-
## <a name ="partner"></a> Partners
34+
## Partners
3635

3736
[!INCLUDE [NVA partners](../../includes/virtual-wan-nva-hub-partners.md)]
3837

@@ -87,11 +86,11 @@ NVA Partners may create different resources depending on their appliance deploym
8786

8887
### Managed resource group permissions
8988

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.
9190

9291
However, partners may create exceptions for specific actions that customers are allowed to perform on resources deployed in managed resource groups.
9392

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.
9594

9695
To refresh permissions on the managed resource groups, customers can leverage the [Refresh Permissions REST API ](/rest/api/managedapplications/applications/refresh-permissions).
9796

0 commit comments

Comments
 (0)