Merge pull request #310409 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-12 23:00 UTC

Author: Taojunshen

articles/artifact-signing/how-to-signing-integrations.md

@@ -118,14 +118,14 @@ For example:
 
 To download and install the Artifact Signing dlib package (a .zip file):
 
-1. Download the [Artifact Signing dlib package](https://www.nuget.org/packages/Microsoft.Trusted.Signing.Client).
+1. Download the [Artifact Signing dlib package](https://www.nuget.org/packages/Microsoft.ArtifactSigning.Client).
 
 1. Extract the Artifact Signing dlib zipped content and install it on your signing node in your choice of directory. The node must be the node where you use SignTool to sign files.
 
-Another option is to download the [Artifact Signing dlib package](https://www.nuget.org/packages/Microsoft.Trusted.Signing.Client) via NuGet similar like the Windows SDK Build Tools NuGet package:
+Another option is to download the [Artifact Signing dlib package](https://www.nuget.org/packages/Microsoft.ArtifactSigning.Client) via NuGet similar like the Windows SDK Build Tools NuGet package:
 
 ```powershell
-.\nuget.exe install Microsoft.Trusted.Signing.Client -x
+.\nuget.exe install Microsoft.ArtifactSigning.Client -x
 ```
 
 > [!NOTE]
@@ -223,4 +223,4 @@ You can also use the following tools or platforms to set up signing integrations
 
 - **Artifact Signing SDK**: To create your own signing integration, you can use our open-source [Artifact Signing SDK](https://www.nuget.org/packages/Azure.CodeSigning.Sdk). 
 
-- [**Azure.Developer.TrustedSigning.CryptoProvider**](https://www.nuget.org/packages/Azure.Developer.TrustedSigning.CryptoProvider): Simplifies integration of the service with a .NET crypto provider that abstracts the service endpoint integration from the consumer. 
+- [**Azure.Developer.ArtifactSigning.CryptoProvider**](https://www.nuget.org/packages/Azure.Developer.ArtifactSigning.CryptoProvider): Simplifies integration of the service with a .NET crypto provider that abstracts the service endpoint integration from the consumer. 

articles/azure-app-configuration/concept-snapshot-references.md

@@ -28,6 +28,18 @@ A snapshot reference is stored as a key-value whose value contains the name of t
 > [!NOTE]
 > You don't have to call a specialized API to opt into snapshot references. If you select the key-value that is a snapshot reference, resolution is automatic.
 
+## Creating a snapshot reference
+
+1. Open your App Configuration store in the Azure portal.
+2. Select **Configuration Explorer**.
+3. Choose **Create**.
+4. Select **Snapshot reference**.
+5. Enter a key for the reference. Optionally set a label.
+6. Choose the target snapshot name from the list (or enter it).
+7. Select **Create**.
+
+Once created, the snapshot reference appears alongside other key-values in Configuration Explorer.
+
 ## Consuming snapshot references
 
 No new code is required to use a snapshot reference. If the key for a snapshot reference is part of the selected key-values when building configuration, the provider automatically resolves and loads the referenced snapshot's key-values. Compare this to direct snapshot usage where you explicitly call an API such as `SelectSnapshot("SnapshotName")`, fixing the snapshot choice at startup so switching later requires a code change or redeployment.

articles/azure-functions/durable/durable-functions-azure-storage-provider.md

@@ -249,7 +249,7 @@ As an example, if `durableTask/extendedSessionIdleTimeoutInSeconds` is set to 30
 The specific effects of extended sessions on orchestrator and entity functions are described in the next sections.
 
 > [!NOTE]
-> In the .NET isolated model, the extended sessions feature is currently only supported in orchestrations (not entities). Additionally, this feature is available only for .NET languages such as C# and F#. Setting `extendedSessionsEnabled` to `true` for other platforms can lead to runtime issues, such as silently failing to execute activity and orchestration-triggered functions.
+> This feature is available only for .NET languages such as C# (isolated and in-process models) and F#. Setting `extendedSessionsEnabled` to `true` for other platforms can lead to runtime issues, such as silently failing to execute activity and orchestration-triggered functions.
 
 ### Orchestrator function replay
 

articles/communication-services/.openpublishing.redirection.communication-services.json

@@ -459,7 +459,7 @@
         },
         {
             "source_path_from_root": "/articles/communication-services/concepts/advanced-messaging/message-analysis.md",
-            "redirect_url": "/articles/communication-services/concepts/advanced-messaging/message-analysis/message-analysis.md",
+            "redirect_url": "/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-overview",
             "redirect_document_id": false
         },
         {
@@ -482,6 +482,21 @@
             "redirect_url": "/azure/communication-services/concepts/interop/teams-user-calling",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/communication-services/concepts/advanced-messaging/message-analysis/message-analysis-transparency-faq.md",
+            "redirect_url": "/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/communication-services/concepts/advanced-messaging/message-analysis/message-analysis.md",
+            "redirect_url": "/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/communication-services/quickstarts/advanced-messaging/message-analysis/message-analysis-with-azure-openai-quickstart.md",
+            "redirect_url": "/azure/communication-services/quickstarts/advanced-messaging/whatsapp/get-started",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/azure/communication-services/concepts/interop/tpe/teams-phone-extensibility-client-capabilities.md",
             "redirect_url": "/azure/communication-services/concepts/interop/tpe/teams-phone-extensibility-capabilities",

articles/communication-services/concepts/advanced-messaging/message-analysis/message-analysis-transparency-faq.md

@@ -33,7 +33,6 @@ This section summarizes features for integrating AI into Azure Communication mes
 
 ### Direct Integrations 
 
-- **[Advanced message analysis](../concepts/advanced-messaging/message-analysis/message-analysis.md)**: The Azure Communication Services messaging APIs for WhatsApp provide a built-in integration with Azure OpenAI that analyzes and annotates messages. This integration can detect the user's language, recognize their intent, and extract key phrases. 
 - **[Azure Bot Service: Chat channel integration](../quickstarts/chat/quickstart-botframework-integration.md)**: The Azure Communication Services chat system is directly integrated with Azure Bot Service. This integration simplifies creating chat bots that engage with human users.
 
 ### Accessors

articles/communication-services/concepts/advanced-messaging/message-analysis/message-analysis.md

@@ -64,7 +64,22 @@ To send SMS, you must have a sender ID—this can be a phone number or an alphan
 
 \* For detailed formatting requirements, see [Alphanumeric sender ID FAQ](./sms-faq.md#alphanumeric-sender-id) .
 
-## Sender Type Availability by Country (destination)
+## Sender Type Availability by Country/Region
+
+> [!IMPORTANT]
+> **Sender geographic scope**
+>
+> SMS senders are **country/region-scoped**. A sender can deliver messages only within the country/region (or countries/regions) for which it was provisioned, enabled, or approved.
+>
+> - **Short Codes:**  
+>   US Short Codes send SMS only to the **United States and Puerto Rico**. Short Codes in all other countries/regions can send SMS **only within the country/region where they were obtained**.
+>
+> - **All other sender types** (Toll-Free numbers, 10-digit long codes, mobile numbers, and Alphanumeric Sender IDs) can send SMS **only to the countries/regions where they are purchased, enabled, or registered**.
+>
+> Cross-country/region SMS delivery using a single sender is not supported. For multi-country/region messaging, you can use [Messaging Connect](../sms/messaging-connect.md).
+
+
+
 
 | Supported Destinations           | Toll-Free | Short Code | 10DLC | Mobile Number | Dynamic Alpha | Prereg. Alpha |
 |------------------|-----------|------------|-------|----------------|----------------|----------------|