Merge pull request #235408 from croblesm/crobles-0421-known-issues-update-follow-up

Updating known issues, adding more details about IR issue.

Author: prmerger-automator[bot]

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

@@ -15,7 +15,7 @@ ms.custom: seo-lt-2019
 Known issues and troubleshooting steps associated with the Azure SQL Migration extension for Azure Data Studio.
 
 > [!IMPORTANT]
-> The latest version of Integration Runtime (5.28.8488) prevents access to a network file share on a local host. This security measure will lead to failures when performing the pre-migration validation using Azure Data Studio as a client. Please ensure you run Integration Runtime on a different machine than the network share hosting.
+> The latest version of Integration Runtime (5.28.8488) prevents access to a network file share on a local host. This security measure will lead to failures when performing migrations to Azure SQL using DMS. Please ensure you run Integration Runtime on a different machine than the network share hosting.
 
 ## Error code: 2007 - CutoverFailedOrCancelled 
 
@@ -215,6 +215,18 @@ 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: 2049 - FileShareTestConnectionFailed
+
+- **Message**: `The value of the property '' is invalid: 'Access to <share path> is denied, resolved IP address is <IP address>, network type is OnPremise'.`
+
+- **Cause**: The network share where the database backups are stored is in the same machine as the self-hosted Integration Runtime (SHIR).
+
+- **Recommendation**: The latest version of Integration Runtime (**5.28.8488**) prevents access to a network file share on a local host. Please ensure you run Integration Runtime on a different machine than the network share hosting. If hosting the self-hosted Integration Runtime and the network share on different machines is not possible with your current migration setup, you can use the option to opt-out using ```DisableLocalFolderPathValidation```. 
+    > [!NOTE]
+    > For more information, see [Set up an existing self-hosted IR via local PowerShell](../data-factory/create-self-hosted-integration-runtime.md#set-up-an-existing-self-hosted-ir-via-local-powershell). Use the disabling option with discretion as this is less secure.
+
+
 ## 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>.`