Skip to content

Commit 7d9fcc6

Browse files
committed
Review fixes
1 parent 3563093 commit 7d9fcc6

3 files changed

Lines changed: 7 additions & 6 deletions

File tree

articles/virtual-network/accelerated-networking-mana-existing-sizes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Dsv5, Dv5, Ddsv5, Ddv5, Dlsv5, Dldsv5, Esv5, Ev5, Edsv5, Edv5, Ebsv5, Ebdsv5, Ds
3333

3434
Note that some of these VM sizes will soon be retired. It's highly recommended that customers utilize the latest generations of Azure VMs for improved performance, functionality, and resiliency.
3535

36-
### Will existing VMs deployed on MANA hardware?
36+
### Will existing VMs be deployed on MANA hardware?
3737
VMs already deployed will be eligible to land on MANA capable hardware following a "stop-deallocate and start" command, or through a redeploy operation. All new VMs in the series listed above are eligible to be deployed on MANA capable hardware as well.
3838

3939
### How will I know if my VM is deployed on MANA capable hardware?

articles/virtual-network/accelerated-networking-mana-nva-opt-out.md renamed to articles/virtual-network/accelerated-networking-mana-network-virtual-appliance-opt-out.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: MANA support for Network Virtual Appliances (NVAs)
3+
titleSuffix: Microsoft Azure Network Adapter
34
description: Learn about MANA support for Network Virtual Appliances (NVAs) using existing VM sizes, including how to use Azure Policy to manage MANA deployments and ensure optimal performance.
45
author: mattmcinnes
56
ms.author: mattmcinnes
@@ -41,7 +42,7 @@ No action is required if the NVA or the underlying OS already supports MANA.
4142

4243
### What if additional time is needed to migrate to an NVA that fully supports MANA?
4344

44-
You can apply a tag to Network Virtual Appliances (NVAs), VMs, and Virtual Machine Scale Sets (VMSS) for MANA support. This tag provides a temporary reprieve and allows time to migrate to an NVA or operating system that fully supports MANA.
45+
You can apply a tag to Network Virtual Appliances (NVAs), VMs, and Virtual Machine Scale Sets for MANA support. This tag provides a temporary reprieve and allows time to migrate to an NVA or operating system that fully supports MANA.
4546

4647
### What if the NVA is acquired directly from the NVA provider and not through the Azure Marketplace?
4748

@@ -57,7 +58,7 @@ The tag will be usable until the end of September 2026. After this time, the sys
5758

5859
### What support is available to help apply this tag on my applicable resources?
5960

60-
To apply this tag across applicable resources at scale, you can apply a built-in Azure Policy definition: **Adds a tag to Network Virtual Appliances (NVAs) VMs and VMSS for MANA support**.
61+
To apply this tag across applicable resources at scale, you can apply a built-in Azure Policy definition: **Adds a tag to Network Virtual Appliances (NVAs) VMs and Virtual Machine Scale Sets for MANA support**.
6162

6263
Like any other Azure Policy assignment, it can be applied at the following scope levels to cover applicable resources underneath it:
6364

@@ -69,7 +70,7 @@ Like any other Azure Policy assignment, it can be applied at the following scope
6970
| Resource Group | Resources in that resource group |
7071
| Resource | Single resource |
7172

72-
The policy applies a specific tag, `LegacyVMNVA`, to NVA deployments. The policy covers individual workloads and VMSS scenarios as well.
73+
The policy applies a specific tag, `LegacyVMNVA`, to NVA deployments. The policy covers individual workloads and Virtual Machine Scale Sets scenarios as well.
7374

7475
Logic in the policy definition scopes the tag application to specific NVA publishers and associated product IDs, which are available in the Azure Marketplace. The tag inhibits deployment of NVAs on MANA-enabled hardware.
7576

@@ -113,7 +114,7 @@ VM sizes are specified in [Microsoft Azure Network Adapter (MANA) support for ex
113114

114115
### How can I verify that the tag has been applied to my resources?
115116

116-
The tag `LegacyVMNVA` is visible in the Azure portal for IaaS VMs and for VM Scale Set (VMSS) scenarios.
117+
The tag `LegacyVMNVA` is visible in the Azure portal for IaaS VMs and for VM Scale Set scenarios.
117118

118119
Azure Policy collects and aggregates compliance data, which can be used to see which resources are *compliant* against the definition (the tag is applied) versus which ones are *non-compliant* and must be remediated (the tag isn't applied). This compliance report can be viewed in the Azure portal under the **Policy** tab.
119120

articles/virtual-network/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,7 @@
213213
- name: MANA support for existing VM sizes
214214
href: accelerated-networking-mana-existing-sizes.md
215215
- name: MANA on Network Virtual Appliances (NVAs) for existing VM sizes
216-
href: accelerated-networking-mana-nva-opt-out.md
216+
href: accelerated-networking-mana-network-virtual-appliance-opt-out.md
217217
- name: Migrate a VM public IP address to a NAT gateway
218218
href: /azure/nat-gateway/tutorial-migrate-ilip-nat?toc=%2Fazure%2Fvirtual-network%2Ftoc.json
219219
- name: Network bandwidth

0 commit comments

Comments
 (0)