Merge pull request #296677 from MicrosoftDocs/main

3/20/2025 AM Publish

Author: Taojunshen

articles/active-directory-b2c/tutorial-create-user-flows.md

@@ -213,7 +213,7 @@ Next, specify that the application should be treated as a public client:
 1. Ensure that **"isFallbackPublicClient": true** is set in the application manifest:
     1. In the left menu, under **Manage**, select **Manifest** to open application manifest.
     1. Switch from the **Microsoft Graph App Manifest (New)** tab to the **AAD Graph App Manifest (Deprecating Soon)** tab.
-    1. Find **allowPublicClient** key and ensure its value is set to **true**.
+    1. Find **isFallbackPublicClient** key and ensure its value is set to **true**.
 
 
 Now, grant permissions to the API scope you exposed earlier in the *IdentityExperienceFramework* registration:

articles/application-gateway/ingress-controller-install-new.md

@@ -288,7 +288,7 @@ If you use [Cloud Shell](https://shell.azure.com/), you don't need to install He
 1. Install the AGIC package:
 
     ```bash
-    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.7.5 -f helm-config.yaml
+    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.8.0 -f helm-config.yaml
     ```
 
 ## Install a sample app

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: ram-kakani
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 02/28/2025
+ms.date: 03/20/2025
 ms.author: ramakk
 ms.custom: references_regions
 ---
@@ -40,7 +40,7 @@ The following table describes what’s supported for each network features confi
 |     Number of IPs in a VNet (including immediately peered VNets) accessing volumes in an Azure NetApp Files hosting VNet    |     [Same standard limits as virtual machines (VMs)](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-manager-virtual-networking-limits)    |     1000    |
 |     Azure NetApp Files delegated subnets per VNet    |     1    |     1    |
 |     [Network Security Groups](../virtual-network/network-security-groups-overview.md) (NSGs) on Azure NetApp Files delegated   subnets    |     Yes    |     No    |
-| NSG support for private endpoints | Yes* | No | 
+| [NSG support for private endpoints](../private-link/disable-private-endpoint-network-policy.md) | Yes | No | 
 |     [User-defined routes](../virtual-network/virtual-networks-udr-overview.md#user-defined) (UDRs) on Azure NetApp Files delegated subnets    |     Yes    |     No    |
 |     Connectivity to [Private Endpoints](../private-link/private-endpoint-overview.md)    |     Yes    |     No    |
 |     Connectivity to [Service Endpoints](../virtual-network/virtual-network-service-endpoints-overview.md)    |     Yes  |     No    |
@@ -49,8 +49,6 @@ The following table describes what’s supported for each network features confi
 |     Dual stack (IPv4 and   IPv6) VNet    |     No <br> (IPv4 only supported)    |     No <br> (IPv4 only supported)   |
 |    Traffic routed via NVA from peered VNet | Yes    | No |
 
-\* This feature is currently in preview in all regions where Azure NetApp Files is supported. For guidance on configuring NSG policies for private endpoints, see [Manage network policies for private endpoints](../private-link/disable-private-endpoint-network-policy.md).
-
 ### Supported network topologies
 
 The following table describes the network topologies supported by each network features configuration of Azure NetApp Files. 

articles/azure-netapp-files/whats-new.md

@@ -6,7 +6,7 @@ author: b-hchen
 ms.service: azure-netapp-files
 ms.custom: linux-related-content
 ms.topic: overview
-ms.date: 03/13/2025
+ms.date: 03/20/2025
 ms.author: anfdocs
 ---
 
@@ -16,6 +16,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## March 2025
 
+* [Network security group (NSG) support for private link connectivity](azure-netapp-files-network-topologies.md) is now generally available (GA)
+
+    Azure NetApp Files now supports private links with NSGs in all regions. This feature enables you to apply NSG policies to private link endpoints, enhancing the security of your workload deployments. 
+
 * [Application volume group for Oracle](application-volume-group-oracle-introduction.md) is now generally available (GA)
 
     Application volume group for Oracle enables you to deploy all volumes required to install and operate Oracle databases at enterprise scale, with optimal performance and according to best practices in a single one-step and optimized workflow. The application volume group feature uses the Azure NetApp Files ability to place all volumes in the same availability zone as the VMs to achieve automated, latency-optimized deployments. Azure NetApp Files application volume group shortens Oracle database deployment time and increases overall application performance and stability, including the use of multiple storage endpoints. The application volume group feature supports a wide range of Oracle database layouts from small databases with a single volume up to multi 100-TiB sized databases. Application volume group for Oracle is supported in all Azure NetApp Files-enabled regions.

articles/communication-services/how-tos/call-automation/actions-for-call-control.md

@@ -247,7 +247,7 @@ A successful response provides you with CallConnection object that you can use t
 1. `CallConnected` event notifying that you successfully connect to the call.
 2. `ParticipantsUpdated` event that contains the latest list of participants in the call.
 
-At any point after a successful connection, if your service is disconnected from this call you will be notified via a CallDisconected event. Failure to connect to the call in the first place results in ConnectFailed event.  
+At any point after a successful connection, if your service is disconnected from this call you will be notified via a CallDisconnected event. Failure to connect to the call in the first place results in ConnectFailed event.  
 
 ![Sequence diagram for connecting to call.](media/connect-call-flow.png)
 
@@ -489,7 +489,7 @@ voip_headers = {"customVoipHeader1", "customVoipHeaderValue1"}
 result = call_connection_client.transfer_call_to_participant(
     target_participant=transfer_destination,
     voip_headers=voip_headers,
-    opration_context="Your context",
+    operation_context="Your context",
     operationCallbackUrl="<url_endpoint>"
 )
 ```
@@ -548,7 +548,7 @@ options.getCustomCallingContext().addVoip("voipHeaderName", "voipHeaderValue");
 Response<TransferCallResult> transferResponse = callConnectionAsync.transferToParticipantCallWithResponse(options).block();
 
 // Transfer Pstn User
-CommunicationIdentifier transferDestination = new PhoneNumberIdentifier("<taget_phoneNumber>");
+CommunicationIdentifier transferDestination = new PhoneNumberIdentifier("<target_phoneNumber>");
 CommunicationIdentifier transferee = new PhoneNumberIdentifier("<transferee_phoneNumber>"); 
 TransferCallToParticipantOptions options = new TransferCallToParticipantOptions(transferDestination);
 options.setTransferee(transferee);
@@ -578,7 +578,7 @@ options.customCallingContext = customCallingContext;
 const result = await callConnection.transferCallToParticipant(transferDestination, options);
 
 // Transfer pstn User
-const transferDestination = { phoneNumber: "<taget_phoneNumber>" };
+const transferDestination = { phoneNumber: "<target_phoneNumber>" };
 const transferee = { phoneNumber: "<transferee_phoneNumber>" };
 const options = { transferee: transferee, operationContext: "<Your_context>", operationCallbackUrl: "<url_endpoint>" };
 
@@ -596,7 +596,7 @@ const result = await callConnection.transferCallToParticipant(transferDestinatio
 ```python
 # Transfer to user
 transfer_destination = CommunicationUserIdentifier("<user_id>")
-transferee = CommnunicationUserIdentifer("transferee_user_id")
+transferee = CommunicationUserIdentifier("transferee_user_id")
 call_connection_client = call_automation_client.get_call_connection("<call_connection_id_from_ongoing_call>")
 
 # create custom context
@@ -606,13 +606,13 @@ result = call_connection_client.transfer_call_to_participant(
     target_participant=transfer_destination,
     transferee=transferee,
     voip_headers=voip_headers,
-    opration_context="Your context",
+    operation_context="Your context",
     operationCallbackUrl="<url_endpoint>"
 )
 
 # Transfer to PSTN user
-transfer_destination = PhoneNumberIdentifer("<target_phoneNumber>")
-transferee = PhoneNumberIdentifer("transferee_phoneNumber")
+transfer_destination = PhoneNumberIdentifier("<target_phoneNumber>")
+transferee = PhoneNumberIdentifier("transferee_phoneNumber")
 
 # create custom context
 sip_headers={}
@@ -624,7 +624,7 @@ result = call_connection_client.transfer_call_to_participant(
     target_participant=transfer_destination,
     transferee=transferee,
     sip_headers=sip_headers,
-    opration_context="Your context",
+    operation_context="Your context",
     operationCallbackUrl="<url_endpoint>"
 )
 ```
@@ -737,7 +737,7 @@ call_connection_client = call_automation_client.get_call_connection(
 result = call_connection_client.add_participant(
     target,
     voip_headers=voip_headers,
-    opration_context="Your context",
+    operation_context="Your context",
     operationCallbackUrl="<url_endpoint>"
 )
 
@@ -756,7 +756,7 @@ call_connection_client = call_automation_client.get_call_connection(
 result = call_connection_client.add_participant(
     target,
     sip_headers=sip_headers,
-    opration_context="Your context",
+    operation_context="Your context",
     operationCallbackUrl="<url_endpoint>",
     source_caller_id_number=caller_id_number
 )
@@ -833,7 +833,7 @@ call_connection_client = call_automation_client.get_call_connection(
 result = call_connection_client.add_participant(target)
 
 # cancel the request
-call_connection_client.cancel_add_participant_operation(result.invitation_id, opration_context="Your context", operationCallbackUrl="<url_endpoint>")
+call_connection_client.cancel_add_participant_operation(result.invitation_id, operation_context="Your context", operationCallbackUrl="<url_endpoint>")
 ```
 -----
 
@@ -881,7 +881,7 @@ remove_this_user = CommunicationUserIdentifier("<user_id>")
 call_connection_client = call_automation_client.get_call_connection(
     "<call_connection_id_from_ongoing_call>"
 )
-result = call_connection_client.remove_participant(remove_this_user, opration_context="Your context", operationCallbackUrl="<url_endpoint>")
+result = call_connection_client.remove_participant(remove_this_user, operation_context="Your context", operationCallbackUrl="<url_endpoint>")
 ```
 
 -----

articles/communication-services/how-tos/call-automation/control-mid-call-media-actions.md

@@ -328,7 +328,7 @@ if event.type == "Microsoft.Communication.ContinuousDtmfRecognitionToneFailed":
 ```
 -----
 
-### ContinuousDtmfRecogntionStopped Event
+### ContinuousDtmfRecognitionStopped Event
 Example of how to handle when continuous DTMF recognition has stopped, this could be because your application invoked the `StopContinuousDtmfRecognitionAsync` event or because the call has ended.
 ### [csharp](#tab/csharp)
 ``` csharp
@@ -353,7 +353,7 @@ if (event.type === "Microsoft.Communication.ContinuousDtmfRecognitionStopped") {
 ### [Python](#tab/python)
 ```python
 if event.type == "Microsoft.Communication.ContinuousDtmfRecognitionStopped":
-    app.logger.info("Tone stoped: context=%s", event.data["operationContext"])
+    app.logger.info("Tone stopped: context=%s", event.data["operationContext"])
 ```
 -----
 

articles/communication-services/how-tos/call-automation/custom-context.md

@@ -155,7 +155,7 @@ options.getCustomCallingContext().addVoip("voipHeaderName", "voipHeaderValue");
 Response<TransferCallResult> transferResponse = callConnectionAsync.transferToParticipantCallWithResponse(options).block();
 
 //Transfer a PSTN call to phone number and set UUI and custom SIP headers
-CommunicationIdentifier transferDestination = new PhoneNumberIdentifier("<taget_phoneNumber>");
+CommunicationIdentifier transferDestination = new PhoneNumberIdentifier("<target_phoneNumber>");
 TransferCallToParticipantOptions options = new TransferCallToParticipantOptions(transferDestination);
 options.getCustomCallingContext().addSipUui("UUIvalue");
 options.getCustomCallingContext().addSipX("sipHeaderName", "value");
@@ -174,7 +174,7 @@ options.customCallingContext = customCallingContext;
 const result = await callConnection.transferCallToParticipant(transferDestination, options);
 
 //Transfer a PSTN call to phone number and set UUI and custom SIP headers
-const transferDestination = { phoneNumber: "<taget_phoneNumber>" };
+const transferDestination = { phoneNumber: "<target_phoneNumber>" };
 const transferee = { phoneNumber: "<transferee_phoneNumber>" };
 const options = { transferee: transferee, operationContext: "<Your_context>", operationCallbackUrl: "<url_endpoint>" };
 const customCallingContext: CustomCallingContext = [];
@@ -188,27 +188,27 @@ const result = await callConnection.transferCallToParticipant(transferDestinatio
 ```python
 #Transfer to communication services user and include one VOIP header
 transfer_destination = CommunicationUserIdentifier("<user_id>")
-transferee = CommnunicationUserIdentifer("transferee_user_id")
+transferee = CommunicationUserIdentifier("transferee_user_id")
 voip_headers = {"customVoipHeader1", "customVoipHeaderValue1"}
 result = call_connection_client.transfer_call_to_participant(
     target_participant=transfer_destination,
     transferee=transferee,
     voip_headers=voip_headers,
-    opration_context="Your context",
+    operation_context="Your context",
     operationCallbackUrl="<url_endpoint>"
 )
 
 #Transfer a PSTN call to phone number and set UUI and custom SIP headers
-transfer_destination = PhoneNumberIdentifer("<target_phoneNumber>")
-transferee = PhoneNumberIdentifer("transferee_phoneNumber")
+transfer_destination = PhoneNumberIdentifier("<target_phoneNumber>")
+transferee = PhoneNumberIdentifier("transferee_phoneNumber")
 sip_headers={}
 sip_headers["X-MS-Custom-headerName"] = "headerValue"
 sip_headers["User-To-User"] = "uuivalue"
 result = call_connection_client.transfer_call_to_participant(
     target_participant=transfer_destination,
     transferee=transferee,
     sip_headers=sip_headers,
-    opration_context="Your context",
+    operation_context="Your context",
     operationCallbackUrl="<url_endpoint>"
 )
 ```

articles/communication-services/how-tos/call-automation/handle-events-with-event-processor.md

@@ -100,7 +100,7 @@ else
 ```
 
 > [!WARNING]
-> EventProcessor utilizes OperationContext to track event with its related request. If OperationContext was not set during request, EventProcessor will set generated GUID to track future events to the request. If you are setting your own OperationContext during reuest, EventProcessor will still work - but it's advised to set them differently from request to request, to allow EventProcessor to distinguish request 1's event and request 2's event.
+> EventProcessor utilizes OperationContext to track event with its related request. If OperationContext was not set during request, EventProcessor will set generated GUID to track future events to the request. If you are setting your own OperationContext during request, EventProcessor will still work - but it's advised to set them differently from request to request, to allow EventProcessor to distinguish request 1's event and request 2's event.
 
 ## Handling events with Ongoing EventProcessor
 
@@ -110,10 +110,10 @@ Some events could happen anytime during the call, such as CallDisconnected or Pa
 // Use your call automation client that established the call
 CallAutomationEventProcessor eventProcessor = callAutomationClient.GetEventProcessor();
 
-// attatch ongoing EventProcessor for this particular call,
+// attach ongoing EventProcessor for this particular call,
 // then prints out # of participants in the call
-eventProcessor.AttachOngoingEventProcessor<ParticipantsUpdated>(callConnectionId, recievedEvent => {
-    logger.LogInformation($"Number of participants in this Call: [{callConnectionId}], Number Of Participants[{recievedEvent.Participants.Count}]");
+eventProcessor.AttachOngoingEventProcessor<ParticipantsUpdated>(callConnectionId, receivedEvent => {
+    logger.LogInformation($"Number of participants in this Call: [{callConnectionId}], Number Of Participants[{receivedEvent.Participants.Count}]");
 });
 ```
 
@@ -130,7 +130,7 @@ If you would like to wait for specific event with given predicate without relyin
 // Use your call automation client that established the call
 CallAutomationEventProcessor eventProcessor = callAutomationClient.GetEventProcessor();
 
-// With given matching informations, wait for this specific event
+// With given matching information, wait for this specific event
 CallDisconnected disconnectedEvent = (CallDisconnected)await eventProcessor.WaitForEvent(predicate
 =>
     predicate.CallConnectionId == myConnectionId

articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-js.md

@@ -100,7 +100,7 @@ const playSource: SsmlSource = { ssmlText: ssmlToPlay, kind: "ssmlSource" };
 ### Custom voice models
 If you wish to enhance your prompts more and include custom voice models, the play action Text-To-Speech now supports these custom voices. These are a great option if you are trying to give customers a more local, personalized experience or have situations where the default models may not cover the words and accents you're trying to pronounce. To learn more about creating and deploying custom models you can read this [guide](/azure/ai-services/speech-service/how-to-custom-voice).
 
-**Custom voice names regular text exmaple**
+**Custom voice names regular text example**
 ``` javascript
 const textToPlay = "Welcome to Contoso";
 // Provide VoiceName and CustomVoiceEndpointID to play your custom voice

articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-python.md

@@ -175,7 +175,7 @@ call_automation_client.get_call_connection(call_connection_id).play_media(
 ### Custom voice models
 If you wish to enhance your prompts more and include custom voice models, the play action Text-To-Speech now supports these custom voices. These are a great option if you are trying to give customers a more local, personalized experience or have situations where the default models may not cover the words and accents you're trying to pronounce. To learn more about creating and deploying custom models you can read this [guide](/azure/ai-services/speech-service/how-to-custom-voice).
 
-**Custom voice names regular text exmaple**
+**Custom voice names regular text example**
 ``` python
 text_to_play = "Welcome to Contoso"