Merge pull request #310651 from MicrosoftDocs/main

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

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

articles/azure-netapp-files/migrate-data.md

@@ -5,7 +5,7 @@ ms.service: azure-netapp-files
 ms.topic: conceptual
 author: b-ahibbard
 ms.author: anfdocs
-ms.date: 09/04/2025
+ms.date: 01/20/2026
 ---
 # Migrating data into Azure NetApp Files volumes
 
@@ -15,9 +15,10 @@ Azure NetApp Files supports several methods to migrate data. You can migrate dat
 
 The Azure NetApp Files [migration assistant](migrate-volumes.md) feature helps you accelerate and simplify migrations of business-critical applications and data to Azure. Benefits include:
 
-* Efficient and cost-effective data migration leveraging ONTAP's built-in replication engine for seamless transition from on-premises or Cloud Volumes ONTAP storage to Azure NetApp Files. 
-* Storage-efficient data transfer that reduces network transfer costs for both baseline and incremental updates. 
-* Low cutover/downtime window, ensuring faster and more efficient final updates, thus minimizing disruption to your operations.
+* Efficient, cost-effective migration powered by ONTAP’s built-in replication engine for a seamless transition from on-premises or Cloud Volumes ONTAP to Azure NetApp Files.
+* Storage-optimized data migration that lowers network costs for both baseline and incremental updates.
+* Minimal cutover window for faster final syncs, reducing downtime and keeping your business running smoothly.
+* Existing volume snapshots included to safeguard data integrity and reduce risk, delivering a reliable and worry-free migration experience.
 
 To use Azure NetApp Files migration assistant, you need to establish connectivity between your on-premises storage cluster and the target volume in your Azure NetApp Files region of choice. For detailed instructions, see [Migrate volumes to Azure NetApp Files](migrate-volumes.md).
 
@@ -41,4 +42,4 @@ To migrate data from one Azure region to another Azure region, use [Azure NetApp
 * [Migrate volumes to Azure NetApp Files](migrate-volumes.md)
 * [Azure NetApp Files replication](replication.md)
 * [Data migration and protection FAQs for Azure NetApp Files](faq-data-migration-protection.md)
- 
+ 

articles/azure-netapp-files/replication-requirements.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 01/08/2026
+ms.date: 01/20/2026
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -70,8 +70,6 @@ If you use [cross-zone-region replication](replication.md#cross-zone-region-repl
 
 * You can revert a source or destination volume of a cross-region replication to a snapshot if the snapshot is newer than the most recent SnapMirror snapshot. You can't use snapshots that are older than the SnapMirror snapshot for a volume revert operation. For more information, see [Revert a volume by using snapshot revert](snapshots-revert-volume.md).
 
-* You can revert a source or destination volume of a cross-region replication to a snapshot if the snapshot is newer than the most recent SnapMirror snapshot. You can't use snapshots that are older than the SnapMirror snapshot for a volume revert operation. For more information, see [Revert a volume by using snapshot revert](snapshots-revert-volume.md).
-
 * If you copy large datasets into a volume that has cross-region replication enabled and you have spare capacity in the capacity pool, you should set the replication interval to 10 minutes, increase the volume size to allow for the changes to be stored, and temporarily disable replication.
 
 * If you use the cool access feature, understand the considerations in [Manage Azure NetApp Files storage with cool access](manage-cool-access.md#considerations).

articles/backup/quick-backup-postgresql-flexible-server-terraform.md

@@ -31,7 +31,7 @@ Before you configure backup for Azure Database for PostgreSQL - Flexible Server,
   >[!Note]
   >Terraform only supports authenticating to Azure with the Azure CLI. Authenticating using Azure PowerShell isn't supported. Therefore, while you can use the Azure PowerShell module when doing your Terraform work, you first need to authenticate to Azure.
 
-## Implement the Terraform code
+## Implement the Terraform code for PostgreSQL Flexible Server backup configuration
 
 > [!NOTE]
 > See more [articles and sample code showing how to use Terraform to manage Azure resources](/azure/terraform).
@@ -227,15 +227,15 @@ variable "retention_duration_in_months" {
 ```
 
 
-## Initialize Terraform
+## Initialize Terraform for PostgreSQL Flexible Server backup
 
 [!INCLUDE [terraform-init.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-init.md)]
 
-## Create a Terraform execution plan
+## Create a Terraform execution plan for PostgreSQL Flexible Server backup
 
 [!INCLUDE [terraform-plan.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-plan.md)]
 
-## Apply a Terraform execution plan
+## Apply a Terraform execution plan for PostgreSQL Flexible Server backup
 
 [!INCLUDE [terraform-apply-plan.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-apply-plan.md)]
 

articles/data-factory/connector-amazon-rds-for-sql-server.md

@@ -6,7 +6,7 @@ ms.author: jianleishen
 author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
-ms.date: 06/17/2024
+ms.date: 12/31/2025
 ms.custom:
   - synapse
   - sfi-image-nochange
@@ -495,6 +495,51 @@ If the table has physical partition, you would see "HasPartition" as "yes" like
 
 :::image type="content" source="./media/connector-azure-sql-database/sql-query-result.png" alt-text="Sql query result":::
 
+## Data type mapping for Amazon RDS for SQL Server
+
+When copying data from Amazon RDS for SQL Server, the following mappings are used from Amazon RDS for SQL Server data types to interim data types used by the service internally. See [Schema and data type mappings](copy-activity-schema-and-type-mapping.md) to learn about how copy activity maps the source schema and data type to the sink.
+
+| Amazon RDS for SQL Server data type | Interim service data type |
+| ------ | ------ |
+| bigint | Int64 |
+| binary | Byte[] |
+| bit | Boolean |
+| char | String, Char[] |
+| date | DateTime |
+| Datetime | DateTime |
+| datetime2 | DateTime |
+| Datetimeoffset | DateTimeOffset |
+| Decimal | Decimal |
+| FILESTREAM attribute (varbinary(max)) | Byte[] |
+| Float | Double |
+| image | Byte[] |
+| int | Int32 |
+| money | Decimal |
+| nchar | String, Char[] |
+| ntext | String, Char[] |
+| numeric | Decimal |
+| nvarchar | String, Char[] |
+| real | Single |
+| rowversion | Byte[] |
+| smalldatetime | DateTime |
+| smallint | Int16 |
+| smallmoney | Decimal |
+| sql_variant | Object |
+| text | String, Char[] |
+| time | TimeSpan |
+| timestamp | Byte[] |
+| tinyint | Int16 |
+| uniqueidentifier | Guid |
+| varbinary | Byte[] |
+| varchar | String, Char[] |
+| xml | String |
+
+>[!NOTE]
+> For data types that map to the Decimal interim type, currently Copy activity supports precision up to 28. If you have data that requires precision larger than 28, consider converting to a string in a SQL query.  
+>
+> When copying data from Amazon RDS for SQL Server using Azure Data Factory, the bit data type is mapped to the Boolean interim data type. If you have data that need to be kept as the bit data type, use queries with [T-SQL CAST or CONVERT](/sql/t-sql/functions/cast-and-convert-transact-sql?view=sql-server-ver15&preserve-view=true). 
+
+
 ## Lookup activity properties
 
 To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).

articles/data-factory/connector-azure-cosmos-db-mongodb-api.md

@@ -6,7 +6,7 @@ ms.author: jianleishen
 author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
-ms.date: 01/05/2024
+ms.date: 12/25/2025
 ms.custom:
   - synapse
   - sfi-image-nochange
@@ -266,6 +266,28 @@ After copy activity execution, below BSON ObjectId is generated in sink:
 }
 ``` 
 
+## Data type mapping for Azure Cosmos DB for MongoDB
+
+When copying data from Azure Cosmos DB for MongoDB, the following mappings are used from Azure Cosmos DB for MongoDB data types to interim data types used by the service internally. See [Schema and data type mappings](copy-activity-schema-and-type-mapping.md) to learn about how copy activity maps the source schema and data type to the sink.
+
+| Azure Cosmos DB for MongoDB data type | Interim service data type |
+| ------ | ------ |
+| Date | Int64 |
+| ObjectId | String |
+| Decimal128 | String |
+| TimeStamp | The most significant 32 bits -> Int64<br>The least significant 32 bits -> Int64 |
+| String | String |
+| Double | Double |
+| Int32 | Int64 |
+| Int64 | Int64 |
+| Boolean | Boolean |
+| Null | Null |
+| JavaScript | String |
+| Regular Expression | String |
+| Min key | Int64 |
+| Max key | Int64 |
+| Binary | String |
+
 ## Related content
 
 For a list of data stores that Copy Activity supports as sources and sinks, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).

articles/data-factory/connector-mongodb-atlas.md

@@ -6,7 +6,7 @@ author: jianleishen
 ms.author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
-ms.date: 09/20/2023
+ms.date: 12/25/2025
 ms.custom:
   - synapse
   - sfi-image-nochange
@@ -247,5 +247,27 @@ To achieve such schema-agnostic copy, skip the "structure" (also called *schema*
 
 To copy data from MongoDB Atlas to tabular sink or reversed, refer to [schema mapping](copy-activity-schema-and-type-mapping.md#schema-mapping).
 
+## Data type mapping for MongoDB Atlas
+
+When copying data from MongoDB Atlas, the following mappings are used from MongoDB Atlas data types to interim data types used by the service internally. See [Schema and data type mappings](copy-activity-schema-and-type-mapping.md) to learn about how copy activity maps the source schema and data type to the sink.
+
+| MongoDB Atlas data type | Interim service data type |
+| ------ | ------ |
+| Date | String |
+| ObjectId | String |
+| Decimal128 | String |
+| TimeStamp | The most significant 32 bits -> Int64<br>The least significant 32 bits -> Int64 |
+| String | String |
+| Double | String |
+| Int32 | String |
+| Int64 | String |
+| Boolean | Boolean |
+| Null | Null |
+| JavaScript | String |
+| Regular Expression | String |
+| Min key | Int64 |
+| Max key | Int64 |
+| Binary | String |
+
 ## Related content
 For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).