Merge pull request #308704 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/api-management/api-management-policy-expressions.md

@@ -142,7 +142,7 @@ The following table lists the .NET Framework types and members allowed in policy
 |`System.Security.Cryptography.SHA384Managed`|All|
 |`System.Security.Cryptography.SHA512`|All|
 |`System.Security.Cryptography.SHA512Managed`|All|
-|`System.Security.Cryptography.SymmetricAlgorithm`|All|
+|`System.Security.Cryptography.SymmetricAlgorithm`|All except parameterless `Create()`|
 |`System.Security.Cryptography.X509Certificates.PublicKey`|All|
 |`System.Security.Cryptography.X509Certificates.RSACertificateExtensions`|All|
 |`System.Security.Cryptography.X509Certificates.X500DistinguishedName`|`Name`|

articles/azure-functions/functions-bindings-web-pubsub.md

@@ -75,7 +75,7 @@ By default, an application setting named `WebPubSubConnectionString` is used to
 For details on how to configure and use Web PubSub and Azure Functions together, refer to [Tutorial: Create a serverless notification app with Azure Functions and Azure Web PubSub service](../azure-web-pubsub/tutorial-serverless-notification.md).
 ::: zone pivot="programming-language-csharp"
 > [!NOTE]
-> When running in the isolated worker model, the Azure Web PubSub binding doesn't currently support Microsoft Entra ID authetication using managed identities. In the isolated model, you must continue to use a connection string, which includes a shared secret key.
+> When running in the isolated worker model, the Azure Web PubSub binding doesn't currently support Microsoft Entra ID authentication using managed identities. In the isolated model, you must continue to use a connection string, which includes a shared secret key.
 ::: zone-end
 ## Next steps
 

articles/azure-functions/opentelemetry-howto.md

@@ -103,15 +103,15 @@ Examples in this article assume your app uses `IHostApplicationBuilder`, which i
     ### [Application Insights](#tab/app-insights)
 
     ```cmd
-    dotnet add package Microsoft.Azure.Functions.Worker.OpenTelemetry --version  1.1.0-preview6
+    dotnet add package Microsoft.Azure.Functions.Worker.OpenTelemetry
     dotnet add package OpenTelemetry.Extensions.Hosting 
     dotnet add package Azure.Monitor.OpenTelemetry.Exporter  
     ```
 
     ### [OTLP Exporter](#tab/otlp-export) 
 
     ```cmd
-    dotnet add package Microsoft.Azure.Functions.Worker.OpenTelemetry --version 1.1.0-preview6
+    dotnet add package Microsoft.Azure.Functions.Worker.OpenTelemetry
     dotnet add package OpenTelemetry.Extensions.Hosting 
     dotnet add package OpenTelemetry.Exporter.OpenTelemetryProtocol   
     ```

articles/backup/troubleshoot-azure-files.md

@@ -315,7 +315,7 @@ Recommended Actions: Ensure that the following configurations in the storage acc
 
 **Error message**: Storage account does not support key based authentication required for Azure Backup integration.
 
-**Recommended action**: Enable storage key based authentication on storage account and the retry opertaion.
+**Recommended action**: Enable storage key based authentication on storage account and the retry operation.
 
 ## Common policy modification errors
 

articles/container-apps/sessions.md

@@ -78,9 +78,10 @@ Dynamic sessions are available in the following regions:
 | Region | Code interpreter | Custom container |
 |--------|------------------|------------------|
 | Australia East | ✔ | ✔ |
-| Brazil South | - | ✔ |
-| Canada Central | ✔ | - |
-| Canada East | - | ✔ |
+| Brazil South | ✔ | ✔ |
+| Canada Central | ✔ | ✔ |
+| Canada East | ✔ | ✔ |
+| Central US | ✔ | ✔ |
 | East Asia | ✔ | ✔ |
 | East US | ✔ | ✔ |
 | East US 2 | ✔ | ✔ |