DirSync Office 365 deletion threshold \ OU scope

[gshaw]

One for @EduTech I think...

 

We had an issue this morning with our source student data that led to some accounts being moved to an out-of-scope container in AD as far as DirSync is concerned. The deletion threshold kicked in as it should so fortunately it hasn't have an effect on those users in terms of their Office 365 accounts.

 

The not-so-good bit is that we're still stuck with the deletion threshold reached and DirSync doesn't seem to have realised that we've since moved the objects back in scope (now back in their original OU). None of the documentation online refers to this scenario (only really deals with accounts that have been deleted rather than moved) so we're a bit unsure as to what the correct line of action is next.

 

From what I understand DirSync does Delta syncs all the time after the initial run so my thought is to manually force a Full Sync along the lines of:

 

http://2.bp.blogspot.com/-Bl3WN4gaeuw/Tpnc6smbtJI/AAAAAAAAAEw/U4JHIV5lGzg/s1600/ilm8.jpg

 

http://4.bp.blogspot.com/-mEO2m2hr6No/TpndLo9sZzI/AAAAAAAAAE4/RWQ34L-kuMY/s1600/ilm9.jpg

 

Will probably raise this with Office 365 support as well but wondering if you've seen something similar in your experience?

Edited March 24, 2015 by gshaw

[apearce]

Hi,

Do you see the users in the meta verse (are they syncing into FIM). I notice from the screenshot you are clicking on Target Source which would be Azure AD and you should be running a full export there (Sync) rather than an import.

 

Let me know if don't see them in the metaverse as they are being included in teh sync in from AD.

[gshaw]

Hi @apearce thanks for replying

 

Just searched the metaverse using the userPrincipalName for one of the affected users and they do appear in the search results. Double-clicking on the record that is found shows the contributing MA as "Active Directory Connector" and on the Connectors tab both the Active Directory and Windows Azure Active Directory connectors are listed.

 

Edit: had a call back from Microsoft Support, looks like my initial theory was along the right lines and a Full Sync was what we needed.

 

What the documentation doesn't mention is a slight addition to the end of the usual command:

 

Start-OnlineCoexistenceSync -FullSync

Edited March 25, 2015 by gshaw