Merge pull request #310584 from MicrosoftDocs/main

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

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

articles/backup/backup-azure-about-mars.md

@@ -2,7 +2,7 @@
 title: About the MARS Agent
 description: Learn how the MARS Agent supports the backup scenarios
 ms.topic: overview
-ms.date: 02/28/2025
+ms.date: 01/16/2026
 ms.service: azure-backup
 ms.custom: engagement-fy24
 author: AbhishekMallick-MS
@@ -14,7 +14,7 @@ ms.author: v-mallicka
 
 Azure Backup uses the Microsoft Azure Recovery Services (MARS) agent to back up and recover files, folders, and the volume or system state from an on-premises computer to Azure.
 
-## Backup scenarios
+## Backup scenarios for MARS agent
 
 The MARS agent supports the following backup scenarios:
 
@@ -32,7 +32,7 @@ The MARS agent supports the following backup scenarios:
 
 - **Offline seeding**: Initial full backups of data to Azure typically transfer large amounts of data and require more network bandwidth. Subsequent backups transfer only the delta, or incremental, amount of data. Azure Backup compresses the initial backups. Through the process of *offline seeding*, Azure Backup can use disks to upload the compressed initial backup data offline to Azure. For more information, see [Azure Backup offline-backup using Azure Data Box](offline-backup-azure-data-box.md).
 
-## Recovery scenarios
+## Recovery scenarios for MARS agent
 
 The MARS agent supports the following recovery scenarios:
 
@@ -49,7 +49,7 @@ The MARS agent supports the following recovery scenarios:
 |   | **Volume Level** | Choose the volume and recovery point that you want to restore to another location. Create a copy of existing files, overwrite existing files, or skip recovering existing files. |
 |   | **System Level** | Choose the system state and recovery point to restore as a System State file to an alternate machine. |
 
-## Backup process
+## Backup process for MARS agent
 
 To back up files, folders, and the volume or system state from an on-premises computer to Azure using Microsoft Azure Recovery Services (MARS) agent:
 

articles/backup/backup-azure-sql-database.md

@@ -2,7 +2,7 @@
 title: Back up SQL Server databases to Azure 
 description: This article explains how to back up SQL Server to Azure. The article also explains SQL Server recovery.
 ms.topic: overview
-ms.date: 12/09/2025
+ms.date: 01/16/2026
 author: AbhishekMallick-MS
 ms.author: v-mallicka
 # Customer intent: "As a database administrator, I want to implement SQL Server backups to Azure, so that I can ensure reliable data recovery and minimize downtime in case of data loss."
@@ -19,7 +19,7 @@ ms.author: v-mallicka
 To view the backup and restore scenarios that we support today, see the [support matrix](sql-support-matrix.md#scenario-support).
 
 >[!Note]
->Private Preview for Snapshot based backup is now available! Snapshot based backup will help you backup large sized databases in a performant way and will also ensure faster restores from instant restore tier. To enroll in the private preview or know more about the feature, reach out to [email protected].
+>Private Preview for Snapshot based backup is now available! Snapshot based backup will help you backup large sized databases in a performant way and will also ensure faster restores from instant restore tier.
 
 ## Backup process
 

articles/data-factory/connector-amazon-redshift.md

@@ -6,7 +6,7 @@ ms.author: jianleishen
 author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
-ms.date: 12/29/2025
+ms.date: 01/15/2026
 ms.custom:
   - synapse
   - sfi-image-nochange
@@ -19,7 +19,7 @@ ms.custom:
 This article outlines how to use the Copy Activity in Azure Data Factory and Synapse Analytics pipelines to copy data from an Amazon Redshift. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 
 > [!IMPORTANT]
-> The Amazon Redshift version 2.0 provides improved native Amazon Redshift support. If you are using the Amazon Redshift version 1.0 in your solution, please [upgrade your Amazon Redshift connector](#upgrade-the-amazon-redshift-connector) as version 1.0 is at [End of Support stage](connector-release-stages-and-timelines.md). Your pipeline will fail after **March 31, 2026**. Refer to this [section](#differences-between-amazon-redshift-connector-version-20-and-version-10) for details on the difference between version 2.0 and version 1.0.
+> The Amazon Redshift version 2.0 provides improved native Amazon Redshift support. If you are using the Amazon Redshift version 1.0 in your solution, please [upgrade your Amazon Redshift connector](#upgrade-the-amazon-redshift-connector) before **March 31, 2026**. Refer to this [section](#differences-between-amazon-redshift-connector-version-20-and-version-10) for details on the difference between version 2.0 and version 1.0.
 
 ## Supported capabilities
 

articles/sentinel/whats-new.md

@@ -41,6 +41,15 @@ UEBA behaviors can be enabled independently from UEBA anomaly detection.
 
 For more information, see [Translate raw security logs to behavioral insights using UEBA behaviors in Microsoft Sentinel](../sentinel/entity-behaviors-layer.md).
 
+### New detections for Sentinel solution for SAP BTP
+
+This update expands [detection coverage for SAP BTP](../sentinel/sap/sap-btp-security-content.md#built-in-analytics-rules), strengthening visibility into high‑risk control plane, integration, and identity activities.
+
+- **SAP Integration Suite**: Detects unauthorized changes to integration artifacts, access policies, JDBC data sources, and package imports that could enable data exfiltration or backdoors.
+- **SAP Cloud Identity Service**: Monitors user deletions, privilege grants, and SAML/OIDC configuration changes that weaken authentication controls or create persistent access.
+- **SAP Build Work Zone**: Identifies mass role deletions and unauthorized access to restricted portal resources.
+- **SAP BTP Audit Logging**: Detects audit log ingestion gaps and disruptions that reduce security visibility and enable stealthy activity.
+
 ## November 2025
 
 ### New Entity Behavior Analytics (UEBA) experiences in the Defender portal (Preview)

articles/service-bus-messaging/overview-emulator.md

@@ -31,7 +31,7 @@ The emulator provides these features:
 
 - **Containerized deployment**: It runs as a Docker container (Linux based).
 - **Cross-platform compatibility**: You can use it on any platform, including Windows, macOS, and Linux.
-- **Configurability**: You can manage the number of Service bus entities by using the JSON supplied configuration.
+- **Configurability**: You can manage the number of Service bus entities by using the ServiceBus administration client or JSON supplied configuration.
 - **Streaming support**: It supports streaming messages by using the Advanced Message Queuing Protocol (AMQP).
 - **Observability**: It provides observability features, including console and file logging.
 
@@ -41,7 +41,6 @@ The current version of the emulator has the following limitations:
 
 - It can't stream messages by using the JMS protocol.
 - Partitioned entities aren't compatible with emulator. 
-- It doesn't support on-the-fly management operations through a client-side SDK.
 - AMQP Web Sockets are not supported. AMQP TCP is the only supported transport type.
 
 > [!NOTE]
@@ -85,16 +84,18 @@ Like the Service bus cloud service, the emulator provides the following quotas f
 
 
 
-## Quota configuration changes
+## Create and manage entities within Service Bus emulator
 
-By default, the emulator runs with the [config.json](https://github.com/Azure/azure-service-bus-emulator-installer/blob/main/ServiceBus-Emulator/Config/Config.json) configuration file. You can configure the quotas associated with Service bus by editing this file in the following ways, based on your needs:
+You can create and manage Service Bus entities—such as queues and topics—using the Service Bus [Administration Client](service-bus-management-libraries.md). By default, the emulator runs with the [config.json](https://github.com/Azure/azure-service-bus-emulator-installer/blob/main/ServiceBus-Emulator/Config/Config.json) configuration file. You can also make declarative changes to the configuration file as per your needs:
 
 - **Entities**: You can add more Service bus entities in accordance with the supported quotas. 
 - **Logging**: The emulator supports logging on a console, in a file, or both. You can choose according to your personal preference.
 
 > [!IMPORTANT]
 > You must supply any changes in JSON configuration before you run the emulator. Changes aren't honored on the fly. For changes to take effect, you must restart the container.
->
+> 
+> At emulator initialization, settings defined in the configuration file override any entities previously created or modified using the Service Bus Administration Client.
+> 
 > You can't rename the preset namespace (`name`) in the configuration file.
 
 ## Logs for debugging
@@ -107,3 +108,5 @@ During testing, console or file logs help you debug unexpected failures. To revi
 ## Related content
 
 [Test locally by using the Azure Service Bus emulator](test-locally-with-service-bus-emulator.md)
+
+[Service Bus emulator Samples](https://github.com/Azure/azure-service-bus-emulator-installer/tree/main/Sample-Code-Snippets)

articles/service-bus-messaging/service-bus-emulator-whats-new.md

@@ -18,9 +18,16 @@ This article provides a detailed overview of the enhancements introduced in the
 >
 > Kindly report any problems or suggestions in the emulator's [GitHub installer repository](https://github.com/Azure/azure-service-bus-emulator-installer/issues).
 
-## Latest version ``1.1.2``
+## Latest version ``2.0.0``
 
-> *Released March 11th, 2025*
+> *Released January 16th, 2026*
+
+- Provides native .NET Administration Client support in the Service Bus emulator  
+
+## Previous releases
+
+
+### ``1.1.2`` (11th March,2025)
 
 This release introduces new features, bug fixes for Service Bus emulator. The details are as follows:
 
@@ -30,7 +37,6 @@ This release introduces new features, bug fixes for Service Bus emulator. The de
 - Added support for updating LockDuration to a minimum of 5 seconds.
 - Other bug fixes.
 
-## Previous releases
 
 ### ``1.0.1`` (19th November,2024)
 

articles/service-bus-messaging/test-locally-with-service-bus-emulator.md

@@ -226,11 +226,12 @@ When you use Docker, the service bus emulator is fetched from the [Microsoft Con
         - "${CONFIG_PATH}:/ServiceBus_Emulator/ConfigFiles/Config.json"
       ports:
         - "5672:5672"
-        - "5300:5300"
+        - "5300:${EMULATOR_HTTP_PORT:-5300}"
       environment:
         SQL_SERVER: mssql
         MSSQL_SA_PASSWORD: "${MSSQL_SA_PASSWORD}"  # Password should be same as what is set for SQL Server Linux 
         ACCEPT_EULA: ${ACCEPT_EULA}
+        EMULATOR_HTTP_PORT: ${EMULATOR_HTTP_PORT:-5300}
         SQL_WAIT_INTERVAL: ${SQL_WAIT_INTERVAL} # Optional: Time in seconds to wait for SQL to be ready (default is 15 seconds)
       depends_on:
         - mssql
@@ -269,6 +270,9 @@ When you use Docker, the service bus emulator is fetched from the [Microsoft Con
     
     # 3. MSSQL_SA_PASSWORD to be filled by user as per policy
     MSSQL_SA_PASSWORD=""
+
+    # 4. Port on which emulator will expose Management & Health-check APIs
+    EMULATOR_HTTP_PORT=5300
     ```
     
     > [!IMPORTANT]
@@ -304,9 +308,11 @@ You can verify the containers are running by checking Docker Desktop or using th
 
 ## Interact with the emulator
 
-By default, emulator uses [config.json](https://github.com/Azure/azure-service-bus-emulator-installer/blob/main/ServiceBus-Emulator/Config/Config.json) configuration file. You can configure entities by making changes to configuration file. To know more, visit [make configuration changes](overview-emulator.md#quota-configuration-changes)
+You can create and manage Service Bus entities—such as queues and topics—using the Service Bus [Administration Client](service-bus-management-libraries.md). By default, emulator uses [config.json](https://github.com/Azure/azure-service-bus-emulator-installer/blob/main/ServiceBus-Emulator/Config/Config.json) configuration file. You can also configure entities by making declarative changes to configuration file. To know more, visit [create and manage entities within Service Bus emulator](overview-emulator.md#create-and-manage-entities-within-service-bus-emulator) 
+
+### Choosing the right connection string
 
-You can use the following connection string to connect to the Service Bus emulator:
+The Service Bus emulator uses a static connection string, but the host value varies depending on how your application is deployed relative to the emulator. Use the appropriate connection string for your setup:
 
  - When the emulator container and interacting application are running natively on local machine, use following connection string:
 
@@ -332,6 +338,16 @@ You can use the following connection string to connect to the Service Bus emulat
     "Endpoint=sb://host.docker.internal;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;"
     ```
 
+> [!IMPORTANT]
+> By default, management operations using the Service Bus Administration Client require appending the **port number** to the emulator connection string. For example, when both the emulator and the application are running on the same machine, use the following connection string for administration operations:
+>  ```
+> "Endpoint=sb://localhost:5300;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;";
+>  ```
+> For management operations, the emulator uses port 5300 by default. You can configure the emulator to use a different port if required. Refer to know [more](https://github.com/Azure/azure-service-bus-emulator-installer?tab=readme-ov-file#interacting-with-the-emulator).
+> 
+> For the Service Bus Emulator, creating and managing entities via the Service Bus Administration client is natively supported only in .NET.
+>
+> 
 You can use the latest client SDKs to interact with the Service Bus emulator across various programming languages. To get started, refer to the [Service Bus emulator samples on GitHub](https://github.com/Azure/azure-service-bus-emulator-installer/tree/main/Sample-Code-Snippets/NET/ServiceBus.Emulator.Console.Sample).
 
 ## Related content

articles/site-recovery/toc.yml

@@ -12,7 +12,7 @@
     items:
     - name: Azure to Azure - Costs
       href: site-recovery-cost.md
-    - name: Estimate cost
+    - name: About Azure Site Recovery deployment planner
       href: deployment-planner-cost-estimation.md
 - name: What's New
   items: