Merge pull request #222441 from KimForss/main

Restructure planning documentation

Author: prmerger-automator[bot]

articles/virtual-machines/workloads/sap/automation-plan-deployment.md

@@ -18,9 +18,29 @@ For generic SAP on Azure design considerations please visit [Introduction to an
 > [!NOTE]
 > The Terraform deployment uses Terraform templates provided by Microsoft from the [SAP on Azure Deployment Automation Framework repository](https://github.com/Azure/sap-automation/). The templates use parameter files with your system-specific information to perform the deployment.
 
+## Workload partitioning
+
+Most SAP configurations have multiple [workload zones](automation-deployment-framework.md#deployment-components) for different application tiers. For example, you might have different workload zones for development, quality assurance, and production.
+
+You'll be creating or granting access to the following services in each workload zone:
+
+* Azure Virtual Networks, for virtual networks, subnets and network security groups.
+* Azure Key Vault, for system credentials and the deployment Service Principal.
+* Azure Storage accounts, for Boot Diagnostics and Cloud Witness.
+* Shared storage for the SAP Systems either Azure Files or Azure NetApp Files.
+
+Before you design your workload zone layout, consider the following questions:
+
+* How many workload zones does your scenario require?
+* In which regions do you need to deploy workloads?
+* What's your [deployment scenario](#supported-deployment-scenarios)?
+
+For more information, see [how to configure a workload zone deployment for automation](automation-deploy-workload-zone.md).
+
+
 ## Credentials management
 
-The automation framework uses [Service Principals](#service-principal-creation) for infrastructure deployment. You can use different deployment credentials (service principals) for each [workload zone](#workload-zone-structure). The framework stores these credentials in the [deployer's](automation-deployment-framework.md#deployment-components) key vault in Azure Key Vault. Then, the framework retrieves these credentials dynamically during the deployment process.
+The automation framework uses [Service Principals](#service-principal-creation) for infrastructure deployment. You can use different deployment credentials (service principals) for each [workload zone](#workload-partitioning). The framework stores these credentials in the [deployer's](automation-deployment-framework.md#deployment-components) key vault in Azure Key Vault. Then, the framework retrieves these credentials dynamically during the deployment process.
 
 The automation framework also defines the credentials for the default virtual machine (VM) accounts, as provided at the time of the VM creation. These credentials include:
 
@@ -152,25 +172,6 @@ For more information, see the [in-depth explanation of how to configure the depl
 
 The SAP library provides storage for SAP installation media, Bill of Material (BOM) files,  and Terraform state files. The configuration file defines the region and environment name for the SAP library. For parameter information and examples, see [how to configure the SAP library for automation](automation-configure-control-plane.md).
 
-## Workload zone structure
-
-Most SAP configurations have multiple [workload zones](automation-deployment-framework.md#deployment-components) for different application tiers. For example, you might have different workload zones for development, quality assurance, and production.
-
-You'll be creating or granting access to the following services in each workload zone:
-
-* Azure Virtual Networks, for virtual networks, subnets and network security groups.
-* Azure Key Vault, for system credentials and the deployment Service Principal.
-* Azure Storage accounts, for Boot Diagnostics and Cloud Witness.
-* Shared storage for the SAP Systems either Azure Files or Azure NetApp Files.
-
-Before you design your workload zone layout, consider the following questions:
-
-* How many workload zones does your scenario require?
-* In which regions do you need to deploy workloads?
-* What's your [deployment scenario](#supported-deployment-scenarios)?
-
-For more information, see [how to configure a workload zone deployment for automation](automation-deploy-workload-zone.md).
-
 ## SAP system setup
 
 The SAP system contains all Azure components required to host the SAP application.
@@ -199,7 +200,7 @@ When planning a deployment, it's important to consider the overall flow. There a
     1. Creating shared storage for Terraform state files
     1. Creating shared storage for SAP installation media
 
-1. Deploy the workload zone. This step deploys the [workload zone components](#workload-zone-structure), such as the virtual network and key vaults.
+1. Deploy the workload zone. This step deploys the [workload zone components](#workload-partitioning), such as the virtual network and key vaults.
 
 1. Deploy the system. This step includes the [infrastructure for the SAP system](#sap-system-setup) deployment and the SAP configuration [configuration and SAP installation](automation-run-ansible.md).