how to convert "in cloud" to "synced from AD"?

%3CLINGO-SUB%20id%3D%22lingo-sub-691744%22%20slang%3D%22en-US%22%3ERe%3A%20how%20to%20convert%26nbsp%3B%22in%20cloud%22%20to%20%22synced%20from%20AD%22%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-691744%22%20slang%3D%22en-US%22%3EIf%20they%20are%20restored%20and%20then%20in%20a%20synced%20OU%2C%20they%20should%20match%20and%20start%20to%20sync%20again%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-691761%22%20slang%3D%22en-US%22%3ERe%3A%20how%20to%20convert%26nbsp%3B%22in%20cloud%22%20to%20%22synced%20from%20AD%22%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-691761%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3E%26nbsp%3B%20after%20restoring%20%22deleted%20User%22%2C%20i%20ran%20delta%20sync%2C%20the%20ad%20profile%20was%20visible%20in%20%22adds%22%20in%20sync%20service%20manager%20but%20the%20profile%20in%20O365%20is%20still%20%22in%20cloud%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-691802%22%20slang%3D%22en-US%22%3ERe%3A%20how%20to%20convert%26nbsp%3B%22in%20cloud%22%20to%20%22synced%20from%20AD%22%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-691802%22%20slang%3D%22en-US%22%3ETry%20running%20a%20full%20sync%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-692484%22%20slang%3D%22en-US%22%3ERe%3A%20how%20to%20convert%26nbsp%3B%22in%20cloud%22%20to%20%22synced%20from%20AD%22%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-692484%22%20slang%3D%22en-US%22%3EIf%20you%20had%20to%20manually%20restore%20them%2C%20then%20the%20sync%20isn't%20picking%20up%20the%20OU%20and%20the%20users%20in%20it%2C%20it%20should%20match%20them%20right%20back%20up%20and%20restore%20them%20for%20you%2C%20but%20if%20you%20did%20it%20ahead%20of%20time.%20as%20adam%20said%2C%20since%20adding%20an%20OU%20you%20probably%20need%20a%20full%20sync.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-693899%22%20slang%3D%22en-US%22%3ERe%3A%20how%20to%20convert%26nbsp%3B%22in%20cloud%22%20to%20%22synced%20from%20AD%22%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-693899%22%20slang%3D%22en-US%22%3E%3CP%3Eusers%20are%20restored%20from%20%22deleted%20users%22%20in%20O365%3CBR%20%2F%3E%3CBR%20%2F%3Ewhich%20should%20come%20first%2C%20restoring%20from%20%22deleted%20users%22%20in%20O365%20or%20resynching%20the%20OU%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-693927%22%20slang%3D%22en-US%22%3ERe%3A%20how%20to%20convert%26nbsp%3B%22in%20cloud%22%20to%20%22synced%20from%20AD%22%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-693927%22%20slang%3D%22en-US%22%3EShouldn't%20matter%2C%20either%20method%20will%20end%20up%20with%20synced%20accounts.%20If%20you%20do%20OU%20first%2C%20it'll%20take%20the%20account%20back%20active%20automatically%20I%20believe%2C%20or%20if%20you%20restore%20manually%20first%2C%20then%20sync%2C%20it'll%20update%20the%20o365%20user%20and%20sync%20to%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-694044%22%20slang%3D%22en-US%22%3ERe%3A%20how%20to%20convert%26nbsp%3B%22in%20cloud%22%20to%20%22synced%20from%20AD%22%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-694044%22%20slang%3D%22en-US%22%3EYeah!%20Have%20you%20tried%20a%20full%20sync%20yet%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-691719%22%20slang%3D%22en-US%22%3Ehow%20to%20convert%26nbsp%3B%22in%20cloud%22%20to%20%22synced%20from%20AD%22%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-691719%22%20slang%3D%22en-US%22%3E%3CP%3Ean%20OU%20was%20accidentally%20omitted%20in%20sync%20scope%20from%20AD%20(200%20users)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eusers%20was%20deemed%20%22deleted%20users%22%20in%20O365%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Etried%20the%20ff%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20revert%20and%20include%20OU%20in%20sync%20scope%3C%2FP%3E%3CP%3E-%20restore%20%22deleted%20users%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eissue%20is%20that%20restored%20user%20are%20%22in%20cloud%22%20and%20not%20%22synched%20from%20AD%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehow%20to%20convert%26nbsp%3B%22in%20cloud%22%20to%20%22synced%20from%20AD%22%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-691719%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Super Contributor

an OU was accidentally omitted in sync scope from AD (200 users)

 

users was deemed "deleted users" in O365

 

tried the ff:

 

- revert and include OU in sync scope

- restore "deleted users"

 

issue is that restored user are "in cloud" and not "synched from AD"

 

how to convert "in cloud" to "synced from AD"?

7 Replies
Highlighted
If they are restored and then in a synced OU, they should match and start to sync again
Highlighted

@adam deltinger  after restoring "deleted User", i ran delta sync, the ad profile was visible in "adds" in sync service manager but the profile in O365 is still "in cloud"

Highlighted
Try running a full sync
Highlighted
If you had to manually restore them, then the sync isn't picking up the OU and the users in it, it should match them right back up and restore them for you, but if you did it ahead of time. as adam said, since adding an OU you probably need a full sync.
Highlighted

users are restored from "deleted users" in O365

which should come first, restoring from "deleted users" in O365 or resynching the OU?

Highlighted
Shouldn't matter, either method will end up with synced accounts. If you do OU first, it'll take the account back active automatically I believe, or if you restore manually first, then sync, it'll update the o365 user and sync to it.
Highlighted
Yeah! Have you tried a full sync yet?