DirSync Errors Today

[StephenHardy]

FYI This was also happening for users that had been disabled.

[jaminben]

Anyone not able to get to the O365 login page this morning?... none of our user's can get to the actual login page and wondering if this is related.

[StephenHardy]

Having similar issues - works for some users and not others

[Boredguy]

Connection issues raised in this post earlier

[jaminben]

Connection issues raised in this post earlier

 

Thanks

[gaz350b]

glad its not just me, we had fixed a sync issue and started recieving these after fixing the issue!

[garethEds]

Anyone not able to get to the O365 login page this morning?... none of our user's can get to the actual login page and wondering if this is related.

 

Weirdly enough - our OneDriveMapper script is not working this morning.

 

Neither can I reach http or https login.microsoftonline.com - so that could explain why the script isn't working

 

Gareth

[psydii]

Part of the world's IT brought down by Azure Active Directory issue • The Register

[FN-GM]

Weirdly enough - our OneDriveMapper script is not working this morning.

 

Neither can I reach http or https login.microsoftonline.com - so that could explain why the script isn't working

 

Gareth

 

What script is that please?

[EduTech]

Hey All,

 

Some customers may have received an email similar to the following ion Wednesday / Thursday for any objects that were recently updated on their on-premise.

 

----

Hello ,

 

 

 

You can troubleshoot this issue by running the Directory Synchronization troubleshooter on the server that has Azure Active Directory identity synchronization tools installed.

 

The Identity synchronization tool batch run was completed on for directory Tenant Name [Contoso.onmicrosoft.com].

 

 

The following errors occurred during synchronization:

 

Identity Error Description sourceAnchor

 

[email protected] SourceAnchor1

 

[email protected] SourceAnchor2

 

 

Tracking ID:

-----

 

note: the blank error and descriptions fields being reported in the emails.

 

After investigation, we have determined these are false positives. If a customer sees this it means the object was actually provisioned/updated successfully. Please verify this by reviewing the object modified on their Azure Active Directory ex. the respective portal or powershell

 

This has since been fixed and so you shouldn't get any errors, unless they are actual errors.

 

I hope that helps,

James.