Fix links

Author: cdpark

articles/batch/batch-applications-to-pool-nodes.md

@@ -20,9 +20,9 @@ You need to determine the scope of a file - is the file required for a pool, a j
 
 For applications or data that need to be installed on every node in the pool, use pool start task resource files. Use this method along with either an [application package](batch-application-packages.md) or the start task's resource file collection in order to perform an install command.  
 
-For example, you can use the start task command line to move or install applications. You can also specify a list of files or containers in an Azure storage account. For more information, see [Add#ResourceFile in REST documentation](/rest/api/batchservice/pool/add#resourcefile).
+For example, you can use the start task command line to move or install applications. You can also specify a list of files or containers in an Azure storage account. For more information, see [Add#ResourceFile in REST documentation](/rest/api/batchservice/pools/create-pool#resourcefile).
 
-If every job that runs on the pool runs an application (.exe) that must first be installed with a .msi file, you'll need to set the start task's **wait for success** property to **true**. For more information, see [Add#StartTask in REST documentation](/rest/api/batchservice/pool/add#starttask).
+If every job that runs on the pool runs an application (.exe) that must first be installed with a .msi file, you'll need to set the start task's **wait for success** property to **true**. For more information, see [Add#StartTask in REST documentation](/rest/api/batchmanagement/pool/create#starttask).
 
 ## Application package references
 

articles/batch/batch-custom-images.md

@@ -39,7 +39,7 @@ To scale Batch pools reliably with a managed image, we recommend creating the ma
 
 ### Prepare a VM
 
-If you're creating a new VM for the image, use a first party Azure Marketplace image supported by Batch as the base image for your managed image. Only first party images can be used as a base image. To get a full list of Azure Marketplace image references supported by Azure Batch, see [List Supported Images](/rest/api/batchservice/account/listsupportedimages).
+If you're creating a new VM for the image, use a first party Azure Marketplace image supported by Batch as the base image for your managed image. Only first party images can be used as a base image. To get a full list of Azure Marketplace image references supported by Azure Batch, see [List Supported Images](/rest/api/batchservice/pools/list-supported-images).
 
 > [!NOTE]
 > You can't use a third-party image that has additional license and purchase terms as your base image. For information about these Marketplace images, see the guidance for [Linux](/azure/virtual-machines/linux/cli-ps-findimage#check-the-purchase-plan-information) or [Windows](/azure/virtual-machines/windows/cli-ps-findimage#view-purchase-plan-properties) VMs.
@@ -138,7 +138,7 @@ Also note the following considerations:
 
   Limits may be reduced if you configure the pool with [inbound NAT pools](pool-endpoint-configuration.md).
 
-- **Resize timeout** - If your pool contains a fixed number of nodes (doesn't autoscale), increase the resizeTimeout property of the pool to a value such as 20-30 minutes. If your pool doesn't reach its target size within the timeout period, perform another [resize operation](/rest/api/batchservice/pool/resize).
+- **Resize timeout** - If your pool contains a fixed number of nodes (doesn't autoscale), increase the resizeTimeout property of the pool to a value such as 20-30 minutes. If your pool doesn't reach its target size within the timeout period, perform another [resize operation](/rest/api/batchservice/pools/resize-pool).
 
   If you plan a pool with more than 300 compute nodes, you might need to resize the pool multiple times to reach the target size.
 

articles/batch/batch-customer-managed-key.md

@@ -215,7 +215,7 @@ az batch account set \
 - **How can I rotate my keys?** Customer-managed keys aren't automatically rotated unless the [key is versionless with an appropriate key rotation policy set within Key Vault](/azure/key-vault/keys/how-to-configure-key-rotation). To manually rotate the key, update the Key Identifier that the account is associated with.
 - **After I restore access how long will it take for the Batch account to work again?** It can take up to 10 minutes for the account to be accessible again once access is restored.
 - **While the Batch Account is unavailable what happens to my resources?** Any pools that are active when Batch access to the customer-managed key is lost will continue to run. However, the nodes in these pools will transition into an unavailable state, and tasks will stop running (and be requeued). Once access is restored, nodes become available again, and tasks are restarted.
-- **Does this encryption mechanism apply to VM disks in a Batch pool?** No. For Cloud Services Configuration pools (which are [deprecated](https://azure.microsoft.com/updates/azure-batch-cloudserviceconfiguration-pools-will-be-retired-on-29-february-2024/)), no encryption is applied for the OS and temporary disk. For Virtual Machine Configuration pools, the OS and any specified data disks are encrypted with a Microsoft platform managed key by default. Currently, you can't specify your own key for these disks. To encrypt the temporary disk of VMs for a Batch pool with a Microsoft platform managed key, you must enable the [diskEncryptionConfiguration](/rest/api/batchservice/pool/add#diskencryptionconfiguration) property in your [Virtual Machine Configuration](/rest/api/batchservice/pool/add#virtualmachineconfiguration) Pool. For highly sensitive environments, we recommend enabling temporary disk encryption and avoiding storing sensitive data on OS and data disks. For more information, see [Create a pool with disk encryption enabled](./disk-encryption.md)
+- **Does this encryption mechanism apply to VM disks in a Batch pool?** No. For Cloud Services Configuration pools (which are [deprecated](https://azure.microsoft.com/updates/azure-batch-cloudserviceconfiguration-pools-will-be-retired-on-29-february-2024/)), no encryption is applied for the OS and temporary disk. For Virtual Machine Configuration pools, the OS and any specified data disks are encrypted with a Microsoft platform managed key by default. Currently, you can't specify your own key for these disks. To encrypt the temporary disk of VMs for a Batch pool with a Microsoft platform managed key, you must enable the [diskEncryptionConfiguration](/rest/api/batchservice/pools/create-pool#diskencryptionconfiguration) property in your [Virtual Machine Configuration](/rest/api/batchservice/pools/create-pool#virtualmachineconfiguration) Pool. For highly sensitive environments, we recommend enabling temporary disk encryption and avoiding storing sensitive data on OS and data disks. For more information, see [Create a pool with disk encryption enabled](./disk-encryption.md)
 - **Is the system-assigned managed identity on the Batch account available on the compute nodes?** No. The system-assigned managed identity is currently used only for accessing the Azure Key Vault for the customer-managed key. To use a user-assigned managed identity on compute nodes, see [Configure managed identities in Batch pools](managed-identity-pools.md).
 
 ## Next steps

articles/batch/batch-efficient-list-queries.md

@@ -52,7 +52,7 @@ You can use the [Batch .NET](/dotnet/api/microsoft.azure.batch) and [Batch REST]
 
 For the Batch .NET API, see the [ODATADetailLevel Class properties](/dotnet/api/microsoft.azure.batch.odatadetaillevel#properties). Also review the section [Efficient querying in Batch .NET](#efficient-querying-in-batch-net).
 
-For the Batch REST API, see the [Batch REST API reference](/rest/api/batchservice/). Find the **List** reference for the resource you want to query. Then, review the **URI Parameters** section for details about `$filter`, `$select`, and `$expand`. For example, see the [URI parameters for Pool - List](/rest/api/batchservice/pool/list#uri-parameters). Also see [how to make efficient Batch queries with the Azure CLI](batch-cli-get-started.md#query-batch-resources-efficiently).
+For the Batch REST API, see the [Batch REST API reference](/rest/api/batchservice/). Find the **List** reference for the resource you want to query. Then, review the **URI Parameters** section for details about `$filter`, `$select`, and `$expand`. For example, see the [URI parameters for Pool - List](/rest/api/batchservice/pools/create-pool#uri-parameters). Also see [how to make efficient Batch queries with the Azure CLI](batch-cli-get-started.md#query-batch-resources-efficiently).
 
 > [!NOTE]
 > When constructing any of the three query string types, you must ensure that the property names and case match that of their REST API element counterparts. For example, when working with the .NET [CloudTask](/dotnet/api/microsoft.azure.batch.cloudtask) class, you must specify **state** instead of **State**, even though the .NET property is [CloudTask.State](/dotnet/api/microsoft.azure.batch.cloudtask.state#Microsoft_Azure_Batch_CloudTask_State). For more information, see the [property mappings between the .NET and REST APIs](#mappings-for-select-strings).
@@ -141,16 +141,16 @@ Property names in filter, select, and expand strings must reflect their REST API
 
 | .NET list methods | REST list requests |
 | --- | --- |
-| [CertificateOperations.ListCertificates](/dotnet/api/microsoft.azure.batch.certificateoperations) |[List the certificates in an account](/rest/api/batchservice/certificate/list) |
+| [CertificateOperations.ListCertificates](/dotnet/api/microsoft.azure.batch.certificateoperations) |[List the certificates in an account](/rest/api/batchmanagement/certificate/list-by-batch-account) |
 | [CloudTask.ListNodeFiles](/dotnet/api/microsoft.azure.batch.cloudtask) |[List the files associated with a task](/rest/api/batchservice/file/listfromtask) |
 | [JobOperations.ListJobPreparationAndReleaseTaskStatus](/dotnet/api/microsoft.azure.batch.joboperations) |[List the status of the job preparation and job release tasks for a job](/rest/api/batchservice/job/listpreparationandreleasetaskstatus) |
-| [JobOperations.ListJobs](/dotnet/api/microsoft.azure.batch.joboperations) |[List the jobs in an account](/rest/api/batchservice/job/list) |
+| [JobOperations.ListJobs](/dotnet/api/microsoft.azure.batch.joboperations) |[List the jobs in an account](/rest/api/batchservice/jobs/list-jobs-from-schedule) |
 | [JobOperations.ListNodeFiles](/dotnet/api/microsoft.azure.batch.joboperations) |[List the files on a node](/rest/api/batchservice/file/listfromcomputenode) |
-| [JobOperations.ListTasks](/dotnet/api/microsoft.azure.batch.joboperations) |[List the tasks associated with a job](/rest/api/batchservice/task/list) |
+| [JobOperations.ListTasks](/dotnet/api/microsoft.azure.batch.joboperations) |[List the tasks associated with a job](/rest/api/batchservice/tasks/list-tasks) |
 | [JobScheduleOperations.ListJobSchedules](/dotnet/api/microsoft.azure.batch.jobscheduleoperations) |[List the job schedules in an account](/rest/api/batchservice/jobschedule/list) |
 | [JobScheduleOperations.ListJobs](/dotnet/api/microsoft.azure.batch.jobscheduleoperations) |[List the jobs associated with a job schedule](/rest/api/batchservice/job/listfromjobschedule) |
-| [PoolOperations.ListComputeNodes](/dotnet/api/microsoft.azure.batch.pooloperations) |[List the compute nodes in a pool](/rest/api/batchservice/computenode/list) |
-| [PoolOperations.ListPools](/dotnet/api/microsoft.azure.batch.pooloperations) |[List the pools in an account](/rest/api/batchservice/pool/list) |
+| [PoolOperations.ListComputeNodes](/dotnet/api/microsoft.azure.batch.pooloperations) |[List the compute nodes in a pool](/rest/api/batchservice/nodes/list-nodes) |
+| [PoolOperations.ListPools](/dotnet/api/microsoft.azure.batch.pooloperations) |[List the pools in an account](/rest/api/batchservice/pools/list-pools) |
 
 ### Mappings for select strings
 
@@ -159,16 +159,16 @@ Property names in filter, select, and expand strings must reflect their REST API
 
 | Batch .NET types | REST API entities |
 | --- | --- |
-| [Certificate](/dotnet/api/microsoft.azure.batch.certificate) |[Get information about a certificate](/rest/api/batchservice/certificate/get) |
+| [Certificate](/dotnet/api/microsoft.azure.batch.certificate) |[Get information about a certificate](/rest/api/batchmanagement/certificate/get) |
 | [CloudJob](/dotnet/api/microsoft.azure.batch.cloudjob) |[Get information about a job](/rest/api/batchservice/job/get) |
-| [CloudJobSchedule](/dotnet/api/microsoft.azure.batch.cloudjobschedule) |[Get information about a job schedule](/rest/api/batchservice/jobschedule/get) |
+| [CloudJobSchedule](/dotnet/api/microsoft.azure.batch.cloudjobschedule) |[Get information about a job schedule](/rest/api/batchservice/jobs/get-job) |
 | [ComputeNode](/dotnet/api/microsoft.azure.batch.computenode) |[Get information about a node](/rest/api/batchservice/computenode/get) |
-| [CloudPool](/dotnet/api/microsoft.azure.batch.cloudpool) |[Get information about a pool](/rest/api/batchservice/pool/get) |
-| [CloudTask](/dotnet/api/microsoft.azure.batch.cloudtask) |[Get information about a task](/rest/api/batchservice/task/get) |
+| [CloudPool](/dotnet/api/microsoft.azure.batch.cloudpool) |[Get information about a pool](/rest/api/batchservice/pools/get-pool) |
+| [CloudTask](/dotnet/api/microsoft.azure.batch.cloudtask) |[Get information about a task](/rest/api/batchservice/tasks/get-task) |
 
 ## Example: construct a filter string
 
-To construct a filter string for [ODATADetailLevel.FilterClause](/dotnet/api/microsoft.azure.batch.odatadetaillevel.filterclause), find the [corresponding REST API page](#mappings-for-filter-strings). Selectable properties and their supported operators are in the first multi-row table. For example, to retrieve all tasks whose exit code was nonzero, check [List the tasks associated with a job](/rest/api/batchservice/task/list) for the applicable property string and allowable operators:
+To construct a filter string for [ODATADetailLevel.FilterClause](/dotnet/api/microsoft.azure.batch.odatadetaillevel.filterclause), find the [corresponding REST API page](#mappings-for-filter-strings). Selectable properties and their supported operators are in the first multi-row table. For example, to retrieve all tasks whose exit code was nonzero, check [List the tasks associated with a job](/rest/api/batchservice/tasks/list-tasks) for the applicable property string and allowable operators:
 
 | Property | Operations allowed | Type |
 |:--- |:--- |:--- |
@@ -180,7 +180,7 @@ The related filter string is:
 
 ## Example: construct a select string
 
-To construct [ODATADetailLevel.SelectClause](/dotnet/api/microsoft.azure.batch.odatadetaillevel.selectclause), find the [corresponding REST API page](#mappings-for-filter-strings) for the entity that you're listing. Selectable properties and their supported operators are in the first multi-row table. For example, to retrieve only the ID and command line for each task in a list, check [Get information about a task](/rest/api/batchservice/task/get):
+To construct [ODATADetailLevel.SelectClause](/dotnet/api/microsoft.azure.batch.odatadetaillevel.selectclause), find the [corresponding REST API page](#mappings-for-filter-strings) for the entity that you're listing. Selectable properties and their supported operators are in the first multi-row table. For example, to retrieve only the ID and command line for each task in a list, check [Get information about a task](/rest/api/batchservice/tasks/get-task):
 
 | Property | Type | Notes |
 |:--- |:--- |:--- |

articles/batch/batch-get-resource-counts.md

@@ -21,9 +21,9 @@ At times, the numbers returned by these operations may not be up to date. If you
 The `Get` Task Counts operation counts tasks by the following states:
 
 - **Active**: A task that's queued and ready to run but isn't currently assigned to any compute node. A task is also `active` if it's [dependent on a parent task](batch-task-dependencies.md) that hasn't yet completed.
-- **Running**: A task that has been assigned to a compute node but hasn't yet finished. A task is counted as `running` when its state is either `preparing` or `running`, as indicated by the [`Get`information about a task](/rest/api/batchservice/task/get) operation.
+- **Running**: A task that has been assigned to a compute node but hasn't yet finished. A task is counted as `running` when its state is either `preparing` or `running`, as indicated by the [`Get`information about a task](/rest/api/batchservice/tasks/get-task) operation.
 - **Completed**: A task that's no longer eligible to run, because it either finished successfully, or finished unsuccessfully and also exhausted its retry limit.
-- **Succeeded**: A task where the result of task execution is `success`. Batch determines whether a task has succeeded or failed by checking the `TaskExecutionResult` property of the [executionInfo](/rest/api/batchservice/task/get) property.
+- **Succeeded**: A task where the result of task execution is `success`. Batch determines whether a task has succeeded or failed by checking the `TaskExecutionResult` property of the [executionInfo](/rest/api/batchservice/tasks/get-task) property.
 - **Failed**: A task where the result of task execution is `failure`.
 
 The following .NET code sample shows how to retrieve task counts by state.
@@ -53,7 +53,7 @@ The List Pool Node Counts operation counts compute nodes by the following states
 - **Reimaging**: A node where the OS is being reinstalled.
 - **Running** : A node that is running one or more tasks (other than the start task).
 - **Starting**: A node where the Batch service is starting up.
-- **StartTaskFailed**: A node where the [start task](/rest/api/batchservice/pool/add#starttask) failed after all retries, and `waitForSuccess` is enabled. This node cannot run tasks.
+- **StartTaskFailed**: A node where the [start task](/rest/api/batchmanagement/pool/create#starttask) failed after all retries, and `waitForSuccess` is enabled. This node cannot run tasks.
 - **Unknown**: A node that lost contact with the Batch service and whose state isn't known.
 - **Unusable**: A node that can't be used for task execution because of errors.
 - **WaitingForStartTask**: A node on which the start task is running, but `waitForSuccess` is enabled and it hasn't completed.

articles/batch/batch-pool-update-properties.md

@@ -146,16 +146,10 @@ Request Body
 ### Data Plane: Pool - Patch or Update Properties
 
 The Data Plane offers the ability to either patch or update select pool properties. The
-available APIs are the [Pool - Patch API](/rest/api/batchservice/pool/patch) or the
-[Pool - Update Properties API](/rest/api/batchservice/pool/update-properties) as part of
+available API is the [Pool - Update Properties API](/rest/api/batchmanagement/pool/update) as part of
 the [Batch Data Plane API or SDK](batch-apis-tools.md#batch-service-apis).
 
-The [Patch API](/rest/api/batchservice/pool/patch) allows patching of select pool properties
-as specified in the documentation such as the `startTask`. Since this operation is a `PATCH`,
-only pool properties specified in the request are updated. If properties aren't specified as
-part of the request, then the existing values remain unmodified.
-
-The [Update Properties API](/rest/api/batchservice/pool/update-properties) allows select
+The [Update Properties API](/rest/api/batchmanagement/pool/update) allows select
 update of the pool properties as specified in the documentation. This request fully
 replaces the existing properties, therefore any property that isn't specified in the
 request is removed.