Forum Discussion
Looking to run AAD Sync soon
If anything goes wrong, you can simply delete the synced users and start fresh. Or if you want to test it, spin a trial tenant and configure the sync to it, then if everything works as expected rerun the AAD Connect setup wizard and configure it to sync with the "real" tenant.
Is there any consequence to running against a trial tenant and then later coming back to run against the production tenant?
I think the trial tenant idea sounds attractive, but it doesn't actually sync anything back to the local domain if I pick STAGING correct?
I added the username@domain.com as an alternate UPN, but it doesn't appear that it will let users log in to the domain with that.
If I make the username@domain.com the PRIMARY login, do I then have to create new profiles for each user?
Nothing is synced back, DirSync is one-way process, from on-premises to Azure AD. Only when you have some of the additional features enabled there is (limited) writeback to the local domain.
Not sure what you mean by "alternate" UPN, did you perhaps add a new UPN suffix?
YES, I meant UPN Suffix. They were all xxx.local. I added user@domain.com
Can I filter it down to just do a specific user possibly? I could do one of my test accounts and just see how that goes?
The issue we have is that our On-Prem users don't have listed managers, etc. All the detail is in the users cloud account. So the Sync isn't going to populate the on-prem account by default correct?
What we would like to do is allow the users to change their own passwords for starters. That will require write-back correct?