Home

Sync Linked Mailboxes to Office 365

%3CLINGO-SUB%20id%3D%22lingo-sub-476035%22%20slang%3D%22en-US%22%3ESync%20Linked%20Mailboxes%20to%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-476035%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3EDear%20all%2C%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3EI%20have%20a%20very%20interesting%20situation%20with%20Office%20365%20hybrid%20migration.%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3EMy%20client%20has%202%20forests%20(with%20trust%20between%20them)%20with%20Exchange%20on%20Forest%26nbsp%3BA.local%26nbsp%3BForest%26nbsp%3BB.local%26nbsp%3Bhas%20only%20accounts%20on%20it.%26nbsp%3BUsers%20on%26nbsp%3BForest%20A%26nbsp%3Bare%20regular%20mailbox%20users%20and%20most%20of%20them%20have%20been%20migrated%20to%20Office%20365%2C%20and%20users%20on%26nbsp%3BForest%20B%26nbsp%3Bare%20linked%20mailboxes%20on%20Forest%20A%20and%20are%20disabled%20users%20but%20they%20can%20be%20seen%20and%20synced%20on%20Office%20365%26nbsp%3BOn%20office%20365%20the%20Linked%20Mailboxes%20are%20synced%20as%202%20different%20users.%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%3CSTRONG%3EProblem%20was%3A%26nbsp%3B%3C%2FSTRONG%3EI%20was%20supposed%20to%20solve%20a%20problem%20with%20join%20both%20users%20identity%20in%20Office%20365%20to%20a%20single%20user%20which%20I%20managed%20to%20but%20Password%20was%20not%20working%20because%20it's%20in%20the%20Account%20Forest%20(B)%20and%20not%20syncing%20because%20the%20user%20in%20forest%20B%20is%20not%20the%20one%20synced%20to%20Office%20365%20but%20the%20Linked%20Mailbox%20on%20Forest%20A.%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%3CSTRONG%3EProblem%20now%20is%3A%3C%2FSTRONG%3E%26nbsp%3BAfter%20realizing%20that%20even%20when%20changing%20the%20disabled%20user's%20password%20on%20Forest%20A%20doesn't%20sync%20I%20decided%20to%20upgrade%20Dirsync%20but%20after%20the%20upgrade%20I%20got%20an%20alert%20that%20Dirsync%20stopped%20exporting%20changes%20to%20Office%20365%20due%20to%20the%20limited%20threshold%20of%20requested%20deletions%20which%20is%20by%20default%20500%20objects%20but%20in%20my%20case%20it%20reached%20up%20to%202250%20users.%26nbsp%3B%26nbsp%3BI%20checked%20the%20Dirsync%20users%20that%20are%20about%20to%20get%20deleted%20and%20found%20that%20all%20of%20them%20are%20Linkedmailboxes.%26nbsp%3BThings%20I%20tried%20so%20far%20to%20sync%20the%20users%3A%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E1-%20Tried%20Enabling%20the%20syncing%20of%20Disabled%20users%20by%20edit%20sync%20rules%20(Scoping%20filter)%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%3CSTRONG%3EUserAccountControl%20from%20Operator%20value%20%3D%20ISBITNOTSET%20%3D2%20to%20ISNOTNULL%20%3D%200%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E2-%20Tried%20Changing%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%3CSTRONG%3EIn%20from%20AD%20%E2%80%93%20User%20Common%20from%20Exchange%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Eof%20the%20Exchange%20forest%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%3CSTRONG%3EFrom%3C%2FSTRONG%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3EExpression%20%26gt%3B%26gt%3B%20SourceObjectType%20%26gt%3B%26gt%3B%26gt%3B%20IIF(IsPresent(%5BmsExchRecipientTypeDetails%5D)%2C%20IIF(%5BmsExchRecipientTypeDetails%5D%3D2%2C%20NULL%2C%20%E2%80%9CUser%E2%80%9D)%2C%20%E2%80%9CUser%E2%80%9D)%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%3CSTRONG%3EChanged%20to%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3EIIF(IsPresent(%5BmsExchRecipientTypeDetails%5D)%2C%20IIF(%5BmsExchRecipientTypeDetails%5D%3D666%2C%20NULL%2C%20%E2%80%9CUser%E2%80%9D)%2C%20%E2%80%9CUser%E2%80%9D)%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3EPrior%20to%20Upgrading%20Dirsync%2C%20I%20took%20a%20backup%20of%20all%20the%20rules%20that%20I%20have%20in%20Dirsync%2C%20I%20tried%20checking%20them%20but%20couldn't%20find%20where%20the%20rule%20that%20allows%20Linkedmailboxes%20to%20get%20synced%20and%20couldn't%20find%20it.%26nbsp%3BI%20would%20be%20happy%20to%20share%20this%20and%20get%20help%20from%20anyone%20who%20did%20this%20before.Thank%20you%3C%2FP%3E%3CP%20class%3D%22s1w8oh2o-10%20bQeEFC%22%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22_3Oa0THmZ3f5iZXAQ0hBJ0k%20s1smblml-1%20reNdX%22%3E%3CA%20href%3D%22https%3A%2F%2Fi.redd.it%2F4mcmfx6kw9t21.png%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fi.redd.it%2F4mcmfx6kw9t21.png%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-476035%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481744%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20Linked%20Mailboxes%20to%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481744%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F26060%22%20target%3D%22_blank%22%3E%40Mohammed%20Hamada%3C%2FA%3E%26nbsp%3BI%20have%20done%20a%20recovery%20from%20backup%20and%20it's%20all%20working%20well%20now.%3C%2FP%3E%3CP%3ECouldn't%20find%20out%20where%20is%20the%20culprit%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Mohammed Hamada
Occasional Contributor

Dear all,

 

I have a very interesting situation with Office 365 hybrid migration. 

 

My client has 2 forests (with trust between them) with Exchange on Forest A.local Forest B.local has only accounts on it. Users on Forest A are regular mailbox users and most of them have been migrated to Office 365, and users on Forest B are linked mailboxes on Forest A and are disabled users but they can be seen and synced on Office 365 On office 365 the Linked Mailboxes are synced as 2 different users. 

 

Problem was: I was supposed to solve a problem with join both users identity in Office 365 to a single user which I managed to but Password was not working because it's in the Account Forest (B) and not syncing because the user in forest B is not the one synced to Office 365 but the Linked Mailbox on Forest A.   

 

Problem now is: After realizing that even when changing the disabled user's password on Forest A doesn't sync I decided to upgrade Dirsync but after the upgrade I got an alert that Dirsync stopped exporting changes to Office 365 due to the limited threshold of requested deletions which is by default 500 objects but in my case it reached up to 2250 users.  I checked the Dirsync users that are about to get deleted and found that all of them are Linkedmailboxes. Things I tried so far to sync the users: 

 

1- Tried Enabling the syncing of Disabled users by edit sync rules (Scoping filter)

UserAccountControl from Operator value = ISBITNOTSET =2 to ISNOTNULL = 0

 

2- Tried Changing 

 

In from AD – User Common from Exchange
of the Exchange forest

From 

 

Expression >> SourceObjectType >>> IIF(IsPresent([msExchRecipientTypeDetails]), IIF([msExchRecipientTypeDetails]=2, NULL, “User”), “User”)

 

Changed to

 

IIF(IsPresent([msExchRecipientTypeDetails]), IIF([msExchRecipientTypeDetails]=666, NULL, “User”), “User”)

 

Prior to Upgrading Dirsync, I took a backup of all the rules that I have in Dirsync, I tried checking them but couldn't find where the rule that allows Linkedmailboxes to get synced and couldn't find it. I would be happy to share this and get help from anyone who did this before.Thank you

 

1 Reply

@Mohammed Hamada I have done a recovery from backup and it's all working well now.

Couldn't find out where is the culprit though.