Merge pull request #300285 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

articles/azure-functions/functions-bindings-http-webhook-trigger.md

@@ -2,7 +2,7 @@
 title: Azure Functions HTTP trigger
 description: Learn how to call an Azure Function via HTTP.
 ms.topic: reference
-ms.date: 07/16/2024
+ms.date: 05/02/2025
 ms.devlang: csharp
 # ms.devlang: csharp, java, javascript, powershell, python
 ms.custom: devx-track-csharp, devx-track-python, devx-track-extended-java, devx-track-js, devx-track-ts
@@ -286,7 +286,7 @@ public HttpResponseMessage run(
 
 # [Model v4](#tab/nodejs-v4)
 
-The following example shows an HTTP trigger [TypeScript function](functions-reference-node.md?tabs=typescript). The function looks for a `name` parameter either in the query string or the body of the HTTP request.
+The following example shows an HTTP trigger [TypeScript function](functions-reference-node.md?tabs=typescript). The function looks for a `name` parameter either in the query string or the body of the [HTTP request](functions-reference-node.md?tabs=typescript&pivots=nodejs-model-v4#http-request). 
 
 :::code language="typescript" source="~/azure-functions-nodejs-v4/ts/src/functions/httpTrigger1.ts" :::
 
@@ -301,13 +301,13 @@ TypeScript samples aren't documented for model v3.
 
 # [Model v4](#tab/nodejs-v4)
 
-The following example shows an HTTP trigger [JavaScript function](functions-reference-node.md). The function looks for a `name` parameter either in the query string or the body of the HTTP request.
+The following example shows an HTTP trigger [JavaScript function](functions-reference-node.md). The function looks for a `name` parameter either in the query string or the body of the [HTTP request](functions-reference-node.md?tabs=javascript&pivots=nodejs-model-v4#http-request). 
 
 :::code language="javascript" source="~/azure-functions-nodejs-v4/js/src/functions/httpTrigger1.js" :::
 
 # [Model v3](#tab/nodejs-v3)
 
-The following example shows a trigger binding in a *function.json* file and a [JavaScript function](functions-reference-node.md) that uses the binding. The function looks for a `name` parameter either in the query string or the body of the HTTP request.
+The following example shows a trigger binding in a *function.json* file and a [JavaScript function](functions-reference-node.md) that uses the binding. The function looks for a `name` parameter either in the query string or the body of the [HTTP request](functions-reference-node.md?tabs=javascript&pivots=nodejs-model-v3#http-request). 
 
 Here's the *function.json* file:
 

articles/azure-functions/functions-how-to-use-azure-function-app-settings.md

@@ -3,7 +3,7 @@ title: Configure function app settings in Azure Functions
 description: Learn how to configure function app settings in Azure Functions.
 ms.service: azure-functions
 ms.topic: how-to
-ms.date: 11/11/2024
+ms.date: 05/21/2025
 ms.custom: cc996988-fb4f-47, devx-track-azurecli, devx-track-azurepowershell, ignite-2024
 ms.assetid: 81eb04f8-9a27-45bb-bf24-9ab6c30d205c
 ---
@@ -211,17 +211,21 @@ Choose the direction of the migration for your app on Windows.
 
 ### [Consumption-to-Premium](#tab/to-premium/azure-portal)
 
-1. In the Azure portal, navigate to your Consumption plan app and choose **Change App Service plan** under **App Service plan**.
+1. In the Azure portal, navigate to your Consumption plan app, and in the left pane expand **App Service plan** and select **App Service plan**.
 
-1. Select **Premium** under **Plan type**, create a new Premium plan, and select **OK**.
+1. In the **App Service plan** page, select **Change plan** under **Current App Service plan**. 
+
+1. In **Change App Service plan**, select **Premium** for **Plan type**, create a new Premium plan, and select **OK**.
 
 For more information, see [Move an app to another App Service plan](../app-service/app-service-plan-manage.md#move-an-app-to-another-app-service-plan).
 
 ### [Premium-to-Consumption](#tab/to-consumption/azure-portal)
 
-1. In the Azure portal, navigate to your Premium plan app and choose **Change App Service plan** under **App Service plan**.
+1. In the Azure portal, navigate to your Elastic Premium plan app, and in the left pane expand **App Service plan** and select **App Service plan**.
+
+1. In the **App Service plan** page, select **Change plan** under **Current App Service plan**. 
 
-1. Select **Consumption** under **Plan type**, create a new Consumption plan, and select **OK**.
+1. In **Change App Service plan**, select **Consumption** under **Plan type**, create a new Consumption plan, and select **OK**.
 
 For more information, see [Move an app to another App Service plan](../app-service/app-service-plan-manage.md#move-an-app-to-another-app-service-plan).
 

articles/cost-management-billing/manage/mca-setup-account.md

@@ -6,7 +6,7 @@ ms.reviewer: jkinma
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
-ms.date: 03/21/2025
+ms.date: 05/22/2025
 ms.author: jkinma
 ---
 
@@ -408,6 +408,7 @@ Enterprise administrators and department administrators are listed as invoice se
 - EA API keys - Azure Enterprise Reporting APIs are retired aren't available on MCA. Instead, you use Microsoft Cost Management APIs. For more information, see [Migrate from Azure Enterprise Reporting to Microsoft Cost Management APIs overview](../automate/migrate-ea-reporting-arm-apis-overview.md).
 - Automatic purchases - If used under your old EA enrollment, you need to set them up under your new Microsoft Customer Agreement.
 - Management groups – Subscriptions in management groups under a Microsoft Customer Agreement aren’t supported in Cost Management yet. Cost Management + Billing is managed with APIs and Azure portal functionality. For more information, see [Azure RBAC scopes](../costs/understand-work-scopes.md#azure-rbac-scopes).
+- Tax exemption certificates - If your EA account has a tax exemption certificate, you need to create an Azure support request to have a support representative associate your existing tax exempt certificate to your new Microsoft Customer Agreement account. Create a support request in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
 
 Here are some points to consider after migration.
 

articles/cost-management-billing/microsoft-customer-agreement/onboard-microsoft-customer-agreement.md

@@ -5,7 +5,7 @@ author: bandersmsft
 ms.service: cost-management-billing
 ms.subservice: microsoft-customer-agreement
 ms.topic: conceptual
-ms.date: 03/28/2025
+ms.date: 05/22/2025
 ms.author: banders
 ms.reviewer: clionabolger
 ---
@@ -234,6 +234,7 @@ This section of the onboarding guide describes the steps you follow to migrate f
 - EA API keys - Azure Enterprise Reporting APIs are retired aren't available on MCA. Instead, you use Microsoft Cost Management APIs. For more information, see [Migrate from Azure Enterprise Reporting to Microsoft Cost Management APIs overview](../automate/migrate-ea-reporting-arm-apis-overview.md).
 - Automatic purchases - If used under your old EA enrollment, you need to set them up under your new Microsoft Customer Agreement.
 - Management groups – Subscriptions in management groups under a Microsoft Customer Agreement aren’t supported in Cost Management yet. Cost Management + Billing is managed with APIs and Azure portal functionality. For more information, see [Azure RBAC scopes](../costs/understand-work-scopes.md#azure-rbac-scopes).
+- Tax exemption certificates - If your EA account has a tax exemption certificate, you need to create an Azure support request to have a support representative associate your existing tax exempt certificate to your new Microsoft Customer Agreement account. Create a support request in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
 
 Here are some points to consider after migration.
 

articles/logic-apps/.openpublishing.redirection.logic-apps.json

@@ -964,7 +964,7 @@
             "source_path_from_root": "/articles/connectors/connectors-create-api-github.md",
             "redirect_url": "/connectors/github",
             "redirect_document_id": false
-        },        
+        },
         {
             "source_path_from_root": "/articles/connectors/connectors-schema-migration.md",
             "redirect_url": "/azure/logic-apps/update-workflow-definition-language-schema",
@@ -999,6 +999,21 @@
             "source_path_from_root": "/articles/logic-apps/logic-apps-track-integration-account-custom-tracking-schema.md",
             "redirect_url": "/azure/logic-apps/tracking-schemas-consumption",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/logic-apps/create-unit-tests-standard-workflow-definitions-visual-studio-code.md",
+            "redirect_url": "/azure/logic-apps/testing-framework/create-unit-tests-standard-workflow-definitions-visual-studio-code",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/logic-apps/create-unit-tests-standard-workflow-runs-visual-studio-code.md",
+            "redirect_url": "/azure/logic-apps/testing-framework/create-unit-tests-standard-workflow-runs-visual-studio-code",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/logic-apps/test-logic-apps-mock-data-static-results.md",
+            "redirect_url": "/azure/logic-apps/testing-framework/test-logic-apps-mock-data-static-results",
+            "redirect_document_id": true
         }
     ]
-}
+}

articles/logic-apps/logic-apps-workflow-actions-triggers.md

@@ -2340,7 +2340,7 @@ You can change the default runtime behavior for triggers and actions by adding t
 | `runtimeConfiguration.concurrency.repetitions` | Integer | Change the [*default limit*](../logic-apps/logic-apps-limits-and-config.md#looping-debatching-limits) on the number of "for each" loop iterations that can run at the same time (concurrently or in parallel). <br><br>Setting the `repetitions` property to `1` works the same way as setting the `operationOptions` property to `SingleInstance`. You can set either property, but not both. <br><br>To change the default limit, see [Change "for each" concurrency](#change-for-each-concurrency) or [Run "for each" loops sequentially](#sequential-for-each). | Action: <br><br>[Foreach](#foreach-action) |
 | `runtimeConfiguration.paginationPolicy.minimumItemCount` | Integer | For specific actions that support and have pagination turned on, this value specifies the *minimum* number of results to retrieve. <br><br>To turn on pagination, see [Get bulk data, items, or results by using pagination](../logic-apps/logic-apps-exceed-default-page-size-with-pagination.md) | Action: Varied |
 | `runtimeConfiguration.secureData.properties` | Array | On many triggers and actions, these settings hide inputs, outputs, or both from the logic app's run history. <br><br>To learn more about safeguarding this data, see [Hide inputs and outputs from run history](../logic-apps/logic-apps-securing-a-logic-app.md#secure-data-code-view). | Most triggers and actions |
-| `runtimeConfiguration.staticResult` | JSON Object | For actions that support and have the [static result](../logic-apps/test-logic-apps-mock-data-static-results.md) setting turned on, the `staticResult` object has these attributes: <br><br>- `name`, which references the current action's static result definition name, which appears inside the `staticResults` attribute in your logic app workflow's `definition` attribute. For more information, see [Static results - Schema reference for Workflow Definition Language](../logic-apps/logic-apps-workflow-definition-language.md#static-results). <br><br> - `staticResultOptions`, which specifies whether static results are `Enabled` or not for the current action. <br><br>To turn on static results, see [Test logic apps with mock data by setting up static results](../logic-apps/test-logic-apps-mock-data-static-results.md) | Action: Varied |
+| `runtimeConfiguration.staticResult` | JSON Object | For actions that support and have the [static result](../logic-apps/testing-framework/test-logic-apps-mock-data-static-results.md) setting turned on, the `staticResult` object has these attributes: <br><br>- `name`, which references the current action's static result definition name, which appears inside the `staticResults` attribute in your logic app workflow's `definition` attribute. For more information, see [Static results - Schema reference for Workflow Definition Language](../logic-apps/logic-apps-workflow-definition-language.md#static-results). <br><br> - `staticResultOptions`, which specifies whether static results are `Enabled` or not for the current action. <br><br>To turn on static results, see [Test logic apps with mock data by setting up static results](../logic-apps/testing-framework/test-logic-apps-mock-data-static-results.md) | Action: Varied |
 
 <a name="operation-options"></a>