cleanup on previous PR

Author: JnHs

articles/batch/batch-docker-container-workloads.md

@@ -2,7 +2,7 @@
 title: Container workloads
 description: Learn how to run and scale apps from container images on Azure Batch. Create a pool of compute nodes that support running container tasks.
 ms.topic: how-to
-ms.date: 08/13/2021
+ms.date: 08/18/2021
 ms.custom: "seodec18, devx-track-csharp"
 ---
 # Run container applications on Azure Batch
@@ -269,7 +269,7 @@ CloudPool pool = batchClient.PoolOperations.CreatePool(
 
 ### Managed Identity support for ACR
 
-When accessing containers stored in [Azure Container Registry](https://azure.microsoft.com/services/container-registry), either a username/password or a Managed Identity can be used to authenticate with the service. To use a Managed Identity, first ensure that the identity has been [assigned to the pool](managed-identity-pools.md) and that the identity has the `AcrPull` role assigned for the container registry you wish to access. Then, simply tell Batch which identity to use when authenticating with ACR.
+When accessing containers stored in [Azure Container Registry](https://azure.microsoft.com/services/container-registry), either a username/password or a managed identity can be used to authenticate with the service. To use a managed identity, first ensure that the identity has been [assigned to the pool](managed-identity-pools.md) and that the identity has the `AcrPull` role assigned for the container registry you wish to access. Then, simply tell Batch which identity to use when authenticating with ACR.
 
 ```csharp
 ContainerRegistry containerRegistry = new ContainerRegistry(

articles/batch/batch-task-output-files.md

@@ -2,7 +2,7 @@
 title: Persist output data to Azure Storage with Batch service API
 description: Learn how to use the Batch service API to persist Batch task and job output data to Azure Storage.
 ms.topic: how-to
-ms.date: 07/30/2020
+ms.date: 08/18/2021
 ms.custom: "seodec18, devx-track-csharp"
 
 ---
@@ -11,9 +11,9 @@ ms.custom: "seodec18, devx-track-csharp"
 
 [!INCLUDE [batch-task-output-include](../../includes/batch-task-output-include.md)]
 
-The Batch service API supports persisting output data to Azure Storage for tasks and job manager tasks that run on pools with the virtual machine configuration. When you add a task, you can specify a container in Azure Storage as the destination for the task's output. The Batch service then writes any output data to that container when the task is complete.
+The Batch service API supports persisting output data to Azure Storage for tasks and job manager tasks that run on pools with [Virtual Machine Configuration](nodes-and-pools.md#virtual-machine-configuration). When you add a task, you can specify a container in Azure Storage as the destination for the task's output. The Batch service then writes any output data to that container when the task is complete.
 
-An advantage to using the Batch service API to persist task output is that you do not need to modify the application that the task is running. Instead, with a few modifications to your client application, you can persist the task's output from within the same code that creates the task.
+When using the Batch service API to persist task output, you don't need to modify the application that the task is running. Instead, with a few modifications to your client application, you can persist the task's output from within the same code that creates the task.
 
 > [!IMPORTANT]
 > Persisting task data to Azure Storage with the Batch service API does not work with pools created before [February 1, 2018](https://github.com/Azure/Batch/blob/master/changelogs/nodeagent/CHANGELOG.md#1204).
@@ -27,11 +27,11 @@ Azure Batch provides more than one way to persist task output. Using the Batch s
 - You want to persist output to an Azure Storage container with an arbitrary name.
 - You want to persist output to an Azure Storage container named according to the [Batch File Conventions standard](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/batch/Microsoft.Azure.Batch.Conventions.Files).
 
-If your scenario differs from those listed above, you may need to consider a different approach. For example, the Batch service API does not currently support streaming output to Azure Storage while the task is running. To stream output, consider using the Batch File Conventions library, available for .NET. For other languages, you'll need to implement your own solution. For information on other options for persisting task output, see [Persist job and task output to Azure Storage](batch-task-output.md).
+If your scenario differs from those listed above, you may need to consider a different approach. For example, the Batch service API does not currently support streaming output to Azure Storage while the task is running. To stream output, consider using the Batch File Conventions library, available for .NET. For other languages, you'll need to implement your own solution. For more information about other options, see [Persist job and task output to Azure Storage](batch-task-output.md).
 
 ## Create a container in Azure Storage
 
-To persist task output to Azure Storage, you'll need to create a container that serves as the destination for your output files. Create the container before you run your task, preferably before you submit your job. To create the container, use the appropriate Azure Storage client library or SDK. For more information about Azure Storage APIs, see the [Azure Storage documentation](../storage/index.yml).
+To persist task output to Azure Storage, you'll need to create a container that serves as the destination for your output files. Create the container before you run your task, preferably before you submit your job, by using the appropriate Azure Storage client library or SDK. For more information about Azure Storage APIs, see the [Azure Storage documentation](../storage/index.yml).
 
 For example, if you are writing your application in C#, use the [Azure Storage client library for .NET](https://www.nuget.org/packages/WindowsAzure.Storage/). The following example shows how to create a container:
 
@@ -42,7 +42,7 @@ await container.CreateIfNotExists();
 
 ## Get a shared access signature for the container
 
-After you create the container, get a shared access signature (SAS) with write access to the container. A SAS provides delegated access to the container. The SAS grants access with a specified set of permissions and over a specified time interval. The Batch service needs a SAS with write permissions to write task output to the container. For more information about SAS, see [Using shared access signatures \(SAS\) in Azure Storage](../storage/common/storage-sas-overview.md).
+After you create the container, get a shared access signature (SAS) with write access to the container. A SAS provides delegated access to the container. The SAS grants access with a specified set of permissions and over a specified time interval. The Batch service needs an SAS with write permissions to write task output to the container. For more information about SAS, see [Using shared access signatures \(SAS\) in Azure Storage](../storage/common/storage-sas-overview.md).
 
 When you get a SAS using the Azure Storage APIs, the API returns a SAS token string. This token string includes all parameters of the SAS, including the permissions and the interval over which the SAS is valid. To use the SAS to access a container in Azure Storage, you need to append the SAS token string to the resource URI. The resource URI, together with the appended SAS token, provides authenticated access to Azure Storage.
 
@@ -60,9 +60,9 @@ string containerSasUrl = container.Uri.AbsoluteUri + containerSasToken;
 
 ## Specify output files for task output
 
-To specify output files for a task, create a collection of [OutputFile](/dotnet/api/microsoft.azure.batch.outputfile) objects and assign it to the [CloudTask.OutputFiles](/dotnet/api/microsoft.azure.batch.cloudtask.outputfiles#Microsoft_Azure_Batch_CloudTask_OutputFiles) property when you create the task.
+To specify output files for a task, create a collection of [OutputFile](/dotnet/api/microsoft.azure.batch.outputfile) objects and assign it to the [CloudTask.OutputFiles](/dotnet/api/microsoft.azure.batch.cloudtask.outputfiles) property when you create the task.
 
-The following C# code example creates a task that writes random numbers to a file named `output.txt`. The example creates an output file for `output.txt` to be written to the container. The example also creates output files for any log files that match the file pattern `std*.txt` (_e.g._, `stdout.txt` and `stderr.txt`). The container URL requires the SAS that was created previously for the container. The Batch service uses the SAS to authenticate access to the container:
+The following C# code example creates a task that writes random numbers to a file named `output.txt`. The example creates an output file for `output.txt` to be written to the container. The example also creates output files for any log files that match the file pattern `std*.txt` (_e.g._, `stdout.txt` and `stderr.txt`). The container URL requires the SAS that was created previously for the container. The Batch service uses the SAS to authenticate access to the container.
 
 ```csharp
 new CloudTask(taskId, "cmd /v:ON /c \"echo off && set && (FOR /L %i IN (1,1,100000) DO (ECHO !RANDOM!)) > output.txt\"")
@@ -118,7 +118,7 @@ new CloudTask(taskId, "cmd /v:ON /c \"echo off && set && (FOR /L %i IN (1,1,1000
 
 ### Specify a file pattern for matching
 
-When you specify an output file, you can use the [OutputFile.FilePattern](/dotnet/api/microsoft.azure.batch.outputfile.filepattern#Microsoft_Azure_Batch_OutputFile_FilePattern) property to specify a file pattern for matching. The file pattern may match zero files, a single file, or a set of files that are created by the task.
+When you specify an output file, you can use the [OutputFile.FilePattern](/dotnet/api/microsoft.azure.batch.outputfile.filepattern) property to specify a file pattern for matching. The file pattern may match zero files, a single file, or a set of files that are created by the task.
 
 The **FilePattern** property supports standard filesystem wildcards such as `*` (for non-recursive matches) and `**` (for recursive matches). For example, the code sample above specifies the file pattern to match `std*.txt` non-recursively:
 
@@ -130,7 +130,7 @@ To upload a single file, specify a file pattern with no wildcards. For example,
 
 ### Specify an upload condition
 
-The [Output​File​Upload​Options.UploadCondition](/dotnet/api/microsoft.azure.batch.outputfileuploadoptions.uploadcondition#Microsoft_Azure_Batch_OutputFileUploadOptions_UploadCondition) property permits conditional uploading of output files. A common scenario is to upload one set of files if the task succeeds, and a different set of files if it fails. For example, you may want to upload verbose log files only when the task fails and exits with a nonzero exit code. Similarly, you may want to upload result files only if the task succeeds, as those files may be missing or incomplete if the task fails.
+The [Output​File​Upload​Options.UploadCondition](/dotnet/api/microsoft.azure.batch.outputfileuploadoptions.uploadcondition) property permits conditional uploading of output files. A common scenario is to upload one set of files if the task succeeds, and a different set of files if it fails. For example, you may want to upload verbose log files only when the task fails and exits with a nonzero exit code. Similarly, you may want to upload result files only if the task succeeds, as those files may be missing or incomplete if the task fails.
 
 The code sample above sets the **UploadCondition** property to **TaskCompletion**. This setting specifies that the file is to be uploaded after the tasks completes, regardless of the value of the exit code.
 
@@ -142,7 +142,7 @@ For other settings, see the [Output​File​Upload​Condition](/dotnet/api/mic
 
 The tasks in a job may produce files that have the same name. For example, `stdout.txt` and `stderr.txt` are created for every task that runs in a job. Because each task runs in its own context, these files don't conflict on the node's file system. However, when you upload files from multiple tasks to a shared container, you'll need to disambiguate files with the same name.
 
-The [Output​File​Blob​Container​Destination.​Path](/dotnet/api/microsoft.azure.batch.outputfileblobcontainerdestination.path#Microsoft_Azure_Batch_OutputFileBlobContainerDestination_Path) property specifies the destination blob or virtual directory for output files. You can use the **Path** property to name the blob or virtual directory in such a way that output files with the same name are uniquely named in Azure Storage. Using the task ID in the path is a good way to ensure unique names and easily identify files.
+The [Output​File​Blob​Container​Destination.​Path](/dotnet/api/microsoft.azure.batch.outputfileblobcontainerdestination.path) property specifies the destination blob or virtual directory for output files. You can use the **Path** property to name the blob or virtual directory in such a way that output files with the same name are uniquely named in Azure Storage. Using the task ID in the path is a good way to ensure unique names and easily identify files.
 
 If the **FilePattern** property is set to a wildcard expression, then all files that match the pattern are uploaded to the virtual directory specified by the **Path** property. For example, if the container is `mycontainer`, the task ID is `mytask`, and the file pattern is `..\std*.txt`, then the absolute URIs to the output files in Azure Storage will be similar to:
 
@@ -166,7 +166,7 @@ For more information about virtual directories in Azure Storage, see [List the b
 
 ## Diagnose file upload errors
 
-If uploading output files to Azure Storage fails, then the task moves to the **Completed** state and the [Task​Execution​Information.​Failure​Information](/dotnet/api/microsoft.azure.batch.taskexecutioninformation.failureinformation#Microsoft_Azure_Batch_TaskExecutionInformation_FailureInformation) property is set. Examine the **FailureInformation** property to determine what error occurred. For example, here is an error that occurs on file upload if the container cannot be found:
+If uploading output files to Azure Storage fails, then the task moves to the **Completed** state and the [Task​Execution​Information.​Failure​Information](/dotnet/api/microsoft.azure.batch.taskexecutioninformation.failureinformation) property is set. Examine the **FailureInformation** property to determine what error occurred. For example, here is an error that occurs on file upload if the container cannot be found:
 
 ```
 Category: UserError

articles/batch/managed-identity-pools.md

@@ -2,7 +2,7 @@
 title: Configure managed identities in Batch pools
 description: Learn how to enable user-assigned managed identities on Batch pools and how to use managed identities within the nodes.
 ms.topic: conceptual
-ms.date: 05/25/2021
+ms.date: 08/18/2021
 
 ---
 # Configure managed identities in Batch pools
@@ -66,13 +66,12 @@ var pool = await managementClient.Pool.CreateWithHttpMessagesAsync(
 
 ## Use user-assigned managed identities in Batch nodes
 
-Many Azure Batch technologies which access other Azure resources, such as Azure Storage or Azure Container Registries, support using Managed Identities.
-Please refer to the following for more information on using Managed Identity with Azure Batch:
+Many Azure Batch technologies which access other Azure resources, such as Azure Storage or Azure Container Registry, support managed identities. For more information on using managed identities with Azure Batch, see the following links:
 
-- [Resource Files](resource-files.md)
-- [Output Files](batch-task-output-files.md#specify-output-files-using-managed-identity)
-- [Azure Container Registries](batch-docker-container-workloads.md#managed-identity-support-for-acr)
-- [Azure Blob Container Filesystem](virtual-file-mount.md#azure-blob-container)
+- [Resource files](resource-files.md)
+- [Output files](batch-task-output-files.md#specify-output-files-using-managed-identity)
+- [Azure Container Registry](batch-docker-container-workloads.md#managed-identity-support-for-acr)
+- [Azure Blob container file system](virtual-file-mount.md#azure-blob-container)
 
 You can also manually configure your tasks so that the managed identities can directly access [Azure resources that support managed identities](../active-directory/managed-identities-azure-resources/services-support-managed-identities.md).
 

articles/batch/resource-files.md

@@ -1,7 +1,7 @@
 ---
 title: Creating and using resource files 
 description: Learn how to create Batch resource files from various input sources. This article covers a few common methods on how to create and place them on a VM.
-ms.date: 05/25/2021
+ms.date: 08/18/2021
 ms.topic: how-to
 ---
 
@@ -28,8 +28,7 @@ There are a few different options available to generate resource files, each wit
 
 Using a storage container URL means, with the correct permissions, you can access files in any storage container in Azure.
 
-In this C# example, the files have already been uploaded to an Azure storage container as blob storage. To access the data needed to create a resource file, we first need to get access to the storage container.
-
+In this C# example, the files have already been uploaded to an Azure storage container as blob storage. To access the data needed to create a resource file, we first need to get access to the storage container. This can be done in several ways.
 
 #### Shared Access Signature
 
@@ -63,19 +62,19 @@ If desired, you can use the [blobPrefix](/dotnet/api/microsoft.azure.batch.resou
 ResourceFile inputFile = ResourceFile.FromStorageContainerUrl(containerSasUrl, blobPrefix = yourPrefix);
 ```
 
-#### Managed Identity
+#### Managed identity
 
-Create a User Assigned Managed Identity and assign it the `Storage Blob Data Reader` role for your Azure Storage container. Next, [assign the managed identity to your pool](managed-identity-pools.md) so that your VMs can access the identity. Finally, you can access the files in your container by specifying the identity for Batch to use.
+Create a [user-assigned managed identity](../active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-portal.md#create-a-user-assigned-managed-identity) and assign it the `Storage Blob Data Reader` role for your Azure Storage container. Next, [assign the managed identity to your pool](managed-identity-pools.md) so that your VMs can access the identity. Finally, you can access the files in your container by specifying the identity for Batch to use.
 
 ```csharp
 CloudBlobContainer container = blobClient.GetContainerReference(containerName);
 
 ResourceFile inputFile = ResourceFile.FromStorageContainerUrl(container.Uri, identityReference: new ComputeNodeIdentityReference() { ResourceId = "/subscriptions/SUB/resourceGroups/RG/providers/Microsoft.ManagedIdentity/userAssignedIdentities/identity-name" });
 ```
 
-#### Public Access
+#### Public access
 
-An alternative to generating a SAS URL or using a Managed Identity is to enable anonymous, public read-access to a container and its blobs in Azure Blob storage. By doing so, you can grant read-only access to these resources without sharing your account key, and without requiring a SAS. Public read-access is typically used for scenarios where you want certain blobs to be always available for anonymous read-access. If this scenario suits your solution, see the [Anonymous access to blobs](../storage/blobs/anonymous-read-access-configure.md) article to learn more about managing access to your blob data.
+An alternative to generating a SAS URL or using a managed identity is to enable anonymous, public read-access to a container and its blobs in Azure Blob storage. By doing so, you can grant read-only access to these resources without sharing your account key, and without requiring a SAS. Public access is typically used for scenarios where you want certain blobs to be always available for anonymous read-access. If this scenario suits your solution, see [Configure anonymous public read access for containers and blobs](../storage/blobs/anonymous-read-access-configure.md) to learn more about managing access to your blob data.
 
 ### Storage container name (autostorage)
 
@@ -111,7 +110,7 @@ You can also use a string that you define as a URL (or a combination of strings
 ResourceFile inputFile = ResourceFile.FromUrl(yourDomain + yourFile, filePath);
 ```
 
-If your file is in Azure Storage, you can use a Managed Identity instead of generating a Shared Access Signature for the resource file.
+If your file is in Azure Storage, you can use a managed identity instead of generating a Shared Access Signature for the resource file.
 
 ```csharp
 ResourceFile inputFile = ResourceFile.FromUrl(yourURLFromAzureStorage, 
@@ -121,7 +120,7 @@ ResourceFile inputFile = ResourceFile.FromUrl(yourURLFromAzureStorage,
 ```
 
 > [!Note]
-> Managed Identity authentication will only work with files in Azure Storage. The Managed Identity needs the `Storage Blob Data Reader` role assignment for the container the file is in and it must also be [assigned to the Batch pool](managed-identity-pools.md).
+> Managed identity authentication will only work with files in Azure Storage. The nanaged identity needs the `Storage Blob Data Reader` role assignment for the container the file is in, and it must also be [assigned to the Batch pool](managed-identity-pools.md).
 
 ## Tips and suggestions
 

articles/batch/virtual-file-mount.md

@@ -3,7 +3,7 @@ title: Mount a virtual file system on a pool
 description: Learn how to mount a virtual file system on a Batch pool.
 ms.topic: how-to
 ms.custom: devx-track-csharp
-ms.date: 03/26/2021
+ms.date: 08/18/2021
 ---
 
 # Mount a virtual file system on a Batch pool
@@ -73,7 +73,7 @@ new PoolAddParameter
 
 ### Azure Blob container
 
-Another option is to use Azure Blob storage via [blobfuse](../storage/blobs/storage-how-to-mount-container-linux.md). Mounting a blob file system requires an `AccountKey`, `SasKey` or `Managed Identity` with access to your storage account. For information on getting these keys, see [Manage storage account access keys](../storage/common/storage-account-keys-manage.md), [Grant limited access to Azure Storage resources using shared access signatures (SAS)](../storage/common/storage-sas-overview.md) or [Assigning Managed Identities to pools](managed-identity-pools.md). For more information and tips on using blobfuse, see the [blobfuse project](https://github.com/Azure/azure-storage-fuse).
+Another option is to use Azure Blob storage via [blobfuse](../storage/blobs/storage-how-to-mount-container-linux.md). Mounting a blob file system requires an `AccountKey`, `SasKey` or `Managed Identity` with access to your storage account. For information on getting these keys, see [Manage storage account access keys](../storage/common/storage-account-keys-manage.md), [Grant limited access to Azure Storage resources using shared access signatures (SAS)](../storage/common/storage-sas-overview.md), and [Configure managed identities in Batch pools](managed-identity-pools.md). For more information and tips on using blobfuse, see the [blobfuse project](https://github.com/Azure/azure-storage-fuse).
 
 To get default access to the blobfuse mounted directory, run the task as an **Administrator**. Blobfuse mounts the directory at the user space, and at pool creation it is mounted as root. In Linux all **Administrator** tasks are root. All options for the FUSE module are described in the [FUSE reference page](https://manpages.ubuntu.com/manpages/xenial/man8/mount.fuse.8.html).
 
@@ -106,7 +106,7 @@ new PoolAddParameter
 > `AccountKey`, `SasKey` and `IdentityReference` are mutually exclusive, only one can be specified.
 
 > [!NOTE]
->If using a Managed Identity, ensure that the Identity has been assigned to the pool so that it is available on the VM doing the mounting. The identity will need to have the `Storage Blob Data Contributor` role assigned to function properly.
+>If using a managed identity, ensure that the identity has been [assigned to the pool](managed-identity-pools.md) so that it is available on the VM doing the mounting. The identity will need to have the `Storage Blob Data Contributor` role in order to function properly.
 
 ### Network File System
 
@@ -162,7 +162,7 @@ If a mount configuration fails, the compute node in the pool will fail and the n
 
 To get the log files for debugging, use [OutputFiles](batch-task-output-files.md) 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` will have a mount log file named: `cifs-test.log`.
 
-## Support Matrix
+## Support matrix
 
 Azure Batch supports the following virtual file system types for node agents produced for their respective publisher and offer.