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

Author: pauljewellmsft

.openpublishing.redirection.json

@@ -30,6 +30,11 @@
       "redirect_url": "/previous-versions/azure/partner-solutions/logzio/troubleshoot",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/event-grid/event-schema-storage-actions.md",
+      "redirect_url": "/azure/storage-actions/overview",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/hdinsight-aks/index.yml",
       "redirect_url": "/previous-versions/azure/hdinsight-aks",
@@ -5935,6 +5940,11 @@
       "redirect_url": "/azure/reliability/overview-reliability-guidance",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/reliability/sovereign-cloud-china.md",
+      "redirect_url": "/azure/china/concepts-service-availability",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/managed-grafana/concept-role-based-access-control.md",
       "redirect_url": "/azure/managed-grafana/how-to-manage-access-permissions-users-identities",

articles/active-directory-b2c/localization-string-ids.md

@@ -496,18 +496,18 @@ The following IDs are used for a [time-based one-time password (TOTP) display co
       </LocalizedResources>
 ```
 
-## Restful service error messages
+## RESTful service error messages
 
-The following IDs are used for [Restful service technical profile](restful-technical-profile.md) error messages:
+The following IDs are used for [RESTful service technical profile](restful-technical-profile.md) error messages:
 
 | ID | Default value |
 | --- | ------------- |
-| `DefaultUserMessageIfRequestFailed` | Failed to establish connection to restful service end point. Restful service URL: {0} |
-| `UserMessageIfCircuitOpen` | {0} Restful Service URL: {1} |
-| `UserMessageIfDnsResolutionFailed` | Failed to resolve the hostname of the restful service endpoint. Restful service URL: {0} |
-| `UserMessageIfRequestTimeout` | Failed to establish connection to restful service end point within timeout limit {0} seconds. Restful service URL: {1} |
+| `DefaultUserMessageIfRequestFailed` | Failed to establish connection to restful service end point. RESTful service URL: {0} |
+| `UserMessageIfCircuitOpen` | {0} RESTful Service URL: {1} |
+| `UserMessageIfDnsResolutionFailed` | Failed to resolve the hostname of the restful service endpoint. RESTful service URL: {0} |
+| `UserMessageIfRequestTimeout` | Failed to establish connection to restful service end point within timeout limit {0} seconds. RESTful service URL: {1} |
 
-### Restful service example
+### RESTful service example
 
 ```xml
 <LocalizedResources Id="api.localaccountsignup.en">

articles/api-management/graphql-apis-overview.md

@@ -21,7 +21,7 @@ API Management helps you import, manage, protect, test, publish, and monitor Gra
 
 |Pass-through GraphQL   |Synthetic GraphQL  |
 |---------|---------|
-| ▪️ Pass-through API to existing GraphQL service endpoint<br><br/>▪️ Support for GraphQL queries, mutations, and subscriptions  |   ▪️ API based on a custom GraphQL schema<br></br>▪️ Support for GraphQL queries, mutations, and subscriptions<br/><br/>▪️  Configure custom resolvers, for example, to HTTP data sources<br/><br/>▪️ Develop GraphQL schemas and GraphQL-based clients while consuming data from legacy APIs     |
+| ▪️ Pass-through API to existing GraphQL service endpoint<br><br/>▪️ Support for GraphQL queries, mutations, and subscriptions  |   ▪️ API based on a custom GraphQL schema<br></br>▪️ Support for GraphQL queries, mutations, and subscriptions<br/><br/>▪️  Configure custom resolvers, for example, to HTTP data sources<br/><br/>▪️ Develop GraphQL schemas and GraphQL-based clients while consuming data from legacy APIs<br/><br/>▪️ Synthetic subscriptions do not require resolvers. See [publish-event](publish-event-policy.md) policy.    |
 
 ## Availability
 

articles/api-management/publish-event-policy.md

@@ -53,6 +53,7 @@ The `publish-event` policy publishes an event to one or more subscriptions speci
 ### Usage notes
 
 * This policy is invoked only when a related GraphQL query or mutation is executed.
+* Resolver *should not* be defined for the corresponding subscription. Defining a `publish-event` policy on a source query or mutation is sufficient to trigger subscription events.
 
 ## Example
 

articles/app-service/app-service-configure-premium-tier.md

@@ -4,27 +4,32 @@ description: Learn how to better performance for your web, mobile, and API app i
 keywords: app service, azure app service, scale, scalable, app service plan, app service cost
 ms.assetid: ff00902b-9858-4bee-ab95-d3406018c688
 ms.topic: article
-ms.date: 08/29/2023
+ms.date: 02/21/2025
 ms.author: msangapu
 author: msangapu-msft
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
+#customer intent: As a deployment engineer, I want to understand the process and the benefits of scaling up apps to the Premium V3 pricing tier in Azure App Service.
 ---
 
 # Configure Premium V3 tier for Azure App Service
 
-The new Premium V3 pricing tier gives you faster processors, SSD storage, memory-optimized options, and quadruple the memory-to-core ratio of the existing pricing tiers (double the Premium V2 tier). With the performance advantage, you could save money by running your apps on fewer instances. In this article, you learn how to create an app in Premium V3 tier or scale up an app to Premium V3 tier.
+The new Premium V3 pricing tier gives you faster processors, SSD storage, and memory-optimized options. It offers to quadruple the memory-to-core ratio of the existing pricing tiers. The memory-to-core ratio is double the Premium V2 tier. With the performance advantage, you could save money by running your apps on fewer instances. In this article, you learn how to create an app in Premium V3 tier or scale up an app to Premium V3 tier.
 
 ## Prerequisites
 
-To scale-up an app to Premium V3, you need to have an Azure App Service app that runs in a pricing tier lower than Premium V3, and the app must be running in an App Service deployment that supports Premium V3. Additionally the App Service deployment must support the desired SKU within Premium V3.
+To scale-up an app to Premium V3:
+
+- An Azure App Service app that runs in a pricing tier lower than Premium V3.
+- The app must run in an App Service deployment that supports Premium V3.
+- The App Service deployment must support the desired SKU in Premium V3.
 
 <a name="availability"></a>
 
 ## Premium V3 availability
 
 The Premium V3 tier is available for both native and custom containers, including both Windows containers and Linux containers.
 
-Premium V3 as well as specific Premium V3 SKUs are available in some Azure regions and availability in additional regions is being added continually. To see if a specific PremiumV3 offering is available in your region, run the following Azure CLI command in the [Azure Cloud Shell](../cloud-shell/overview.md) (substitute _P1v3_ with the desired SKU):
+Premium V3 and specific Premium V3 SKUs are available in some Azure regions. Microsoft is adding availability in other regions continually. To see if a specific PremiumV3 offering is available in your region, run the following Azure CLI command in the [Azure Cloud Shell](../cloud-shell/overview.md). Substitute *P1v3* with the desired SKU:
 
 **Windows** SKU availability
 
@@ -43,61 +48,62 @@ az appservice list-locations --linux-workers-enabled --sku P1V3
 
 The pricing tier of an App Service app is defined in the [App Service plan](overview-hosting-plans.md) that it runs on. You can create an App Service plan by itself or create it as part of app creation.
 
-When configuring the new App Service plan in the <a href="https://portal.azure.com" target="_blank">Azure portal</a>, select **Pricing plan** and pick one of the **Premium V3** tiers.
+When you configure the new App Service plan in the <a href="https://portal.azure.com" target="_blank">Azure portal</a>, select **Pricing plan** and choose one of the **Premium V3** tiers.
 
 To see all the Premium V3 options, select **Explore pricing plans**, then select one of the Premium V3 plans and select **Select**.
 
 :::image type="content" source="media/app-service-configure-premium-tier/explore-pricing-plans.png" alt-text="Screenshot showing the Explore pricing plans page with a Premium V3 plan selected.":::
 
-> [!IMPORTANT] 
-> If you don't see **P0V3**, **P1V3**, **P2V3**, **P3V3**, **P1mV3**, **P2mV3**, **P3mV3**, **P4mV3**, and **P5mV3** as options, or if some options are greyed out, then either **Premium V3** or an individual SKU within **Premium V3** isn't available in the underlying App Service deployment that contains the App Service plan. See [Scale up from an unsupported resource group and region combination](#unsupported) for more details.
->
+> [!IMPORTANT]
+> You might not see **P0V3**, **P1V3**, **P2V3**, **P3V3**, **P1mV3**, **P2mV3**, **P3mV3**, **P4mV3**, and **P5mV3** as options or some options might be grayed out. If so, either **Premium V3** or an individual SKU in **Premium V3** isn't available in the underlying App Service deployment. For more information, see [Scale up from an unsupported resource group and region combination](#unsupported).
 
 ## Scale up an existing app to Premium V3 tier
 
-Before scaling an existing app to Premium V3 tier, make sure that both Premium V3 as well as the specific SKU within Premium V3 are available. For information, see [PremiumV3 availability](#availability). If it's not available, see [Scale up from an unsupported resource group and region combination](#unsupported).
+Before you scale an existing app to Premium V3 tier, make sure that both Premium V3 and the specific SKU in Premium V3 are available. For more information, see [PremiumV3 availability](#availability). If it's not available, see [Scale up from an unsupported resource group and region combination](#unsupported).
 
-Depending on your hosting environment, scaling up may require extra steps. 
+Depending on your hosting environment, scaling up can require extra steps.
 
-In the <a href="https://portal.azure.com" target="_blank">Azure portal</a>, open your App Service app page.
+1. In the <a href="https://portal.azure.com" target="_blank">Azure portal</a>, open your App Service app page.
 
-In the left navigation of your App Service app page, select **Scale up (App Service plan)**.
+1. In the left navigation of your App Service app page, select **Settings** > **Scale up (App Service plan)**.
 
-![Screenshot showing how to scale up your app service plan.](media/app-service-configure-premium-tier/scale-up-tier-portal.png)
+   :::image type="content" source="media/app-service-configure-premium-tier/scale-up-tier-portal.png" alt-text="Screenshot showing how to scale up your app service plan.":::
 
-Select one of the Premium V3 plans and select **Select**.
+1. Select one of the Premium V3 plans and select **Select**.
 
-:::image type="content" source="media/app-service-configure-premium-tier/explore-pricing-plans.png" alt-text="Screenshot showing the Explore pricing plans page with a Premium V3 plan selected.":::
+   :::image type="content" source="media/app-service-configure-premium-tier/explore-pricing-plans.png" alt-text="Screenshot showing the Explore pricing plans page with a Premium V3 plan selected.":::
 
-If your operation finishes successfully, your app's overview page shows that it's now in a Premium V3 tier.
+   If your operation finishes successfully, your app's overview page shows that it's now in a Premium V3 tier.
 
-![Screenshot showing the Premium V3 pricing tier on your app's overview page.](media/app-service-configure-premium-tier/finished.png)
+   :::image type="content" source="media/app-service-configure-premium-tier/finished.png" alt-text="Screenshot showing the Premium V3 pricing tier on your app's overview page.":::
 
 ### If you get an error
 
-Some App Service plans can't scale up to the Premium V3 tier, or to a newer SKU within Premium V3, if the underlying App Service deployment doesn’t support the requested Premium V3 SKU. See [Scale up from an unsupported resource group and region combination](#unsupported) for more details.
+If the underlying App Service deployment doesn't support the requested Premium V3 SKU, some App Service plans can't scale up to the Premium V3 tier, or to a newer SKU in Premium V3. For more information, see [Scale up from an unsupported resource group and region combination](#unsupported).
 
 <a name="unsupported"></a>
 
 ## Scale up from an unsupported resource group and region combination
 
-If your app runs in an App Service deployment where Premium V3 isn't available, or if your app runs in a region that currently does not support Premium V3, you need to re-deploy your app to take advantage of Premium V3. Alternatively newer Premium V3 SKUs may not be available, in which case you also need to re-deploy your app to take advantage of newer SKUs within Premium V3. You have two options:
+If your app runs in an App Service deployment where Premium V3 isn't available or in a region that doesn't support Premium V3, redeploy your app to take advantage of Premium V3. If newer Premium V3 SKUs aren't available, you also need to redeploy your app to use newer SKUs in Premium V3. You have two options:
+
+- Create an app in a new resource group and with a new App Service plan.
 
-- Create an app in a new resource group and with a new App Service plan. When creating the App Service plan, select the desired Premium V3 tier. This step ensures that the App Service plan is deployed into a deployment unit that supports Premium V3 as well as the specific SKU within Premium V3. Then, redeploy your application code into the newly created app. Even if you scale the new App Service plan down to a lower tier to save costs, you can always scale back up to Premium V3 and the desired SKU within Premium V3 because the deployment unit supports it.
+  When creating the App Service plan, select the desired Premium V3 tier. This step ensures that the App Service plan is deployed into a deployment unit that supports Premium V3 and the specific SKU in Premium V3. Then, redeploy your application code into the newly created app. Even if you scale the new App Service plan down to a lower tier to save costs, you can always scale up again to Premium V3 and the desired SKU in Premium V3 because the deployment unit supports it.
 
-    ![Screenshot showing how to clone your app.](media/app-service-configure-premium-tier/clone-app.png)
+- In the **Development tools** > **Clone app** page, you can create an App Service plan using Premium V3 in the region you want, and specify the app settings and configuration that you want to clone.
+
+  :::image type="content" source="media/app-service-configure-premium-tier/clone-app.png" alt-text="Screenshot showing how to clone your app.":::
 
-    In the **Clone app** page, you can create an App Service plan using Premium V3 in the region you want, and specify the app settings and configuration that you want to clone.
- 
 ## Automate with scripts
 
 You can automate app creation in the Premium V3 tier with scripts, using the [Azure CLI](/cli/azure/install-azure-cli) or [Azure PowerShell](/powershell/azure/).
 
 ### Azure CLI
 
-The following command creates an App Service plan in _P1V3_. You can run it in the Cloud Shell. The options for `--sku` are _P0V3_, _P1V3_, _P2V3_, _P3V3_, _P1mV3_, _P2mV3_, _P3mV3_, _P4mV3_, and _P5mV3_.
+The following command creates an App Service plan in *P1V3*. You can run it in the Cloud Shell. The options for `--sku` are *P0V3*, *P1V3*, *P2V3*, *P3V3*, *P1mV3*, *P2mV3*, *P3mV3*, *P4mV3*, and *P5mV3*.
 
-```azurecli-interactive
+```azurecli
 az appservice plan create \
     --resource-group <resource_group_name> \
     --name <app_service_plan_name> \
@@ -108,7 +114,7 @@ az appservice plan create \
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
-The following command creates an App Service plan in _P1V3_. The options for `-WorkerSize` are _Small_, _Medium_, and _Large_.
+The following command creates an App Service plan in _P1V3_. The options for `-WorkerSize` are *Small*, *Medium*, and *Large*.
 
 ```powershell
 New-AzAppServicePlan -ResourceGroupName <resource_group_name> `
@@ -118,8 +124,8 @@ New-AzAppServicePlan -ResourceGroupName <resource_group_name> `
     -WorkerSize "Small"
 ```
 
-## More resources
+## Related content
 
-* [Scale up an app in Azure](manage-scale-up.md)
-* [Scale instance count manually or automatically](/azure/azure-monitor/autoscale/autoscale-get-started)
-* [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
+- [Scale up an app in Azure App Service](manage-scale-up.md)
+- [Get started with autoscale in Azure](/azure/azure-monitor/autoscale/autoscale-get-started)
+- [Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)