More

Author: sethmanheim

azure-stack/operator/app-service-remove.md

@@ -1,31 +1,27 @@
 ---
 title: Remove Azure App Service from Azure Stack Hub 
-description: Learn how to remove Azure App Service from Azure Stack Hub
-author: apwestgarth
-
+description: Learn how to remove Azure App Service from Azure Stack Hub.
+author: sethmanheim
 ms.topic: article
-ms.date: 04/17/2020
-ms.author: anwestg
+ms.date: 08/12/2024
+ms.author: sethm
 ms.reviewer: anwestg
-ms.lastreviewed: 04/17/20207
-
-# Intent: Notdone: As a < type of user >, I want < what? > so that < why? >
-# Keyword: Notdone: keyword noun phrase
+ms.lastreviewed: 04/17/2020
 
 ---
 
 # Remove Azure App Service from Azure Stack Hub
 
-This article shows how to remove the Azure App Service resource provider and related components, from Azure Stack Hub.
+This article describes how to remove the Azure App Service resource provider and related components from Azure Stack Hub.
 
 ## Remove resource provider
 
-> [!Important]
-> This operation will remove all tenant resources, remove the service and quotas from all plans and remove the Azure App Service resource provider in it's entirety.  If you have deployed the App Service Highly Available File Server and SQL Server Quickstart template, these resources will also be removed as they are deployed in the same resource group as Azure App Service on Azure Stack Hub.
+> [!IMPORTANT]
+> This operation removes all tenant resources, removes the service and quotas from all plans, and removes the Azure App Service resource provider in its entirety. If you have deployed the App Service Highly Available File Server and SQL Server Quickstart template, these resources are also removed, as they are deployed in the same resource group as Azure App Service on Azure Stack Hub.
 
 To remove Azure App Service from Azure Stack Hub, follow this one step:
 
-1. Delete the Resource Group that holds the Azure App Service on Azure Stack Hub Resources, for example AppService.local
+- Delete the resource group that holds the Azure App Service on Azure Stack Hub Resources; for example, **AppService.local**.
 
 ## Remove databases and file share content
 
@@ -51,7 +47,7 @@ You only need to follow this section if your SQL Server and/or File Server is de
    DROP DATABASE [appservice_metering]
    GO
 
-   DECLARE @sql NVARCHAR(MAX) = N'';	
+   DECLARE @sql NVARCHAR(MAX) = N'';    
 
    SELECT @sql += '
    DROP LOGIN [' + name + '];' 
@@ -69,7 +65,7 @@ You only need to follow this section if your SQL Server and/or File Server is de
 
 ### Remove the application file content from the file server
 
-1. Remove the content fileshare from your file server.
+Remove the content fileshare from your file server.
 
 ## Next steps
 

azure-stack/operator/app-service-rotate-certificates.md

@@ -1,10 +1,10 @@
 ---
 title: Rotate App Service on Azure Stack Hub secrets and certificates 
 description: Learn how to rotate secrets and certificates used by Azure App Service on Azure Stack Hub.
-author: apwestgarth
+author: sethmanheim
 ms.topic: article
-ms.date: 04/09/2020
-ms.author: anwestg
+ms.date: 08/12/2024
+ms.author: sethm
 ms.reviewer: anwestg
 ms.lastreviewed: 04/09/2020
 
@@ -17,7 +17,7 @@ ms.lastreviewed: 04/09/2020
 
 These instructions only apply to Azure App Service on Azure Stack Hub. Rotation of Azure App Service on Azure Stack Hub secrets is not included in the centralized secret rotation procedure for Azure Stack Hub. Operators can monitor the validity of secrets within the system, the date on which they were last updated, and the time remaining until the secrets expire.
 
-> [!Important]
+> [!IMPORTANT]
 > Operators won't receive alerts for secret expiration on the Azure Stack Hub dashboard as Azure App Service on Azure Stack Hub is not integrated with the Azure Stack Hub alerting service. Operators must regularly monitor their secrets using the Azure App Service on Azure Stack Hub administration experience in the Azure Stack Hub administrator portal.
 
 This document contains the procedure for rotating the following secrets:
@@ -172,3 +172,7 @@ To rotate the system credentials used within Azure App Service on Azure Stack Hu
 1. Specify a **new Local Admin User Name** and a new **Password**. Then confirm the **Password** and select **OK**.
 
 1. The credential(s) are rotated as required throughout the corresponding Azure App Service on Azure Stack Hub role instance. Operators can check the status of the procedure using the **Status** button.
+
+## Next steps
+
+[Azure App Service on Azure Stack overview](azure-stack-app-service-overview.md)

azure-stack/operator/azure-site-recovery-capacity-planning.md

@@ -4,7 +4,7 @@ description: Learn about capacity planning for Azure Site Recovery.
 author: ronmiab
 ms.author: robess
 ms.topic: conceptual
-ms.date: 04/15/2024
+ms.date: 08/12/2024
 ms.reviewer: rtiberiu
 ms.lastreviewed: 04/15/2024
 ---

azure-stack/operator/azure-site-recovery-overview.md

@@ -4,7 +4,7 @@ description: Azure Site Recovery on Azure Stack Hub helps ensure business contin
 author: ronmiab
 ms.author: robess
 ms.topic: overview
-ms.date: 05/07/2024
+ms.date: 08/12/2024
 ms.reviewer: rtiberiu
 ms.lastreviewed: 04/18/2024
 

azure-stack/operator/azure-stack-add-ips.md

@@ -1,10 +1,9 @@
 ---
 title: Add public IP addresses in Azure Stack Hub 
-description: Learn how to add public IP addresses to Azure Stack Hub.  
+description: Learn how to add public IP addresses to an Azure Stack Hub system.  
 author: sethmanheim
-
 ms.topic: article
-ms.date: 10/21/2022
+ms.date: 08/12/2024
 ms.author: sethm
 ms.lastreviewed: 09/10/2019
 
@@ -15,40 +14,43 @@ ms.lastreviewed: 09/10/2019
 
 # Add public IP addresses
 
-In this article, we refer to external addresses as public IP addresses. In the context of Azure Stack Hub, a public IP address is an IP address that's accessible from outside of Azure Stack Hub. Whether that external network is public internet routable or is on an intranet and uses private address space doesn't matter for the purposes of this article, the steps are the same. 
+In this article, we refer to external addresses as public IP addresses. In the context of Azure Stack Hub, a public IP address is an IP address that's accessible from outside of Azure Stack Hub. Whether that external network is public internet routable or is on an intranet and uses private address space doesn't matter for the purposes of this article; the steps are the same.
 
-While you can set up multiple IP pools, you won't be able to select which pool is used to allocate Public IP addresses. Azure Stack Hub treats all IP pools as one. IP addresses from any additional pools are allocated only after the IP addresses in existing pool(s) have been exhausted. When you create a network resource, you cannot pick a specific Public IP for assignment, but once assigned it can be made static.
+While you can set up multiple IP pools, you can't select which pool is used to allocate public IP addresses. Azure Stack Hub treats all IP pools as one. IP addresses from any additional pools are allocated only after the IP addresses in existing pools are exhausted. When you create a network resource, you can't choose a specific public IP for assignment, but once assigned it can be made static.
 
 > [!IMPORTANT]
 > The steps in this article apply only to systems that were deployed using the partner toolkit version 1809 or later. Systems that were deployed before version 1809 require the top-of-rack (TOR) switch access control lists (ACLs) to be updated to PERMIT the new public VIP pool range. If you are running older switch configurations, work with your OEM to either add the appropriate PERMIT ACLs for the new public IP pool or reconfigure your switch using the latest partner toolkit to prevent the new public IP addresses from being blocked.
 
 ## Add a public IP address pool
-You can add public IP addresses to your Azure Stack Hub system at any time after the initial deployment of the Azure Stack Hub system. The network size on this subnet for the new Public IP Pool can range from a minimum of /26 (64 hosts) to a maximum of /22 (1022 hosts). We recommend that you plan for a /24 network.
-Check out how to [View public IP address consumption](azure-stack-viewing-public-ip-address-consumption.md) to see what the current usage and public IP address availability is on your Azure Stack Hub.
+
+You can add public IP addresses to your Azure Stack Hub system at any time after the initial deployment of the Azure Stack Hub system. The network size on this subnet for the new public IP pool can range from a minimum of /26 (64 hosts) to a maximum of /22 (1022 hosts). We recommend that you plan for a /24 network.
+
+See [how to view public IP address consumption](azure-stack-viewing-public-ip-address-consumption.md) to determine what the current usage and public IP address availability is on your Azure Stack Hub.
 
 At a high level, the process of adding a new public IP address block to Azure Stack Hub looks like this:
 
- ![Add IP flow](media/azure-stack-add-ips/flow.svg)
+![Screenshot showing adding IP flow.](media/azure-stack-add-ips/flow.svg)
 
 ## Obtain the address block from your provider
-The first thing you'll need to do is to obtain the address block you want to add to Azure Stack Hub. Depending on where you obtain your address block from, consider what the lead time is and manage this against the rate at which you're consuming public IP addresses in Azure Stack Hub.
+
+First, obtain the address block you want to add to Azure Stack Hub. Depending on where you obtain your address block from, consider what the lead time is and manage this against the rate at which you're consuming public IP addresses in Azure Stack Hub.
 
 > [!IMPORTANT]
-> Azure Stack Hub will accept any address block that you provide if it's a valid address block and doesn't overlap with an existing address range in Azure Stack Hub. Please make sure you obtain a valid address block that's routable and non-overlapping with the external network to which Azure Stack Hub is connected. After you add the range to Azure Stack Hub, you cannot remove it without the assistance of Microsoft Support. Only IP pools specified post deployment can be removed. The IP pool range specified during deployment cannot be modified or removed; a redeployment of the stamp is required if the original IP pool range needs to be changed.
+> Azure Stack Hub accepts any address block that you provide as long as it's a valid address block and doesn't overlap with an existing address range in Azure Stack Hub. Make sure you obtain a valid address block that's routable and doesn't overlap with the external network to which Azure Stack Hub is connected. After you add the range to Azure Stack Hub, you can't remove it without the assistance of Microsoft Support. Only IP pools specified post-deployment can be removed. The IP pool range specified during deployment cannot be modified or removed; a redeployment of the stamp is required if the original IP pool range needs to be changed.
 
 ## Add the IP address range to Azure Stack Hub
 
-1. In a browser, go to your administrator portal dashboard. For this example, we'll use `https://adminportal.local.azurestack.external`.
-2. Sign in to the Azure Stack Hub administrator portal as a cloud operator.
-3. On the default dashboard, find the Region management list and select the region you want to manage. For this example, we use local.
-4. Find the Resource providers tile and click on the network resource provider.
-5. Click on the Public IP pools usage tile.
-6. Click on the Add IP pool button.
-7. Provide a name for the IP pool. The name you choose helps you easily identify the IP pool. You can't use a special character like "/" in this field. It's a good practice to make the name the same as the address range, but that isn't required.
-8. Enter the address block you want to add in CIDR notation. For example: 192.168.203.0/24
-9. When you provide a valid CIDR range in the Address range (CIDR block) field the Start IP address, End IP address and Available IP addresses fields will automatically populate. They're read-only and automatically generated so you can't change these fields without modifying the value in the Address range field.
-10. After you review the info on the blade and confirm that everything looks correct, select **Ok** to commit the change and add the address range to Azure Stack Hub.
+1. In a browser, go to your administrator portal dashboard. This example uses `https://adminportal.local.azurestack.external`.
+1. Sign in to the Azure Stack Hub administrator portal as a cloud operator.
+1. On the default dashboard, find the region management list and select the region you want to manage. This example uses **local**.
+1. Find the **Resource providers** tile and select the network resource provider.
+1. Select **Public IP pools usage**.
+1. Select **Add IP pool**.
+1. Provide a name for the IP pool. The name you choose helps you easily identify the IP pool. You can't use a special character like `/` in this field. It's a good practice to make the name the same as the address range, but that isn't required.
+1. Enter the address block you want to add, in CIDR notation. For example, **192.168.203.0/24**.
+1. When you provide a valid CIDR range in the address range (CIDR block) field, the **Start IP address**, **End IP address**, and **Available IP addresses** fields automatically populate. They're read-only so you can't change these fields without modifying the value in the **Address range** field.
+1. After you review the info on the blade and confirm that everything looks correct, select **Ok** to commit the change and add the address range to Azure Stack Hub.
 
+## Next steps
 
-## Next steps 
 [Review scale unit node actions](azure-stack-node-actions.md).