SOLVED

Undelegated mailboxes wont stop auto mapping to User

%3CLINGO-SUB%20id%3D%22lingo-sub-217755%22%20slang%3D%22en-US%22%3EUndelegated%20mailboxes%20wont%20stop%20auto%20mapping%20to%20User%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-217755%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStumped%20with%20this%20one%20(and%20it%20seems%20Office365%20Support%20are%20too)%2C%20I%20thought%20I%20would%20give%20it%20a%20try%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20environment%20used%20to%20run%20on%20Exchange%202013%20On%20premise%2C%20now%20runs%20365%20Synced%20with%20our%20DC.%3CBR%20%2F%3E%3CBR%20%2F%3EUser%20A%20used%20to%20have%20delegated%20access%20to%20example%201%20(a%20shared%20mailbox)%20and%20example%202%20(a%20users%20mailbox)%3CBR%20%2F%3E%3CBR%20%2F%3EThese%20have%20been%20removed%20a%20long%20time%20ago%2C%20however%20they%20continue%20to%20propagate%20to%20User%20A.%20Create%20a%20new%20cached%20or%20non%20cached%20profile%20on%20Outlook%2C%20within%20moments%20the%20boxes%20that%20have%20no%20conceived%20connection%20(checked%20via%20power%20shell%20or%20the%20365%20GUI)%20have%20returned!%3CBR%20%2F%3E%3CBR%20%2F%3EHave%20tried%20restoring%20those%20delegations%2C%20then%20removing%20again%2C%20deleting%20profile%20on%20PC%20and%20starting%20from%20scratch%2C%20checked%20the%20DC%20for%20any%20links%20and%20nothing!%3CBR%20%2F%3E%3CBR%20%2F%3E365%20Support%20have%20escalated%20the%20case%20twice%2C%20and%20now%20aren't%20responding.%3CBR%20%2F%3E%3CBR%20%2F%3EDoes%20anybody%20have%20any%20ideas%20or%20insights%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-217755%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-219106%22%20slang%3D%22en-US%22%3ERe%3A%20Undelegated%20mailboxes%20wont%20stop%20auto%20mapping%20to%20User%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-219106%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Vasil%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%20this%20solved%20my%20issue!%20Clearing%20the%20mapping%20did%20the%20trick!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-218037%22%20slang%3D%22en-US%22%3ERe%3A%20Undelegated%20mailboxes%20wont%20stop%20auto%20mapping%20to%20User%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-218037%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20try%20using%20the%20%E2%80%93ClearAutoMapping%20flag%20for%20Remove-MailboxPermission%2C%20I've%20posted%20some%20examples%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.michev.info%2FBlog%2FPost%2F1382%2Fremoving-automapping-and-resetting-default-mailbox-permissions-in-exchange-online%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.michev.info%2FBlog%2FPost%2F1382%2Fremoving-automapping-and-resetting-default-mailbox-permissions-in-exchange-online%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20those%20mailboxes%20previously%20existed%20on-premises%2C%20you%20might%20need%20to%20clean%20up%20the%20AD%20attributes%20as%20well%2C%20msExchDelegateListLink%20in%20specific.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-217776%22%20slang%3D%22en-US%22%3ERe%3A%20Undelegated%20mailboxes%20wont%20stop%20auto%20mapping%20to%20User%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-217776%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3Bjust%20appear%20on%20the%20Outlook%2C%20when%20you%20try%20to%20open%20them%20the%20User%20receives%20an%20error%20stating%20it%20cannot%20be%20opened.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-217772%22%20slang%3D%22en-US%22%3ERe%3A%20Undelegated%20mailboxes%20wont%20stop%20auto%20mapping%20to%20User%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-217772%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Clinton%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20the%20user%20A%20access%20example%201%20and%20example%202%20or%20do%20they%20just%20appear%20to%20the%20Outlook%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi Everyone,

 

Stumped with this one (and it seems Office365 Support are too), I thought I would give it a try here.

 

The environment used to run on Exchange 2013 On premise, now runs 365 Synced with our DC.

User A used to have delegated access to example 1 (a shared mailbox) and example 2 (a users mailbox)

These have been removed a long time ago, however they continue to propagate to User A. Create a new cached or non cached profile on Outlook, within moments the boxes that have no conceived connection (checked via power shell or the 365 GUI) have returned!

Have tried restoring those delegations, then removing again, deleting profile on PC and starting from scratch, checked the DC for any links and nothing!

365 Support have escalated the case twice, and now aren't responding.

Does anybody have any ideas or insights?

4 Replies
Highlighted

Hi Clinton,

 

Can the user A access example 1 and example 2 or do they just appear to the Outlook?

Highlighted

 just appear on the Outlook, when you try to open them the User receives an error stating it cannot be opened.

Highlighted
Solution

You can try using the –ClearAutoMapping flag for Remove-MailboxPermission, I've posted some examples here: https://www.michev.info/Blog/Post/1382/removing-automapping-and-resetting-default-mailbox-permission...

 

If those mailboxes previously existed on-premises, you might need to clean up the AD attributes as well, msExchDelegateListLink in specific.

Highlighted

Hi Vasil,

 

Thanks, this solved my issue! Clearing the mapping did the trick!