edits

Author: ktoliver

articles/batch/batch-certificate-migration-guide.md

@@ -1,28 +1,28 @@
 ---
-title: Migrate Azure Batch access management to Azure Key Vault
-description: Learn how to migrate access management from Azure Batch to Azure Key Vault to prepare for end of support for certificates in Batch.
+title: Migrate Batch certificates to Azure Key Vault
+description: Learn how to migrate access management from using certificates in Azure Batch to Azure Key Vault and plan for feature end of support.
 author: harperche
 ms.author: harpercheng
 ms.service: batch
 ms.topic: how-to
 ms.date: 08/15/2022
 ---
 
-# Migrate Azure Batch access management to Azure Key Vault (feature retirement)
+# Migrate Batch certificates to Azure Key Vault
 
-On *February 29, 2024*, the certificates feature for Azure Batch access management will be retired. Learn how to migrate access management from using certificates in Azure Batch to using Azure Key Vault.
+On *February 29, 2024*, the certificates feature for Azure Batch access management will be retired. Learn how to migrate your access management approach from using certificates in Azure Batch to using Azure Key Vault.
 
-## Batch secure access options
+## About the feature
 
 Often, you need to store secure data in an application. Your data must be securely managed so that only administrators or authorized users can access it.
 
 Azure Batch offers two ways to secure access management. You can use a certificate that you create and manage in Azure Batch or you can use Azure Key Vault to store an access key. Using a key vault is an Azure standard way to deliver more controlled secure access management.
 
 Currently, you can use a certificate at the account level in Azure Batch. You must generate the certificate and upload it manually to Batch by using the Azure portal. To access the certificate, the certificate must be associated with and installed for only the current user. A certificate typically is valid for one year, and it must be updated each year.
 
-## Certificates in Batch retirement
+## Feature end of support
 
-To move toward a simpler, standardized way to secure access to your Batch resources, on *February 29, 2024*, we'll retire the certificates feature in Azure Batch. We recommend that you instead use Azure Key Vault as a standard and more modern method to secure your resources in Batch.
+To move toward a simpler, standardized way to secure access to your Batch resources, on February 29, 2024, we'll retire the certificates feature in Azure Batch. We recommend that you use Azure Key Vault as a standard and more modern method to secure your resources in Batch.
 
 In Key Vault, you get these benefits:
 
@@ -32,7 +32,7 @@ In Key Vault, you get these benefits:
 
 After the certificates feature in Azure Batch is retired on February 29, 2024, a certificate in Batch might not work as expected. After that date, you won't be able to create a pool by using a certificate. Pools that continue to use certificates after the feature is retired might increase in size and cost.
 
-## Use Key Vault to secure your Batch resources
+## Alternative: Use Key Vault to secure your Batch resources
 
 Azure Key Vault is an Azure service you can use to store and manage secrets, certificates, tokens, keys, and other configuration values that give authenticated users access to secure applications and services. Key Vault is based on the idea that security is improved and standardized when you remove hard-coded secrets and keys from application code that's deployed.
 

articles/batch/batch-pools-without-public-ip-addresses-classic-retirement-migration-guide.md

@@ -1,5 +1,5 @@
 ---
-title: Opt in to migrate Azure Batch pools without public IP addresses (classic)
+title: Migrate pools without public IP addresses (classic) in Batch
 description: Learn how to opt in to migrate Azure Batch pools without public IP addresses (classic) and plan for feature end of support.
 author: harperche
 ms.author: harpercheng
@@ -8,31 +8,31 @@ ms.topic: how-to
 ms.date: 09/01/2022
 ---
 
-# Opt in to migrate Batch pools without public IP addresses (feature retirement)
+# Migrate pools without public IP addresses (classic) in Batch
 
-Azure Batch pools without public IP addresses (classic) will retire on *March 31, 2023*. Existing pools will migrate to simplified compute node communication pools without public IP addresses. You must opt in to migrate your Batch pools.
+The Azure Batch feature pools without public IP addresses (classic) will retire on *March 31, 2023*. Learn how to migrate eligible pools to simplified compute node communication (preview) pools without public IP addresses. You must opt in to migrate your Batch pools.
 
-## About Batch pools without public IP addresses
+## About the feature
 
-By default, all the compute nodes in an Azure Batch virtual machine (VM) configuration pool are assigned a public IP address. The Batch service uses the IP address to schedule tasks and for communication with compute nodes, including outbound access to the internet. To restrict access to these nodes and reduce the discoverability of these nodes from the internet, we released [Batch pools without public IP addresses (classic)](./batch-pool-no-public-ip-address.md).
+By default, all the compute nodes in an Azure Batch virtual machine (VM) configuration pool are assigned a public IP address. The Batch service uses the IP address to schedule tasks and for communication with compute nodes, including outbound access to the internet. To restrict access to these nodes and reduce public discoverability of the nodes, we released the Batch feature [pools without public IP addresses (classic)](./batch-pool-no-public-ip-address.md). Currently, the feature is in preview.
 
-## End of support for pools without public IP addresses
+## Feature end of support
 
-In late 2021, we launched a simplified compute node communication model for Azure Batch. The new communication model improves security and simplifies the user experience. Batch pools no longer require inbound internet access and outbound access to Azure Storage. Batch pools now need only outbound access to the Batch service. As a result, Batch pools without public IP addresses (classic), currently in public preview, will be retired on *March 31, 2023*. The feature will be replaced by simplified compute node communication pools without public IPs.
+In late 2021, we launched a simplified compute node communication model for Azure Batch. The new communication model improves security and simplifies the user experience. Batch pools no longer require inbound internet access and outbound access to Azure Storage. Batch pools now need only outbound access to the Batch service. As a result, on March 31, 2023, we will retire the Batch feature pools without public IP addresses (classic). The feature will be replaced in Batch with simplified compute node communication for pools without public IP addresses.
 
-## Use simplified node communication for a pool with no public IP address
+## Alternative: Use simplified node communication
 
-The alternative to using a Batch pool without a public IP address (classic) requires using [simplified node communication](./simplified-node-communication-pool-no-public-ip.md). The option gives you enhanced security for your workload environments on network isolation and data exfiltration to Azure Batch accounts. Its key benefits include:
+The alternative to using a Batch pool without a public IP address (classic) requires using [simplified node communication](./simplified-node-communication-pool-no-public-ip.md). The option gives you enhanced security for your workload environments on network isolation and data exfiltration to Batch accounts. The key benefits include:
 
 - You can create simplified node communication pools without public IP addresses.
-- You can create a Batch private pool by using a new private endpoint (sub-resource nodeManagement) for an Azure Batch account.
-- A simplified private link DNS zone for Batch account private endpoints. The private link changed from `privatelink.<region>.batch.azure.com` to `privatelink.batch.azure.com`.
-- Mutable public network access for Batch accounts.
-- Firewall support for Batch account public endpoints. You can configure IP address network rules to restrict public network access with Batch accounts.
+- You can create a Batch private pool by using a new private endpoint (in the nodeManagement sub-resource) for an Azure Batch account.
+- Use a simplified private link DNS zone for Batch account private endpoints. The private link changes from `privatelink.<region>.batch.azure.com` to `privatelink.batch.azure.com`.
+- Use mutable public network access for Batch accounts.
+- Get firewall support for Batch account public endpoints. You can configure IP address network rules to restrict public network access to your Batch account.
 
 ## Opt in and migrate your eligible pools
 
-Batch pools without public IP addresses (classic) will retire on *March 31, 2023*. For existing pools that use the earlier preview version of Batch pools without public IP addresses (classic), you can migrate only pools that you created in a virtual network. To migrate the pool, follow the opt-in process for simplified compute node communication:
+When the Batch feature pools without public IP addresses (classic) retires on March 31, 2023, existing pools that use the feature can migrate only if the pools were created in a virtual network. To migrate your eligible pools, complete the opt-in process to use simplified compute node communication:
 
 1. Opt in to [use simplified compute node communication](./simplified-compute-node-communication.md#opt-your-batch-account-in-or-out-of-simplified-compute-node-communication).
 
@@ -52,29 +52,31 @@ Batch pools without public IP addresses (classic) will retire on *March 31, 2023
 
 ## FAQs
 
-- How can I migrate my Batch pool without public IP addresses (classic) to simplified compute node communication pools without public IPs?
+- How can I migrate my Batch pools that use the pools without public IP addresses (classic) feature to simplified compute node communication?
 
-  You can migrate your pool to simplified compute node communication pools only if you created the pool in a virtual network. Otherwise, create a new simplified compute node communication pool without public IP addresses.
+  If you created the pools in a virtual network, [opt in and complete the migration process](#opt-in-and-migrate-your-eligible-pools).
+  
+  If your pools weren't created in a virtual network, create a new simplified compute node communication pool without public IP addresses.
 
 - What differences will I see in billing?
 
-  Compared with Batch pools without public IP addresses (classic), the simplified compute node communication pools without public IPs support will reduce costs because it won’t need to create the following network resources: load balancer, network security groups, and private link service with the Batch pool deployments. However, there will be a [cost associated with  private link](https://azure.microsoft.com/pricing/details/private-link/) or other outbound network connectivity used by pools, as controlled by the user, to allow communication with the Batch service without public IP addresses.
+  Compared to Batch pools without public IP addresses (classic), the simplified compute node communication pools without public IPs support reduces cost because it doesn't create the following network resources with Batch pool deployments: load balancer, network security groups, and private link service. However, you'll see a cost associated with [Azure Private Link](https://azure.microsoft.com/pricing/details/private-link/) or other outbound network connectivity that your pools use for communication with the Batch service.
 
 - Will I see any changes in performance?
 
   No known performance differences exist for simplified compute node communication pools without public IPs compared to Batch pools without public IP addresses (classic).
 
 - How can I connect to my pool nodes for troubleshooting?
 
-  Similar to Batch pools without public IP addresses (classic). As there is no public IP address for the Batch pool, users will need to connect their pool nodes from within the virtual network. You can create a jump box VM in the virtual network or use other remote connectivity solutions like [Azure Bastion](../bastion/bastion-overview.md).
+  The process is similar to the way you connect for pools without public IP addresses (classic). Because there the Batch pool doesn't have a public IP address, connect to your pool nodes from within the virtual network. You can create a jump box VM in the virtual network or use a remote connectivity solution like [Azure Bastion](../bastion/bastion-overview.md).
 
 - Will there be any change to how my workloads are downloaded from Azure Storage?
 
-  Similar to Batch pools without public IP addresses (classic), users will need to provide their own internet outbound connectivity if their workloads need access to other resources like Azure Storage.
+  Like for Batch pools without public IP addresses (classic), you must provide your own internet outbound connectivity if your workloads need access to a resource like Azure Storage.
 
-- What if I don’t migrate to simplified compute node communication pools without public IPs?
+- What if I don’t migrate my pools to simplified compute node communication pools without public IP addresses?
 
-  After *March 31, 2023*, we will stop supporting Batch pools without public IP addresses. The functionality of the existing pool in that configuration might break, including scale-out operations, or the pool might be actively scaled down to zero at any point in time after that date.
+  After *March 31, 2023*, we will stop supporting Batch pools without public IP addresses (classic). After that date, existing pool functionality, including scale-out operations, might break. The pool might actively be scaled down to zero at any time.
 
 ## Next steps
 

articles/batch/batch-tls-101-migration-guide.md

@@ -1,24 +1,24 @@
 ---
-title: Migrate to TLS 1.2 in Azure Batch client code
-description: Learn how to migrate to TLS 1.2 in Azure Batch client code to prepare for feature end of support for TLS 1.0/1.1.
+title: Migrate client code to TLS 1.2 in Azure Batch
+description: Learn how to migrate client code to TLS 1.2 in Azure Batch to prepare for end of support for TLS 1.0 and TLS 1.1.
 author: harperche
 ms.author: harpercheng
 ms.service: batch
 ms.topic: how-to
 ms.date: 08/16/2022
 ---
 
-# Migrate client code to TLS 1.2 in Batch (feature retirement)
+# Migrate client code to TLS 1.2 in Batch
 
 To support security best practices and remain in compliance with industry standards, Azure Batch will retire Transport Layer Security (TLS) 1.0 and TLS 1.1 in Azure Batch on *March 31, 2023*. Learn how to migrate to TLS 1.2 in the client code you manage by using Batch.
 
-## End of support for TLS 1.0 and TLS 1.1
+## End of support for TLS 1.0 and TLS 1.1 in Batch
 
 TLS versions 1.0 and 1.1 are known to be susceptible to BEAST and POODLE attacks and to have other Common Vulnerabilities and Exposures (CVE) weaknesses. TLS 1.0 and 1.1 don't support the modern encryption methods and cipher suites that the Payment Card Industry (PCI) compliance standards recommends. Microsoft is participating in an industry-wide push toward the exclusive use of TLS version 1.2 or later.
 
 Most customers have already migrated to TLS 1.2. Customers who continue to use TLS 1.0 or 1.1 can be identified via existing BatchOperation telemetry. If you're using TLS 1.0 or 1.1, to avoid disruption to your Batch workflows, you must adjust existing workflows to ensure that you're using TLS 1.2.
 
-## Migrate to TLS 1.2
+## Alternative: Migrate to TLS 1.2
 
 To avoid disruption to your Batch workflows, you must update your client code to use TLS 1.2 before the TLS 1.0 and 1.1 retirement in Batch on March 31, 2023.
 
@@ -30,7 +30,7 @@ For specific development use cases, see the following information:
 
 - If you use the .NET Framework and you *can't* upgrade to .NET 4.7 or later, see the guidance in [TLS for network programming](/dotnet/framework/network-programming/tls) to enforce TLS 1.2.
 
-For TLS best practices, see [TLS best practices for the .NET Framework](/dotnet/framework/network-programming/tls).
+For more information, see [TLS best practices for the .NET Framework](/dotnet/framework/network-programming/tls).
 
 ## FAQs