Merge pull request #267108 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-monitor/app/convert-classic-resource.md

@@ -295,10 +295,9 @@ If you don't wish to have your classic resource automatically migrated to a work
 
 ### Is there any implication on the cost from migration?
 
-There's usually no difference, with a couple of exceptions:
+There's usually no difference, with one exeception - Application Insights resources that were receiving 1 GB per month free via legacy Application Insights pricing model will no longer receive the free data.
 
- - Migrated Application Insights resources can use [Log Analytics commitment tiers](../logs/cost-logs.md#commitment-tiers) to reduce cost if the data volumes in the workspace are high enough.
- - Grandfathered Application Insights resources no longer get 1 GB per month free from the original Application Insights pricing model.
+The migration to workspace-based Application Insights offers a number of options to further [optimize cost](../logs/cost-logs.md), including [Log Analytics commitment tiers](../logs/cost-logs.md#commitment-tiers), [dedicated clusters](../logs/cost-logs.md#dedicated-clusters), and [basic logs](../logs/cost-logs.md#basic-logs).  
 
 ### How will telemetry capping work?
 
@@ -344,7 +343,7 @@ To avoid this issue, make sure to use the latest version of the Terraform [azure
 
 For backwards compatibility, calls to the old API for creating Application Insights resources will continue to work. Each of these calls will eventually create both a workspace-based Application Insights resource and a Log Analytics workspace to store the data.
 
-We strongly encourage updating to the [new API](https://learn.microsoft.com/azure/azure-monitor/app/resource-manager-app-resource) for better control over resource creation.
+We strongly encourage updating to the [new API](resource-manager-app-resource.md) for better control over resource creation.
 
 ### Should I migrate diagnostic settings on classic Application Insights before moving to a workspace-based AI?
 Yes, we recommend migrating diagnostic settings on classic Application Insights resources before transitioning to a workspace-based Application Insights. It ensures continuity and compatibility of your diagnostic settings.

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

@@ -2,7 +2,7 @@
 title: Azure Communication Services Call Automation how-to for passing call contextual data in Call Automation 
 titleSuffix: An Azure Communication Services how-to document
 description: Provides a how-to guide for passing contextual information with Call Automation.
-author: juta
+author: jutik0
 ms.topic: how-to
 ms.service: azure-communication-services
 ms.subservice: call-automation
@@ -34,7 +34,7 @@ For all the code samples, `client` is CallAutomationClient object that can be cr
 ## Technical parameters
 Call Automation supports up to 5 custom SIP headers and 1000 custom VOIP headers. Additionally, developers can include a dedicated User-To-User header as part of SIP headers list.
 
-The custom SIP header key must start with a mandatory ‘X-MS-Custom-’ prefix.  The maximum length of a SIP header key is 64 chars, including the X-MS-Custom prefix. The maximum length of SIP header value is 256 chars. The same limitations apply when configuring the SIP headers on your SBC.
+The custom SIP header key must start with a mandatory ‘X-MS-Custom-’ prefix.  The maximum length of a SIP header key is 64 chars, including the X-MS-Custom prefix. The SIP header key may consist of alphanumeric characters and a few selected symbols which includes ".", "!", "%", "\*", "_", "+", "~", "-". The maximum length of SIP header value is 256 chars. The same limitations apply when configuring the SIP headers on your SBC. The SIP header value may consist of alphanumeric characters and a few selected symbols which includes "=", ";", ".", "!", "%", "*", "_", "+", "~", "-".
 
 The maximum length of a VOIP header key is 64 chars. These headers can be sent without ‘x-MS-Custom’ prefix. The maximum length of VOIP header value is 1024 chars.