Merge pull request #228931 from croblesm/crobles-0228-updating-known-issues

Updating known issues

Author: v-shils

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

@@ -30,7 +30,7 @@ Known issues and troubleshooting steps associated with the Azure SQL Migration e
 
 - **Message**: `Migration for Database 'DatabaseName' failed with error cannot find server certificate with thumbprint.`
 
-- **Cause**: The source SQL Server instance certificate from a database protected by Transparent Data Encryption (TDE) hasn't been migrated to the target Azure SQL Managed Instance or SQL Server on Azure Virtual Machine before migrating data.
+- **Cause**: The source database is protected with Transparent Data Encryption (TDE). You need to migrate the Database Encryption Key (DEK) to the target Azure SQL Managed Instance or SQL Server on Azure Virtual Machine before starting the migration.
 
 - **Recommendation**: Migrate the TDE certificate to the target instance and retry the process. For more information about migrating TDE-enabled databases, see [Tutorial: Migrate TDE-enabled databases (preview) to Azure SQL in Azure Data Studio](./tutorial-transparent-data-encryption-migration-ads.md).  
 
@@ -90,7 +90,7 @@ Known issues and troubleshooting steps associated with the Azure SQL Migration e
 
 - **Message**: `Failed to test connections using provided Integration Runtime. Error details: 'Remote name could not be resolved.'`
 
-- **Cause**: The Self-Hosted Integration Runtime can't connect to the service back end. This issue is caused by network settings in the firewall.
+- **Cause**: DMS cannot connect to Self-Hosted Integration Runtime (SHIR) due to network settings in the firewall.
 
 - **Recommendation**: There's a Domain Name System (DNS) issue. Contact your network team to fix the issue. For more information, see [Troubleshoot Self-Hosted Integration Runtime](../data-factory/self-hosted-integration-runtime-troubleshoot-guide.md).
 
@@ -183,7 +183,6 @@ SELECT [ROLLBACK] FROM [dbo].[__migration_status]
 WHERE STEP in (5,7,8) ORDER BY STEP DESC;
 ```
 
-
 ## Error code: 2042 - PreCopyStepsCompletedDuringCancel 
 
 - **Message**: `Pre Copy steps finished successfully before canceling completed. Target database Foreign keys and temporal tables have been altered. Schema migration may be required again for future migrations. Target server: <Target Server>, Target database: <Target Database>.`
@@ -196,7 +195,6 @@ WHERE STEP in (5,7,8) ORDER BY STEP DESC;
 SELECT [ROLLBACK] FROM [dbo].[__migration_status]  
 WHERE STEP in (3,4,6);
 ```
-  
 
 ## Error code: 2043 - CreateContainerFailed
 
@@ -206,6 +204,7 @@ WHERE STEP in (3,4,6);
 
 - **Recommendation**: For more troubleshooting steps, see [Troubleshoot Azure Data Factory and Synapse pipelines](../data-factory/data-factory-troubleshoot-guide.md#error-code-2108). 
 
+
 ## Error code: 2056 - SqlInfoValidationFailed
 
 - **Message**: CollationMismatch: `Source database collation <CollationOptionSource> is not the same as the target database <CollationOptionTarget>. Source database: <SourceDatabaseName> Target database: <TargetDatabaseName>.`
@@ -248,6 +247,29 @@ WHERE STEP in (3,4,6);
 - **Recommendation**: Check if the selected tables exist in the target Azure SQL Database. If this migration is called from a PowerShell script, check if the table list parameter includes the correct table names and is passed into the migration.
 
 
+## Error code: Ext_RestoreSettingsError
+
+- **Message**: Unable to read blobs in storage container, exception: The remote server returned an error: (403) Forbidden. The remote server returned an error: (403) Forbidden
+
+- **Cause**: Target is unable to connect to blob storage.
+
+- **Recommendation**: Confirm that target network settings allow access to blob storage. For example, if migrating to SQL VM, ensure that outbound connections on VM aren't being blocked.
+
+
+- **Message**: Failed to create restore job. Unable to read blobs in storage container, exception: The remote name could not be resolved.
+
+- **Cause**: Target is unable to connect to blob storage.
+
+- **Recommendation**: Confirm that target network settings allow access to blob storage. For example, if migrating to SQL VM, ensure that outbound connections on VM are not being blocked.
+
+
+- **Message**: `Migration for Database <Database Name> failed with error 'Migration cannot be completed because provided backup file name <Backup File Name> should be the last restore backup file <Last Restore Backup File Name>'`.
+
+- **Cause**: Most recent backup was not specified in backup settings.
+
+- **Recommendation**: Specify most recent backup file name in backup settings and retry operation.
+
+
 ## Azure SQL Database limitations 
 
 Migrating to Azure SQL Database by using the Azure SQL extension for Azure Data Studio has the following limitations: