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

Author: gitName

articles/api-management/v2-service-tiers-overview.md

@@ -72,6 +72,7 @@ The following API Management capabilities are currently unavailable in the v2 ti
 
 **Infrastructure and networking**
 * Multi-region deployment 
+* Availability zone support
 * Multiple custom domain names 
 * Capacity metric - *replaced by CPU Percentage of Gateway and Memory Percentage of Gateway metrics*
 * Built-in analytics - *replaced by Azure Monitor-based dashboard*

articles/application-gateway/ssl-overview.md

@@ -123,6 +123,9 @@ The following tables outline the differences in SNI between the v1 and v2 SKU in
 | If the client doesn't specify a SNI header and if all the multi-site headers are enabled with "Require SNI" | Resets the connection | Returns the certificate of the first HTTPS listener according to the order specified by the request routing rules associated with the HTTPS listeners
 | If the client doesn't specify SNI header and if there's a basic listener configured with a certificate | Returns the certificate configured in the basic listener to the client (default or fallback certificate) | Returns the certificate configured in the basic listener |
 
+> [!NOTE]
+> When the client does not specify an SNI header, it is recommended that the user add a basic listener and rule to present a default SSL/TLS certificate.
+
 > [!TIP]
 > The SNI flag can be configured with PowerShell or by using an ARM template. For more information, see [RequireServerNameIndication](/powershell/module/az.network/set-azapplicationgatewayhttplistener#-requireservernameindication) and [Quickstart: Direct web traffic with Azure Application Gateway - ARM template](quick-create-template.md#review-the-template).
 

articles/azure-cache-for-redis/TOC.yml

@@ -444,7 +444,7 @@
         - name: Azure CLI
           href: /cli/azure/redisenterprise
         - name: REST
-          href: /rest/api/redis/redisenterprisecache
+          href: /rest/api/redis/redisenterprisecache/operation-groups
         - name: Resource Manager template
           href: /azure/templates/microsoft.cache/redisenterprise
     - name: Azure Cache for Redis

articles/azure-edge-hardware-center/media/azure-edge-hardware-center-manage-order/cancel-order-2.png

@@ -30,7 +30,7 @@ The following table summarizes the configuration options available for each stac
 |-|-|
 | .NET (in-process model) | `host.json` |
 | .NET (isolated model) | Default (send custom logs to the Functions host): `host.json`<br/>To send logs directly to Application Insights, see: [Configure Application Insights in the HostBuilder](./dotnet-isolated-process-guide.md#application-insights)  |
-| Node.JS | `host.json` |
+| Node.js | `host.json` |
 | Python | `host.json` |
 | Java | Default (send custom logs to the Functions host): `host.json`<br/>To send logs directly to Application Insights, see: [Configure the Application Insights Java agent](/azure/azure-monitor/app/monitor-functions#distributed-tracing-for-java-applications) |
 | PowerShell | `host.json` |

articles/azure-edge-hardware-center/media/azure-edge-hardware-center-manage-order/cancel-order-3.png

@@ -23,7 +23,7 @@ There are several options for hosting your containerized function apps in Azure:
 
 | Hosting option | Benefits |
 | --- | --- |  
-| **[Azure Container Apps]** | Azure Functions provides integrated support for developing, deploying, and managing containerized function apps on [Azure Container Apps](../container-apps/overview.md). This enables you to manage your apps using the same Functions tools and pages in the Azure portal. Use Azure Container Apps to host your function app containers when you need to run your event-driven functions in Azure in the same environment as other microservices, APIs, websites, workflows, or any container hosted programs. Container Apps hosting lets you run your functions in a managed Kubernetes-based environment with built-in support for open-source monitoring, mTLS, Dapr, and KEDA. Supports scale-to-zero and provides a servless pay-for-what-you-use hosting model. You can also request dedicated hardware, even GPUs, by using workload profiles. _Recommended hosting option for running containerized function apps on Azure._ | 
+| **[Azure Container Apps]** | Azure Functions provides integrated support for developing, deploying, and managing containerized function apps on [Azure Container Apps](../container-apps/overview.md). This enables you to manage your apps using the same Functions tools and pages in the Azure portal. Use Azure Container Apps to host your function app containers when you need to run your event-driven functions in Azure in the same environment as other microservices, APIs, websites, workflows, or any container hosted programs. Container Apps hosting lets you run your functions in a managed Kubernetes-based environment with built-in support for open-source monitoring, mTLS, Dapr, and KEDA. Supports scale-to-zero and provides a serverless pay-for-what-you-use hosting model. You can also request dedicated hardware, even GPUs, by using workload profiles. _Recommended hosting option for running containerized function apps on Azure._ | 
 | **Azure Arc-enabled Kubernetes clusters (preview)** | You can host your function apps on Azure Arc-enabled Kubernetes clusters as either a [code-only deployment](./create-first-function-arc-cli.md) or in a [custom Linux container](./create-first-function-arc-custom-container.md). Azure Arc lets you attach Kubernetes clusters so that you can manage and configure them in Azure. _Hosting Azure Functions containers on Azure Arc-enabled Kubernetes clusters is currently in preview._ |
 | **[Azure Functions]** | You can host your containerized function apps in Azure Functions by running the container in either an [Elastic Premium plan](./functions-premium-plan.md) or a [Dedicated plan](./dedicated-plan.md). Premium plan hosting provides you with the benefits of dynamic scaling. You might want to use Dedicated plan hosting to take advantage of existing unused App Service plan resources. |  
 | **[Kubernetes]** | Because the Azure Functions runtime provides flexibility in hosting where and how you want, you can host and manage your function app containers directly in Kubernetes clusters. [KEDA](https://keda.sh) (Kubernetes-based Event Driven Autoscaling) pairs seamlessly with the Azure Functions runtime and tooling to provide event driven scale in Kubernetes. Just keep in mind that running your containerized function apps on Kubernetes, either by using KEDA or by direct deployment, is an open-source effort that you can use free of cost, with best-effort support provided by contributors and from the community. You're responsible for maintaining your own function app containers in a cluster, even when deploying to Azure Kubernetes Service (AKS). |
@@ -44,7 +44,7 @@ The degree to which various features and behaviors of Azure Functions are suppor
 | [Revisions](../container-apps/revisions.md) | No | Yes |No |No |No |
 | [Deployment slots](./functions-deployment-slots.md) |No |No |Yes |Yes |No |
 | [Streaming logs](./streaming-logs.md) | Yes | [Yes](../container-apps/log-streaming.md) | Yes | Yes | No |
-| [Console access](../container-apps/container-console.md) | Not currently available<sup>4</sup> | Yes | Yes (using [Kudu](./functions-how-to-custom-container.md#enable-ssh-connections)) | Yes (using [Kudu](./functions-how-to-custom-container.md#enable-ssh-connections)) | Yes (in pods [using `kubctl`](https://kubernetes.io/docs/reference/kubectl/)) |
+| [Console access](../container-apps/container-console.md) | Not currently available<sup>4</sup> | Yes | Yes (using [Kudu](./functions-how-to-custom-container.md#enable-ssh-connections)) | Yes (using [Kudu](./functions-how-to-custom-container.md#enable-ssh-connections)) | Yes (in pods [using `kubectl`](https://kubernetes.io/docs/reference/kubectl/)) |
 | Cold start mitigation | Minimum replicas | [Scale rules](../container-apps/scale-app.md#scale-rules) | [Always-ready/pre-warmed instances](functions-premium-plan.md#eliminate-cold-starts) | n/a | n/a |
 | [App Service authentication](../app-service/overview-authentication-authorization.md) | Not currently available<sup>4</sup> | Yes | Yes | Yes | No |
 | [Custom domain names](../app-service/app-service-web-tutorial-custom-domain.md) | Not currently available<sup>4</sup> | Yes | Yes | Yes | No |

articles/azure-functions/configure-monitoring.md

@@ -30,7 +30,7 @@ You pay for function apps in an App Service Plan as you would for other App Serv
 When you run your app on an App Service plan, you should enable the **Always on** setting so that your function app runs correctly. On an App Service plan, the Functions runtime goes idle after a few minutes of inactivity. The **Always on** setting is available only on an App Service plan. In other plans, the platform activates function apps automatically. If you choose not to enable **Always on**, you can reactivate an idled app in these ways:
 
 + Send a request to an HTTP trigger endpoint or any other endpoint on the app. Even a failed request should wake up your app. 
-+ Acccess your app in the [Azure portal](https://portal.azure.com). 
++ Access your app in the [Azure portal](https://portal.azure.com). 
 
 Even with **Always on** enabled, the execution timeout for individual functions is controlled by the `functionTimeout` setting in the [host.json](functions-host-json.md#functiontimeout) project file.
 

articles/azure-functions/container-concepts.md

@@ -61,7 +61,7 @@ public class MyActivity : TaskActivity<string, string>
 {
     private readonly ILogger logger;
 
-    public MyActivity(ILogger<MyActivity> logger) // activites have access to DI.
+    public MyActivity(ILogger<MyActivity> logger) // activities have access to DI.
     {
         this.logger = logger;
     }

articles/azure-functions/dedicated-plan.md

@@ -451,10 +451,10 @@ public static async Task<HttpResponseData> Run(
 
     if (entity is null)
     {
-        return request.CreateResponse(HttpStatusCode.NotFound);
+        return req.CreateResponse(HttpStatusCode.NotFound);
     }
 
-    HttpResponseData response = request.CreateResponse(HttpStatusCode.OK);
+    HttpResponseData response = req.CreateResponse(HttpStatusCode.OK);
     await response.WriteAsJsonAsync(entity);
 
     return response;