Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us543898-nat-ip-v2-preview-remove

Author: asudbring

articles/azure-functions/durable/durable-functions-azure-storage-provider.md

@@ -249,7 +249,7 @@ As an example, if `durableTask/extendedSessionIdleTimeoutInSeconds` is set to 30
 The specific effects of extended sessions on orchestrator and entity functions are described in the next sections.
 
 > [!NOTE]
-> In the .NET isolated model, the extended sessions feature is currently only supported in orchestrations (not entities). Additionally, this feature is available only for .NET languages such as C# and F#. Setting `extendedSessionsEnabled` to `true` for other platforms can lead to runtime issues, such as silently failing to execute activity and orchestration-triggered functions.
+> This feature is available only for .NET languages such as C# (isolated and in-process models) and F#. Setting `extendedSessionsEnabled` to `true` for other platforms can lead to runtime issues, such as silently failing to execute activity and orchestration-triggered functions.
 
 ### Orchestrator function replay
 

articles/deployment-environments/.openpublishing.redirection.deployment-environments.json

@@ -32,7 +32,7 @@
     },
     {
       "source_path_from_root": "/articles/deployment-environments/concept-environments-reliability-availability.md",
-      "redirect_url": "/azure/reliability/reliability-deployment-environments",
+      "redirect_url": "/azure/deployment-environments/concept-reliability-deployment-environments",
       "redirect_document_id": false
     },
     {

articles/service-connector/tutorial-csharp-webapp-storage-cli.md

@@ -1,18 +1,18 @@
 ---
-title: Deploy a webapp connected to Azure Blob Storage
+title: Deploy a Webapp Connected to Azure Blob Storage
 description: This tutorial guides you through creating and deploying a web application that connects to Azure Blob Storage using Service Connector.
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: tutorial
-ms.date: 12/18/2024
+ms.date: 12/02/2025
 ms.devlang: azurecli
 ms.custom: devx-track-azurecli
 ---
 
 # Tutorial: Deploy a web application connected to Azure Blob Storage with Service Connector
 
-In this tutorial, you learn how to access Azure Blob Storage for a web app (not a signed-in user) running on Azure App Service by using managed identities. In this tutorial, you'll use the Azure CLI to complete the following tasks:
+In this tutorial, you learn how to access Azure Blob Storage for a web app (not a signed-in user) running on Azure App Service by using managed identities. In this tutorial, you use the Azure CLI to complete the following tasks:
 
 > [!div class="checklist"]
 >
@@ -22,7 +22,7 @@ In this tutorial, you learn how to access Azure Blob Storage for a web app (not
 
 ## Prerequisites
 
-* An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 [!INCLUDE [azure-cli-prepare-your-environment-no-header.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
@@ -64,12 +64,12 @@ In this tutorial, you learn how to access Azure Blob Storage for a web app (not
 
 1. In the terminal, make sure you're in the *WebAppStorageMISample* repository folder that contains the app code.
 
-1. Create an App Service app (the host process) with the [`az webapp up`](/cli/azure/webapp#az-webapp-up) command below and replace the placeholders with your own data:
+1. Create an App Service app (the host process) with the [`az webapp up`](/cli/azure/webapp#az-webapp-up) command and replace the following placeholders with your own data:
 
-    * For the `--location` argument, use a [region supported by Service Connector](concept-region-support.md).
-    * Replace `<app-name>` with a unique name across Azure. The server endpoint is `https://<app-name>.azurewebsites.net`. Allowed characters for `<app-name>` are `A`-`Z`, `0`-`9`, and `-`. A good pattern is to use a combination of your company name and an app identifier.
+    - For the `--location` argument, use a [region supported by Service Connector](concept-region-support.md).
+    - Replace `<app-name>` with a unique name across Azure. The server endpoint is `https://<app-name>.azurewebsites.net`. Allowed characters for `<app-name>` are `A`-`Z`, `0`-`9`, and `-`. A good pattern is to use a combination of your company name and an app identifier.
 
-   ```azurecli
+    ```azurecli
     az webapp up --name <app-name> --sku B1 --location eastus --resource-group ServiceConnector-tutorial-rg
     ```
 
@@ -93,8 +93,8 @@ az webapp connection create storage-blob -g ServiceConnector-tutorial-rg -n <app
 
 Replace the following placeholders with your own data:
 
-* Replace `<app-name>` with the web app name you used in step 3.
-* Replace `<storage-name>` with the storage app name you used in step 4.
+- Replace `<app-name>` with the web app name you used in step 3.
+- Replace `<storage-name>` with the storage app name you used in step 4.
 
 > [!NOTE]
 > If you see the error message "The subscription is not registered to use Microsoft.ServiceLinker", run `az provider register -n Microsoft.ServiceLinker` to register the Service Connector resource provider and run the connection command again.
@@ -111,7 +111,7 @@ The sample code is a web application. Each time you refresh the index page, the
 
 ## Next step
 
-To learn more about Service Connector, read the guide below.
+To learn more about Service Connector, read the following guide.
 
 > [!div class="nextstepaction"]
 > [Service Connector concepts](./concept-service-connector-internals.md)

articles/service-connector/tutorial-python-functions-storage-queue-as-trigger.md

@@ -1,12 +1,12 @@
 ---
-title: 'Tutorial: Python function with Azure Queue Storage as trigger'
-description: Learn how you can connect a Python function to a storage queue as trigger using Service Connector
+title: 'Tutorial: Python Function with Azure Queue Storage as Trigger'
+description: Learn how you can connect a Python function to a storage queue as trigger using Service Connector.
 author: houk-ms
 ms.author: honc
 ms.service: service-connector
 ms.custom: devx-track-python
 ms.topic: tutorial
-ms.date: 10/22/2024
+ms.date: 12/04/2025
 ---
 # Tutorial: Python function with Azure Queue Storage as trigger
 
@@ -29,7 +29,7 @@ An overview of the function project components in this tutorial:
 | Cloud Function Auth Type | Connection String        |
 
 > [!WARNING]
-> Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
+> Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a high degree of trust in the application, and carries risks that aren't present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 ## Prerequisites
 
@@ -40,7 +40,7 @@ An overview of the function project components in this tutorial:
 
 ## Create a Python function project
 
-Follow the [tutorial to create a local Azure Functions project](../azure-functions/how-to-create-function-vs-code.md?pivot=programming-language-python?pivots=python-mode-configuration#create-an-azure-functions-project), and provide the following information at the prompts:
+Follow the [tutorial to create a local Azure Functions project](../azure-functions/how-to-create-function-vs-code.md?pivot=programming-language-python?pivots=python-mode-configuration#create-an-azure-functions-project). Provide the following information at the prompts:
 
 | Prompt                                                                | Selection                                                                                                                                   |
 | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -50,29 +50,29 @@ Follow the [tutorial to create a local Azure Functions project](../azure-functio
 | **Provide a function name**                                     | Enter `QueueStorageTriggerFunc`.                                                                                                          |
 | **Select setting from "local.settings.json"**                   | Choose `Create new local app settings`, which lets you select your Storage Account and provide your queue name that works as the trigger. |
 
-You created a Python function project with Azure Storage Queue as trigger. The local project connects to Azure Storage using the connection string saved into the `local.settings.json` file. Finally, the `main` function in `__init__.py` file of the function can consume the connection string with the help of the Function Binding defined in the `function.json` file.
+With this information, Visual Studio Code generates a Python function project with Azure Storage Queue as the trigger. The local project connects to Azure Storage using the connection string saved into the `local.settings.json` file. Finally, the `main` function in the `__init__.py` file of the function can consume the connection string with the help of the Function Binding defined in the `function.json` file.
 
 ## Run the function locally
 
 Follow the [tutorial](../azure-functions/how-to-create-function-vs-code.md?pivot=programming-language-python?pivots=python-mode-configuration#run-the-function-locally) to run the function locally and verify the trigger.
 
-1. Select the storage account as you chose when creating the Azure Function resource if you're prompted to connect to storage. This value is used for Azure Function's runtime, and it isn't necessarily the same as the storage account you use for the trigger.
+1. If you're prompted to connect to storage, select the storage account you chose when creating the Azure Function resource. This value is used for Azure Function's runtime, and it isn't necessarily the same as the storage account you use for the trigger.
 1. To start the function locally, press `<kbd>`F5 `</kbd>` or select the **Run and Debug** icon in the left-hand side Activity bar.
-1. To verify the trigger works properly, keep the function running locally and open the Storage Queue pane in Azure portal, select **Add message** and provide a test message. You should see the function is triggered and processed as a queue item in your Visual Studio Code terminal.
+1. To verify the trigger works properly, keep the function running locally and open the Storage Queue pane in Azure portal. Select **Add message**, and provide a test message. You should see the function is triggered and processed as a queue item in your Visual Studio Code terminal.
 
 ## Create a connection using Service Connector
 
-In last step, you verified the function project locally. Now you'll learn how to configure the connection between the Azure Function and Azure Storage Queue in the cloud, so that your function can be triggered by the storage queue after being deployed to the cloud.
+In the last step, you verified the function project locally. Next, you learn how to configure the connection between the Azure Function and Azure Storage Queue. Once your function is deployed to the cloud, this connection allows your function to receive triggers from the storage queue.
 
-1. Open the `function.json` file in your local project, change the value of the `connection` property in `bindings` to be `AZURE_STORAGEQUEUE_CONNECTIONSTRING`.
+1. Open the `function.json` file in your local project, and change the value of the `connection` property in `bindings` to be `AZURE_STORAGEQUEUE_CONNECTIONSTRING`.
 1. Run the following Azure CLI command to create a connection between your Azure Function and your Azure storage account.
 
 ```azurecli
 az functionapp connection create storage-queue --source-id "<your-function-resource-id>" --target-id "<your-storage-queue-resource-id>" --secret
 ```
 
-* `--source-id` format: `/subscriptions/{subscription}/resourceGroups/{source_resource_group}/providers/Microsoft.Web/sites/{site}`
-* `--target-id` format: `/subscriptions/{subscription}/resourceGroups/{target_resource_group}/providers/Microsoft.Storage/storageAccounts/{account}/queueServices/default`
+- `--source-id` format: `/subscriptions/{subscription}/resourceGroups/{source_resource_group}/providers/Microsoft.Web/sites/{site}`
+- `--target-id` format: `/subscriptions/{subscription}/resourceGroups/{target_resource_group}/providers/Microsoft.Storage/storageAccounts/{account}/queueServices/default`
 
 This step creates a Service Connector resource that configures an `AZURE_STORAGEQUEUE_CONNECTIONSTRING` variable in the function's App Settings. The function binding runtime uses it to connect to the storage, so that the function can accept triggers from the storage queue. For more information, go to [how Service Connector helps Azure Functions connect to services](./how-to-use-service-connector-in-function.md).
 
@@ -81,7 +81,7 @@ This step creates a Service Connector resource that configures an `AZURE_STORAGE
 Now you can deploy your function to Azure and verify the storage queue trigger works.
 
 1. Follow this [Azure Functions tutorial](../azure-functions/how-to-create-function-vs-code.md?pivot=programming-language-python?pivots=python-mode-configuration#deploy-the-project-to-azure) to deploy your function to Azure.
-1. Open the Storage Queue pane in the Azure portal, select **Add message** and provide a test message. You should see the function is triggered and processed as a queue item in your function logs.
+1. Open the Storage Queue pane in the Azure portal. Select **Add message**, and provide a test message. You should see the function is triggered and processed as a queue item in your function logs.
 
 ## Troubleshoot
 
@@ -112,7 +112,7 @@ az functionapp delete --name <function-name> --resource-group <resource-group>
 
 ## Next steps
 
-Read the articles below to learn more about Service Connector concepts and how it helps Azure Functions connect to services.
+Read the following articles to learn more about Service Connector concepts and how it helps Azure Functions connect to services.
 
 > [!div class="nextstepaction"]
 > [Learn about Service Connector concepts](./concept-service-connector-internals.md)

articles/storage/container-storage/use-container-storage-with-local-disk.md

@@ -278,7 +278,7 @@ In this section, you learn how to check node ephemeral disk capacity, expand sto
 
 An ephemeral volume is allocated on a single node. When you configure the size of your ephemeral volumes, the size should be less than the available capacity of the single node's ephemeral disk.
 
-Make sure a StorageClass for **localdisk.csi.acstor.io** exists. Run the following command to check the available capacity of ephemeral disk for each node.
+Make sure a StorageClass for `localdisk.csi.acstor.io` exists. Run the following command to check the available capacity of ephemeral disk for each node.
 
 ```azurecli
 kubectl get csistoragecapacities.storage.k8s.io -n kube-system -o custom-columns=NAME:.metadata.name,STORAGE_CLASS:.storageClassName,CAPACITY:.capacity,NODE:.nodeTopology.matchLabels."topology\.localdisk\.csi\.acstor\.io/node"