Merge branch 'MicrosoftDocs:main' into main

Author: gmndrg

articles/api-management/rate-limit-policy.md

@@ -40,7 +40,6 @@ To understand the difference between rate limits and quotas, [see Rate limits an
 | -------------- | ----------------------------------------------------------------------------------------------------- | -------- | ------- |
 | calls          | The maximum total number of calls allowed during the time interval specified in `renewal-period`. Policy expressions aren't allowed.| Yes      | N/A     |
 | renewal-period | The length in seconds of the sliding window during which the number of allowed requests should not exceed the value specified in `calls`. Maximum allowed value: 300 seconds. Policy expressions aren't allowed.                                           | Yes      | N/A     |
-| total-calls-header-name    | The name of a response header whose value is the value specified in `calls`. Policy expressions aren't allowed. |  No | N/A  |
 | retry-after-header-name    | The name of a custom response header whose value is the recommended retry interval in seconds after the specified call rate is exceeded. Policy expressions aren't allowed. |  No | `Retry-After`  |
 | retry-after-variable-name    | The name of a variable that stores the recommended retry interval in seconds after the specified call rate is exceeded. Policy expressions aren't allowed. |  No | N/A  |
 | remaining-calls-header-name    | The name of a response header whose value after each policy execution is the number of remaining calls allowed for the time interval specified in the `renewal-period`. Policy expressions aren't allowed.|  No | N/A  |
@@ -109,4 +108,4 @@ In the following example, the per subscription rate limit is 20 calls per 90 sec
 
 * [API Management access restriction policies](api-management-access-restriction-policies.md)
 
-[!INCLUDE [api-management-policy-ref-next-steps](../../includes/api-management-policy-ref-next-steps.md)]
+[!INCLUDE [api-management-policy-ref-next-steps](../../includes/api-management-policy-ref-next-steps.md)]

articles/azure-arc/kubernetes/extensions-troubleshooting.md

@@ -1,6 +1,6 @@
 ---
 title: "Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters"
-ms.date: 12/15/2023
+ms.date: 12/19/2023
 ms.topic: how-to
 description: "Learn how to resolve common issues with Azure Arc-enabled Kubernetes cluster extensions."
 ---
@@ -113,12 +113,37 @@ az k8s-configuration create <parameters> --debug
 
 ## Azure Monitor Container Insights
 
-[Azure Monitor Container Insights](/azure/azure-monitor/containers/container-insights-enable-arc-enabled-clusters?toc=%2Fazure%2Fazure-arc%2Fkubernetes%2Ftoc.json&bc=%2Fazure%2Fazure-arc%2Fkubernetes%2Fbreadcrumb%2Ftoc.json&tabs=create-cli%2Cverify-portal) requires its DaemonSet to run in privileged mode. To successfully set up a Canonical Charmed Kubernetes cluster for monitoring, run the following command:
+This section provides help troubleshooting issues with [Azure Monitor Container Insights for Azure Arc-enabled Kubernetes clusters](/azure/azure-monitor/containers/container-insights-enable-arc-enabled-clusters?toc=%2Fazure%2Fazure-arc%2Fkubernetes%2Ftoc.json&bc=%2Fazure%2Fazure-arc%2Fkubernetes%2Fbreadcrumb%2Ftoc.json&tabs=create-cli%2Cverify-portal).
+
+### Enabling privileged mode for Canonical Charmed Kubernetes cluster
+
+Azure Monitor Container Insights requires its DaemonSet to run in privileged mode. To successfully set up a Canonical Charmed Kubernetes cluster for monitoring, run the following command:
 
 ```console
 juju config kubernetes-worker allow-privileged=true
 ```
 
+### Unable to install Azure Monitor Agent (AMA) on Oracle Linux 9.x
+
+When trying to install the Azure Monitor Agent (AMA) on an Oracle Linux (RHEL) 9.x Kubernetes cluster, the AMA pods and the AMA-RS pod might not work properly due to the `addon-token-adapter` container in the pod. With this error, when checking the logs of the `ama-logs-rs` pod, `addon-token-adapter container`, you see output similar to the following:
+
+```output
+Command: kubectl -n kube-system logs ama-logs-rs-xxxxxxxxxx-xxxxx -c addon-token-adapter
+ 
+Error displayed: error modifying iptable rules: error adding rules to custom chain: running [/sbin/iptables -t nat -N aad-metadata --wait]: exit status 3: modprobe: can't change directory to '/lib/modules': No such file or directory
+
+iptables v1.8.9 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
+
+Perhaps iptables or your kernel needs to be upgraded.
+```
+
+This error occurs because installing the extension requires the `iptable_nat` module, but this module isn't automatically loaded in Oracle Linux (RHEL) 9.x distributions.
+
+To fix this issue, you must explicitly load the `iptables_nat` module on each node in the cluster, using the `modprobe` command `sudo modprobe iptables_nat`. After you have signed into each node and manually added the `iptable_nat` module, retry the AMA installation.
+
+> [!NOTE]
+> Performing this step does not make the `iptables_nat` module persistent.  
+
 ## Azure Arc-enabled Open Service Mesh
 
 This section provides commands that you can use to validate and troubleshoot the deployment of the [Open Service Mesh (OSM)](tutorial-arc-enabled-open-service-mesh.md) extension components on your cluster.

articles/azure-arc/kubernetes/troubleshooting.md

@@ -10,7 +10,7 @@ description: "Learn how to resolve common issues with Azure Arc-enabled Kubernet
 
 This document provides troubleshooting guides for issues with Azure Arc-enabled Kubernetes connectivity, permissions, and agents. It also provides troubleshooting guides for Azure GitOps, which can be used in either Azure Arc-enabled Kubernetes or Azure Kubernetes Service (AKS) clusters.
 
-For help troubleshooting issues related to extensions, see [Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters](extensions-troubleshooting.md).
+For help troubleshooting issues related to extensions, such as GitOps (Flux v2), Azure Monitor Container Insights, Open Service Mesh, see [Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters](extensions-troubleshooting.md).
 
 ## Azure CLI
 

articles/azure-netapp-files/manage-availability-zone-volume-placement.md

@@ -36,6 +36,9 @@ You can deploy new volumes in the logical availability zone of your choice. You
 
 [!INCLUDE [Availability Zone volumes have the same level of support as other volumes in the subscription](includes/availability-zone-service-callout.md)]
 
+>[!IMPORTANT]
+>It's not recommended that you use availability zones for Terraform-managed volumes. If you do, you must [add the zone property to your volume](#populate-availability-zone-for-terraform-managed-volumes).
+
 ## Create a volume with an availability zone 
 
 1.	Select **Volumes** from your capacity pool. Then select **+ Add volume** to create a volume.
@@ -84,13 +87,35 @@ You can deploy new volumes in the logical availability zone of your choice. You
 1. Navigate to the volume that you want to populate with availability zone information.
 1. Select **Populate availability zone**.
 1. The Populate Availability Zone window appears and displays the availability zone in which the Azure NetApp Files volume is deployed.
-1. Click **Save** if you want to populate this availability zone to the volume, or click **Cancel** if you want to keep the volume regional.
+1. Select **Save** if you want to populate this availability zone to the volume, or select **Cancel** if you want to keep the volume regional.
 
     > [!IMPORTANT]
     > Availability zone information can only be populated as provided. You can't select an availability zone or move the volume to another availability zone by using this feature. If you want to move this volume to another availability zone, consider using [cross-zone replication](create-cross-zone-replication.md) (after populating the volume with the availability zone information). 
     >
     > :::image type="content" source="../media/azure-netapp-files/populate-availability-zone.png" alt-text="Screenshot of the Populate Availability Zone window." lightbox="../media/azure-netapp-files/populate-availability-zone.png":::
+
+## Populate availability zone for Terraform-managed volumes
+
+The populate availability zone features requires a `zone` property on the volume. You can set the zone property only when you create the Terraform-managed volume, but you cannot modify it. Adding the `zone` property after the volume has been created can cause data loss or loss of the volume if the specified zone value does not match the availability zone. 
+
+1. Navigate to the Terraform module `terraform.tfstate`. The `"zone"` property should be an empty string. 
+1. In the Terraform-managed volume's configuration file (`main.tf`), locate the lifecycle configuration block. Modify the block with `ignore_changes = [zone]`. If no lifecycle configuration block exists, add it:
+    ```
+    lifecycle {
+        ignore_changes = [zone]
+    }
+    ```
+1. In the Azure portal, locate the Terraform module. In the volume **Overview**, select **Populate availability zone** and make note of the availability zone. Do _not_ select save. 
+
+    :::image type="content" source="../media/azure-netapp-files/populate-availability-zone.png" alt-text="Screenshot of the Populate Availability Zone menu." lightbox="../media/azure-netapp-files/populate-availability-zone.png":::
     
+1. In the volume's configuration file (`main.tf`), add a value for `zone`, entering the numerical value you retrieved in the previous step. For example, if the volume's availability zone is 2, enter `zone = 2`. Save the file. 
+1. Return to the Azure portal. Select **Save** to populate the availability zone. 
+1. Run `terraform plan` to confirm that no changes will be made to your volume. The CLI output should display: `No changes. Your infrastructure matches the configuration.`
+1. Run `terraform apply` to apply the changes. You should see the same CLI output as in the previous step. 
+
+If you need to delete and recreate the volume in a different availability zone, remove the `ignore_changes = [zone]` line in the configuration file then run `terraform plan`. If the output indicates that no changes will be made to the volume, you can successfully populate the availability zone.
+ 
 ## Next steps  
 
 * [Use availability zones for high availability](use-availability-zones.md)

articles/azure-netapp-files/use-availability-zones.md

@@ -32,7 +32,7 @@ Azure NetApp Files' [availability zone volume placement](manage-availability-zon
 
 [!INCLUDE [Availability Zone volumes have the same level of support as other volumes in the subscription](includes/availability-zone-service-callout.md)]
 
-All Virtual Machines within the region in (peered) VNets can access all Azure NetApp Files resources (blue arrows). Virtual Machines accessing Azure NetApp Files volumes in the same zone (green arrows) share the availability zone failure domain. 
+All virtual machines (VMs) within the region in (peered) VNets can access all Azure NetApp Files resources (blue arrows). VMs accessing Azure NetApp Files volumes in the same zone (green arrows) share the availability zone failure domain. 
 
 Azure NetApp Files deployments will occur in the availability of zone of choice if Azure NetApp Files is present in that availability zone and has sufficient capacity.
 
@@ -43,6 +43,9 @@ You can co-locate your compute, storage, networking, and data resources across a
 
 Latency is subject to availability zone latency for within availability zone access and the regional latency envelope for cross-availability zone access.
 
+>[!IMPORTANT]
+>It's not recommended that you use availability zones with Terraform-managed volumes. If you do, you must [add the zone property to your volume](manage-availability-zone-volume-placement.md#populate-availability-zone-for-terraform-managed-volumes).
+
 ## Azure regions with availability zones
 
 For a list of regions that currently support availability zones, see [Azure regions with availability zone support](../reliability/availability-zones-service-support.md).

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

@@ -44,7 +44,7 @@ The following list presents the set of features that are currently available in
 |                   | Invite another VoIP participant to join an ongoing group call                                                       | ✔️   | ✔️       | ✔️              | ✔️                 |
 | Mid call control  | Turn your video on/off                                                                                              | ✔️   | ✔️       | ✔️              | ✔️                 |
 |                   | Mute/Unmute mic                                                                                                     | ✔️   | ✔️       | ✔️              | ✔️                 |
-|                   | Mute other participants    |✔️<sup>1</sup>        |   ✔️<sup>1</sup>     |    ❌              |     ❌      |
+|                   | Mute other participants    |✔️<sup>1</sup>        |   ✔️<sup>1</sup>       |    ✔️<sup>1</sup>              |     ✔️<sup>1</sup>      |
 |                   | Switch between cameras                                                                                              | ✔️   | ✔️       | ✔️              | ✔️                 |
 |                   | Local hold/un-hold                                                                                                  | ✔️   | ✔️       | ✔️              | ✔️                 |
 |                   | Active speaker                                                                                                      | ✔️   | ✔️       | ✔️              | ✔️                 |

articles/communication-services/how-tos/calling-sdk/includes/manage-calls/manage-calls-android.md

@@ -171,6 +171,23 @@ Context appContext = this.getApplicationContext();
 call.mute(appContext).get();
 call.unmute(appContext).get();
 ```
+
+## Mute other participants
+> [!NOTE]
+> This API is provided as a public preview for developers and may change based on feedback that we receive.
+
+To mute all other participants in a call, use the `muteAllRemoteParticipants` API on the call.
+
+```java
+call.muteAllRemoteParticipants();
+```
+
+To mute a specific remote participant, use the `mute` API on a given remote participant.
+
+```java
+remoteParticipant.mute();
+```
+
 ## Change the volume of the call
 
 While you are in a call, the hardware volume keys on the phone should allow the user to change the call volume.

articles/communication-services/how-tos/calling-sdk/includes/manage-calls/manage-calls-ios.md

@@ -178,6 +178,35 @@ call!.unmute { (error) in
 }
 ```
 
+## Mute other participants
+> [!NOTE]
+> This API is provided as a public preview for developers and may change based on feedback that we receive.
+
+To mute all other participants in a call, use the `muteAllRemoteParticipants` API on the call.
+
+```swift
+call!.muteAllRemoteParticipants { (error) in
+    if error == nil {
+        print("Successfully muted all remote participants.")
+    } else {
+        print("Failed to mute remote participants.")
+    }
+}
+```
+
+To mute a specific remote participant, use the `mute` API on a given remote participant.
+
+```swift
+remoteParticipant.mute { (error) in
+    if error == nil {
+        print("Successfully muted participant.")
+    } else {
+        print("Failed to mute participant.")
+    }
+}
+```
+
+
 ## Manage remote participants
 
 All remote participants are represented by the `RemoteParticipant` type and are available through the `remoteParticipants` collection on a call instance.

articles/data-share/concepts-pricing.md

@@ -5,7 +5,7 @@ author:  sidontha
 ms.author: sidontha
 ms.service: data-share
 ms.topic: conceptual
-ms.date: 11/15/2022
+ms.date: 12/19/2023
 ---
 
 # Understand Azure Data Share pricing