Skip to content

Commit 119a07f

Browse files
authored
Doc quality improvements
1 parent 86a1e90 commit 119a07f

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ zone_pivot_groups:
2020
In this article, you learn how to upgrade the [Azure App Service resource provider](azure-stack-app-service-overview.md) deployed in an Azure Stack Hub environment that is connected or disconnected from the Internet and, secured by Entra ID or Active Directory Federation Services (AD FS).
2121

2222
> [!IMPORTANT]
23-
> Prior to running the upgrade, you must complete [deployment of Azure App Service on Azure Stack Hub](./azure-stack-app-service-deploy.md).
23+
> Before running the upgrade, you must complete [deployment of Azure App Service on Azure Stack Hub](./azure-stack-app-service-deploy.md).
2424
2525
## Run the App Service resource provider installer
2626

@@ -41,7 +41,7 @@ During this process, the upgrade will:
4141
## Complete the upgrade of App Service on Azure Stack Hub
4242

4343
> [!IMPORTANT]
44-
> The Azure App Service installer must be run on a machine which can reach the Azure Stack Hub Administrator Azure Resource Manager Endpoint.
44+
> The Azure App Service installer must be run on a machine, which can reach the Azure Stack Hub Administrator Azure Resource Manager Endpoint.
4545
4646
# [Azure App Service on Azure Stack 2022 H1](#tab/22h1)
4747

@@ -53,7 +53,7 @@ During this process, the upgrade will:
5353

5454
![Screenshot showing the Azure App Service on Azure Stack Hub installer advanced options.][7]
5555

56-
1. Browse to the location of the offline upgrade package you previously dopwnloaded and then select **Next**.
56+
1. Browse to the location of the offline upgrade package you previously downloaded and then select **Next**.
5757

5858
1. Review and accept the Microsoft Software License Terms and then select **Next**.
5959

@@ -73,21 +73,21 @@ During this process, the upgrade will:
7373
- The service principal that you use **must** have **Owner** rights on the **Default Provider Subscription**
7474
- Provide the **Service Principal ID**, **Certificate File**, and **Password** and select **Connect**.
7575

76-
1. In **Azure Stack Hub Subscriptions**, select the **Default Provider Subscription**. Azure App Service on Azure Stack Hub **must** be deployed in the **Default Provider Subscription**.
76+
1. In **Azure Stack Hub Subscriptions**, select the **Default Provider Subscription**. Azure App Service on Azure Stack Hub **must** be deployed in the **Default Provider Subscription**.
7777

78-
1. In the **Azure Stack Hub Locations**, select the location that corresponds to the region you're deploying to. For example, select **local** if you're deploying to the ASDK.
78+
1. In the **Azure Stack Hub Locations**, select the location that corresponds to the region you're deploying to. For example, select **local** if you're deploying to the Azure Stack Deployment Kit.
7979

8080
1. If an existing App Service deployment is detected, then the resource group and storage account will be populated and greyed out.
8181

82-
1. **NEW**: Administrators can specify a three character **Deployment Prefix** for the individual instances in each Virtual Machine Scale Set that are deployed. This is useful if managing multiple Azure Stack Hub instances.
82+
1. **NEW**: Administrators can specify a three character **Deployment Prefix** for the individual instances in each Virtual Machine Scale Set that are deployed. The Deployment Prefix is useful if managing multiple Azure Stack Hub instances.
8383

8484
![Screenshot showing Azure App Service on Azure Stack Hub installation detected.][9]
8585

86-
1. In the next screen, you'll see the results of a status check performed against the App Service Resource Provider. This status check has been added to verify the deployment is in the correct state to be upgraded. The status check verifies that all roles are ready, all worker tiers are valid, all virtual machine scale sets are healthy and verifies access to the App Service secrets.
86+
1. In the next screen, you'll see the results of a status check performed against the App Service Resource Provider. This status check was added to verify the deployment is in the correct state to be upgraded. The status check verifies that all roles are ready, all worker tiers are valid, all virtual machine scale sets are healthy and verifies access to the App Service secrets.
8787

8888
![Screenshot showing Azure App Service on Azure Stack Hub pre-upgrade status check.][10]
8989

90-
1. The Platform Image and SKU screen gives Administrators the opportunity to choose the correct [Windows 2022 Platform](azure-stack-app-service-before-you-get-started.md#download-items-from-the-azure-marketplace) image to be used to deploy the new role instances.
90+
1. The Platform Image and SKU screen, gives Administrators the opportunity to choose the correct [Windows 2022 Platform](azure-stack-app-service-before-you-get-started.md#download-items-from-the-azure-marketplace) image to be used to deploy the new role instances.
9191
1. **Select** the correct Platform Image
9292
1. Over time the minimum recommended spec of VM/VM Scale Set instance SKUs has changed and here you see the details of what is currently deployed and the new recommended SKU.
9393

@@ -99,7 +99,7 @@ During this process, the upgrade will:
9999
![Screenshot showing Azure App Service on Azure Stack Hub upgrade summary.][4]
100100

101101
> [!NOTE]
102-
> Upgrading to 2022.H1 can take a considerable amount of time dependent on the number of role instances deployed within the App Service on Azure Stack Hub Resource Provider deployment.
102+
> Upgrade to 25R1 can take a considerable amount of time dependent on the number of role instances within the App Service on Azure Stack Hub Resource Provider deployment.
103103
>
104104
105105
1. Upgrade progress page:

0 commit comments

Comments
 (0)