Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into privlink-patch

Author: asudbring

articles/active-directory/authentication/how-to-mfa-microsoft-managed.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: conceptual
-ms.date: 11/11/2021
+ms.date: 02/22/2022
 
 ms.author: justinha
 author: mjsantani
@@ -26,7 +26,7 @@ The option to let Azure AD manage the setting is a convenient way for an organiz
 
 ## Settings that can be Microsoft managed
 
-The following table lists settings that can be set to Microsoft managed and whether it is enabled or disabled. 
+The following table list each setting that can be set to Microsoft managed and whether that setting is enabled or disabled by default. 
 
 | Setting                                                                                                                         | Configuration |
 |---------------------------------------------------------------------------------------------------------------------------------|---------------|

articles/azure-monitor/app/change-analysis-troubleshoot.md

@@ -4,7 +4,7 @@ description: Learn how to troubleshoot problems in Application Change Analysis.
 ms.topic: conceptual
 author: cawams
 ms.author: cawa
-ms.date: 01/07/2022 
+ms.date: 02/17/2022 
 ms.custom: devx-track-azurepowershell
 
 ---
@@ -66,12 +66,9 @@ This general unauthorized error message occurs when the current user does not ha
 * To view infrastructure changes returned by Azure Resource Graph and Azure Resource Manager, reader access is required. 
 * For web app in-guest file changes and configuration changes, contributor role is required. 
 
-You may not immediately see web app in-guest file changes and configuration changes. While we work on providing the option to restart the app in the Azure portal, the current procedure is:
+## Cannot see in-guest changes for newly enabled Web App.
 
-1. User adds the hidden tracking tag, notifying the scheduled worker.
-2. Scheduled worker scans the web app within a few hours.
-3. While scanning, scheduled worker creates a handshake file via AST.
-4. The Web App team checks that handshake file when it restarts.
+You may not immediately see web app in-guest file changes and configuration changes. Restart your web app and you should be able to view changes within 30 minutes. If not, contact the [Change Analysis help team](mailto:[email protected]).
 
 ## Diagnose and solve problems tool for virtual machines
 

articles/static-web-apps/get-started-cli.md

@@ -108,6 +108,19 @@ Now that the repository is created, you can create a static web app from the Azu
         --login-with-github
     ```
 
+    # [Blazor](#tab/blazor)
+
+    ```azurecli
+    az staticwebapp create \
+        --name my-first-static-web-app \
+        --resource-group my-swa-group \
+        --source https://github.com/$GITHUB_USER_NAME/my-first-static-web-app \
+        --location "eastus2" \
+        --branch main \
+        --app-location "Client" \
+        --output-location "wwwroot"  \
+        --login-with-github
+    ```
     ---
 
     > [!IMPORTANT]

articles/static-web-apps/get-started-portal.md

@@ -85,6 +85,13 @@ After you sign in with GitHub, enter the repository information.
     1. Keep the default value in the _App location_ box.
     1. Leave the _Api location_ box empty.
     1. Keep the default value in the _App artifact location_ box.
+    
+    # [Blazor](#tab/blazor)
+
+    1. Select **Blazor** from the _Build Presets_ dropdown.
+    1. Keep the default value of **Client** in the _App location_ box.
+    1. Leave the _Api location_ box empty.
+    1. Keep the default value of **wwwroot** in the _App artifact location_ box.
 
     ---
 

articles/static-web-apps/getting-started.md

@@ -110,6 +110,14 @@ If you don't already have the [Azure Static Web Apps extension for Visual Studio
 
     Enter **dist** as the build output location.
 
+    # [Blazor](#tab/blazor)
+
+    :::image type="content" source="media/getting-started/extension-presets-blazor.png" alt-text="Application presets: Blazor":::
+
+    Enter **Client** as the location for the application files, since this is the root folder of the Blazor project.
+
+    Enter **wwwroot** as the build output location.
+
     ---
 
 1. Once the app is created, a confirmation notification is shown in Visual Studio Code.
@@ -132,7 +140,7 @@ If you're not going to continue to use this application, you can delete the Azur
 
 In the Visual Studio Code Explorer window, return to the _Static Web Apps_ section and right-click on **my-first-static-web-app** and select **Delete**.
 
-:::image type="content" source="media/getting-started/extension-delete.png" alt-text="Delete app":::
+:::image type="content" source="media/getting-started/extension-delete.png" alt-text="Delete app"::: 
 
 ## Next steps
 

articles/static-web-apps/index.yml

@@ -31,6 +31,8 @@ landingContent:
             url: ./getting-started.md?tabs=react
           - text: Deploy a Vue app
             url: ./getting-started.md?tabs=vue
+          - text: Deploy a Blazor app
+            url: ./getting-started.md?tabs=blazor
       - linkListType: learn
         links:
           - text: Publish an Angular, React, Svelte, or Vue JavaScript app

articles/static-web-apps/media/getting-started/extension-presets-blazor.png

@@ -37,6 +37,12 @@ This article uses a GitHub template repository to make it easy for you to get st
     1. [https://github.com/staticwebdev/vue-basic/generate](https://github.com/login?return_to=%2Fstaticwebdev%2Fvue-basic%2Fgenerate)
 1. Name your repository **my-first-static-web-app**
 
+# [Blazor](#tab/blazor)
+
+1. Navigate to the following location to create a new repository:
+    1. [https://github.com/staticwebdev/blazor-basic/generate](https://github.com/login?return_to=%2Fstaticwebdev%2Fblazor-basic%2Fgenerate)
+1. Name your repository **my-first-static-web-app**
+
 ---
 
 Select **Create repository from template**.