Rename V2 md to simplified-node-communication-pool-no-public-ip.md

lilinvictorms · lilinvictorms · commit 61023d4d2388 · 2022-05-31T14:29:36.000-07:00
diff --git a/articles/batch/TOC.yml b/articles/batch/TOC.yml
@@ -176,7 +176,7 @@
       href: batch-pool-no-public-ip-address.md
     - name: Create simplified node communication pool without public IP addresses
       displayName: private
-      href: simplified-node-communication-pool-no-public-ip-addresses.md
+      href: simplified-node-communication-pool-no-public-ip.md
     - name: Create a pool with ephemeral OS disk nodes
       href: create-pool-ephemeral-os-disk.md
     - name: Use extensions with pools
diff --git a/articles/batch/batch-pool-no-public-ip-address.md b/articles/batch/batch-pool-no-public-ip-address.md
@@ -10,7 +10,7 @@ ms.custom: references_regions
 
 > [!IMPORTANT]
 > - Support for pools without public IP addresses in Azure Batch is currently in public preview for the following regions: France Central, East Asia, West Central US, South Central US, West US 2, East US, North Europe, East US 2, Central US, West Europe, North Central US, West US, Australia East, Japan East, Japan West.
-> - This preview version will be replaced by [Azure Batch pool withoud public IP addresses (V2)](batch-pool-no-public-ip-address-v2.md), which requires using the new [simplified compute node communication](simplified-compute-node-communication.md) with Batch accounts.
+> - This preview version will be replaced by [Simplified node communication pool without public IP addresses](simplified-node-communication-pool-no-public-ip.md).
 > - This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
 > - For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
diff --git a/articles/batch/create-pool-availability-zones.md b/articles/batch/create-pool-availability-zones.md
@@ -78,4 +78,4 @@ Request body
 
 - Learn about the [Batch service workflow and primary resources](batch-service-workflow-features.md) such as pools, nodes, jobs, and tasks.
 - Learn about [creating a pool in a subnet of an Azure virtual network](batch-virtual-network.md).
-- Learn about [creating an Azure Batch pool without public IP addresses](./batch-pool-no-public-ip-address-v2.md).
+- Learn about [creating an Azure Batch pool without public IP addresses](./simplified-node-communication-pool-no-public-ip.md).
diff --git a/articles/batch/create-pool-public-ip.md b/articles/batch/create-pool-public-ip.md
@@ -11,7 +11,7 @@ In Azure Batch, you can [create a Batch pool in a subnet of an Azure virtual net
 
 You can create a list of static public IP addresses to use with the VMs in your pool instead. In some cases, you might need to control the list of public IP addresses to make sure they don't change unexpectedly.  For example, you might be working with an external service, such as a database, which restricts access to specific IP addresses.
 
-For information about creating pools without public IP addresses, read [Create an Azure Batch pool without public IP addresses](./batch-pool-no-public-ip-address-v2.md).
+For information about creating pools without public IP addresses, read [Create an Azure Batch pool without public IP addresses](./simplified-node-communication-pool-no-public-ip.md).
 
 ## Prerequisites
 
diff --git a/articles/batch/private-connectivity.md b/articles/batch/private-connectivity.md
@@ -84,20 +84,20 @@ When you're creating the private endpoint, you can integrate it with a [private
 
 With the introduction of the new private endpoint sub-resource `nodeManagement` for Batch node management endpoint, the default private DNS zone for Batch account is simplified from `privatelink.<region>.batch.azure.com` to `privatelink.batch.azure.com`. The existing private endpoints for sub-resource `batchAccount` will continue to work, and no action is needed.
 
-However, if you have existing `batchAccount` private endpoints that are enabled with automatic private DNS integration, configure these endpoints together with newly created private endpoints in the same virtual network.
+However, if you have existing `batchAccount` private endpoints that are enabled with automatic private DNS integration using previous private DNS zone, extra configuration is needed for the new `batchAccount` private endpoint to create in the same virtual network:
 
-- If you don't need the previous private endpoint anymore, delete the private endpoint. Also unlink the previous private DNS zone from your virtual network.
+- If you don't need the previous private endpoint anymore, delete the private endpoint. Also unlink the previous private DNS zone from your virtual network. No more configuration is needed for the new private endpoint.
 
-You can create a private endpoint with private DNS integration in a virtual network that has any existing `batchAccount` private endpoint with the previous private DNS zone:
- 
-1. After the new private endpoint is created, make sure the automatic private DNS integration has a DNS A record created in the new private DNS zone `privatelink.batch.azure.com`. For example, `myaccount.<region>     A  <IPv4 address>`.
+- Otherwise, after the new private endpoint is created:
 
-1. Go to previous private DNS zone `privatelink.<region>.batch.azure.com`. 
+  1. make sure the automatic private DNS integration has a DNS A record created in the new private DNS zone `privatelink.batch.azure.com`. For example, `myaccount.<region>     A  <IPv4 address>`.
 
-1. Manually add a DNS CNAME record. For example, `myaccount     CNAME => myaccount.<region>.privatelink.batch.azure.com`.
+  1. Go to previous private DNS zone `privatelink.<region>.batch.azure.com`.
+
+  1. Manually add a DNS CNAME record. For example, `myaccount     CNAME => myaccount.<region>.privatelink.batch.azure.com`.
 
 > [!IMPORTANT]
-> This manual mitigation is only needed when you create a new private endpoint with private DNS integration in the same virtual network which has existing private endpoints.
+> This manual mitigation is only needed when you create a new **batchAccount** private endpoint with private DNS integration in the same virtual network which has existing private endpoints.
 
 ## Pricing
 
@@ -116,7 +116,7 @@ When creating private endpoint with your Batch account, keep in mind the followi
 ## Next steps
 
 - Learn how to [create Batch pools in virtual networks](batch-virtual-network.md).
-- Learn how to [create Batch pools without public IP addresses](batch-pool-no-public-ip-address-v2.md).
+- Learn how to [create Batch pools without public IP addresses](simplified-node-communication-pool-no-public-ip.md).
 - Learn how to [configure public network access for Batch accounts](public-network-access.md).
 - Learn how to [manage private endpoint connections for Batch accounts](manage-private-endpoint-connections.md).
 - Learn about [Azure Private Link](../private-link/private-link-overview.md).
diff --git a/articles/batch/security-best-practices.md b/articles/batch/security-best-practices.md
@@ -13,7 +13,7 @@ By default, Azure Batch accounts have a public endpoint and are publicly accessi
 
 :::image type="content" source="media/security-best-practices/typical-environment.png" alt-text="Diagram showing a typical Batch environment.":::
 
-Many features are available to help you create a more secure Azure Batch deployment. You can restrict access to nodes and reduce the discoverability of the nodes from the internet by [provisioning the pool without public IP addresses](batch-pool-no-public-ip-address-v2.md). The compute nodes can securely communicate with other virtual machines or with an on-premises network by [provisioning the pool in a subnet of an Azure virtual network](batch-virtual-network.md). And you can enable [private access from virtual networks](private-connectivity.md) from a service powered by Azure Private Link.
+Many features are available to help you create a more secure Azure Batch deployment. You can restrict access to nodes and reduce the discoverability of the nodes from the internet by [provisioning the pool without public IP addresses](simplified-node-communication-pool-no-public-ip.md). The compute nodes can securely communicate with other virtual machines or with an on-premises network by [provisioning the pool in a subnet of an Azure virtual network](batch-virtual-network.md). And you can enable [private access from virtual networks](private-connectivity.md) from a service powered by Azure Private Link.
 
 :::image type="content" source="media/security-best-practices/secure-environment.png" alt-text="Diagram showing a more secure Batch environment.":::
 
@@ -99,7 +99,7 @@ By default, all the compute nodes in an Azure Batch virtual machine configuratio
 
 To restrict access to these nodes and reduce the discoverability of these nodes from the internet, you can provision the pool without public IP addresses.
 
-For more information, see [Create a pool without public IP addresses](batch-pool-no-public-ip-address-v2.md).
+For more information, see [Create a pool without public IP addresses](simplified-node-communication-pool-no-public-ip.md).
 
 #### Limit remote access to pool nodes
 
@@ -108,7 +108,7 @@ By default, Batch allows a node user with network connectivity to connect extern
 To limit remote access to nodes, use one of the following methods:
 
 - Configure the [PoolEndpointConfiguration](/rest/api/batchservice/pool/add#poolendpointconfiguration) to deny access. The appropriate network security group (NSG) will be associated with the pool.
-- Create your pool [without public IP addresses](batch-pool-no-public-ip-address-v2.md). By default, these pools can't be accessed outside of the VNet.
+- Create your pool [without public IP addresses](simplified-node-communication-pool-no-public-ip.md). By default, these pools can't be accessed outside of the VNet.
 - Associate an NSG with the VNet to deny access to the RDP or SSH ports.
 - Don't create any users on the node. Without any node users, remote access won't be possible.
 
diff --git a/articles/batch/simplified-compute-node-communication.md b/articles/batch/simplified-compute-node-communication.md
@@ -127,4 +127,4 @@ The following are known limitations for accounts that opt in to simplified compu
 - Learn how to [use private endpoints with Batch accounts](private-connectivity.md).
 - Learn more about [pools in virtual networks](batch-virtual-network.md).
 - Learn how to [create a pool with specified public IP addresses](create-pool-public-ip.md).
-- Learn how to [create a pool without public IP addresses](batch-pool-no-public-ip-address-v2.md).
+- Learn how to [create a pool without public IP addresses](simplified-node-communication-pool-no-public-ip.md).
diff --git a/articles/batch/simplified-node-communication-pool-no-public-ip.md b/articles/batch/simplified-node-communication-pool-no-public-ip.md
@@ -9,7 +9,7 @@ ms.custom: references_regions
 # Create a simplified node communication pool without public IP addresses (preview)
 
 > [!NOTE]
-> This is replacement to the current preview version of [Azure Batch pool withoud public IP addresses](batch-pool-no-public-ip-address.md). This new version requires [using simplified compute node communication](simplified-compute-node-communication.md).
+> This replaces the previous preview version of [Azure Batch pool without public IP addresses](batch-pool-no-public-ip-address.md). This new version requires [using simplified compute node communication](simplified-compute-node-communication.md).
 
 > [!IMPORTANT]
 > - Support for pools without public IP addresses in Azure Batch is currently in public preview for selected regions.
@@ -124,11 +124,11 @@ In a pool without public IP addresses, your virtual machines won't be able to ac
 Another way to provide outbound connectivity is to use a user-defined route (UDR). This lets you route traffic to a proxy machine that has public internet access, for example [Azure Firewall](../firewall/overview.md).
 
 > [!IMPORTANT]
-> There is no extra network resource (load balancer, network security group) created for pools without public IP addresses (No Public IP v2). Since the compute nodes in the pool are not bound to any load balancer, Azure may provide [Default Outbound Access](../virtual-network/ip-services/default-outbound-access.md). However, Default Outbound Access is not suitable for production workloads, so it is strongly recommended to bring your own Internet outbound access.
+> There is no extra network resource (load balancer, network security group) created for simplified node communication pools without public IP addresses. Since the compute nodes in the pool are not bound to any load balancer, Azure may provide [Default Outbound Access](../virtual-network/ip-services/default-outbound-access.md). However, Default Outbound Access is not suitable for production workloads, so it is strongly recommended to bring your own Internet outbound access.
 
-## Migration from No Public IP v1 pools
+## Migration from previous preview version of No Public IP pools
 
-For existing pools using the previous preview version of [Azure Batch No Public IP pool](batch-pool-no-public-ip-address.md), they can only be migrated if the pool was created in a [virtual network](batch-virtual-network.md). The pool can be migrated following the [opt-in process for simplified node communication](simplified-compute-node-communication.md):
+For existing pools that use the [previous preview version of Azure Batch No Public IP pool](batch-pool-no-public-ip-address.md), it's only possible to migrate pools created in a [virtual network](batch-virtual-network.md). To migrate the pool, follow the [opt-in process for simplified node communication](simplified-compute-node-communication.md):
 
 1. Opt in to use simplified node communication.
 1. Create a [private endpoint for Batch node management](private-connectivity.md) in the virtual network.
