You’re offline. This is a read only version of the page.
3,079
We have been investigating moving from On-prem to Online, so I set up an instance a while back, and imported first our solutions, then our data. Since we only had a handful of licenses for this testing period, and we also have a number of disabled users who own records, I investigated how to bring all of these non-licensed users into the system just for this record tracking type of purpose (i.e. not needing to log in, in most cases). I saw some posts on here about using the Config Migration Tool for this, which seemed easy enough since I had to use it for other things anyway.
So I brought everything into our Dev environment, and did a lot of testing, code updating, etc... Got everything working the way we'd expect, and went to bring in larger portions of test data. However, any records that reference any of these imported users were giving the error "Access to Microsoft Dynamics 365 has not yet been fully configured for this user. The user needs at least one security role before you can continue". I'm not able to assign the role while they're disabled. Since at this point we've decided to move ahead with Online, I got some more licenses, and I tried to assign one to one of these users. They did not enable. I opened a ticket with Microsoft, who pointed out that the user names were in the on-premise format (<domain>\<username>) rather than the email address format.
I changed this for a couple of users, re-assigned the licenses, and they worked fine. However, every other user I've tried this with other than the first two will not allow me to change the user name. I get a Duplicate Record error, even though there is no other user with that user name. I even tried complete garbage user names that for sure have never been in any of our systems, and still the Duplicate error. I went back to MS, but it's been a couple of weeks now and they haven't been able to solve the issue. They've confirm there isn't a duplicate, but don't know why it's saying there is.
I'm losing time on this migration and having to deal with parallel development while trying to resolve this. I very much do not want to start over on Online, since it was a lot of work and testing to get the environment running correctly. Anyone else have any ideas of how I might be able to fix this?
*This post is locked for comments
Well, the migration is done now, so it doesn't really save us anything. And by migrating users in instead of adding them through the normal procedure, we appear to have broken things, so...I'll stick with the "only add via adding licensing in O365" path from now on if we have to do anything over. It's a giant pain for many situations, but...*shrug*
Thank you though.
Hi Alison, sounds like you've had quite a journey! We manage users differently with Synchronicity Echo (www.synchronicity-systems.com/Echo), and have been investigating extending our custom IP (the Echo Managed Service) to provide the ability to set the owner without the user needing security roles. Another option (which we've used in the past) is to assign the required permissions to the default Business Unit team, such that the users should inherit the permissions. Of course, let us know if you're tired of the whole thing and want us to complete an Echo managed service migration for you :).
Kind Regards
Alex.
I managed to fix the existing users. The one that was stuck with the all zeros - I changed the user name to a temporary user account I made in O365 just for this, and then changed it back, and re-assigned the license. Apparently that was finally enough to kick it to connect to the proper account, and populate the Azure ID. Logged in as the account, and it seems to work just fine. Most importantly, I was able to assign a role, so that we can import records with these users as the owner. After this, I was able to change the user name on the next one, enable the license, and it was fine. Sadly, I could only do this one at a time, since if I tried to change two user names it would give me the duplicate error on the second one.
Anyway, went through one by one and got every user working. Which would be great, except that new users I add aren't showing up - they'll show up in new instances, but not this instance or anything I copy from this instance. I've asked support to do a force sync, so hopefully that will be enough. If not, not sure what else to try.
Anyway, long story short - don't ever import users to Online using the Config Migration Tool, even though it lets you (which it shouldn't, if it causes this many issues). Even though the only other way to bring in historical users is to make sure they're in O365, then enable a license on them, assign a role, then deactivate the license - that's irritating, but way less work than trying to clean up after an import, apparently.
I should note - I'm fine to re-create these users, now that I 1. have licenses and 2. understand how badly this apparently breaks everything. However, there's no way to remove the existing broken users, and it's not actually letting me create new users. I created a new user in O365, licensed it, and it does not show up in these instances. I made a brand new instance, though, and it's there fine.
If I make a new instance and start over by importing the solutions instead of doing a copy, the GUIDs for everything are different, and that breaks so many of our workflows and Business Rules. We spent weeks fixing/re-testing all of it - even things like having the Currency referenced in a Business Rule were now broken, and with BR's it's the worst because you get no warnings/error messages at all. I'm very much hoping to not have to start over and re-do all of that work. :-(
So I looked at the entity more, and found that one of the fields is the Azure AD Object ID. For most users, this is blank. However, for the one user I was able to change the user name for (but it's still not syncing) this field is all zeros. I’m wondering if when I try to change the user name on the others, it’s trying to set that to zeros on that one as well, which is then what’s throwing the duplicate error. I've been able to find the Azure AD Object IDs for my other users, but the field is locked. Is there any way to load this? Nothing I've tried works, which I suppose is not terribly surprising.
At this point I'm mostly surprised it let me bring these users in at all this way - if this is so incompatible with the system how did the import even work?
Also, it did allow me to fix two users before all of this...that's the other really puzzling thing. Two worked, and then it stopped. And those two seem to have the appropriate Azure ID somehow.
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
52
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
