Azure AD User sync error

somee.gupta_32091 over 3 years ago

Hi,

We have recently set up azure sync in our project. We are currently testing out the import of Azure AD schema into our database. The sync for groups and other schema types is working fine. But for users sync we are getting the below error for all user objects in sync log.

[ServiceException]: Code: MailboxNotEnabledForRESTAPI - Message: REST API is not yet supported for this mailbox.

Microsoft.Graph.ServiceException: Exception of type 'Microsoft.Graph.ServiceException' was thrown.

Could you please advise on the error.

Thanks,

Somee

Parents

0 Markus Weiss-Ehlers over 3 years ago

If you Google this error, you will find many explanations why this error may occur while talking to the Microsoft Graph API. One reason could be that the mailbox of the Azure AD User is an OnPrem mailbox and the Exchange Server hasn't the property CUs installed, another could be that the Exchange server is a private one that Microsoft offers for large environments (e.g. Universities).

Just for interest, we are talking here about the Azure AD sync, not any Exchange Online sync. Correct?

What version are you using?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 somee.gupta_32091 over 3 years ago in reply to Markus Weiss-Ehlers

Hi Markus,

Thanks for the reply. We are trying out Azure AD sync not Exchange Online. The version we are using is 8.0.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

0 somee.gupta_32091 over 3 years ago in reply to Markus Weiss-Ehlers

Hi Markus,

Thanks for the reply. We are trying out Azure AD sync not Exchange Online. The version we are using is 8.0.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

0 Markus Weiss-Ehlers over 3 years ago in reply to somee.gupta_32091

As I have written before, the error message you are seeing is coming from the GraphAPI call and does not seem to be OneIM specific.

Newer versions of OneIM (8.1.x) are using newer versions of the GraphAPI libraries that might not show this issue but this is no guarantee as this issue seems to be data situation driven.

By the way, Version 8.0 (no service pack) attached is out-of-support so you might want to update your environment.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel