Forum Discussion
Jerry Meyer
Feb 20, 2017Iron Contributor
Issue with new Azure AD connect to new domain
Currently we are on the verge of a migration. In this migration we have an existing tenant connected to DomainA. DomainA will be decommisioned and all users will be migrated to DomainB. Currently...
- Feb 21, 2017We found the issue, we deleted the new Azure AD sync and run the Wizard again. This time customized the setting and set the right Immutable ID. After this everything updated.
The test users became visible and and the dirsynserviceaccount updated as-well.
No we have Attributes from our resource domain and user attributes from the User Domain :) and it is all syncing.
Jerry Meyer
Feb 21, 2017Iron Contributor
Thanks for the advise. The issue we run against now is that when we ask for the company information on O365 (get-msolcompanyinformation) we still see the dirsyncerviceaccount used in the old situation. Is there any way to change or refresh this? This dirsync account contains the name of the old dirsyncserver from the old domain.
You have any advise on this?
Jerry Meyer
Feb 21, 2017Iron Contributor
We found the issue, we deleted the new Azure AD sync and run the Wizard again. This time customized the setting and set the right Immutable ID. After this everything updated.
The test users became visible and and the dirsynserviceaccount updated as-well.
No we have Attributes from our resource domain and user attributes from the User Domain :) and it is all syncing.
The test users became visible and and the dirsynserviceaccount updated as-well.
No we have Attributes from our resource domain and user attributes from the User Domain :) and it is all syncing.
- Margaret BarrettSep 12, 2017Copper ContributorRemove