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

Author: gitName

articles/azure-functions/functions-app-settings.md

@@ -910,6 +910,7 @@ In the [Flex Consumption plan](./flex-consumption-plan.md), these site propertie
 | `WEBSITE_CONTENTOVERVNET` |Not used for networking in Flex Consumption|
 | `WEBSITE_CONTENTSHARE` |Replaced by functionAppConfig's deployment section|
 | `WEBSITE_DNS_SERVER` |DNS is inherited from the integrated virtual network in Flex|
+| `WEBSITE_MAX_DYNAMIC_APPLICATION_SCALE_OUT` |Replaced by `maximumInstanceCount` in `properties.functionAppConfig.scaleAndConcurrency`|
 | `WEBSITE_NODE_DEFAULT_VERSION` |Replaced by `version` in `properties.functionAppConfig.runtime`|
 | `WEBSITE_RUN_FROM_PACKAGE`|Not used for deployments in Flex Consumption|
 | `WEBSITE_SKIP_CONTENTSHARE_VALIDATION` |Content share is not used in Flex Consumption|

articles/azure-maps/power-bi-visual-add-path-layer.md

@@ -69,7 +69,7 @@ Examine the connections and insights revealed by the path layer visualization. F
 
 Adding a field to the legend field well creates a higher level of grouping. So, paths and locations associated with the same legend are colored identically. Here's the process:
 
-- **Grouping by Legend**: When a legend is provided, the paths and locations are grouped based on the legend. For instance, if visualizing flight paths with the airline as the legend, all paths and locations associated with the same airline share the same color. Moreover, if there are two rows, one with legend "Contoso" and path ID "A123," and another with legend "MSAirline" and path ID "A123," the path layer interprets these as two distinct paths: "Contoso-A123" and "MSAirline-A123".
+- **Grouping by Legend**: When a legend is provided, the paths and locations are grouped based on the legend. For instance, if visualizing flight paths with the airline as the legend, all paths and locations associated with the same airline share the same color. Moreover, if there are two rows, one with legend "Contoso" and path ID "A123" and another with legend "MSAirline" and path ID "A123" the path layer interprets these as two distinct paths: "Contoso-A123" and "MSAirline-A123".
 - **Styling by Legend**: Configure the style (color, line width, opacity) using the legend to visually differentiate path groups.
 - **Interaction by Legend**: When interacting with the path layer, selecting a path or point also selects other reports based on legend, path ID, location, and point order. This ensures all related data points are highlighted together.
 

articles/azure-maps/power-bi-visual-add-reference-layer.md

@@ -130,7 +130,7 @@ To use the custom styling options for reference layers, follow these steps:
 
 | Setting name        | Description                                          | Setting values                                                       |
 |---------------------|------------------------------------------------------|----------------------------------------------------------------------|
-| Fill colors         | Fill color of points and polygons.                   | Set colors for different data category or gradient for numeric data. |
+| Fill color          | Fill color of points and polygons.                   | Set colors for different data category or gradient for numeric data. |
 | Border color        | The color of the points, lines, and polygons outline.| Color picker                                                         |
 | Border width        | The width of the border in pixels. Default: 3 px     | Width 1-20 pixels                                                    |
 | Border transparency | The transparency of the borders. Default: 0%         | Transparency 0-100%                                                  |

articles/azure-vmware/faq.yml

@@ -275,8 +275,8 @@ sections:
   - name: Hosts, clusters, and private clouds
     questions:
 
-      - question: Is there more than one type of host available?
-        answer:  No. There's only one type available.
+      - question: Is there more than one type of host available per private cloud? Is it possible to combine different host types in a cluster or private cloud?
+        answer:  With the exception of AV64 cluster requiring a separate 3-node cluster minimum of AV36, AV36P, or AV52, you cannot combine different host types in a private cloud. In all scenarios, clusters require the same host type. Multiple clusters can be deployed within a single private cloud. All hosts must be the same type within a private cloud. If different host types are required to meet use case needs, additional private clouds must be deployed.
 
       - question: Do I use the same tools that I use now to manage private cloud resources?
         answer: Yes. The Azure portal is used for deployment and several management operations. vCenter Server and NSX Manager are used to manage vSphere and NSX resources.

articles/communication-services/concepts/rooms/room-concept.md

@@ -26,16 +26,14 @@ Virtual Rooms empower developers with essential security and control capabilitie
 | Voice (VoIP) | ✔️ |
 | Video | ✔️ |
 | Client initiated dial-out to a PSTN number | ✔️ |
-| Server initiated dial-out to a PSTN number** | ✔️ |
+| Server initiated dial-out to a PSTN number | ✔️ |
 | Server-side call management (Call Automation)*  | ✔️ |
 | PSTN Dial-in | ❌ |
 | Async Messaging (Chat) | ❌ |
 | Interoperability with Microsoft Teams | ❌ |
 
 \* Some exceptions apply. The full list of supported [Call Automation capabilities](#how-to-conduct-calls-in-virtual-rooms) are listed in this document.
 
-\*\* Currently in [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
-
 ## When to use Virtual Rooms
 
 Following table shows when to use Virtual Rooms.
@@ -70,27 +68,25 @@ At a high level, to conduct calls in a Virtual Rooms you need to create and mana
 | Virtual Rooms security-controls management - Set/Update flag to allow PSTN dial-out from specific Virtual Rooms   | ✔️ | ❌ |  ❌ |
 | Get list of users invited to join a Virtual Room | ✔️ | ❌ |  ❌ |
 | A user initiates a Virtual Rooms call or joins an in-progress call | ❌ | ✔️ |  ❌ |
-| Dial-out to a PSTN user  | ❌ | ✔️ | ✔️* |
-| Add/Remove VoIP participants to an in-progress call | ❌ | ✔️ |  ✔️* |
-| Get list of participants who joined the in-progress call | ❌ | ✔️ |  ✔️* |
+| Dial-out to a PSTN user  | ❌ | ✔️ | ✔️ |
+| Add/Remove VoIP participants to an in-progress call | ❌ | ✔️ |  ✔️ |
+| Get list of participants who joined the in-progress call | ❌ | ✔️ |  ✔️ |
 | Start/Stop call captions and change captions language | ❌ | ✔️ |  ❌ |
 | Manage call recording | ❌ | ❌ |  ✔️ |
-| Send/Receive DTMF to/from PSTN participants | ❌ | ❌ | ✔️* |
-| Play audio prompts to participants  | ❌ | ❌ | ✔️* |
+| Send/Receive DTMF to/from PSTN participants | ❌ | ❌ | ✔️ |
+| Play audio prompts to participants  | ❌ | ❌ | ✔️ |
 
 [Calling client SDK](../voice-video-calling/calling-sdk-features.md#detailed-capabilities) provides the full list of client-side in-call operations and explains how to use them.
 
-\* Currently in [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
-
 ## Managing Virtual Rooms calls from the server-side using Call Automation Server SDK
 
 Call Automation SDK empowers developers to manage Virtual Rooms calls from the server-side and execute in-call operations. Call Automation capabilities are being progressively enabled in Virtual Rooms calls. The following table shows the current status of these capabilities. Developers manage and control Call Automation capabilities from the server-side, which operate at a higher level than a call participant's privileges. So Call Automation capabilities aren't controlled through user roles and permissions.
 
 | Call Automation capability | Supported in Rooms call | 
 | ------ | :------: |
-| Dial-out to PSTN participant * | ✔️ |
-| Send/Read DTMF to/from PSTN participant * | ✔️ |
-| Send announcements to specific call participants * | ✔️ |
+| Dial-out to PSTN participant | ✔️ |
+| Send/Read DTMF to/from PSTN participant | ✔️ |
+| Send announcements to specific call participants | ✔️ |
 | Add/Remove a VoIP participant from an ongoing call | ✔️ |
 | End call for all users | ✔️ |
 | Call transcriptions | ❌ |
@@ -129,7 +125,6 @@ Developers can allow/disallow the ability for call participants to dial-out to a
 1. A participant with Presenter role adds PSTN number into a call
 1. PSTN user accepts and joins a room call
 
-
 ### Virtual Rooms API/SDKs
 
 Rooms are created and managed via rooms APIs or SDKs. Use the rooms API/SDKs in your server application for `room` operations:
@@ -156,6 +151,8 @@ Room participants can be assigned one of the following roles: **Presenter**, **A
 
 The following table provides detailed capabilities mapped to the roles. At a high level, **Presenter** role has full control, **Attendee** capabilities are limited to audio and video, while **Consumer** can only receive audio, video, and screen sharing.
 
+<b>Note:</b> A PSTN call participant is not a part of Room roster, so a user role is not assigned to them. They capabilities are limited to mute/unmute themselves on the local device.
+
 | Capability | Role: Presenter | Role: Attendee | Role: Consumer
 |---------------------------------------------| :--------: | :--------: | :--------: |
 | **Mid call controls** | | |

articles/container-apps/ip-restrictions.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: how-to
-ms.date: 03/28/2023
+ms.date: 12/02/2024
 ms.author: cshoe
 zone_pivot_groups: azure-cli-or-portal
 ---
@@ -62,7 +62,6 @@ You can manage IP access restrictions rules through the Azure portal or Azure CL
 1. Select **Add**.
 1. Repeat steps 4-6 to add more rules.
 1. When you have finished adding rules, select **Save**.
-    :::image type="content" source="media/ingress/screenshot-save-ip-restriction.png" alt-text="Screenshot to save IP restrictions on container app Ingress page.":::
 
 ### Update a rule
 

articles/container-apps/log-streaming.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: how-to
-ms.date: 03/24/2023
+ms.date: 12/02/2024
 ms.author: cshoe
 ---
 
@@ -30,23 +30,18 @@ To troubleshoot issues in your container app environment, you can view the syste
 1. Go to your environment in the Azure portal.
 1. Select **Log stream** under the *Monitoring* section on the sidebar menu.
 
-    :::image type="content" source="media/observability/system-log-streaming-env.png" alt-text="Screenshot of Container Apps environment system log stream page.":::
-
 ### Container app log stream
 
 You can view a log stream of your container app's system or console logs from your container app page.
 
 1. Go to your container app in the Azure portal.
 1. Select **Log stream** under the *Monitoring* section on the sidebar menu.
 1. To view the console log stream, select **Console**.
-    1. If you have multiple revisions, replicas, or containers, you can select from the drop-down menus to choose a container. If your app has only one container, you can skip this step.
 
-    :::image type="content" source="media/observability/screenshot-log-stream-console-app.png" alt-text="Screenshot of Container Apps console log stream from app page.":::
+    1. If you have multiple revisions, replicas, or containers, you can select from the drop-down menus to choose a container. If your app has only one container, you can skip this step.
 
 1. To view the system log stream, select **System**. The system log stream displays the system logs for all running containers in your container app.
 
-    :::image type="content" source="media/observability/screenshot-log-stream-system-app.png" alt-text="Screenshot of Container Apps system log stream from app page.":::
-
 ## View log streams via the Azure CLI
 
 You can view your container app's log streams from the Azure CLI with the `az containerapp logs show` command or your container app's environment system log stream with the `az containerapp env logs show` command.