apim

Author: Harikrishnan-M-B

articles/application-gateway/proxy-buffers.md

@@ -5,36 +5,36 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 08/03/2022
+ms.date: 09/25/2024
 ms.author: greglin
 #Customer intent: As a user, I want to know how can I disable/enable proxy buffers.
 ---
 
 # Configure Request and Response Proxy Buffers
 
-Azure Application Gateway Standard v2 SKU supports buffering Requests (from clients) or Responses (from the backend servers). Based on the processing capabilities of the clients that interact with your Application Gateway, you can use these buffers to configure the speed of packet delivery.
+Azure Application Gateway Standard v2 SKU supports buffering Requests from clients or Responses (from the backend servers). Based on the processing capabilities of the clients that interact with your application gateway, you can use these buffers to configure the speed of packet delivery.
 
 ## Response Buffer 
 
-Application Gateway's Response buffer can collect all or parts of the response packets sent by the backend server, before delivering them to the clients. By default, the Response buffering is enabled on Application Gateway which is useful to accommodate slow clients. This setting allows you to conserve the backend TCP connections as they can be closed once Application Gateway receives complete response and work according to the client's processing speed. This way, your Application Gateway will continue to deliver the response as per client’s pace. 
+Application Gateway's response buffer can collect all or parts of the response packets sent by the backend server, before delivering them to the clients. By default, the Response buffering is enabled on Application Gateway which is useful to accommodate slow clients. This setting allows you to conserve the backend TCP connections as they can be closed once Application Gateway receives complete response and work according to the client's processing speed. This way, your Application Gateway continues to deliver the response as per the client’s pace. 
 
 
 ## Request Buffer 
 
-In a similar way, Application Gateway's Request buffer can temporarily store the entire or parts of the request body, and then forward a larger upload request at once to the backend server. By default, Request buffering setting is enabled on Application Gateway and is useful to offload the processing function of re-assembling the smaller packets of data on the backend server.
+In a similar way, Application Gateway's Request buffer can temporarily store the entire or parts of the request body, and then forward a larger upload request at once to the backend server. By default, Request buffering setting is enabled on Application Gateway and is useful to offload the processing function of reassembling the smaller packets of data on the backend server.
 
 
 >[!NOTE]
->By default, both Request and Response buffers are enabled on your Application Gateway resource but you can choose to configure them separately. Further, the settings are applied at a resource level and cannot be managed separately for each listener.
+>By default, both Request and Response buffers are enabled on your Application Gateway resource but you can choose to configure them separately. Further, the settings are applied at a resource level and can't be managed separately for each listener.
  
 </br>
 
-You can keep either the Request or Response buffer, enabled or disable, based on your requirements and/or the observed performance of the client systems that communicate with your Application Gateway. 
+You can keep either the Request or Response buffer, enabled or disabled, based on your requirements and the observed performance of the client systems that communicate with your Application Gateway. 
 
 </br>
 
 > [!WARNING]
->We strongly recommend that you test and evaluate the performance before rolling this out on the production gateways. 
+> We strongly recommend that you test and evaluate the performance before rolling this out on the production gateways. 
 
 ## How to change the buffer settings? 
 
@@ -51,6 +51,20 @@ az network application-gateway update --name <gw-name> --resource-group <rg-name
  az network application-gateway update --name <gw-name> --resource-group <rg-name> --set globalConfiguration.enableRequestBuffering=false
 ```
 
+### PowerShell method
+
+**New application gateway**
+```PowerShell
+$AppGw02 = New-AzApplicationGateway -Name "ApplicationGateway02" -ResourceGroupName "ResourceGroup02" -Location $location -BackendAddressPools $pool -BackendHttpSettingsCollection $poolSetting01 -FrontendIpConfigurations $fipconfig -GatewayIpConfigurations $gipconfig -FrontendPorts $fp01 -HttpListeners $listener01 -RequestRoutingRules $rule01 -Sku $sku -EnableRequestBuffering:$false -EnableResponseBuffering:$false
+```
+**Update an existing application gateway**
+```PowerShell
+$appgw = Get-AzApplicationGateway -Name $appgwName -ResourceGroupName $rgname
+$appgw.EnableRequestBuffering = $false
+$appgw.EnableResponseBuffering = $false
+Set-AzApplicationGateway -ApplicationGateway $appgw
+```
+
 ### ARM template method
 
 ```json
@@ -85,5 +99,5 @@ For reference, visit [Azure SDK for .NET](/dotnet/api/microsoft.azure.management
 
 ## Limitations
 - API version 2020-01-01 or later should be used to configure buffers.
-- Currently, these changes are not supported through Portal and PowerShell.
-- Request buffering cannot be disabled if you are running the WAF SKU of Application Gateway. The WAF requires the full request to buffer as part of processing, therefore, even if you disable request buffering within Application Gateway the WAF will still buffer the request. Response buffering is not impacted by the WAF.
+- Currently, these changes aren't supported through Portal and PowerShell.
+- Request buffering can't be disabled if you're running the WAF SKU of Application Gateway. The WAF requires the full request to buffer as part of processing, therefore, even if you disable request buffering within Application Gateway the WAF still buffers the request. Response buffering isn't impacted by the WAF.

articles/azure-functions/dotnet-isolated-process-guide.md

@@ -65,9 +65,14 @@ The following packages are required to run your .NET functions in an isolated wo
 
 #### Version 2.x (Preview)
 
-The 2.x versions of the core packages change the supported framework assets and bring in support for new .NET APIs from these later versions. When using .NET 9 (Preview) or later, your app needs to reference version 2.0.0-preview1 or later of both packages. 
+The 2.x versions of the core packages change the supported framework assets and bring in support for new .NET APIs from these later versions. When using .NET 9 (Preview) or later, your app needs to reference version 2.0.0-preview1 or later of both packages.
+
+The initial preview versions are compatible with code written against version 1.x. However, during the preview period, newer versions may introduce behavior changes that could influence the code you write.
+
+When updating to the 2.x versions, please note the following changes:
+
+- Starting with version 2.0.0-preview2, [Microsoft.Azure.Functions.Worker.Sdk] adds default configurations for [SDK container builds](/dotnet/core/docker/publish-as-container).
 
-The 2.0.0-preview1 versions are compatible with code written against version 1.x. However, during the preview period, newer versions may introduce behavior changes that could influence the code you write.
 
 ### Extension packages
 

articles/azure-netapp-files/configure-customer-managed-keys-hardware.md

@@ -37,6 +37,7 @@ Azure NetApp Files volume encryption with customer-managed keys with the managed
 * Australia East
 * Brazil South
 * Canada Central
+* Central India
 * Central US
 * East Asia
 * East US
@@ -51,6 +52,7 @@ Azure NetApp Files volume encryption with customer-managed keys with the managed
 * Qatar Central
 * South Africa North
 * South Central US
+* South India
 * Southeast Asia
 * Spain Central
 * Sweden Central

articles/cdn/classic-cdn-retirement-faq.md

@@ -3,11 +3,11 @@ title: Azure CDN Standard from Microsoft (classic) retirement FAQ
 titleSuffix:  Azure CDN Standard from Microsoft
 description: Common questions about the retirement of Azure CDN Standard from Microsoft (classic).
 services: front-door
-author: duongau, hmb
+author: duongau
 ms.service: azure-cdn
 ms.topic: faq
 ms.date: 09/26/2024
-ms.author: duau, hmb
+ms.author: duau
 ms.custom: ai-usage
 ---
 
@@ -95,8 +95,6 @@ If you have a support plan and you need technical assistance, you can create a [
 * *Summary*, describe the problem you’re experiencing with the migration.
 * *Problem type*, select **Migrating Microsoft CDN to Front Door Standard or Premium**
 
-:::image type="content" source="./media/classic-retirement-faq/support-request.png" alt-text="Screenshot of a new support request for Azure CDN Standard from Microsoft (classic) migration issue.":::
-
 ## Next steps
 
 - Migrate from Azure CDN Standard from Microsoft (classic) to Standard or Premium tier using the [Azure portal](migrate-tier.md)

articles/communication-services/concepts/government.md

@@ -25,4 +25,15 @@ Azure Communication Services (ACS) can be used within [Azure Government](https:/
 
 Azure Communication Services in Azure Government is currently In Process for the FedRAMP High accreditation as part of the [M365 GCC-High service offering](https://marketplace.fedramp.gov/products/FR1824057433). Once the FedRAMP High certification process is completed and the authorization is granted, Azure Communication Services in the Azure Government cloud will GA and be officially recognized as meeting the requirements set forth by the FedRAMP, providing government customers with the confidence that the service is secure and compliant with federal standards.
 
+## General Availability and Upcoming Feature Releases
+Azure Communication Services for US Government is scheduled for General Availability (GA) in 2025. The initial release will focus on delivering core capabilities, including basic video calling and messaging, to provide government customers with a secure and compliant communication solution.
+
+Additional advanced features, such as:
+- Call Logs
+- Call Records
+- Transcriptions
+- Live Captions
+- Email Integration
+will be introduced in a subsequent release later in 2025, following GA. Azure Communication Services is committed to releasing these features as part of its roadmap, ensuring feature parity with Azure Communication Services Commercial within six months of each feature becoming available in the commercial cloud.
+
 You can find more information about the Office 365 Government – GCC High offering for US Government customers at [Office 365 Government plans](https://products.office.com/government/compare-office-365-government-plans). Please see [eligibility requirements](https://azure.microsoft.com/global-infrastructure/government/how-to-buy/) for Azure Government. 

articles/communication-services/concepts/voice-video-calling/known-issues-native.md

@@ -11,29 +11,12 @@ ms.topic: conceptual
 ms.service: azure-communication-services
 ---
 
-# Known issues associated with the Azure Communication Services Calling Native and Native UI SDKs.
+# Known issues associated with the Azure Communication Services Calling Native and Native UI SDKs
 This article provides known issues related to using the Azure Communication Services native calling SDKs.
 
 ## Issues with Android API emulators
 
-When utilizing Android API emulators on Android 5.0 (API level 21) and Android 5.1 (API level 22), some crashes are expected.  
-
-## Android chat and calling conflicts
-
-You can't use Azure Communication Services chat and calling Android SDK at the same time, the chat real-time notifications feature doesn't work. You might get a dependency resolving issue.
-
-To resolve this issue, you can turn off real-time notifications by adding the following dependency information in your app's build.gradle file and instead poll the GetMessages API to display incoming messages to end users.
-
-**Java**
-```java
- implementation ("com.azure.android:azure-communication-chat:1.0.0") {
-     exclude group: 'com.microsoft', module: 'trouter-client-android'
- }
- implementation 'com.azure.android:azure-communication-calling:1.0.0'
- ```
- 
-> [!NOTE]
-> If your application uses the notification APIs like `chatAsyncClient.startRealtimeNotifications()` or `chatAsyncClient.addEventHandler()`, you will see a runtime error.
+When utilizing Android API emulators on Android 5.0 (API level 21) and Android 5.1 (API level 22), some crashes are expected.
 
 ## iOS ongoing video Picture in Picture (PiP)
 

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

@@ -172,24 +172,6 @@ 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 use this API please use 'beta' release of Azure Communication Services Calling Android SDK version 2.6.0-beta.8 or higher. 
-
-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();
-```
-
-To notify the local participant they have been muted by others, subscribe to the `onMutedByOthers` event. 
-
 ## 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.
@@ -281,6 +263,24 @@ State can be one of
     ```java
     List<RemoteVideoStream> videoStreams = remoteParticipant.getVideoStreams(); // [RemoteVideoStream, RemoteVideoStream, ...]
     ```
+### Mute other participants
+> [!NOTE]
+> To use this API please use the Azure Communication Services Calling Android SDK version 2.11.0 or higher. 
+
+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();
+```
+
+To notify the local participant they have been muted by others, subscribe to the `onMutedByOthers` event. 
+
 ## Using Foreground Services
 
 In cases when you want to run a user visible task even when your application is in background, you can use [Foreground Services](https://developer.android.com/guide/components/foreground-services).

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

@@ -178,36 +178,6 @@ 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 use this API please use 'beta' release of Azure Communication Services Calling iOS SDK version 2.9.0-beta.1 or higher. 
-
-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.")
-    }
-}
-```
-
-To notify the local participant they have been muted by others, subscribe to the `onMutedByOthers` event. 
-
 ## Manage remote participants
 
 All remote participants are represented by the `RemoteParticipant` type and are available through the `remoteParticipants` collection on a call instance.
@@ -263,3 +233,33 @@ var isSpeaking = remoteParticipant.isSpeaking
 // RemoteVideoStream[] - collection of video streams this participants has
 var videoStreams = remoteParticipant.videoStreams // [RemoteVideoStream, RemoteVideoStream, ...]
 ```
+
+### Mute other participants
+> [!NOTE]
+> To use this API please use the Azure Communication Services Calling iOS SDK version 2.13.0 or higher. 
+
+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.")
+    }
+}
+```
+
+To notify the local participant they have been muted by others, subscribe to the `onMutedByOthers` event. 

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

@@ -160,22 +160,6 @@ await call.unmuteIncomingAudio();
 
 When incoming audio is muted, the participant client SDK still receives the call audio (remote participant's audio). The call audio isn't heard in the speaker and the participant isn't able to listen until 'call.unmuteIncomingAudio()' is called. However, we can apply filter on call audio and play the filtered audio. 
 
-## Mute other participants
-> [!NOTE]
-> To use this API please use Azure Communication Services Calling Web SDK version 1.26.1 or higher. 
-
-To mute all other participants or mute a specific participant who are connected to a call, you can use the asynchronous APIs `muteAllRemoteParticipants` on the call and `mute` on the remote participant. The `mutedByOthers` event from Call is raised when the local participant has been muted by others.
-
- *Note: The scenarios to mute PSTN (phone number) participants or 1:1 call participants are not supported.* 
-
-```js
-//mute all participants except yourself
-await call.muteAllRemoteParticipants();
-
-//mute a specific participant
-await call.remoteParticipants[0].mute();
-```
-
 ## Manage remote participants
 
 All remote participants are detailed in  the `RemoteParticipant` object and available through the `remoteParticipants` collection on a call instance. The `remoteParticipants` is accessible from a `Call` instance.
@@ -277,6 +261,21 @@ const state = remoteParticipant.state;
     ```
     *Note: A remote participant could be in the call from many endpoints, and each endpoint has its own unique `participantId`. `participantId` is different from the RemoteParticipant.identifier's raw ID.*
 
+### Mute other participants
+> [!NOTE]
+> To use this API please use Azure Communication Services Calling Web SDK version 1.26.1 or higher. 
+
+To mute all other participants or mute a specific participant who are connected to a call, you can use the asynchronous APIs `muteAllRemoteParticipants` on the call and `mute` on the remote participant. The `mutedByOthers` event from Call is raised when the local participant has been muted by others.
+
+ *Note: The scenarios to mute PSTN (phone number) participants or 1:1 call participants are not supported.* 
+
+```js
+//mute all participants except yourself
+await call.muteAllRemoteParticipants();
+
+//mute a specific participant
+await call.remoteParticipants[0].mute();
+```
 ## Check call properties
 
 Get the unique ID (string) for a call:

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

@@ -141,7 +141,7 @@ await this.call.UnmuteOutgoingAudioAsync();
 
 ## Mute other participants
 > [!NOTE]
-> This API is provided as a public preview for developers and may change based on feedback that we receive. To use this API please use 'beta' release of Azure Communication Services Calling Windows SDK version 1.6.0-beta.1 or higher. 
+> To use this API please use the Azure Communication Services Calling Windows SDK version 1.9.0 or higher. 
 
 To mute all other participants or mute a specific participant, you can use the asynchronous APIs `MuteAllRemoteParticipantsAsync` on the call and `MuteAsync` on the remote participant: