Merge pull request #115027 from JnHs/jh-batch-devfeatures

splitting up topic

Author: denrea

.openpublishing.redirection.json

@@ -52433,7 +52433,16 @@
         "source_path": "articles/cdn/endpoint-multiorigin.md",
         "redirect_url": "/azure/cdn/cdn-overview",
         "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/batch/batch-api-basics.md",
+      "redirect_url": "/azure/batch/batch-service-workflow-features",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/batch/batch-retry-after-errors.md",
+      "redirect_url": "/azure/batch/error-handling",
+      "redirect_document_id": false
     }
-
 ]
 }

articles/batch/TOC.yml

@@ -53,12 +53,26 @@
     items:
     - name: Security baseline
       href: security-baseline.md
-  - name: Developer features
-    href: batch-api-basics.md
+  - name: Batch service workflow and resources
+    displayName: developer features
+    href: batch-service-workflow-features.md
+    items:
+    - name: Batch accounts
+      displayName: storage account
+      href: accounts.md
+    - name: Nodes and pools
+      displayName: compute node, application package, scaling, schedule, os
+      href: nodes-and-pools.md
+    - name: Jobs and tasks
+      displayName: Batch job
+      href: jobs-and-tasks.md
+    - name: Files and directories
+      displayName: Batch file
+      href: files-and-directories.md
   - name: APIs and tools
     href: batch-apis-tools.md
-  - name: Detecting and handling Batch service errors
-    href: batch-retry-after-errors.md
+  - name: Error handling and detection
+    href: error-handling.md
   - name: Best practices
     href: best-practices.md
   - name: Quotas and limits

articles/batch/accounts.md

@@ -0,0 +1,39 @@
+---
+title: Batch accounts and Azure Storage accounts
+description: Learn about Azure Batch accounts and how they are used from a development standpoint.
+ms.topic: conceptual
+ms.date: 05/12/2020
+
+---
+# Batch accounts and Azure Storage accounts
+
+An Azure Batch account is a uniquely identified entity within the Batch service. Most Batch solutions use [Azure Storage](../storage/index.yml) for storing resource files and output files, so each Batch account is usually associated with a corresponding storage account.
+
+## Batch accounts
+
+All processing and resources are associated with a Batch account. When your application makes a request against the Batch service, it authenticates the request using the Azure Batch account name, the URL of the account, and either an access key or an Azure Active Directory token.
+
+You can run multiple Batch workloads in a single Batch account. You can also distribute your workloads among Batch accounts that are in the same subscription but located in different Azure regions.
+
+[!INCLUDE [batch-account-mode-include](../../includes/batch-account-mode-include.md)]
+
+You can create a Batch account using the [Azure portal](batch-account-create-portal.md) or programmatically, such as with the [Batch Management .NET library](batch-management-dotnet.md). When creating the account, you can associate an Azure storage account for storing job-related input and output data or applications.
+
+## Azure Storage accounts
+
+Most Batch solutions use Azure Storage for storing resource files and output files. For example, your Batch tasks (including standard tasks, start tasks, job preparation tasks, and job release tasks) typically specify resource files that reside in a storage account. Storage accounts also stores that data that is processed and any output data that is generated.
+
+Batch supports the following types of Azure Storage accounts:
+
+- General-purpose v2 (GPv2) accounts
+- General-purpose v1 (GPv1) accounts
+- Blob storage accounts (currently supported for pools in the Virtual Machine configuration)
+
+For more information about storage accounts, see [Azure storage account overview](../storage/common/storage-account-overview.md).
+
+You can associate a storage account with your Batch account when you create the Batch account, or later. Consider your cost and performance requirements when choosing a storage account. For example, the GPv2 and blob storage account options support greater [capacity and scalability limits](https://azure.microsoft.com/blog/announcing-larger-higher-scale-storage-accounts/) compared with GPv1. (Contact Azure Support to request an increase in a storage limit.) These account options can improve the performance of Batch solutions that contain a large number of parallel tasks that read from or write to the storage account.
+
+## Next steps
+
+- Learn about [Nodes and pools](nodes-and-pools.md).
+- Learn how to create a Batch account using the [Azure portal](batch-account-create-portal.md).

articles/batch/batch-account-create-portal.md

@@ -11,7 +11,7 @@ ms.custom: H1Hack27Feb2017
 
 Learn how to create an Azure Batch account in the [Azure portal][azure_portal], and choose the account properties that fit your compute scenario. Learn where to find important account properties like access keys and account URLs.
 
-For background about Batch accounts and scenarios, see the [feature overview](batch-api-basics.md).
+For background about Batch accounts and scenarios, see [Batch service workflow and resources](batch-service-workflow-features.md).
 
 ## Create a Batch account
 
@@ -35,7 +35,7 @@ For background about Batch accounts and scenarios, see the [feature overview](ba
 
     d. **Location**: The Azure region in which to create the Batch account. Only the regions supported by your subscription and resource group are displayed as options.
 
-    e. **Storage account**: An optional Azure Storage account that you associate with your Batch account. A general-purpose v2 storage account is recommended for the best performance. For all storage account options in Batch, see the [Batch feature overview](batch-api-basics.md#azure-storage-account). In the portal, select an existing storage account, or create a new one.
+    e. **Storage account**: An optional Azure Storage account that you associate with your Batch account. A general-purpose v2 storage account is recommended for the best performance. For all storage account options in Batch, see the [Batch feature overview](accounts.md#azure-storage-accounts). In the portal, select an existing storage account, or create a new one.
 
       ![Create a storage account][storage_account]
 
@@ -133,7 +133,7 @@ In addition to using the Azure portal, you can create and manage Batch accounts
 
 ## Next steps
 
-* See the [Batch feature overview](batch-api-basics.md) to learn more about Batch service concepts and features. The article discusses the primary Batch resources such as pools, compute nodes, jobs, and tasks, and provides an overview of the service's features for large-scale compute workloads.
+* Learn about the [Batch service workflow and primary resources](batch-service-workflow-features.md) such as pools, nodes, jobs, and tasks.
 * Learn the basics of developing a Batch-enabled application using the [Batch .NET client library](quick-run-dotnet.md) or [Python](quick-run-python.md). These quickstarts guide you through a sample application that uses the Batch service to execute a workload on multiple compute nodes, and includes using Azure Storage for workload file staging and retrieval.
 
 [azure_portal]: https://portal.azure.com