Merge pull request #260851 from abhims14/patch-2

Update known-issues-azure-sql-migration-azure-data-studio.md

Author: prmerger-automator[bot]

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

@@ -255,6 +255,12 @@ This article provides a list of known issues and troubleshooting steps associate
 
 ## Error code: 2060 - SqlSchemaCopyFailed
 
+- **Message**: `Login failed for user 'Domain\MachineName$`.
+
+- **Cause**: This error generally happens when customer uses Windows authentication to login the source. The customer provides Windows authentication credential but SHIR converts it to machine account (Domain\MachineName$).
+
+- **Recommendation**: The solution is to add machine account to the SQL Server. [How to Create a SQL Server Computer Account Login](https://stackoverflow.com/questions/38680366/how-to-add-a-new-sql-server-machine-account)
+  
 - **Message**: `The SELECT permission was denied on the object 'sql_logins', database 'master', schema 'sys'.`
 
 - **Cause**: The account customers use to connect Azure SQL Database lacks the permission to access `sys.sql_logins` table.
@@ -263,11 +269,21 @@ This article provides a list of known issues and troubleshooting steps associate
 
   1. Add 'sysadmin' role to the account, which grants the admin permission.
 
-  1. If customers can't use admin account or can't grant admin permission to the account, they can create a user in master and grant **dbmanager** and **loginmanager** permission to the user. For example,
+  1. If customers can't use sysadmin account or can't grant sysadmin permission to the account, then minimum permission on source SQL Server required is "db_owner" and on target Azure SQL DB create a user in master and grant **##MS_DatabaseManager##**,**##MS_DatabaseConnector##**, **##MS_DefinitionReader##** and **##MS_LoginManager##** fixed server roles to the user. For example,
 
      ```sql
      -- Run the script in the master
-     CREATE USER testuser FROM LOGIN testlogin;
+     -- Please run the script on Master database
+     CREATE LOGIN testuser with Password = '*********';
+     ALTER SERVER ROLE ##MS_DefinitionReader## ADD MEMBER [testuser]; 
+      GO
+     ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER [testuser]; 
+      GO
+     ALTER SERVER ROLE ##MS_DatabaseManager## ADD MEMBER [testuser]; 
+      GO
+     ALTER SERVER ROLE ##MS_LoginManager## ADD MEMBER [testuser]; 
+      GO
+     CREATE USER testuser from login testuser;
      EXEC sp_addRoleMember 'dbmanager', 'testuser';
      EXEC sp_addRoleMember 'loginmanager', 'testuser';
      ```