Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into esanMain

Author: roygara

articles/active-directory-b2c/partner-onfido.md

@@ -22,17 +22,6 @@ Known issues and limitations that are associated with online migrations from SQL
 
 ## Backup requirements
 
-- **Backups with checksum**
-
-    Azure Database Migration Service uses the backup and restore method to migrate your on-premises databases to SQL Managed Instance. Azure Database Migration Service only supports backups created using checksum.
-
-    [Enable or Disable Backup Checksums During Backup or Restore (SQL Server)](/sql/relational-databases/backup-restore/enable-or-disable-backup-checksums-during-backup-or-restore-sql-server).
-
-    > [!NOTE]
-    > If you take the database backups with compression, the checksum is a default behavior unless explicitly disabled.
-
-    With offline migrations, if you choose **I will let Azure Database Migration Service…**, then Azure Database Migration Service will take the database backup with the checksum option enabled.
-
 - **Backup media**
 
     Make sure to take every backup on a separate backup media (backup files). Azure Database Migration Service doesn't support backups that are appended to a single backup file. Take full backup and log backups to separate backup files.

articles/dms/known-issues-azure-sql-db-managed-instance-online.md

@@ -65,13 +65,6 @@ Known issues and limitations associated with the Azure SQL Migration extension f
 - **Recommendation**: Ensure the database backups in your Azure Storage container are correct. If you're using network file share, there might be network related issues and lags that are causing this error. Wait for the process to complete.  
 
 
-- **Message**: `Migration for Database <DatabaseName> failed with error 'Full backup <URL of backup in Azure Storage container> is missing checksum. Provide full backup with checksum.'.`
-
-- **Cause**: The database backups haven't been taken with checksum enabled.
-
-- **Recommendation**: See [Enable or disable backup checksums during backup or restore (SQL Server)](/sql/relational-databases/backup-restore/enable-or-disable-backup-checksums-during-backup-or-restore-sql-server) for taking backups with checksum enabled.  
-
-
 - **Message**: `Migration for Database <Database Name> failed with error 'Non retriable error occurred while restoring backup with index 1 - 3234 Logical file <Name> isn't part of database <Database GUID>. Use RESTORE FILELISTONLY to list the logical file names. RESTORE DATABASE is terminating abnormally.'.`
 
 - **Cause**: You've specified a logical file name that isn't in the database backup.

articles/dms/known-issues-azure-sql-migration-azure-data-studio.md

@@ -64,7 +64,6 @@ Pre-requisites that are common across all supported migration scenarios using Az
     > - If your database backup files are provided in an SMB network share, [Create an Azure storage account](../storage/common/storage-account-create.md) that allows the DMS service to upload the database backup files.  Make sure to create the Azure Storage Account in the same region as the Azure Database Migration Service instance is created.
     > - Make sure the Azure storage account blob container is used exclusively to store backup files only. Any other type of files (txt, png, jpg, etc.) will interfere with the restore process leading to a failure.
     > - Azure Database Migration Service does not initiate any backups, and instead uses existing backups, which you may already have as part of your disaster recovery plan, for the migration.
-    > - You should take [backups using the `WITH CHECKSUM` option](/sql/relational-databases/backup-restore/enable-or-disable-backup-checksums-during-backup-or-restore-sql-server). 
     > - Each backup can be written to either a separate backup file or multiple backup files. However, appending multiple backups (i.e. full and t-log) into a single backup media is not supported. 
     > - Use compressed backups to reduce the likelihood of experiencing potential issues associated with migrating large backups.
 * Ensure that the service account running the source SQL Server instance has read and write permissions on the SMB network share that contains database backup files.

articles/dms/migration-dms-powershell-cli.md

@@ -83,6 +83,8 @@ The following list describes each step in the workflow:
 > If your migration target is Azure SQL Database, you don't need backups for this migration. Database migration to Azure SQL Database is considered a logical migration that involves the database's pre-creation and data movement (performed by Database Migration Service).
 
 > [!IMPORTANT]
+> The Azure SQL Migration extension for Azure Data Studio doesn't take database backups, or neither initiate any database backups on your behalf. Instead, the service uses existing database backup files for the migration.
+>
 > In online migration mode, Database Migration Service continuously uploads the backup source files to your Azure storage account and restores them to the target until you complete the final step of cutting over to the target.
 >
 > In offline migration mode, Database Migration Service uploads the backup source files to Azure storage and restores them to the target without requiring a cutover.

articles/dms/migration-using-azure-data-studio.md

@@ -62,9 +62,8 @@ Before you begin the tutorial:
 
   > [!IMPORTANT]
   >
+  > - The Azure SQL Migration extension for Azure Data Studio doesn't take database backups, or neither initiate any database backups on your behalf. Instead, the service uses existing database backup files for the migration.
   > - If your database backup files are in an SMB network share, [create an Azure storage account](../storage/common/storage-account-create.md) that Database Migration Service can use to upload database backup files to and to migrate databases. Make sure you create the Azure storage account in the same region where you create your instance of Database Migration Service.
-  > - Database Migration Service doesn't initiate any backups. Instead, the service uses existing backups for the migration. You might already have these backups as part of your disaster recovery plan.
-  > - Make sure you [create backups by using the WITH CHECKSUM option](/sql/relational-databases/backup-restore/enable-or-disable-backup-checksums-during-backup-or-restore-sql-server?preserve-view=true&view=sql-server-2017).
   > - You can write each backup to either a separate backup file or to multiple backup files. Appending multiple backups such as full and transaction logs into a single backup media isn't supported.
   > - You can provide compressed backups to reduce the likelihood of experiencing potential issues associated with migrating large backups.
 

articles/dms/tutorial-sql-server-managed-instance-offline-ads.md

@@ -59,9 +59,8 @@ To complete this tutorial, you need to:
     - Azure storage account file share or blob container 
 
     > [!IMPORTANT]
+    > - The Azure SQL Migration extension for Azure Data Studio doesn't take database backups, or neither initiate any database backups on your behalf. Instead, the service uses existing database backup files for the migration.
     > - If your database backup files are provided in an SMB network share, [Create an Azure storage account](../storage/common/storage-account-create.md) that allows the DMS service to upload the database backup files.  Make sure to create the Azure Storage Account in the same region as the Azure Database Migration Service instance is created.
-    > - Azure Database Migration Service does not initiate any backups, and instead uses existing backups, which you might already have as part of your disaster recovery plan, for the migration.
-    > - You need to take [backups using the `WITH CHECKSUM` option](/sql/relational-databases/backup-restore/enable-or-disable-backup-checksums-during-backup-or-restore-sql-server). 
     > - Each backup can be written to either a separate backup file or multiple backup files. However, appending multiple backups (that is, full and t-log) into a single backup media isn't supported. 
     > - Use compressed backups to reduce the likelihood of experiencing potential issues associated with migrating large backups.
 * Ensure that the service account running the source SQL Server instance has read and write permissions on the SMB network share that contains database backup files.
@@ -180,12 +179,14 @@ Resource group, Azure storage account, Blob container from the corresponding dro
 
 The final step of the tutorial is to complete the migration cutover to ensure the migrated database in Azure SQL Managed Instance is ready for use. This is the only part in the process that requires downtime for applications that connect to the database and hence the timing of the cutover needs to be carefully planned with business or application stakeholders.
 
-To complete the cutover,
+To complete the cutover:
 
-1. Stop all incoming transactions to the source database and prepare to make any application configuration changes to point to the target database in Azure SQL Managed Instance.
-2. take any tail log backups for the source database in the backup location specified
-3. ensure all database backups have the status *Restored* in the monitoring details page
-4. select *Complete cutover* in the monitoring details page
+1. Stop all incoming transactions to the source database.
+2. Make application configuration changes to point to the target database in Azure SQL Managed Instance.
+3. Take a final log backup of the source database in the backup location specified
+4. Put the source database in read-only mode. Therefore, users can read data from the database but not modify it.
+5. Ensure all database backups have the status *Restored* in the monitoring details page.
+6. Select *Complete cutover* in the monitoring details page.
 
 During the cutover process, the migration status changes from *in progress* to *completing*. When the cutover process is completed, the migration status changes to *succeeded* to indicate that the database migration is successful and that the migrated database is ready for use.
 

articles/dms/tutorial-sql-server-managed-instance-online-ads.md

@@ -31,7 +31,8 @@ You will learn how to:
 
 > [!IMPORTANT]
 > For online migrations from SQL Server to SQL Managed Instance using Azure Database Migration Service, you must provide the full database backup and subsequent log backups in the SMB network share that the service can use to migrate your databases. Azure Database Migration Service does not initiate any backups, and instead uses existing backups, which you may already have as part of your disaster recovery plan, for the migration.
-> Be sure that you take [backups using the WITH CHECKSUM option](/sql/relational-databases/backup-restore/enable-or-disable-backup-checksums-during-backup-or-restore-sql-server?preserve-view=true&view=sql-server-2017). Each backup can be written to either a separate backup file or multiple backup files. However, appending multiple backups (i.e. full and t-log) into a single backup media is not supported. Finally, you can use compressed backups to reduce the likelihood of experiencing potential issues associated with migrating large backups.
+> Each backup can be written to either a separate backup file or multiple backup files. However, appending multiple backups (that is, full and t-log) into a single backup media isn't supported. 
+> Use compressed backups to reduce the likelihood of experiencing potential issues associated with migrating large backups.
 
 > [!NOTE]
 > Using Azure Database Migration Service to perform an online migration requires creating an instance based on the Premium pricing tier.

articles/dms/tutorial-sql-server-managed-instance-online.md

@@ -63,8 +63,8 @@ Before you begin the tutorial:
 
   > [!IMPORTANT]
   >
+  > - The Azure SQL Migration extension for Azure Data Studio doesn't take database backups, or neither initiate any database backups on your behalf. Instead, the service uses existing database backup files for the migration.
   > - If your database backup files are in an SMB network share, [create an Azure storage account](../storage/common/storage-account-create.md) that Database Migration Service can use to upload database backup files to and to migrate databases. Make sure you create the Azure storage account in the same region where you create your instance of Database Migration Service.
-  > - Database Migration Service doesn't initiate any backups. Instead, the service uses existing backups for the migration. You might already have these backups as part of your disaster recovery plan.
   > - You can write each backup to either a separate backup file or to multiple backup files. Appending multiple backups such as full and transaction logs into a single backup media isn't supported.
   > - You can provide compressed backups to reduce the likelihood of experiencing potential issues associated with migrating large backups.
 

articles/dms/tutorial-sql-server-to-virtual-machine-offline-ads.md

@@ -57,6 +57,7 @@ To complete this tutorial, you need to:
     - Azure storage account file share or blob container 
 
     > [!IMPORTANT]
+    > - The Azure SQL Migration extension for Azure Data Studio doesn't take database backups, or neither initiate any database backups on your behalf. Instead, the service uses existing database backup files for the migration.
     > - If your database backup files are provided in an SMB network share, [Create an Azure storage account](../storage/common/storage-account-create.md) that allows the DMS service to upload the database backup files.  Make sure to create the Azure Storage Account in the same region as the Azure Database Migration Service instance is created.
     > - Azure Database Migration Service does not initiate any backups, and instead uses existing backups, which you may already have as part of your disaster recovery plan, for the migration.
     > - Each backup can be written to either a separate backup file or multiple backup files. However, appending multiple backups (i.e. full and t-log) into a single backup media is not supported. 
@@ -180,10 +181,11 @@ The final step of the tutorial is to complete the migration cutover. The complet
 To complete the cutover:
 
 1. Stop all incoming transactions to the source database.
-1. Make application configuration changes to point to the target database in SQL Server on Azure Virtual Machine.
-1. Take any tail log backups for the source database in the backup location specified.
-1. Ensure all database backups have the status *Restored* in the monitoring details page.
-1. Select *Complete cutover* in the monitoring details page.
+2. Make application configuration changes to point to the target database in SQL Server on Azure Virtual Machines.
+3. Take a final log backup of the source database in the backup location specified
+4. Put the source database in read-only mode. Therefore, users can read data from the database but not modify it.
+5. Ensure all database backups have the status *Restored* in the monitoring details page.
+6. Select *Complete cutover* in the monitoring details page.
 
 During the cutover process, the migration status changes from *in progress* to *completing*. The migration status changes to *succeeded* when the cutover process is completed. The database migration is successful and that the migrated database is ready for use.