Merge pull request #310375 from MicrosoftDocs/main

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

Author: learn-build-service-prod[bot]

articles/application-gateway/application-gateway-ssl-policy-overview.md

@@ -5,7 +5,7 @@ services: application gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 07/23/2025
+ms.date: 01/12/2026
 ms.author: mbender
 #customer intent: As an IT administrator, I want to configure a TLS policy for the Application Gateway, so that I can centralize certificate management and ensure compliance with security standards while optimizing backend performance.
 ---
@@ -42,8 +42,8 @@ The following table shows the list of cipher suites and minimum protocol version
 | **Minimum Protocol Version** | 1.0 | 1.1 | 1.2 | 1.2 | 1.2 |
 | **Enabled protocol versions** | 1.0<br/>1.1<br/>1.2 | 1.1<br/>1.2 | 1.2 | 1.2<br/>1.3 | 1.2<br/>1.3 |
 | **Default** | True<br/>(for API version < 2023-02-01) | False | False | True<br/>(for API version >= 2023-02-01) | False |
-| TLS_AES_128_GCM_SHA256 | &cross; | &cross; | &cross; | &check; | &check; |
 | TLS_AES_256_GCM_SHA384 | &cross; | &cross; | &cross; | &check; | &check; |
+| TLS_AES_128_GCM_SHA256 | &cross; | &cross; | &cross; | &check; | &check; |
 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | &check; | &check; | &check; | &check; | &check; |
 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | &check; | &check; | &check; | &check; | &check; |
 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | &check; | &cross; | &cross; | &check; | &cross; |

articles/communication-services/concepts/telephony/direct-routing-infrastructure.md

@@ -69,7 +69,7 @@ Learn more:
 
 SBC pairing works on the Communication Services resource level. It means you can pair many SBCs to a single Communication Services resource. Still, you can't pair a single SBC to more than one Communication Services resource. Unique SBC FQDNs are required for pairing to different resources.
 
-If Mutual TLS (MTLS) support is enabled for the direct routing connection on the SBC, then you must install the Baltimore CyberTrust Root **and** the DigiCert Global Root G2 certificates in the SBC Trusted Root Store of the direct routing TLS context. (This is because the Microsoft service certificates use one of these two root certificates.) To download these root certificates, see [Office 365 Encryption chains](/microsoft-365/compliance/encryption-office-365-certificate-chains). For more information, see [Office TLS Certificate Changes](/microsoft-365/compliance/encryption-office-365-tls-certificates-changes).
+If Mutual TLS (MTLS) support is enabled for the Teams connection on the SBC, then you must install all the CAs listed under the 'Root Certificate Authorities' section in Azure Certificate Authority details page in the SBC Trusted Root Store of the Teams TLS context. (This is because the Microsoft service certificates use these root certificates).  To download the root certificates, see [Microsoft 365 Encryption chains](/microsoft-365/compliance/encryption-office-365-certificate-chains). For more information, see [Office TLS Certificate Changes](/microsoft-365/compliance/encryption-office-365-tls-certificates-changes).
 
 ## SIP Signaling: FQDNs 
 

articles/resource-mover/index.yml

@@ -20,8 +20,8 @@ landingContent:
         links:
           - text: What is Resource Mover
             url: ./overview.md
-          - text: Select a tool to move resources
-            url: ./select-move-tool.md
+          - text: Select options to move resources
+            url: ./select-options-to-move-resources.md
           - text: Common questions
             url: ./common-questions.md
 

articles/resource-mover/overview.md

@@ -49,7 +49,7 @@ After all dependencies are resolved, Resource Mover walks you through a simple m
 2. After the initial move, you can decide whether to commit and complete the move or discard the move.
 3. After the move is done you can decide whether you want to delete the resources in the source location.
 
-You can move resources across regions in the Resource Mover hub or from within a resource group. [Learn more](select-move-tool.md)
+You can move resources across regions in the Resource Mover hub or from within a resource group. [Learn more](select-options-to-move-resources.md)
 
 ## What resources can I move across regions?
 

…icles/resource-mover/select-move-tool.md …over/select-options-to-move-resources.mdarticles/resource-mover/select-move-tool.md renamed to articles/resource-mover/select-options-to-move-resources.md articles/resource-mover/select-move-tool.md renamed to articles/resource-mover/select-options-to-move-resources.md

@@ -11,21 +11,13 @@ ms.custom: mvc, engagement-fy23, UpdateFrequency.5
 # Customer intent: As an Azure administrator, I want to compare the available tools for moving resources across regions, so that I can select the most suitable option for efficiently relocating my Azure resources based on their dependencies and requirements.
 ---
 
-# Choose a tool for moving Azure resources
+# Options to move Azure resources
 
-You can move resources within Azure as follows:
+In this article, you can explore Azure options to move resources across regions, subscriptions,  clouds, and availability zones, and learn when to use each option.
 
-- **Move resources across regions**: Move resources from within the Resource Mover hub, or a resource group. 
-- **Move resources across resource groups/subscriptions**: Move from within a resource group. 
-- **Move resources between Azure clouds**: Use the Azure Site Recovery service to move resources between public and government clouds.
-- **Move resources between availability zones in the same region**: Use the Azure Site Recovery service to move resources between availability zones in the same Azure region.
-
-
-## Compare move tools
-
-| Tool | When to use| Learn more |
+| Options | When to use| Learn more |
 |----- | ---------- | ---------- |
-| **Move within resource group** | Move resources to a different resource group/subscription, or across regions.<br/><br/> If you move across regions, in the resource group you select the resources you want to move, and then you move to the Resource Mover hub, to verify dependencies and move the resources to the target region. | [Move resources to another resource group/subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).<br/><br/> [Move resources to another region from a resource group](move-region-within-resource-group.md). |
+| **Move from resource group overview** | Move resources to a different resource group/subscription, or across regions.<br/><br/> If you move across regions, in the resource group you select the resources you want to move, and then you move to the Resource Mover hub, to verify dependencies and move the resources to the target region. | [Move resources to another resource group/subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).<br/><br/> [Move resources to another region from a resource group](move-region-within-resource-group.md). |
 | **Move from the Resource Mover hub** | Move resources across regions. <br/><br/> You can move to a target region, or to a specific availability zone, or availability set, within the target region. | [Move resources across regions in the Resource Mover hub](). |
 | **Move VMs with Site Recovery** | Use it for moving Azure VMs between government and public clouds.<br/><br/> Use if you want to move VMs between availability zones in the same region. |[Move resources between government/public clouds](../site-recovery/region-move-cross-geos.md), [Move resources to availability zones in the same region](../site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md).|
 

articles/resource-mover/toc.yml

@@ -4,8 +4,8 @@
   items:
   - name: About Azure Resource Mover
     href: overview.md
-  - name: Select a tool to move resources
-    href: select-move-tool.md
+  - name: Select options to move resources
+    href: select-options-to-move-resources.md
   - name: Common questions
     href: common-questions.md
   - name: What's new

articles/sentinel/TOC.yml

@@ -325,12 +325,14 @@
               href: entity-pages.md
             - name: User and entity behavior analytics (UEBA)
               href: identify-threats-with-entity-behavior-analytics.md
+            - name: Aggregate behavioral insights from raw logs 
+              href: entity-behaviors-layer.md 
             - name: Create custom entity activities
               href: customize-entity-activities.md
         - name: Watchlists
           items:
             - name: Overview
-              href: watchlists.md
+              href: watchlists.md 
             - name: Create watchlists
               href: watchlists-create.md
             - name: Build queries or rules
@@ -716,10 +718,12 @@
               href: cef-syslog-ama-overview.md
             - name: CEF and Syslog via AMA
               href: connect-cef-syslog-ama.md
-            - name: CEF - configure security device
+            - name: Device configuration for CEF via AMA
               href: unified-connector-cef-device.md
             - name: Syslog - configure security device
               href: unified-connector-syslog-device.md
+            - name: Troubleshoot CEF and Syslog via AMA
+              href: cef-syslog-ama-troubleshooting.md  
         - name: Custom log sources (text files)
           items:
             - name: Collect logs from text files via AMA
@@ -1039,6 +1043,12 @@
           href: stix-objects-api.md
         - name: Legacy upload indicator API reference
           href: upload-indicators-api.md
+- name: Responsible AI
+  items:
+    - name: Responsible AI FAQ for UEBA behaviors layer
+      href: entity-behaviors-layer-rai-faqs.md
+    - name: Responsible AI FAQ for Microsoft Sentinel MCP
+      href: datalake/sentinel-mcp-responsible-ai-faq.md
 - name: Microsoft Sentinel blog
   href: https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/bg-p/MicrosoftSentinelBlog
 - name: Pricing