fix more links

Author: v-thepet

articles/batch/batch-automatic-scaling.md

@@ -22,7 +22,7 @@ You can enable automatic scaling when you create a pool, or apply it to an exist
 
 ## Autoscale formulas
 
-An autoscale formula is a string value that you define that contains one or more statements. The autoscale formula is assigned to a pool's [autoScaleFormula](/rest/api/batchservice/enable-automatic-scaling-on-a-pool) element (Batch REST) or [CloudPool.AutoScaleFormula](/dotnet/api/microsoft.azure.batch.cloudpool.autoscaleformula) property (Batch .NET). The Batch service uses your formula to determine the target number of compute nodes in the pool for the next interval of processing. The formula string can't exceed 8 KB, can include up to 100 statements that are separated by semicolons, and can include line breaks and comments.
+An autoscale formula is a string value that you define that contains one or more statements. The autoscale formula is assigned to a pool's [autoScaleFormula](/rest/api/batchservice/pools/enable-pool-auto-scale) element (Batch REST) or [CloudPool.AutoScaleFormula](/dotnet/api/microsoft.azure.batch.cloudpool.autoscaleformula) property (Batch .NET). The Batch service uses your formula to determine the target number of compute nodes in the pool for the next interval of processing. The formula string can't exceed 8 KB, can include up to 100 statements that are separated by semicolons, and can include line breaks and comments.
 
 You can think of automatic scaling formulas as a Batch autoscale "language." Formula statements are free-formed expressions that can include both *service-defined variables*, which are defined by the Batch service, and *user-defined variables*. Formulas can perform various operations on these values by using built-in types, operators, and functions. For example, a statement might take the following form:
 
@@ -349,7 +349,7 @@ $NodeDeallocationOption = taskcompletion;
 By default, the Batch service adjusts a pool's size according to its autoscale formula every 15 minutes. This interval is configurable by using the following pool properties:
 
 - [CloudPool.AutoScaleEvaluationInterval](/dotnet/api/microsoft.azure.batch.cloudpool.autoscaleevaluationinterval) (Batch .NET)
-- [autoScaleEvaluationInterval](/rest/api/batchservice/enable-automatic-scaling-on-a-pool) (REST API)
+- [autoScaleEvaluationInterval](/rest/api/batchservice/pools/enable-pool-auto-scale) (REST API)
 
 The minimum interval is five minutes, and the maximum is 168 hours. If an interval outside this range is specified, the Batch service returns a Bad Request (400) error.
 
@@ -446,7 +446,7 @@ response = batch_service_client.pool.enable_auto_scale(pool_id, auto_scale_formu
 Each Batch SDK provides a way to enable automatic scaling. For example:
 
 - [BatchClient.PoolOperations.EnableAutoScaleAsync](/dotnet/api/microsoft.azure.batch.pooloperations.enableautoscaleasync) (Batch .NET)
-- [Enable automatic scaling on a pool](/rest/api/batchservice/enable-automatic-scaling-on-a-pool) (REST API)
+- [Enable automatic scaling on a pool](/rest/api/batchservice/pools/enable-pool-auto-scale) (REST API)
 
 When you enable autoscaling on an existing pool, keep in mind:
 
@@ -501,7 +501,7 @@ Before you can evaluate an autoscale formula, you must first enable autoscaling
 
     These Batch .NET methods require the ID of an existing pool and a string containing the autoscale formula to evaluate.
 
-- [Evaluate an automatic scaling formula](/rest/api/batchservice/evaluate-an-automatic-scaling-formula)
+- [Evaluate an automatic scaling formula](/rest/api/batchservice/pools/evaluate-pool-auto-scale)
 
     In this REST API request, specify the pool ID in the URI, and the autoscale formula in the *autoScaleFormula* element of the request body. The response of the operation contains any error information that might be related to the formula.
 
@@ -593,7 +593,7 @@ In Batch .NET, the [CloudPool.AutoScaleRun](/dotnet/api/microsoft.azure.batch.cl
 - [AutoScaleRun.Results](/dotnet/api/microsoft.azure.batch.autoscalerun.results)
 - [AutoScaleRun.Error](/dotnet/api/microsoft.azure.batch.autoscalerun.error)
 
-In the REST API, [information about a pool](/rest/api/batchservice/get-information-about-a-pool) includes the latest automatic scaling run information in the [autoScaleRun](/rest/api/batchservice/get-information-about-a-pool) property.
+In the REST API, [information about a pool](/rest/api/batchservice/pools/get-pool) includes the latest automatic scaling run information in the [autoScaleRun](/rest/api/batchservice/pools/get-pool#autoscalerun) property.
 
 The following C# example uses the Batch .NET library to print information about the last autoscaling run on pool *myPool*.
 

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

@@ -142,13 +142,13 @@ 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/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) |
+| [CloudTask.ListNodeFiles](/dotnet/api/microsoft.azure.batch.cloudtask) |[List the files associated with a task](/rest/api/batchservice/tasks/list-task-files) |
+| [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/jobs/list-job-preparation-and-release-task-status) |
 | [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.ListNodeFiles](/dotnet/api/microsoft.azure.batch.joboperations) |[List the files on a node](/rest/api/batchservice/nodes/list-node-files) |
 | [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) |
+| [JobScheduleOperations.ListJobs](/dotnet/api/microsoft.azure.batch.jobscheduleoperations) |[List the jobs associated with a job schedule](/rest/api/batchservice/jobs/list-jobs-from-schedule) |
 | [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) |
 
@@ -162,7 +162,7 @@ Property names in filter, select, and expand strings must reflect their REST API
 | [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/jobs/get-job) |
 | [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) |
+| [ComputeNode](/dotnet/api/microsoft.azure.batch.computenode) |[Get information about a node](/rest/api/batchservice/nodes/get-node) |
 | [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) |
 

articles/batch/batch-pool-node-error-checking.md

@@ -117,9 +117,9 @@ Even when Batch successfully allocates nodes in a pool, various issues can cause
 
 You can specify an optional [start task](/rest/api/batchservice/tasks/create-task) for a pool. As with any task, the start task uses a command line and can download resource files from storage. The start task runs for each node when the node starts. The `waitForSuccess` property specifies whether Batch waits until the start task completes successfully before it schedules any tasks to a node. If you configure the node to wait for successful start task completion, but the start task fails, the node isn't usable but still incurs charges.
 
-You can detect start task failures by using the [taskExecutionResult](/rest/api/batchservice/computenode/get#taskexecutionresult) and  [taskFailureInformation](/rest/api/batchservice/computenode/get#taskfailureinformation) properties of the top-level [startTaskInformation](/rest/api/batchservice/computenode/get#starttaskinformation) node property.
+You can detect start task failures by using the [taskExecutionResult](/rest/api/batchservice/nodes/get-node#batchtaskexecutionresult) and  [taskFailureInformation](/rest/api/batchservice/nodes/get-node#batchtaskfailureinfo) properties of the top-level [startTaskInformation](/rest/api/batchservice/nodes/get-node#batchstarttaskinfo) node property.
 
-A failed start task also causes Batch to set the [computeNodeState](/rest/api/batchservice/computenode/get#computenodestate) to `starttaskfailed`, if `waitForSuccess` was set to `true`.
+A failed start task also causes Batch to set the [computeNodeState](/rest/api/batchservice/nodes/get-node#batchnodestate) to `starttaskfailed`, if `waitForSuccess` was set to `true`.
 
 As with any task, there can be many causes for a start task failure. To troubleshoot, check the *stdout*, *stderr*, and any other task-specific log files.
 
@@ -129,21 +129,21 @@ Start tasks must be re-entrant, because the start task can run multiple times on
 
 You can specify one or more application packages for a pool. Batch downloads the specified package files to each node and uncompresses the files after the node starts, but before it schedules tasks. It's common to use a start task command with application packages, for example to copy files to a different location or to run setup.
 
-If an application package fails to download and uncompress, the [computeNodeError](/rest/api/batchservice/computenode/get#computenodeerror) property reports the failure, and sets the node state to `unusable`.
+If an application package fails to download and uncompress, the [computeNodeError](/rest/api/batchservice/nodes/get-node#batchnodeerror) property reports the failure, and sets the node state to `unusable`.
 
 ### Container download failure
 
-You can specify one or more container references on a pool. Batch downloads the specified containers to each node. If the container fails to download, the [computeNodeError](/rest/api/batchservice/computenode/get#computenodeerror) property reports the failure, and sets the node state to `unusable`.
+You can specify one or more container references on a pool. Batch downloads the specified containers to each node. If the container fails to download, the [computeNodeError](/rest/api/batchservice/nodes/get-node#batchnodeerror) property reports the failure, and sets the node state to `unusable`.
 
 ### Node OS updates
 
 For Windows pools, `enableAutomaticUpdates` is set to `true` by default. Although allowing automatic updates is recommended, updates can interrupt task progress, especially if the tasks are long-running. You can set this value to `false` if you need to ensure that an OS update doesn't happen unexpectedly.
 
 ### Node in unusable state
 
-Batch might set the [computeNodeState](/rest/api/batchservice/computenode/get#computenodestate) to `unusable` for many reasons. You can't schedule tasks to an `unusable` node, but the node still incurs charges.
+Batch might set the [computeNodeState](/rest/api/batchservice/nodes/get-node#batchnodestate) to `unusable` for many reasons. You can't schedule tasks to an `unusable` node, but the node still incurs charges.
 
-If Batch can determine the cause, the [computeNodeError](/rest/api/batchservice/computenode/get#computenodeerror) property reports it. If a node is in an `unusable` state, but has no [computeNodeError](/rest/api/batchservice/computenode/get#computenodeerror), it means Batch is unable to communicate with the VM. In this case, Batch always tries to recover the VM. However, Batch doesn't automatically attempt to recover VMs that failed to install application packages or containers, even if their state is `unusable`.
+If Batch can determine the cause, the [computeNodeError](/rest/api/batchservice/nodes/get-node#batchnodeerror) property reports it. If a node is in an `unusable` state, but has no [computeNodeError](/rest/api/batchservice/nodes/get-node#batchnodeerror), it means Batch is unable to communicate with the VM. In this case, Batch always tries to recover the VM. However, Batch doesn't automatically attempt to recover VMs that failed to install application packages or containers, even if their state is `unusable`.
 
 Other reasons for `unusable` nodes might include the following causes:
 
@@ -180,13 +180,13 @@ When you add a pool in the Azure portal, you can display the full list of VM siz
 
 You can specify a retention time for files written by each task. The retention time determines how long to keep the task files before automatically cleaning them up. You can reduce the retention time to lower storage requirements.
 
-If the temporary or OS disk runs out of space, or is close to running out of space, the node moves to the `unusable` [computeNoteState](/rest/api/batchservice/computenode/get#computenodestate), and the node error says that the disk is full.
+If the temporary or OS disk runs out of space, or is close to running out of space, the node moves to the `unusable` [computeNoteState](/rest/api/batchservice/nodes/get-node#computenodestate), and the node error says that the disk is full.
 
-If you're not sure what's taking up space on the node, try remote connecting to the node and investigating manually. You can also use the [File - List From Compute Node](/rest/api/batchservice/file/listfromcomputenode) API to examine files, for example task outputs, in Batch managed folders. This API only lists files in the Batch managed directories. If your tasks created files elsewhere, this API doesn't show them.
+If you're not sure what's taking up space on the node, try remote connecting to the node and investigating manually. You can also use the [File - List From Compute Node](/rest/api/batchservice/nodes/list-node-files) API to examine files, for example task outputs, in Batch managed folders. This API only lists files in the Batch managed directories. If your tasks created files elsewhere, this API doesn't show them.
 
 After you make sure to retrieve any data you need from the node or upload it to a durable store, you can delete data as needed to free up space.
 
-You can delete old completed jobs or tasks whose task data is still on the nodes. Look in the `recentTasks` collection in the [taskInformation](/rest/api/batchservice/computenode/get#taskinformation) on the node, or use the [File - List From Compute Node](/rest/api/batchservice/file/listfromcomputenode) API. Deleting a job deletes all the tasks in the job. Deleting the tasks in the job triggers deletion of data in the task directories on the nodes, and frees up space. Once you've freed up enough space, reboot the node. The node should move out of `unusable` state and into `idle` again.
+You can delete old completed jobs or tasks whose task data is still on the nodes. Look in the `recentTasks` collection in the [taskInformation](/rest/api/batchservice/nodes/get-node#taskinformation) on the node, or use the [File - List From Compute Node](/rest/api/batchservice/nodes/list-node-files) API. Deleting a job deletes all the tasks in the job. Deleting the tasks in the job triggers deletion of data in the task directories on the nodes, and frees up space. Once you've freed up enough space, reboot the node. The node should move out of `unusable` state and into `idle` again.
 
 To recover an unusable node in [VirtualMachineConfiguration](/rest/api/batchservice/pools/get-pool#add-a-virtualmachineconfiguration-pool-with-os-disk) pools, you can remove the node from the pool by using the [Pool - Remove Nodes](/rest/api/batchservice/pools/remove-nodes) API. Then you can grow the pool again to replace the bad node with a fresh one. 
 

articles/batch/virtual-file-mount.md

@@ -188,7 +188,7 @@ Optionally, you can also access the mount files by using the direct path. If you
 
 ## Troubleshoot mount issues
 
-If a mount configuration fails, the compute node fails and the node state is set to **Unusable**. To diagnose a mount configuration failure, inspect the [ComputeNodeError](/rest/api/batchservice/computenode/get#computenodeerror) property for details on the error.
+If a mount configuration fails, the compute node fails and the node state is set to **Unusable**. To diagnose a mount configuration failure, inspect the [ComputeNodeError](/rest/api/batchservice/nodes/get-node#batchnodeerror) property for details on the error.
 
 To get log files for debugging, you can use the [OutputFiles](batch-task-output-files.md#specify-output-files-for-task-output) API to upload the *\*.log* files. The *\*.log* files contain information about the file system mount at the `AZ_BATCH_NODE_MOUNTS_DIR` location. Mount log files have the format: *\<type>-\<mountDirOrDrive>.log* for each mount. For example, a CIFS mount at a mount directory named *test* has a mount log file named: *cifs-test.log*.