Active Directory
A set of directory-based technologies included in Windows Server.
5,973 questions
Why is EAC and On-Prem AD showing different information?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 18%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
RJ
0
Reputation points
Hi All,
We have an issue whereby a users contact information, specifically their mobile number and job title isn't syncing properly between On-Prem AD as well as Exchange Admin Centre.
We have removed the users personal mobile number from AD and performed a Dir Sync and can confirm within Office 365 Admin Centre as well as AAD the number has been removed and shows blank. However, the number is still showing within EAC and still shows under their contact information.
So far this is the only user affected and it looks like there's a sync failure taking place for the particular account but just unsure where the mobile number is still pulling from.
Have attempted to remove using MSol command by adding '0' in for mobile number and using remove command, again, this reflects on AAD but EAC still shows mobile number.
Has anyone come across this previously and able to share a fix?
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 18%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
Noah Ma-MSFT 995 Reputation points Microsoft Vendor2024-04-30T09:43:41.9233333+00:00 Hi @RJ,
Based on your description, I know this issue is that the mobile number information is only synced to Azure AD, not sync to EXO.
In this situation, I need to confirm if you have modified any rules in AAD connect which may affect the sync. If not, you need to contact O365 backend team to do the sync via opening a service request in M365 portal.
-
RJ 0 Reputation points
2024-04-30T09:57:06.4733333+00:00 Hi Noah,
We don't have any particular AAD rules that would be affecting the sync and when this was last raised with MS Support, they pushed a sync on the backend which temporarily corrected the error and removed the mobile number as intended but the number has since re-appeared.
-
Noah Ma-MSFT 995 Reputation points Microsoft Vendor
2024-05-01T09:52:14.2433333+00:00 Hi,
As you said, the MS support pushed a sync on the backend which temporarily corrected the error and removed the mobile number as intended. We could know that this is backend sync issue. Until the problem re-appeared, have you made any changes that could had an impact?
If not, you still need to contact MS backend team. Or since only one user has this issue, one possible solution could be to remove and recreate the user's account.
-
Noah Ma-MSFT 995 Reputation points Microsoft Vendor
2024-05-06T09:49:26.97+00:00 Just checking in to see if above information was helpful.
If the issue has been resolved, please mark the helpful replies as answers.
Sign in to comment