Merge pull request #212007 from MicrosoftDocs/main

Publish to Live, Wednesday 4AM PST, 9/21

Author: PMEds28

articles/active-directory/saas-apps/media/panorama9-tutorial/configuration.png

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 06/07/2021
+ms.date: 09/19/2022
 ms.author: jeedes
 ---
 # Tutorial: Azure Active Directory integration with Panorama9
@@ -120,23 +120,19 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 1. In a different web browser window, sign in to your Panorama9 company site as an administrator.
 
-2. In the toolbar on the top, click **Manage**, and then click **Extensions**.
-   
-	![Extensions](./media/panorama9-tutorial/toolbar.png "Extensions")
-
-3. On the **Extensions** dialog, click **Single Sign-On**.
-   
-	![Single Sign-On](./media/panorama9-tutorial/extension.png "Single Sign-On")
+2. Navigate to **Manage** -> **Extensions** -> **Single Sign-On**.
 
 4. In the **Settings** section, perform the following steps:
 
 	![Settings](./media/panorama9-tutorial/configuration.png "Settings")
 
-	a. In **Identity provider URL** textbox, paste the value of **Login URL**, which you have copied from Azure portal.
+	a. Enable the Single Sign-On.
+    
+    b. In **Identity URL** textbox, paste the value of **Identifier(Entity ID)**, which you have copied from Azure portal.
 
-	b. In **Certificate fingerprint** textbox, paste the **Thumbprint** value of certificate, which you have copied from Azure portal.    
+	c. In **Certificate fingerprint** textbox, paste the **Thumbprint** value of certificate, which you have copied from Azure portal.    
          
-5. Click **Save**.
+5. Click **Save Changes**.
 
 ### Create Panorama9 test user
 
@@ -148,30 +144,21 @@ In the case of Panorama9, provisioning is a manual task.
 
 1. Sign in to your **Panorama9** company site as an administrator.
 
-2. In the menu on the top, click **Manage**, and then click **Users**.
-   
-	![Screenshot that shows the "Manage" and "Users" tabs selected.](./media/panorama9-tutorial/user.png "Users")
-
-3. In the Users section, Click **+** to add new user.
+1. In the Users section, type the email address of a valid Azure Active Directory user you want to provision into the **Email** textbox and give a valid **Name**.
 
 	![Users](./media/panorama9-tutorial/new-user.png "Users")
 
-4. Go to the User data section, type the email address of a valid Azure Active Directory user you want to provision into the **Email** textbox.
-
-5. Come to the Users section, Click **Save**.
-   
-	> [!NOTE]
-    > The Azure Active Directory account holder receives an email and follows a link to confirm their account before it becomes active.
+5. Click **Create user**.
 
 ## Test SSO
 
 In this section, you test your Azure AD single sign-on configuration with following options. 
 
-* Click on **Test this application** in Azure portal. This will redirect to Panorama9 Sign-on URL where you can initiate the login flow. 
+* Click on **Test this application** in Azure portal. This will redirect to Panorama9 Sign on URL where you can initiate the login flow. 
 
-* Go to Panorama9 Sign-on URL directly and initiate the login flow from there.
+* Go to Panorama9 Sign on URL directly and initiate the login flow from there.
 
-* You can use Microsoft My Apps. When you click the Panorama9 tile in the My Apps, this will redirect to Panorama9 Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](https://support.microsoft.com/account-billing/sign-in-and-start-apps-from-the-my-apps-portal-2f3b1bae-0e5a-4a86-a33e-876fbd2a4510).
+* You can use Microsoft My Apps. When you click the Panorama9 tile in the My Apps, this will redirect to Panorama9 Sign on URL. For more information about the My Apps, see [Introduction to the My Apps](https://support.microsoft.com/account-billing/sign-in-and-start-apps-from-the-my-apps-portal-2f3b1bae-0e5a-4a86-a33e-876fbd2a4510).
 
 ## Next steps
 

articles/active-directory/saas-apps/media/panorama9-tutorial/new-user.png

@@ -202,6 +202,18 @@ When persistent storage is disabled, then writes to the `C:\home` directory are
 
 The only exception is the `C:\home\LogFiles` directory, which is used to store the container and application logs. This folder will always persist upon app restarts if [application logging is enabled](troubleshoot-diagnostic-logs.md?#enable-application-logging-windows) with the **File System** option, independently of the persistent storage being enabled or disabled. In other words, enabling or disabling the persistent storage will not affect the application logging behavior.
 
+By default, persistent storage is *disabled* on Windows custom containers. To enable it, set the `WEBSITES_ENABLE_APP_SERVICE_STORAGE` app setting value to `true` via the [Cloud Shell](https://shell.azure.com). In Bash:
+
+```azurecli-interactive
+az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings WEBSITES_ENABLE_APP_SERVICE_STORAGE=true
+```
+
+In PowerShell:
+
+```azurepowershell-interactive
+Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WEBSITES_ENABLE_APP_SERVICE_STORAGE"=true}
+```
+
 ::: zone-end
 
 ::: zone pivot="container-linux"
@@ -214,9 +226,7 @@ The only exception is the `/home/LogFiles` directory, which is used to store the
 
 It is recommended to write data to `/home` or a [mounted azure storage path](configure-connect-to-azure-storage.md?tabs=portal&pivots=container-linux). Data written outside these paths will not be persistent during restarts and will be saved to platform-managed host disk space separate from the App Service Plans file storage quota.
 
-::: zone-end
-
-By default, persistent storage is **enabled** on custom containers, you can disable this through app settings. To disable it, set the `WEBSITES_ENABLE_APP_SERVICE_STORAGE` app setting value to `false` via the [Cloud Shell](https://shell.azure.com). In Bash:
+By default, persistent storage is *enabled* on Linux custom containers. To disable it, set the `WEBSITES_ENABLE_APP_SERVICE_STORAGE` app setting value to `false` via the [Cloud Shell](https://shell.azure.com). In Bash:
 
 ```azurecli-interactive
 az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings WEBSITES_ENABLE_APP_SERVICE_STORAGE=false
@@ -228,6 +238,8 @@ In PowerShell:
 Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WEBSITES_ENABLE_APP_SERVICE_STORAGE"=false}
 ```
 
+::: zone-end
+
 > [!NOTE]
 > You can also [configure your own persistent storage](configure-connect-to-azure-storage.md).
 

articles/active-directory/saas-apps/panorama9-tutorial.md

@@ -412,6 +412,14 @@ You can delete the Azure Arc-enabled Kubernetes resource, any associated configu
 az connectedk8s delete --name AzureArcTest1 --resource-group AzureArcTest
 ```
 
+If the deletion process hangs, use the following command to force deletion (adding `-y` if you want to bypass the confirmation prompt):
+
+```azurecli
+az connectedk8s delete -g AzureArcTest1 -n AzureArcTest --force
+```
+
+This command can also be used if you experience issues when creating a new cluster deployment (due to previously created resources not being completely removed).
+
 >[!NOTE]
 > Deleting the Azure Arc-enabled Kubernetes resource using the Azure portal removes any associated configuration resources, but *does not* remove any agents running on the cluster. Best practice is to delete the Azure Arc-enabled Kubernetes resource using `az connectedk8s delete` rather than deleting the resource in the Azure portal.
 

articles/app-service/configure-custom-container.md

@@ -404,7 +404,7 @@
         - name: Manage a function app
           href: functions-how-to-use-azure-function-app-settings.md
           displayName: app setting, application setting
-        - name: Reference function app settings from App Configuration (preview)
+        - name: App Configuration references
           href: ../app-service/app-service-configuration-references.md?toc=%2fazure%2fazure-functions%2ftoc.json
         - name: Set the runtime version
           href: set-runtime-version.md

articles/azure-arc/kubernetes/quickstart-connect-cluster.md

@@ -3,7 +3,7 @@ title: Develop and run Azure Functions locally
 description: Learn how to code and test Azure Functions on your local computer before you run them on Azure Functions.
 
 ms.topic: conceptual
-ms.date: 05/19/2022
+ms.date: 09/22/2022
 
 ---
 # Code and test Azure Functions locally
@@ -18,9 +18,9 @@ The way in which you develop functions on your local computer depends on your [l
 
 |Environment                              |Languages         |Description|
 |-----------------------------------------|------------|---|
-|[Visual Studio Code](functions-develop-vs-code.md)| [C# (class library)](functions-dotnet-class-library.md)<br/>[C# isolated process (.NET 5.0)](dotnet-isolated-process-guide.md)<br/>[JavaScript](functions-reference-node.md)<br/>[PowerShell](./create-first-function-vs-code-powershell.md)<br/>[Python](functions-reference-python.md) | The [Azure Functions extension for VS Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions) adds Functions support to VS Code. Requires the Core Tools. Supports development on Linux, macOS, and Windows, when using version 2.x of the Core Tools. To learn more, see [Create your first function using Visual Studio Code](./create-first-function-vs-code-csharp.md). |
-| [Command prompt or terminal](functions-run-local.md) | [C# (class library)](functions-dotnet-class-library.md)<br/>[C# isolated process (.NET 5.0)](dotnet-isolated-process-guide.md)<br/>[JavaScript](functions-reference-node.md)<br/>[PowerShell](functions-reference-powershell.md)<br/>[Python](functions-reference-python.md) | [Azure Functions Core Tools] provides the core runtime and templates for creating functions, which enable local development. Version 2.x supports development on Linux, macOS, and Windows. All environments rely on Core Tools for the local Functions runtime. |
-| [Visual Studio 2019](functions-develop-vs.md) | [C# (class library)](functions-dotnet-class-library.md)<br/>[C# isolated process (.NET 5.0)](dotnet-isolated-process-guide.md) | The Azure Functions tools are included in the **Azure development** workload of [Visual Studio 2019](https://www.visualstudio.com/vs/) and later versions. Lets you compile functions in a class library and publish the .dll to Azure. Includes the Core Tools for local testing. To learn more, see [Develop Azure Functions using Visual Studio](functions-develop-vs.md). |
+|[Visual Studio Code](functions-develop-vs-code.md)| [C# (in-process)](functions-dotnet-class-library.md)<br/>[C# (isolated process)](dotnet-isolated-process-guide.md)<br/>[JavaScript](functions-reference-node.md)<br/>[PowerShell](./create-first-function-vs-code-powershell.md)<br/>[Python](functions-reference-python.md) | The [Azure Functions extension for VS Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions) adds Functions support to VS Code. Requires the Core Tools. Supports development on Linux, macOS, and Windows, when using version 2.x of the Core Tools. To learn more, see [Create your first function using Visual Studio Code](./create-first-function-vs-code-csharp.md). |
+| [Command prompt or terminal](functions-run-local.md) | [C# (in-process)](functions-dotnet-class-library.md)<br/>[C# (isolated process)](dotnet-isolated-process-guide.md)<br/>[JavaScript](functions-reference-node.md)<br/>[PowerShell](functions-reference-powershell.md)<br/>[Python](functions-reference-python.md) | [Azure Functions Core Tools] provides the core runtime and templates for creating functions, which enable local development. Version 2.x supports development on Linux, macOS, and Windows. All environments rely on Core Tools for the local Functions runtime. |
+| [Visual Studio](functions-develop-vs.md) | [C# (in-process)](functions-dotnet-class-library.md)<br/>[C# (isolated process)](dotnet-isolated-process-guide.md) | The Azure Functions tools are included in the **Azure development** workload of [Visual Studio](https://www.visualstudio.com/vs/), starting with Visual Studio 2019. Lets you compile functions in a class library and publish the .dll to Azure. Includes the Core Tools for local testing. To learn more, see [Develop Azure Functions using Visual Studio](functions-develop-vs.md). |
 | [Maven](./create-first-function-cli-java.md) (various) | [Java](functions-reference-java.md) | Maven archetype supports Core Tools to enable development of Java functions. Version 2.x supports development on Linux, macOS, and Windows. To learn more, see [Create your first function with Java and Maven](./create-first-function-cli-java.md). Also supports development using [Eclipse](functions-create-maven-eclipse.md) and [IntelliJ IDEA](functions-create-maven-intellij.md). |
 
 [!INCLUDE [Don't mix development environments](../../includes/functions-mixed-dev-environments.md)]
@@ -29,7 +29,7 @@ Each of these local development environments lets you create function app projec
 
 ## Local settings file
 
-The local.settings.json file stores app settings and settings used by local development tools. Settings in the local.settings.json file are used only when you're running your project locally. 
+The local.settings.json file stores app settings and settings used by local development tools. Settings in the local.settings.json file are used only when you're running your project locally. When you publish your project to Azure, be sure to also add any required settings to the app settings for the function app.
 
 > [!IMPORTANT]  
 > Because the local.settings.json may contain secrets, such as connection strings, you should never store it in a remote repository. Tools that support Functions provide ways to synchronize settings in the local.settings.json file with the [app settings](functions-how-to-use-azure-function-app-settings.md#settings) in the function app to which your project is deployed.
@@ -77,12 +77,20 @@ The following application settings can be included in the **`Values`** array whe
 |**`FUNCTIONS_WORKER_RUNTIME`** | `dotnet`<br/>`dotnet-isolated`<br/>`node`<br/>`java`<br/>`powershell`<br/>`python`| Indicates the targeted language of the Functions runtime. Required for version 2.x and higher of the Functions runtime. This setting is generated for your project by Core Tools. To learn more, see the [`FUNCTIONS_WORKER_RUNTIME`](functions-app-settings.md#functions_worker_runtime) reference.|
 | **`FUNCTIONS_WORKER_RUNTIME_VERSION`** | `~7` |Indicates to use PowerShell 7 when running locally. If not set, then PowerShell Core 6 is used. This setting is only used when running locally. The PowerShell runtime version is determined by the `powerShellVersion` site configuration setting, when it runs in Azure, which can be [set in the portal](functions-reference-powershell.md#changing-the-powershell-version). |
 
+## Synchronize settings
+
+When you develop your functions locally, any local settings required by your app must also be present in app settings of the function app to which your code is deployed. You may also need to download current settings from the function app to your local project. While you can [manually configure app settings in the Azure portal](functions-how-to-use-azure-function-app-settings.md?tabs=portal#settings), the following tools also let you synchronize app settings with local settings in your project:
+
++ [Visual Studio Code](functions-develop-vs-code.md#application-settings-in-azure)
++ [Visual Studio](functions-develop-vs.md#function-app-settings)
++ [Azure Functions Core Tools](functions-run-local.md#local-settings)
+
 ## Next steps
 
-+ To learn more about local development of compiled C# functions using Visual Studio 2019, see [Develop Azure Functions using Visual Studio](functions-develop-vs.md).
++ To learn more about local development of compiled C# functions (both in-process and isolated process) using Visual Studio, see [Develop Azure Functions using Visual Studio](functions-develop-vs.md).
 + To learn more about local development of functions using VS Code on a Mac, Linux, or Windows computer, see the Visual Studio Code getting started article for your preferred language:
-    + [C# class library](create-first-function-vs-code-csharp.md)
-    + [C# isolated process (.NET 5.0)](create-first-function-vs-code-csharp.md?tabs=isolated-process)
+    + [C# (in-process)](create-first-function-vs-code-csharp.md)
+    + [C# )isolated process)](create-first-function-vs-code-csharp.md?tabs=isolated-process)
     + [Java](create-first-function-vs-code-java.md)
     + [JavaScript](create-first-function-vs-code-node.md)
     + [PowerShell](create-first-function-vs-code-powershell.md)

articles/azure-functions/TOC.yml

@@ -325,7 +325,7 @@ To learn more about how Azure Monitor metric alerts work and how to configure th
       "EnableClassic": false,    
       "AutoStop_MetricName": "Percentage CPU",
       "AutoStop_Condition": "LessThan",
-      "AutoStop_Description": "Alert to stop the VM if the CPU % exceed the threshold",
+      "AutoStop_Description": "Alert to stop the VM if the CPU % falls below the threshold",
       "AutoStop_Frequency": "00:05:00",
       "AutoStop_Severity": "2",
       "AutoStop_Threshold": "5",
@@ -347,7 +347,7 @@ To learn more about how Azure Monitor metric alerts work and how to configure th
     {
       "Action": "stop",
       "AutoStop_Condition": "LessThan",
-      "AutoStop_Description": "Alert to stop the VM if the CPU % exceed the threshold",
+      "AutoStop_Description": "Alert to stop the VM if the CPU % falls below the threshold",
       "AutoStop_Frequency": "00:05:00",
       "AutoStop_MetricName": "Percentage CPU",
       "AutoStop_Severity": "2",
@@ -372,7 +372,7 @@ To learn more about how Azure Monitor metric alerts work and how to configure th
     {
       "Action": "stop",
       "AutoStop_Condition": "LessThan",
-      "AutoStop_Description": "Alert to stop the VM if the CPU % exceed the threshold",
+      "AutoStop_Description": "Alert to stop the VM if the CPU % falls below the threshold",
       "AutoStop_Frequency": "00:05:00",
       "AutoStop_MetricName": "Percentage CPU",
       "AutoStop_Severity": "2",