diff --git a/sdk/batch/Azure.ResourceManager.Batch/src/Generated/Models/BatchAccountPoolStartTask.cs b/sdk/batch/Azure.ResourceManager.Batch/src/Generated/Models/BatchAccountPoolStartTask.cs
index f04f01cbcbe1..6fbed2628cfa 100644
--- a/sdk/batch/Azure.ResourceManager.Batch/src/Generated/Models/BatchAccountPoolStartTask.cs
+++ b/sdk/batch/Azure.ResourceManager.Batch/src/Generated/Models/BatchAccountPoolStartTask.cs
@@ -25,7 +25,7 @@ public BatchAccountPoolStartTask()
         /// <param name="resourceFiles"> A list of files that the Batch service will download to the compute node before running the command line. </param>
         /// <param name="environmentSettings"> A list of environment variable settings for the start task. </param>
         /// <param name="userIdentity"> If omitted, the task runs as a non-administrative user unique to the task. </param>
-        /// <param name="maxTaskRetryCount"> The Batch service retries a task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the task. If the maximum retry count is -1, the Batch service retries the task without limit. </param>
+        /// <param name="maxTaskRetryCount"> The Batch service retries a task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the task. If the maximum retry count is -1, the Batch service retries the task without limit. Default is 0. </param>
         /// <param name="waitForSuccess"> If true and the start task fails on a compute node, the Batch service retries the start task up to its maximum retry count (maxTaskRetryCount). If the task has still not completed successfully after all retries, then the Batch service marks the compute node unusable, and will not schedule tasks to it. This condition can be detected via the node state and scheduling error detail. If false, the Batch service will not wait for the start task to complete. In this case, other tasks can start executing on the compute node while the start task is still running; and even if the start task fails, new tasks will continue to be scheduled on the node. The default is true. </param>
         /// <param name="containerSettings"> When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all task environment variables are mapped into the container, and the task command line is executed in the container. </param>
         internal BatchAccountPoolStartTask(string commandLine, IList<BatchResourceFile> resourceFiles, IList<BatchEnvironmentSetting> environmentSettings, BatchUserIdentity userIdentity, int? maxTaskRetryCount, bool? waitForSuccess, BatchTaskContainerSettings containerSettings)
@@ -47,7 +47,7 @@ internal BatchAccountPoolStartTask(string commandLine, IList<BatchResourceFile>
         public IList<BatchEnvironmentSetting> EnvironmentSettings { get; }
         /// <summary> If omitted, the task runs as a non-administrative user unique to the task. </summary>
         public BatchUserIdentity UserIdentity { get; set; }
-        /// <summary> The Batch service retries a task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the task. If the maximum retry count is -1, the Batch service retries the task without limit. </summary>
+        /// <summary> The Batch service retries a task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the task. If the maximum retry count is -1, the Batch service retries the task without limit. Default is 0. </summary>
         public int? MaxTaskRetryCount { get; set; }
         /// <summary> If true and the start task fails on a compute node, the Batch service retries the start task up to its maximum retry count (maxTaskRetryCount). If the task has still not completed successfully after all retries, then the Batch service marks the compute node unusable, and will not schedule tasks to it. This condition can be detected via the node state and scheduling error detail. If false, the Batch service will not wait for the start task to complete. In this case, other tasks can start executing on the compute node while the start task is still running; and even if the start task fails, new tasks will continue to be scheduled on the node. The default is true. </summary>
         public bool? WaitForSuccess { get; set; }
diff --git a/sdk/batch/Azure.ResourceManager.Batch/src/autorest.md b/sdk/batch/Azure.ResourceManager.Batch/src/autorest.md
index f1f07a1a634b..eaddc17786e5 100644
--- a/sdk/batch/Azure.ResourceManager.Batch/src/autorest.md
+++ b/sdk/batch/Azure.ResourceManager.Batch/src/autorest.md
@@ -8,7 +8,7 @@ azure-arm: true
 csharp: true
 library-name: Batch
 namespace: Azure.ResourceManager.Batch
-require: https://github.com/Azure/azure-rest-api-specs/blob/ab84b777992cf4ca170a18e1b8e5f3e437209888/specification/batch/resource-manager/readme.md
+require: /mnt/vss/_work/1/s/azure-rest-api-specs/specification/batch/resource-manager/readme.md
 output-folder: $(this-folder)/Generated
 clear-output-folder: true
 skip-csproj: true