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

Author: pauljewellmsft

articles/api-management/api-management-gateways-overview.md

@@ -147,12 +147,11 @@ For details about monitoring options, see [Observability in Azure API Management
 | [OpenTelemetry Collector](how-to-deploy-self-hosted-gateway-kubernetes-opentelemetry.md) |  ❌ | ❌ | ❌ | ✔️ | ❌ |
 | [Request logs in Azure Monitor and Log Analytics](api-management-howto-use-azure-monitor.md#resource-logs) | ✔️ | ✔️ | ❌ | ❌<sup>3</sup> | ❌ |
 | [Local metrics and logs](how-to-configure-local-metrics-logs.md) |  ❌ | ❌ | ❌ | ✔️ | ❌ |  
-| [Request tracing](api-management-howto-api-inspector.md) | ✔️ | ❌<sup>4</sup> | ✔️ | ✔️ | ❌ |
+| [Request tracing](api-management-howto-api-inspector.md) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
 
 <sup>1</sup> The v2 tiers support Azure Monitor-based analytics.<br/>
 <sup>2</sup> Gateway uses [Azure Application Insight's built-in memory buffer](/azure/azure-monitor/app/telemetry-channels#built-in-telemetry-channels) and does not provide delivery guarantees.<br/>
 <sup>3</sup> The self-hosted gateway currently doesn't send resource logs (diagnostic logs) to Azure Monitor. Optionally [send metrics](how-to-configure-cloud-metrics-logs.md) to Azure Monitor, or [configure and persist logs locally](how-to-configure-local-metrics-logs.md) where the self-hosted gateway is deployed.<br/>
-<sup>4</sup> Tracing is currently unavailable in the v2 tiers.
 
 ### Authentication and authorization
 

articles/api-management/workspaces-overview.md

@@ -116,7 +116,7 @@ The following constraints currently apply to workspace gateways:
 * Workspace gateways don't support the API Management service's credential manager
 * Workspace gateways support only internal cache; external cache isn't supported 
 * Workspace gateways don't support synthetic GraphQL APIs and WebSocket APIs
-* Workspace gateways don't support APIs created from Azure resources such as Azure OpenAI Service, App Service, Function Apps, and so on
+* Workspace gateways don't support creating APIs directly from Azure resources such as Azure OpenAI Service, App Service, Function Apps, and so on
 * Request metrics can't be split by workspace in Azure Monitor; all workspace metrics are aggregated at the service level
 * Azure Monitor logs are aggregated at the service level; workspace-level logs aren't available
 * Workspace gateways don't support CA certificates

articles/application-gateway/overview-v2.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: overview
-ms.date: 09/06/2024
+ms.date: 10/02/2024
 ms.author: greglin
 ms.custom: references_regions, devx-track-azurepowershell
 ---
@@ -52,7 +52,7 @@ The following table displays a comparison between Basic and Standard_v2.
 |     :---:                | :---                                     |     :---:      |     :---:         |
 | Reliability              | SLA                                      | 99.9           | 99.95             |
 | Functionality - basic    | HTTP/HTTP2/HTTPS<br>Websocket<br>Public/Private IP<br>Cookie Affinity<br>Path-based affinity<br>Wildcard<br>Multisite<br>KeyVault<br>Zone<br>Header rewrite | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713; | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;|
-| Functionality - advanced | AKS (via AGIC)<br>URL rewrite<br>mTLS<br>Private Link<br>Private-only<sup>1</sup><br>TCP/TLS Proxy |  | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713; |
+| Functionality - advanced | AKS (via AGIC)<br>URL rewrite<br>mTLS<br>Private Link<br>Private-only (preview)<br>TCP/TLS Proxy (preview) |  | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713; |
 | Scale                    | Max. connections per second<br>Number of listeners<br>Number of backend pools<br>Number of backend servers per pool<br>Number of rules | 200<sup>1</sup><br>5<br>5<br>5<br>5  | 62500<sup>1</sup><br>100<br>100<br>1200<br>400 |
 | Capacity Unit            | Connections per second per compute unit<br>Throughput<br>Persistent new connections  | 10<br>2.22 Mbps<br>2500 | 50<br>2.22 Mbps<br>2500 |
 

articles/azure-cache-for-redis/cache-azure-active-directory-for-authentication.md

@@ -63,9 +63,12 @@ Using Microsoft Entra is the secure way to connect your cache. We recommend that
 
 When you disable access key authentication for a cache, all existing client connections are terminated, whether they use access keys or Microsoft Entra authentication. Follow the recommended Redis client best practices to implement proper retry mechanisms for reconnecting Microsoft Entra-based connections, if any.
 
-Before you disable access keys:
+### Before you disable access keys:
 
-- Microsoft Entra authorization must be enabled.
+- Ensure that Microsoft Entra authentication is enabled and you have at least one Redis User configured.
+- Ensure all applications connecting to your cache instance switch to using Microsoft Entra Authentication.
+- Ensure that the metrics _Connected Clients_ and _Connected Clients Using Microsoft Entra Token_ have the same values. If the values for these two metrics are not the same, that means there are still some connections that were created using access keys and not Entra Token.
+- Consider disabling access during the scheduled maintenance window for your cache instance.
 - Disabling access keys is only available for Basic, Standard, and Premium tier caches.
 - For geo-replicated caches, you must:
 

articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0011.md

@@ -9,7 +9,7 @@ ms.date: 01/24/2024
 
 # AZFD0011: The FUNCTIONS_WORKER_RUNTIME setting is required
 
-This event occurs when a function app doesn't have the `FUNCTIONS_WORKER_RUNTIME` application setting, which is required.
+This event occurs when a function app doesn't have a value for the `FUNCTIONS_WORKER_RUNTIME` application setting, which is required.
 
 | | Value |
 |-|-|
@@ -18,18 +18,20 @@ This event occurs when a function app doesn't have the `FUNCTIONS_WORKER_RUNTIME
 
 ## Event description
 
-The `FUNCTIONS_WORKER_RUNTIME` application setting indicates the language or language stack on which the function app runs, such as `python`. For more information on valid values, see the [`FUNCTIONS_WORKER_RUNTIME`](../../functions-app-settings.md#functions_worker_runtime) reference.
+The `FUNCTIONS_WORKER_RUNTIME` application setting indicates the language or language stack on which the function app runs, such as `python`. For more information on valid values, see the [`FUNCTIONS_WORKER_RUNTIME`][fwr] reference.
 
-While not currently required, you should always specify `FUNCTIONS_WORKER_RUNTIME` for your function apps. When you don't have this setting and the Functions host can't determine the correct language or language stack, you might see exceptions or unexpected behaviors. 
+You should always specify a valid `FUNCTIONS_WORKER_RUNTIME` for your function apps. When you don't have this setting and the Functions host can't determine the correct language or language stack, you might see performance degradations, exceptions, or unexpected behaviors. To ensure that your application operates as intended, you should explicitly set it in all of your existing function apps and deployment scripts.
 
-Because `FUNCTIONS_WORKER_RUNTIME` is likely to become a required setting, you should explicitly set it in all of your existing function apps and deployment scripts to prevent any downtime in the future.
+The value of `FUNCTIONS_WORKER_RUNTIME` should align with the language stack used to create the deployed application payload. If these do not align, you may see the [`AZFD0013`](./azfd0013.md) event.
 
 ## How to resolve the event
 
-In a production application, add `FUNCTIONS_WORKER_RUNTIME` to the [application settings](../../functions-how-to-use-azure-function-app-settings.md#settings).
+In a production application, set [`FUNCTIONS_WORKER_RUNTIME` to a valid value][fwr] in the [application settings](../../functions-how-to-use-azure-function-app-settings.md#settings). The value should align with the language stack used to create the application payload.
 
-When running locally in Azure Functions Core Tools, also add `FUNCTIONS_WORKER_RUNTIME` to the [local.settings.json file](../../functions-develop-local.md#local-settings-file).
+When running locally in Azure Functions Core Tools, also set [`FUNCTIONS_WORKER_RUNTIME` to a valid value][fwr] in the [local.settings.json file](../../functions-develop-local.md#local-settings-file). The value should align with the language stack used in the local project.
 
 ## When to suppress the event
 
 This event shouldn't be suppressed.
+
+[fwr]: ../../functions-app-settings.md#functions_worker_runtime

articles/azure-functions/flex-consumption-plan.md

@@ -145,6 +145,7 @@ Keep these other considerations in mind when using Flex Consumption plan during
 + **Scale**: The lowest maximum scale in preview is `40`. The highest currently supported value is `1000`. 
 + **Managed dependencies**: [Managed dependencies in PowerShell](functions-reference-powershell.md#dependency-management) aren't supported by Flex Consumption. You must instead [define your own custom modules](functions-reference-powershell.md#custom-modules).
 + **Diagnostic settings**: Diagnostic settings are not currently supported.
++ **Certificates**: Loading certificates with the WEBSITE_LOAD_CERTIFICATES app setting is currently not supported.
 
 ## Related articles 
 

articles/azure-government/compliance/azure-services-in-fedramp-auditscope.md

@@ -30,7 +30,7 @@ Microsoft Azure cloud environments meet demanding US government compliance requi
 - [DoD IL4](/azure/compliance/offerings/offering-dod-il4) PA issued by DISA
 - [DoD IL5](/azure/compliance/offerings/offering-dod-il5) PA issued by DISA
 
-For current Azure Government regions and available services, see [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=all&regions=non-regional,usgov-non-regional,us-dod-central,us-dod-east,usgov-arizona,usgov-texas,usgov-virginia&rar=true).
+For current Azure Government regions and available services, see [Products available by region](https://go.microsoft.com/fwlink/?linkid=2274941&clcid=0x409).
 
 > [!NOTE]
 >

articles/communication-services/concepts/voice-video-calling/calling-sdk-features.md

@@ -119,7 +119,7 @@ The following table represents the set of supported browsers, which are currentl
 | Platform     | Chrome | Safari | Edge  | Firefox |  Webview |  Electron |
 | ------------ | ------ | ------ | ------ | ------- | ------- |  ------- |
 | Android      | ✔️      | ❌      | ✔️           | ❌      | ✔️     | ❌      |
-| iOS          | ✔️      | ✔️      | ❌           | ❌      | ✔️      | ❌      |
+| iOS          | ✔️      | ✔️      | ✔️           | ❌      | ✔️      | ❌      |
 | macOS        | ✔️      | ✔️      | ✔️           | ✔️      | ❌      | ✔️     |
 | Windows      | ✔️      | ❌      | ✔️           | ✔️      | ❌      | ✔️     |
 | Ubuntu/Linux | ✔️      | ❌      | ❌           | ❌      | ❌      | ❌     |
@@ -128,6 +128,7 @@ The following table represents the set of supported browsers, which are currentl
 - Firefox support is in public preview.
 - Currently, the calling SDK only supports Android System WebView on Android, iOS WebView(WKWebView) in public preview. Other types of embedded browsers or WebView on other OS platforms aren't officially supported, for example, GeckoView, Chromium Embedded Framework (CEF), Microsoft Edge WebView2. Running JavaScript Calling SDK on these platforms isn't actively tested, it might or might not work.
 - [An iOS app on Safari can't enumerate/select mic and speaker devices](../known-issues.md#enumerating-devices-isnt-possible-in-safari-when-the-application-runs-on-ios-or-ipados) (for example, Bluetooth). This issue is a limitation of iOS, and the operating system controls default device selection.
+- iOS Edge browser support is available in public preview in WebJS SDK version [1.30.1-beta.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1301-beta1-2024-10-01) and higher.
 
 ## Calling client - browser security model
 

articles/communication-services/quickstarts/voice-video-calling/get-started-teams-auto-attendant.md

@@ -8,47 +8,27 @@ ms.date: 07/14/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
 ms.subservice: calling
+zone_pivot_groups: acs-plat-web-ios-android-windows
 ms.custom: mode-other, devx-track-js
 ---
 
 # Quickstart: Join your calling app to a Teams Auto Attendant
 
-In this quickstart you are going to learn how to start a call from Azure Communication Services user to Teams Auto Attendant. You are going to achieve it with the following steps:
-
-1. Enable federation of Azure Communication Services resource with Teams Tenant.
-2. Select or create Teams Auto Attendant via Teams Admin Center.
-3. Get email address of Auto Attendant via Teams Admin Center.
-4. Get Object ID of the Auto Attendant via Graph API.
-5. Start a call with Azure Communication Services Calling SDK.
-
-If you'd like to skip ahead to the end, you can download this quickstart as a sample on [GitHub](https://github.com/Azure-Samples/communication-services-javascript-quickstarts/tree/main/voice-apps-calling).
-
-[!INCLUDE [Enable interoperability in your Teams tenant](../../concepts/includes/enable-interoperability-for-teams-tenant.md)]
-
-## Create or select Teams Auto Attendant
-
-Teams Auto Attendant is system that provides an automated call handling system for incoming calls. It serves as a virtual receptionist, allowing callers to be automatically routed to the appropriate person or department without the need for a human operator. You can select existing or create new Auto Attendant via [Teams Admin Center](https://aka.ms/teamsadmincenter).
-
-Learn more about how to create Auto Attendant using Teams Admin Center [here](/microsoftteams/create-a-phone-system-auto-attendant?tabs=general-info).
-
-## Find Object ID for Auto Attendant
-
-After Auto Attendant is created, we need to find correlated Object ID to use it later for calls. Object ID is connected to Resource Account that was attached to Auto Attendant - open [Resource Accounts tab](https://admin.teams.microsoft.com/company-wide-settings/resource-accounts) in Teams Admin and find email of account.
-:::image type="content" source="../media/teams-call-queue-resource-account.PNG" alt-text="Screenshot of Resource Accounts in Teams Admin Portal.":::
-All required information for Resource Account can be found in [Microsoft Graph Explorer](https://developer.microsoft.com/en-us/graph/graph-explorer) using this email in the search.
-
-```console
-https://graph.microsoft.com/v1.0/users/[email protected]
-```
+::: zone pivot="platform-web"
+[!INCLUDE [Auto Attendant with JavaScript](./includes/teams-auto-attendant/teams-auto-attendant-javascript.md)]
+::: zone-end
 
-In results we'll are able to find "ID" field
+::: zone pivot="platform-android"
+[!INCLUDE [Auto Attendant with Android](./includes/teams-auto-attendant/teams-auto-attendant-android.md)]
+::: zone-end
 
-```json
-    "userPrincipalName": "[email protected]",
-    "id": "31a011c2-2672-4dd0-b6f9-9334ef4999db"
-```
+::: zone pivot="platform-ios"
+[!INCLUDE [Auto Attendant with iOS](./includes/teams-auto-attendant/teams-auto-attendant-ios.md)]
+::: zone-end
 
-[!INCLUDE [Auto Attendant with JavaScript](./includes/teams-auto-attendant/teams-auto-attendant-javascript.md)]
+::: zone pivot="platform-windows"
+[!INCLUDE [Auto Attendant with Windows](./includes/teams-auto-attendant/teams-auto-attendant-windows.md)]
+::: zone-end
 
 ## Clean up resources
 

articles/communication-services/quickstarts/voice-video-calling/get-started-teams-call-queue.md

@@ -8,47 +8,27 @@ ms.date: 07/14/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
 ms.subservice: calling
+zone_pivot_groups: acs-plat-web-ios-android-windows
 ms.custom: mode-other, devx-track-js
 ---
 
 # Quickstart: Join your calling app to a Teams call queue
 
-In this quickstart you are going to learn how to start a call from Azure Communication Services user to Teams Call Queue. You are going to achieve it with the following steps:
+::: zone pivot="platform-web"
+[!INCLUDE [Auto Attendant with JavaScript](./includes/teams-call-queue/teams-call-queue-javascript.md)]
+::: zone-end
 
-1. Enable federation of Azure Communication Services resource with Teams Tenant.
-2. Select or create Teams Call Queue via Teams Admin Center.
-3. Get email address of Call Queue via Teams Admin Center.
-4. Get Object ID of the Call Queue via Graph API.
-5. Start a call with Azure Communication Services Calling SDK.
+::: zone pivot="platform-android"
+[!INCLUDE [Auto Attendant with Android](./includes/teams-call-queue/teams-call-queue-android.md)]
+::: zone-end
 
-If you'd like to skip ahead to the end, you can download this quickstart as a sample on [GitHub](https://github.com/Azure-Samples/communication-services-javascript-quickstarts/tree/main/voice-apps-calling).
+::: zone pivot="platform-ios"
+[!INCLUDE [Auto Attendant with iOS](./includes/teams-call-queue/teams-call-queue-ios.md)]
+::: zone-end
 
-[!INCLUDE [Enable interoperability in your Teams tenant](../../concepts/includes/enable-interoperability-for-teams-tenant.md)]
-
-## Create or select Teams Call Queue
-
-Teams Call Queue is a feature in Microsoft Teams that efficiently distributes incoming calls among a group of designated users or agents. It's useful for customer support or call center scenarios. Calls are placed in a queue and assigned to the next available agent based on a predetermined routing method. Agents receive notifications and can handle calls using Teams' call controls. The feature offers reporting and analytics for performance tracking. It simplifies call handling, ensures a consistent customer experience, and optimizes agent productivity. You can select existing or create new Call Queue via [Teams Admin Center](https://aka.ms/teamsadmincenter).
-
-Learn more about how to create Call Queue using Teams Admin Center [here](/microsoftteams/create-a-phone-system-call-queue?tabs=general-info).
-
-## Find Object ID for Call Queue
-
-After Call queue is created, we need to find correlated Object ID to use it later for calls. Object ID is connected to Resource Account that was attached to call queue - open [Resource Accounts tab](https://admin.teams.microsoft.com/company-wide-settings/resource-accounts) in Teams Admin and find email.
-:::image type="content" source="../media/teams-call-queue-resource-account.PNG" alt-text="Screenshot of Resource Accounts in Teams Admin Portal.":::
-All required information for Resource Account can be found in [Microsoft Graph Explorer](https://developer.microsoft.com/en-us/graph/graph-explorer) using this email in the search.
-
-```console
-https://graph.microsoft.com/v1.0/users/[email protected]
-```
-
-In results we'll are able to find "ID" field
-
-```json
-    "userPrincipalName": "[email protected]",
-    "id": "31a011c2-2672-4dd0-b6f9-9334ef4999db"
-```
-
-[!INCLUDE [Call Queue with JavaScript](./includes/teams-call-queue/teams-call-queue-javascript.md)]
+::: zone pivot="platform-windows"
+[!INCLUDE [Auto Attendant with Windows](./includes/teams-call-queue/teams-call-queue-windows.md)]
+::: zone-end
 
 ## Clean up resources