Merge pull request #211828 from Padmalathas/Padmalathas-migration-edits

Padmalathas migration edits

Author: v-ccolin

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

@@ -18,14 +18,14 @@ In late 2021, we launched a simplified compute node communication model for Azur
 [Simplified Compute Node Communication Pools without Public IPs](./simplified-node-communication-pool-no-public-ip.md) requires using simplified compute node communication. It provides customers with enhanced security for their workload environments on network isolation and data exfiltration to Azure Batch accounts. Its key benefits include:
 
 * Allow creating simplified node communication pool without public IP addresses.
-* Support Batch private pool using a new private endpoint (sub-resource nodeManagement) for Azure Batch account.
+* Support Batch private pool using a new private endpoint (sub-resource: **nodeManagement**) for Azure Batch account.
 * Simplified private link DNS zone for Batch account private endpoints: 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: configure IP address network rules to restrict public network access with Batch accounts.
 
 ## Migration steps
 
-Batch pool without public IP addresses (classic) will retire on **31/2023 and will be updated to simplified compute node communication pools without public IPs. For existing pools that use the previous preview version of Batch pool without public IP addresses (classic), it's only possible to migrate pools created in a virtual network. To migrate the pool, follow the opt-in process for simplified compute node communication:
+Batch pool without public IP addresses (classic) will retire on **31 March 2023** and will be updated to simplified compute node communication pools without public IPs. For existing pools that use the previous preview version of Batch pool without public IP addresses (classic), it's only possible to migrate pools created in a virtual network. To migrate the pool, follow the opt-in process for 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).
 
@@ -59,16 +59,16 @@ Batch pool without public IP addresses (classic) will retire on **31/2023 and wi
 
 * 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).
+    Similar to Batch pools without public IP addresses (classic). As there's 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).
 
 * 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.
 
 * What if I don’t migrate to simplified compute node communication pools without public IPs?
 
-    After **31 March 2023**, we will stop supporting Batch pool without public IP addresses. The functionality of the existing pool in that configuration may break, such as scale out operations, or may be actively scaled down to zero at any point in time after that date.
+    After **31 March 2023**, we'll stop supporting Batch pool without public IP addresses. The functionality of the existing pool in that configuration may break, such as scale-out operations, or may be actively scaled down to zero at any point in time after that date.
 
 ## Next steps
 
-For more information, refer to [Simplified compute node communication](./simplified-compute-node-communication.md).
+For more information, see [Simplified compute node communication](./simplified-compute-node-communication.md).

articles/batch/job-pool-lifetime-statistics-migration-guide.md

@@ -11,24 +11,24 @@ ms.date: 08/15/2022
 
 The Azure Batch service currently supports API for Job/Pool to retrieve lifetime statistics. The API is used to get lifetime statistics for all the Pools/Jobs in the specified batch account or for a specified Pool/Job. The API collects the statistical data from when the Batch account was created until the last time updated or entire lifetime of the specified Job/Pool. Job/Pool lifetime statistics API is helpful for customers to analyze and evaluate their usage.
 
-To make the statistical data available for customers, the Batch service allocates batch pools and schedule jobs with an in-house MapReduce implementation to perform background periodic roll-up of statistics. The aggregation is performed for all accounts/pools/jobs in each region, no matter if customer needs or queries the stats for their account/pool/job. The operating cost includes eleven VMs allocated in each region to execute MapReduce aggregation jobs. For busy regions, we had to increase the pool size further to accommodate the extra aggregation load.
+To make the statistical data available for customers, the Batch service allocates batch pools and schedule jobs with an in-house MapReduce implementation to perform background periodic roll-up of statistics. The aggregation is performed for all accounts/pools/jobs in each region, no matter if customer needs or queries the stats for their account/pool/job. The operating cost includes 11 VMs allocated in each region to execute MapReduce aggregation jobs. For busy regions, we had to increase the pool size further to accommodate the extra aggregation load.
 
 The MapReduce aggregation logic was implemented with legacy code, and no new features are being added or improvised due to technical challenges with legacy code. Still, the legacy code and its hosting repo need to be updated frequently to accommodate ever growing load in production and to meet security/compliance requirements. In addition, since the API is featured to provide lifetime statistics, the data is growing and demands more storage and performance issues, even though most customers aren't using the API. Batch service currently eats up all the compute and storage usage charges associated with MapReduce pools and jobs.
 
-The purpose of the API is designed and maintained to serve the customer in troubleshooting. However, not many customers use it in real life, and the customers are interested in extracting the details for not more than a month. Now more advanced ways of log/job/pool data can be collected and used on a need basis using Azure portal logs, Alerts, Log export, and other methods. Therefore, we are retire Job/Pool Lifetime.
+The purpose of the API is designed and maintained to serve the customer in troubleshooting. However, not many customers use it in real life, and the customers are interested in extracting the details for not more than a month. Now more advanced ways of log/job/pool data can be collected and used on a need basis using Azure portal logs, Alerts, Log export, and other methods. Therefore, we're retiring the Job/Pool Lifetime.
 
 Job/Pool Lifetime Statistics API will be retired on **30 April 2023**. Once complete, the API will no longer work and will return an appropriate HTTP response error code back to the client.
 
 ## FAQ
 
 * Is there an alternate way to view logs of Pool/Jobs?
 
-   Azure portal has various options to enable the logs, namely system logs, diagnostic logs. Refer [Monitor Batch Solutions](./monitoring-overview.md) for more information.
+   Azure portal has various options to enable the logs, namely system logs, diagnostic logs. See [Monitor Batch Solutions](./monitoring-overview.md) for more information.
 
 * Can customers extract logs to their system if the API doesn't exist? 
 
-   Azure portal log feature allows every customer to extract the output and error logs to their workspace. Refer [Monitor with Application Insights](./monitor-application-insights.md) for more information.
+   Azure portal log feature allows every customer to extract the output and error logs to their workspace. See [Monitor with Application Insights](./monitor-application-insights.md) for more information.
 
 ## Next steps
 
-For more information, refer to [Azure Monitor Logs](../azure-monitor/logs/data-platform-logs.md).
+For more information, see [Azure Monitor Logs](../azure-monitor/logs/data-platform-logs.md).

articles/batch/low-priority-vms-retirement-migration-guide.md

@@ -13,7 +13,7 @@ Azure Batch offers Low priority and Spot virtual machines (VMs). The virtual mac
 
 Low priority VMs enable the customer to take advantage of unutilized capacity. The amount of available unutilized capacity can vary based on size, region, time of day, and more. At any point in time when Azure needs the capacity back, we'll evict low-priority VMs. Therefore, the low-priority offering is excellent for flexible workloads, like large processing jobs, dev/test environments, demos, and proofs of concept. In addition, low-priority VMs can easily be deployed through our virtual machine scale set offering.
 
-Low priority VMs are a deprecated feature, and it will never become Generally Available (GA). Spot VMs are the official preemptible offering from the Compute platform, and is generally available. Therefore, we'll retire Low Priority VMs on **30 September 2025**. After that, we'll stop supporting Low priority VMs. The existing Low priority pools may no longer work or be provisioned.
+Low priority VMs are a deprecated feature, and it will never become Generally Available (GA). Spot VMs are the official preemptible offering from the Compute platform, and are generally available. Therefore, we'll retire Low Priority VMs on **30 September 2025**. After that, we'll stop supporting Low priority VMs. The existing Low priority pools may no longer work or be provisioned.
 
 ## Retirement alternative
 
@@ -25,7 +25,7 @@ The other key difference is that Azure Spot pricing is variable and based on the
 
 When it comes to eviction, you have two policy options to choose between:
 
-* Stop/Deallocate (default) – when evicted, the VM is deallocated, but you keep (and pay for) underlying disks. This is ideal for cases where the state is stored on disks.
+* Stop/Deallocate (default) – when evicted, the VM is deallocated, but you keep (and pay for) underlying disks. This is the ideal for cases where the state is stored on disks.
 * Delete – when evicted, the VM and underlying disks are deleted.
 
 While similar in idea, there are a few key differences between these two purchasing options:
@@ -38,12 +38,12 @@ While similar in idea, there are a few key differences between these two purchas
 
 ## Migration steps
 
-Customers in User Subscription mode have the option to include Spot VMs using the following the steps below:
+Customers in User Subscription mode can include Spot VMs using the following the steps below:
 
 1. In the Azure portal, select the Batch account and view the existing pool or create a new pool.
 2. Under **Scale**, users can choose 'Target dedicated nodes' or 'Target Spot/low-priority nodes.'
 
-  ![Scale Target Nodes](../batch/media/certificates/lowpriorityvms-scale-target-nodes.png)
+  ![Scale Target Nodes](../batch/media/certificates/low-priority-vms-scale-target-nodes.png)
 
 3. Navigate to the existing Pool and select 'Scale' to update the number of Spot nodes required based on the job scheduled. 
 4. Click **Save**.
@@ -54,15 +54,15 @@ Customers in Batch Managed mode must recreate the Batch account, pool, and jobs
 
 * How to create a new Batch account /job/pool?
 
-    Refer to the quick start [link](./batch-account-create-portal.md) on creating a new Batch account/pool/task.
+    See the quick start [link](./batch-account-create-portal.md) on creating a new Batch account/pool/task.
 
 * Are Spot VMs available in Batch Managed mode?
 
     No, Spot VMs are available in User Subscription mode - Batch accounts only.
 
 * What is the pricing and eviction policy of Spot VMs? Can I view pricing history and eviction rates?
 
-    Refer to [Spot VMs](../virtual-machines/spot-vms.md) for more information on using Spot VMs. Yes, you can see historical pricing and eviction rates per size in a region in the portal.
+    See [Spot VMs](../virtual-machines/spot-vms.md) for more information on using Spot VMs. Yes, you can see historical pricing and eviction rates per size in a region in the portal.
 
 ## Next steps