Good afternoon all!
We are currently getting prepared to move from Dynamics CRM 2016 to D365 and are ready to start migrating data. Our IT department has some security concerns with the service account that we are using for the migration process. We are testing a migration from our on premise CRM server (2016) to Dynamics 365 using Cobalt Migration. It seems to require basic authentication (vs modern authentication). There is a security policy applied to our company's o365 accounts to enforce modern authentication and IT is reluctant to remove the policy from the service account. They are asking for alternative methods of the migration in order to keep the service account using modern auth. Is there an alternative method or software upgrade we can use to allow the migration to take place using an account that uses modern auth.
Appreciate your thoughts and recommendations.
You need to get IT to get you an App Password for the service account to use with the migration. (If they don't know how to do that tell them to find out – mr google is very helpfull).
You then use the service account username eg firstname.lastname@example.org etc and the App Password (it's generated so it is a copy/paste) with the Cobalt Migration.
That's how Kingswaysoft works so Cobalt should be the same. Anyway, talk to the Cobalt people – they will advise you.
See the following Courtesy of stackoverflow and Josh Painter
1. Login to Office Portal. Click on gear in upper right, click Office 365 under "Your App Settings." - it is now under "My Account" under the picture (not the gear wheel) - pete
2. Click on Security & Privacy on left and then Additional Security Verification.
3. Click Create and manage app passwords.
4. Click Create and give your password a name (maybe the name of your application so you remember it later).
5. Copy the generated password (it will never be shown again).
6. Use your normal username and this new password - it will skip multi-factor authentication.
You can create as many App Passwords as you need for legacy apps that don't work with MFA. Try not to reuse them - just create as many as you need. This way you can easily go back and revoke specific passwords when you don't need them any more.
shareimprove this answer
answered Oct 19 '18 at 18:11
3,8361717 silver badges24
If you've found this thread useful, dive deeper into User Group community content by role