Office 365 Contact Sync stopped working 16SP4

[vvoice]

It was running fine on 16SP3, updating contacts almost immediately.
Now noticing it neither updates nor adds contacts on SP4. Same on two separate systems.
Anyone else?

 

[craigreilly]

Did the 365 password expire on the account being used to sync?
(Perhaps not your account but an account for sync only)

 

[vvoice]

No passwords have changed or expired on either tenant.
Can anyone test to see if contact sync is working or not working after upgrade to 16SP4?
On both systems I have enabled only contact sync, not directory or calendar.
Thanks

 

[Constantinos Constantinou]

Hello @vvoice ,

Can you please check the logs for any possible error on 3cxManagementConsole.log or 3cxSystemService.log after restarting the 3CX PhoneSystem 01 System Server service?

Thank you.

 

[vvoice]

The only errors I could identify, on both systems, read:
2020/01/15 05:00:00.975|570|0017|Erro|Error running Office365 synchronization: Object reference not set to an instance of an object.

 

[mcoacollins]

Just setup Office 365 contact sync on 16.0.4.493 appliance - getting the same error.

2020/01/27 10:29:36.979|662|0027|Erro|Error running Office365 synchronization: Object reference not set to an instance of an object.

None of the contacts end up syncing - but I do get the following success message at the top of the Office 365 configuration screen:

Status OK. Real Time Notifications to Office 365 and back are working. This means that changes from Office 365 to 3CX will be updated.

3CX is able to pull the Office 365 user list when I hit "Add Users" for selective sync.

 

[Constantinos Constantinou]

Hello @mcoacollins,

Please proceed and create a group with the name "Azure AD" on Management Console > Groups.

There is a bug that if you do not have selected the "User Sync" on Office 365 and you have only "Contacts Sync" the following exception is thrown.

This issue already fixed and will be released with the upcoming update.

 

[mcoacollins]

Hello @mcoacollins,

Please proceed and create a group with the name "Azure AD" on Management Console > Groups.

There is a bug that if you do not have selected the "User Sync" on Office 365 and you have only "Contacts Sync" the following exception is thrown.

This issue already fixed and will be released with the upcoming update.

That did the trick - thank you!

 

[vvoice]

Creating the group allowed contact sync for some extensions but not all.

 

[Constantinos Constantinou]

Hello @vvoice,

Can you please elaborate a bit more on this one?

What if you choose explicitly those extensions for contact synchronization instead of all? They will get synced?

I would suggest also to proceed and open a support ticket if this is a valid case, in order to investigate it further.

Thank you.

 

[vvoice]

I have explicitly chosen three extensions for contact sync only. Only one of the three started syncing contacts once I added the Azure AD group. I have verified the email boxes contain valid contacts in the primary contacts folder and that the Azure AD UserType attribute field is configured properly as 'Member' for all accounts.
I have a ticket open with support that has been sitting in R&D. I've provided them logs as requested. Have not received a response in 20 days and am concerned that the Azure AD group fix may not be the complete answer to this problem.