Merge pull request #203189 from MicrosoftDocs/release-preview-acss

DO NOT MERGE - comparing changes

Author: huypub

articles/center-sap-solutions/deploy-s4hana.md

@@ -0,0 +1,135 @@
+---
+title: Deploy S/4HANA infrastructure (preview)
+description: Learn how to deploy S/4HANA infrastructure with Azure Center for SAP solutions (ACSS) through the Azure portal. You can deploy High Availability (HA), non-HA, and single-server configurations.
+ms.service: azure-center-sap-solutions
+ms.topic: how-to
+ms.date: 07/19/2022
+ms.author: ladolan
+author: lauradolan
+#Customer intent: As a developer, I want to deploy S/4HANA infrastructure using Azure Center for SAP solutions so that I can manage SAP workloads in the Azure portal.
+---
+
+# Deploy S/4HANA infrastructure with Azure Center for SAP solutions (preview)
+
+[!INCLUDE [Preview content notice](./includes/preview.md)]
+
+In this how-to guide, you'll learn how to deploy S/4HANA infrastructure in *Azure Center for SAP solutions (ACSS)*. There are [three deployment options](#deployment-types): distributed with High Availability (HA), distributed non-HA, and single server. 
+
+## Prerequisites
+
+- An Azure subscription.
+- An Azure account with **Contributor** role access to the subscriptions and resource groups in which you'll create the Virtual Instance for SAP solutions (VIS) resource. 
+- A [network set up for your infrastructure deployment](prepare-network.md).
+
+## Deployment types
+
+There are three deployment options that you can select for your infrastructure, depending on your use case.
+
+- **Distributed with High Availability (HA)** creates distributed HA architecture. This option is recommended for production environments. If you choose this option, you need to select a **High Availability SLA**. Select the appropriate SLA for your use case:
+    - **99.99% (Optimize for availability)** shows available zone pairs for VM deployment. The first zone is primary and the next is secondary. Active ASCS and Database servers are deployed in the primary zone. Passive ASCS and Database servers are deployed in the secondary zone. Application servers are deployed evenly across both zones. This option isn't shown in regions without availability zones, or without at least one M-series and E-series VM SKU available in the zonal pairs within that region.
+    - **99.95% (Optimize for cost)** shows three availability sets for all instances. The HA ASCS cluster is deployed in the first availability set. All Application servers are deployed across the second availability set. The HA Database server is deployed in the third availability set. No availability zone names are shown.
+- **Distributed** creates distributed non-HA architecture. 
+- **Single Server** creates architecture with a single server. This option is available for non-production environments only.
+## Create deployment
+
+1. Sign in to the [Azure portal](https://portal.azure.com).
+
+1. In the search bar, enter and select **Azure Center for SAP solutions**.
+
+1. On the ACSS landing page, select **Create a new SAP system**.
+
+1. On the **Create Virtual Instance for SAP solutions** page, on the **Basics** tab, fill in the details for your project.
+
+    1. For **Subscription**, select the Azure subscription into which you're deploying the infrastructure.
+
+    1. For **Resource group**, select the resource group for all resources that the VIS creates.
+
+1. Under **Instance details**, enter the details for your SAP instance.
+
+    1. For **Name** enter the three-character SAP system identifier (SID). The VIS uses the same name as the SID.
+
+    1. For **Region**, select the Azure region into which you're deploying the resources.
+
+    1. For **Environment type**, select whether your environment is production or non-production. If you select **Production**, you can deploy a distributed HA or non-HA S/4HANA system. It's recommended to use distributed HA deployments for production systems. If you select **Non-production**, you can use a single-server deployment.
+
+    1. For **SAP product**, keep the selection as **S/4HANA**.
+
+    1. For **Database**, keep the selection as **HANA**.
+
+    1. For **HANA scale method**, keep the selection as **Scale up**.
+
+    1. For **Deployment type**, [select and configure your deployment type](#deployment-types).
+
+    1. For **Network**, create the [network you created previously with subnets](prepare-network.md).
+
+    1. For **Application subnet** and **Database subnet**, map the IP address ranges as required. It's recommended to use a different subnet for each deployment.
+
+1. Under **Operating systems**, enter the OS details.
+
+    1. For **Application OS image**, select the OS image for the application server.
+
+    1. For **Database OS image**, select the OS image for the database server.
+
+1. Under **Administrator account**, enter your administrator account details.
+
+    1. For **Authentication type**, keep the setting as **SSH public**.
+
+    1. For **Username**, enter a username.
+
+    1. For **SSH public key source**, select a source for the public key. You can choose to generate a new key pair, use an existing key stored in Azure, or use an existing public key stored on your local computer. If you don't have keys already saved, it's recommended to generate a new key pair.
+
+    1. For **Key pair name**, enter a name for the key pair.
+
+1. Select **Next: Virtual machines**.
+
+1. In the **Virtual machines** tab, generate SKU size and total VM count recommendations for each SAP instance from ACSS. 
+
+    1. For **Generate Recommendation based on**, under **Get virtual machine recommendations**, select **SAP Application Performance Standard (SAPS)**.
+
+    1. For **SAPS for application tier**, provide the total SAPS for the application tier. For example, 30,000.
+
+    1. For **Memory size for database (GiB)**, provide the total memory size required for the database tier. For example, 1024. The value must be greater than zero, and less than or equal to 11,400.
+    
+    1. Select **Generate Recommendation**.
+
+    1. Review the VM size and count recommendations for ASCS, Application Server, and Database instances. 
+
+    1. To change a SKU size recommendation, select the drop-down menu or select **See all sizes**. Filter the list or search for your preferred SKU.
+
+    1. To change the Application server count, enter a new count for **Number of VMs** under **Application virtual machines**.
+    
+        The number of VMs for ASCS and Database instances aren't editable. The default number for each is **2**.
+
+        ACSS automatically configures a database disk layout for the deployment. To view the layout for a single database server, make sure to select a VM SKU. Then, select **View disk configuration**. If there's more than one database server, the layout applies to each server. 
+
+    1. Select **Next: Tags**.
+
+1. Optionally, enter tags to apply to all resources created by the ACSS process. These resources include the VIS, ASCS instances, Application Server instances, Database instances, VMs, disks, and NICs.
+
+1. Select **Review + Create**.
+
+1. Review your settings before deployment. 
+
+    1. Make sure the validations have passed, and there are no errors listed.
+
+    1. Review the Terms of Service, and select the acknowledgment if you agree.
+
+    1. Select **Create**.
+
+1. Wait for the infrastructure deployment to complete. Numerous resources are deployed and configured. This process takes approximately 7 minutes.
+
+## Confirm deployment
+
+To confirm a deployment is successful:
+
+1. In the [Azure portal](https://portal.azure.com), search for and select **Virtual Instances for SAP solutions**.
+
+1. On the **Virtual Instances for SAP solutions** page, select the **Subscription** filter, and choose the subscription where you created the deployment.
+
+1. In the table of records, find the name of the VIS. The **Infrastructure** column value shows **Deployed** for successful deployments.
+
+If the deployment fails, delete the VIS resource in the Azure portal, then recreate the infrastructure. 
+
+## Next steps
+
+- [Install SAP software on your infrastructure](install-software.md)

articles/center-sap-solutions/faq.yml

@@ -0,0 +1,103 @@
+### YamlMime:FAQ
+metadata:
+  title: Azure Center for SAP solutions FAQ (preview)
+  description: "Get answers to common questions about Azure Center for SAP solutions (ACSS) and Virtual Instance for SAP solutions (VIS) resources."
+  ms.topic: faq 
+  ms.service: azure-center-sap-solutions
+  ms.date: 07/19/2022
+  ms.author: ladolan
+  author: lauradolan
+
+title: Common questions about  Azure Center for SAP solutions (preview)
+summary: |
+  This article answers commonly asked questions about Azure Center for SAP solutions (ACSS).
+  
+  [!INCLUDE [Preview content notice](./includes/preview.md)]
+
+sections: 
+  - name: General 
+    questions: 
+      - question:  What capabilities do you gain with Azure Center for SAP solutions?
+        answer: | 
+                Before the availability of ACSS, customers relied on documentation and frameworks to help them set up system architecture. 
+                Then they had to figure out how to access the VMs to install SAP. With ACSS, customers can deploy SAP by using a 
+                guided experience that streamlines their ability to select and configure resources. When a customer deploys or 
+                registers an existing SAP system, ACSS creates a logical representation of the system, or a Virtual Instance for SAP solutions (VIS). 
+                The VIS unlocks management capabilities, such as the ability to run quality checks and to manage and monitor the 
+                system at the SAP layer as well as the virtual machine (VM) layer.
+
+      - question:  Will ACSS replace other services such as Azure Monitor for SAP solutions?
+        answer: | 
+                No. ACSS brings Azure services together into a unified experience for deploying 
+                and managing SAP workloads on Azure. Customers can choose to use other Azure services, such as Azure 
+                Monitor for SAP solutions (AMS), independently or in an integrated manner with ACSS.
+                AMS is an Azure-native monitoring product for customers running SAP 
+                landscapes on Azure. This product helps you collect data from Azure infrastructure and databases in one 
+                central location and visually correlate the data for faster troubleshooting.
+
+      - question:  What are the pricing and licensing implications?
+        answer: | 
+                There's no extra licensing cost for deploying or registering an SAP system and generating a virtual 
+                instance. You pay only for 
+                the compute, storage, networking and other Azure resources you deploy or enable. 
+
+      - question:  Which scenarios does ACSS support?
+        answer: | 
+                ACSS supports the following capabilities at this time.
+
+                - Deployment of infrastructure for SAP S4/HANA systems
+                - Software installation of SAP S4/HANA 1909 SPS 03
+                - Registration of an existing Linux based ABAP/NetWeaver SAP system on Azure
+                - Monitoring the health and status of an SAP system
+                - Creating a new AMS provider or integrating an existing one
+                - Starting and stopping an SAP System
+                - Quality checks and recommendations for an SAP system with Azure Advisor
+
+                ACSS doesn't allow customization of the names of the Azure 
+                resources deployed through it. ACSS follows a prescriptive naming convention for all Azure resources deployed.
+                Consider the open-source [SAP deployment automation framework](../virtual-machines/workloads/sap/automation-deployment-framework.md) 
+                if you need the ability to customize names for your deployments. Then register your open-source deployments in ACSS to unlock intelligent management capabilities.
+
+      - question:  What is a VIS resource?
+        answer: | 
+                The Virtual Instance for SAP solutions (VIS) resource is an essential component of ACSS that 
+                forms the foundation for the new experience. The VIS is a logical representation of your SAP system in Azure
+                that provides SAP awareness in Azure and unlocks new management capabilities. When you deploy a new 
+                SAP system or register an existing SAP system, ACSS automatically creates a 
+                VIS for you.
+
+      - question:  What existing SAP systems can be registered as a VIS?
+        answer: | 
+                You can register any of the following existing systems on Azure to create a VIS in Azure Center 
+                for SAP solutions:
+
+                - SAP systems running on SAP NetWeaver or ABAP stack
+                - SAP systems running on SUSE and RHEL Linux Operating Systems
+                - SAP systems running on HANA, DB2, SQL Server, Oracle, Max DB, SAP ASE databases
+
+      - question:  What are the prerequisites to deploy a new SAP system with ACSS?
+        answer: |
+                Here are prerequisites to deploy a new SAP system with ACSS and create a VIS. For more information, see the [deployment guide](deploy-s4hana.md).
+
+                - Make sure you and the ACSS service have contributor roles at the 
+                subscription or resource group(s) level.
+                - Identify an existing virtual network with outbound internet connectivity where you'll deploy 
+                your new SAP system.
+                - Register appropriate resource providers.
+                - Make sure there are sufficient virtual machine quotas for the region(s) that you're using for deployment.
+
+      - question:  What are the prerequisites to register an existing SAP system in ACSS?
+        answer: | 
+                ACSS requires contributor role access on the resource groups that include the 
+                SAP system(s) that you're trying to register. Alternatively, you can grant contributor access on the 
+                subscription that includes the SAP systems.
+
+      - question:  What regions support the VIS as part of ACSS?
+        answer: | 
+                The VIS resource is available in the following Azure regions: West Europe, North Europe, East US, East 
+                US 2, West US 2, West US 3, Central US, South Central US, East Asia, Southeast Asia, Australia East and 
+                Australia Central.
+
+      - question:  What is the SLA for this service?
+        answer: | 
+                Previews are excluded from service-level agreements.