Merge pull request #214125 from chcomley/users/chcomley/swa-blazor-1995786

Refresh deploy-blazor.md

Author: v-dirichards

articles/static-web-apps/add-mongoose.md

@@ -1,73 +1,59 @@
 ---
-title: "Tutorial: Access data in Azure Cosmos DB using Mongoose with Azure Static Web Apps"
+title: "Access data in Azure Cosmos DB using Mongoose with Azure Static Web Apps"
 description: Learn to access data in Azure Cosmos DB using Mongoose from an Azure Static Web Apps API function.
 author: GeekTrainer
 ms.author: chrhar
 ms.service: static-web-apps
 ms.custom: ignite-2022
 ms.topic: tutorial
-ms.date: 01/25/2021
+ms.date: 10/10/2022
 ---
 
-# Tutorial: Access data in Azure Cosmos DB using Mongoose with Azure Static Web Apps
-
-[Mongoose](https://mongoosejs.com/) is the most popular ODM (Object Document Mapping) client for Node.js. Allowing you to design a data structure and enforce validation, Mongoose provides all the tooling necessary to interact with databases that support the MongoDB API. [Azure Cosmos DB for MongoDB](../cosmos-db/mongodb-introduction.md) supports the necessary MongoDB APIs and is available as a back-end server option on Azure.
-
-In this tutorial, you learn how to:
-
-> [!div class="checklist"]
-> - Create an Azure Cosmos DB serverless account
-> - Create Azure Static Web Apps
-> - Update application settings to store the connection string
-
-If you don’t have an Azure subscription, create a [free trial account](https://azure.microsoft.com/free/).
+# Access data in Azure Cosmos DB using Mongoose with Azure Static Web Apps
 
+[Mongoose](https://mongoosejs.com/) is the most popular ODM (Object Document Mapping) client for Node.js. Mongoose allows you to design a data structure and enforce validation, and provides all the tooling necessary to interact with databases that support the MongoDB API. [Cosmos DB](../cosmos-db/mongodb-introduction.md) supports the necessary MongoDB APIs and is available as a back-end server option on Azure.
 ## Prerequisites
 
-- An [Azure account](https://azure.microsoft.com/free/)
-- A [GitHub account](https://github.com/join)
-
-## Sign in to Azure
-
-Sign in to the [Azure portal](https://portal.azure.com).
+- An [Azure account](https://azure.microsoft.com/free/). If you don’t have an Azure subscription, create a [free trial account](https://azure.microsoft.com/free/).
+- A [GitHub account](https://github.com/join).
+- A [Cosmos DB serverless](../cosmos-db/serverless.md) account. With a serverless account, you only pay for the resources as they're used and avoid needing to create a full infrastructure.
+## 1. Create a Cosmos DB serverless database
 
-## Create an Azure Cosmos DB serverless database
+Complete the following steps to create a Cosmos serverless DB.
 
-Begin by creating an [Azure Cosmos DB serverless](../cosmos-db/serverless.md) account. By using a serverless account, you only pay for the resources as they are used and avoid needing to create a full infrastructure.
-
-1. Navigate to the [Azure portal](https://portal.azure.com)
-2. Select **Create a resource**
-3. Enter **Azure Cosmos DB** in the search box
-4. Select **Azure Cosmos DB**
-5. Select **Create**
-6. If prompted, under **Azure Cosmos DB for MongoDB** select **Create**
-7. Configure your Azure Cosmos DB Account with the following information
+1. Sign in to the [Azure portal](https://portal.azure.com).
+2. Select **Create a resource**.
+3. Enter *Azure Cosmos DB* in the search box.
+4. Select **Azure Cosmos DB**.
+5. Select **Create**.
+6. If prompted, under **Azure Cosmos DB API for MongoDB** select **Create**.
+7. Configure your Azure Cosmos DB Account with the following information:
     - Subscription: Choose the subscription you wish to use
     - Resource: Select **Create new**, and set the name to **aswa-mongoose**
     - Account name: A unique value is required
     - Location: **West US 2**
     - Capacity mode: **Serverless (preview)**
     - Version: **4.0**
-:::image type="content" source="media/add-mongoose/cosmos-db.png" alt-text="Create new Azure Cosmos DB instance":::
-8. Select **Review + create**
-9. Select **Create**
+:::image type="content" source="media/add-mongoose/cosmos-db.png" alt-text="Screenshot showing form for creating new Cosmos DB instance.":::
+8. Select **Review + create**.
+9. Select **Create**.
 
-The creation process will take a few minutes. Later steps will return to the database to gather the connection string.
+The creation process takes a few minutes. We'll come back to the database to gather the connection string after we [create a static web app](#2-create-a-static-web-app).
 
-## Create a static web app
+## 2. Create a static web app
 
 This tutorial uses a GitHub template repository to help you create your application.
 
-1. Navigate to the [starter template](https://github.com/login?return_to=/staticwebdev/mongoose-starter/generate)
-2. Choose the **owner** (if using an organization other than your main account)
-3. Name your repository **aswa-mongoose-tutorial**
-4. Select **Create repository from template**
-5. Return to the [Azure portal](https://portal.azure.com)
-6. Select **Create a resource**
-7. Type **static web app** in the search box
-8. Select **Static Web App**
-9. Select **Create**
-10. Configure your Azure Static Web App with the following information
+1. Go to the [starter template](https://github.com/login?return_to=/staticwebdev/mongoose-starter/generate).
+2. Choose the **owner** (if using an organization other than your main account).
+3. Name your repository **aswa-mongoose-tutorial**.
+4. Select **Create repository from template**.
+5. Return to the [Azure portal](https://portal.azure.com).
+6. Select **Create a resource**.
+7. Enter **static web app** in the search box.
+8. Select **Static Web App**.
+9. Select **Create**.
+10. Configure your Azure Static Web App with the following information:
     - Subscription: Choose the same subscription as before
     - Resource group: Select **aswa-mongoose**
     - Name: **aswa-mongoose-tutorial**
@@ -82,61 +68,63 @@ This tutorial uses a GitHub template repository to help you create your applicat
     - Api location: **api**
     - Output location: **build**
     :::image type="content" source="media/add-mongoose/azure-static-web-apps.png" alt-text="Completed Azure Static Web Apps form":::
-11. Select **Review and create**
-12. Select **Create**
-13. The creation process takes a few moments; select **Go to resource** once the static web app is provisioned
-
-## Configure database connection string
-
-In order to allow the web app to communicate with the database, the database connection string is stored as an [Application Setting](application-settings.md). Setting values are accessible in Node.js using the `process.env` object.
-
-1. Select **Home** in the upper left corner of the Azure portal (or navigate back to [https://portal.azure.com](https://portal.azure.com))
-2. Select **Resource groups**
-3. Select **aswa-mongoose**
-4. Select the name of your database account - it will have a type of **Azure Cosmos DB for Mongo DB**
-5. Under **Settings** select **Connection String**
-6. Copy the connection string listed under **PRIMARY CONNECTION STRING**
-7. In the breadcrumbs, select **aswa-mongoose**
-8. Select **aswa-mongoose-tutorial** to return to the website instance
-9. Under **Settings** select **Configuration**
-10. Select **Add** and create a new Application Setting with the following values
+
+11. Select **Review and create**.
+12. Select **Create**.
+13. The creation process takes a few moments; select **Go to resource** once the static web app is provisioned.
+
+## 3. Configure database connection string
+
+To allow the web app to communicate with the database, the database connection string is stored as an [application setting](application-settings.md). Setting values are accessible in Node.js using the `process.env` object.
+
+1. Select **Home** in the upper left corner of the Azure portal (or go back to [https://portal.azure.com](https://portal.azure.com)).
+2. Select **Resource groups**.
+3. Select **aswa-mongoose**.
+4. Select the name of your database account - it has a type of **Azure Cosmos DB API for Mongo DB**.
+5. Under **Settings** select **Connection String**.
+6. Copy the connection string listed under **PRIMARY CONNECTION STRING**.
+7. In the breadcrumbs, select **aswa-mongoose**.
+8. Select **aswa-mongoose-tutorial** to return to the website instance.
+9. Under **Settings** select **Configuration**.
+10. Select **Add** and create a new Application Setting with the following values:
     - Name: **AZURE_COSMOS_CONNECTION_STRING**
     - Value: \<Paste the connection string you copied earlier\>
-11. Select **OK**
-12. Select **Add** and create a new Application Setting with the following values for name of the database
+11. Select **OK**.
+12. Select **Add** and create a new Application Setting with the following values for name of the database:
     - Name: **AZURE_COSMOS_DATABASE_NAME**
     - Value: **todo**
-13. Select **Save**
+13. Select **OK**.
+14. Select **Save**.
 
-## Navigate to your site
+## 4. Go to your site
 
 You can now explore the static web app.
 
-1. Select **Overview**
-1. Select the URL displayed in the upper right
-    1. It will look similar to `https://calm-pond-05fcdb.azurestaticapps.net`
-1. Select **Please login to see your list of tasks**
-1. Select **Grant consent** to access the application
-1. Create a new lists by typing a name into the textbox labeled **create new list** and selecting **Save**
-1. Create a new task by typing in a title in the textbox labeled **create new item** and selecting **Save**
-1. Confirm the task is displayed (it may take a moment)
-1. Mark the task as complete by **selecting the check**; the task will be moved to the **Done items** section of the page
-1. **Refresh the page** to confirm a database is being used
+1. In the Azure portal, select **Overview**.
+2. Select the URL displayed in the upper right.
+    1. It looks similar to `https://calm-pond-05fcdb.azurestaticapps.net`.
+3. Select **Please login to see your list of tasks**.
+4. Select **Grant consent** to access the application.
+5. Create a new list by entering a name into the textbox labeled **create new list** and selecting **Save**.
+6. Create a new task by typing in a title in the textbox labeled **create new item** and selecting **Save**.
+7. Confirm the task is displayed (it may take a moment).
+8. Mark the task as complete by **selecting the check**; the task moves to the **Done items** section of the page.
+9. **Refresh the page** to confirm a database is being used.
 
 ## Clean up resources
 
 If you're not going to continue to use this application, delete
 the resource group with the following steps:
 
-1. Return to the [Azure portal](https://portal.azure.com)
-2. Select **Resource groups**
-3. Select **aswa-mongoose**
-4. Select **Delete resource group**
-5. Type **aswa-mongoose** into the textbox
-6. Select **Delete**
+1. Return to the [Azure portal](https://portal.azure.com).
+2. Select **Resource groups**.
+3. Select **aswa-mongoose**.
+4. Select **Delete resource group**.
+5. Enter **aswa-mongoose** into the textbox.
+6. Select **Delete**.
 
 ## Next steps
 
 Advance to the next article to learn how to configure local development...
 > [!div class="nextstepaction"]
-> [Setup local development](./local-development.md)
+> [Set up local development](./local-development.md)

articles/static-web-apps/apex-domain-azure-dns.md

@@ -21,17 +21,17 @@ The following procedure requires you to copy settings from an Azure DNS zone you
 
 1. Open the [Azure portal](https://portal.azure.com).
 
-1. Navigate to your static web app.
+1. Go to your static web app.
 
 1. Under *Settings*, select **Custom domains**.
 
-1. Select the **+ Add** button, and select **Custom Domain on Azure DNS** from the drop down.
+1. Select **+ Add**, and then select **Custom Domain on Azure DNS** from the drop down menu.
 
 1. In the *Enter domain* tab, enter your apex domain name.
 
     For instance, if your domain name is `example.com`, enter `example.com` into this box (without any subdomains).
 
-1. Select the **Next** button.
+1. Select **Next**.
 
 1. In the *Validate + Configure* tab, enter the following values.
 
@@ -40,17 +40,17 @@ The following procedure requires you to copy settings from an Azure DNS zone you
     | Domain name | This value should match the domain name you entered in the previous step. |
     | Hostname record type | Select **TXT**. |
 
-1. Select the **Generate code** button.
+1. Select **Generate code**.
 
     Wait as the code is generated. It make take a minute or so to complete.
 
-1. Once the `TXT` record value is generated, select the **copy button** (next to the generated value) to copy the code to the clipboard.
+1. Once the `TXT` record value is generated,  **copy** (next to the generated value) the code to the clipboard.
 
-1. Select the **Close** button.
+1. Select **Close**.
 
-1. Navigate to your Azure DNS zone instance.
+1. Go to your Azure DNS zone instance.
 
-1. Select the **+ Record set** button.
+1. Select **+ Record set**.
 
 1. Enter the following values in the *Add record set* window.
 
@@ -62,23 +62,23 @@ The following procedure requires you to copy settings from an Azure DNS zone you
     | TTL unit | Keep default value. |
     | Value | Paste in the `TXT` record value in your clipboard from your static web app. |
 
-1. Select the **OK** button.
+1. Select **OK**.
 
 1. Return to your static web app in the Azure portal.
 
 1. Under *Settings*, select **Custom domains**.
 
-Observe the *Status* for the row of your apex domain. Once the validation is complete, then your apex domain will be publicly available.
+Observe the *Status* for the row of your apex domain. Once the validation is complete, then your apex domain is publicly available.
 
 While this validation is running, create an ALIAS record to finalize the configuration.
 
 ## Set up ALIAS record
 
 1. Return to the Azure DNS zone in the Azure portal.
 
-1. Select the **+ Record set button** button.
+2. Select **+ Record set**.
 
-1. Enter the following values in the *Add record set* window.
+3. Enter the following values in the *Add record set* window.
 
     | Setting | Property |
     |---|---|
@@ -91,9 +91,9 @@ While this validation is running, create an ALIAS record to finalize the configu
     | TTL | Keep default value. |
     | TTL unit | Keep default value. |
 
-1. Select the **OK** button.
+4. Select **OK**.
 
-1. Open a new browser tab and navigate to your apex domain.
+5. Open a new browser tab and go to your apex domain.
 
     After the DNS records are updated, you should see your static web app in the browser. Also, inspect the location to verify that your site is served securely using `https`.
 

articles/static-web-apps/apex-domain-external.md

@@ -36,40 +36,40 @@ Before you create the `ALIAS` record, you first need to validate that you own th
 
 1. Open the [Azure portal](https://portal.azure.com).
 
-1. Navigate to your static web app.
+1. Go to your static web app.
 
 1. From the *Overview* window, copy the generated **URL** of your site and set it aside in a text editor for future use.
 
 1. Under *Settings*, select **Custom domains**.
 
-1. Select the **+ Add** button.
+2. Select **+ Add**.
 
-1. In the *Enter domain* tab, enter your apex domain name.
+3. In the *Enter domain* tab, enter your apex domain name.
 
     For instance, if your domain name is `example.com`, enter `example.com` into this box (without any subdomains).
 
-1. Select the **Next** button.
+4. Select **Next**.
 
-1. In the *Validate + Configure* tab, enter the following values.
+5. In the *Validate + Configure* tab, enter the following values.
 
     | Setting | Value |
     |---|---|
     | Domain name | This value should match the domain name you entered in the previous step. |
     | Hostname record type | Select **TXT**. |
 
-1. Select the **Generate code** button.
+6. Select **Generate code**.
 
     Wait as the code is generated. It make take a minute or so to complete.
 
-1. Once the `TXT` record value is generated, select the **copy button** (next to the generated value) to copy the code to the clipboard.
+7. Once the `TXT` record value is generated, **copy** (next to the generated value) the code to the clipboard.
 
-1. Select the **Close** button.
+8. Select **Close**.
 
-1. Open a new browser tab and sign in to your domain registrar account.
+9. Open a new browser tab and sign in to your domain registrar account.
 
-1. Navigate to your domain name's DNS configuration settings.
+10. Go to your domain name's DNS configuration settings.
 
-1. Add a new `TXT` record with the following values.
+11. Add a new `TXT` record with the following values.
 
     | Setting | Value |
     |--|--|
@@ -78,7 +78,7 @@ Before you create the `ALIAS` record, you first need to validate that you own th
     | Value | Paste the generated code value you copied from the Azure portal. |
     | TTL (if applicable) | Leave as default value. |
 
-1. Save changes to your DNS record.
+12. Save changes to your DNS record.
 
 ### Set up an ALIAS record
 
@@ -97,7 +97,7 @@ Before you create the `ALIAS` record, you first need to validate that you own th
 
     Since DNS settings need to propagate, this process can take some time to complete.
 
-1. Open a new browser tab and navigate to your apex domain.
+1. Open a new browser tab and go to your apex domain.
 
     After the DNS records are updated, you should see your static web app in the browser. Also, inspect the location to verify that your site is served securely using `https`.
 

articles/static-web-apps/apis-api-management.md

@@ -30,7 +30,7 @@ All Azure API Management pricing tiers are available for use with Azure Static W
 
 To link an Azure API Management service as the API backend for a static web app, follow these steps:
 
-1. In the Azure portal, navigate to the static web app.
+1. In the Azure portal, go to the static web app.
 
 1. Select **APIs** from the navigation menu.
 
@@ -69,13 +69,13 @@ The linking process also automatically applies the following configuration to yo
 * The linked static web app is configured to include the subscription's primary key and a valid access token when proxying requests to the API Management service.
 
 > [!IMPORTANT]
-> Changing the *validate-jwt* policy or regenerating the subscription's primary key will prevent your static web app from proxying requests to the API Management service. Do not modify or delete the subscription or product associated with your static web app while they are linked.
+> Changing the *validate-jwt* policy or regenerating the subscription's primary key prevents your static web app from proxying requests to the API Management service. Do not modify or delete the subscription or product associated with your static web app while they are linked.
 
 ## Unlink an Azure API Management service
 
 To unlink an Azure API Management service from a static web app, follow these steps:
 
-1. In the Azure portal, navigate to the static web app.
+1. In the Azure portal, go to the static web app.
 
 1. Locate the environment that you want to unlink and select the API Management service name.