SOLVED

Send As for Shared Mailbox in Office 365

%3CLINGO-SUB%20id%3D%22lingo-sub-1617403%22%20slang%3D%22en-US%22%3ESend%20As%20for%20Shared%20Mailbox%20in%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1617403%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20Afternoon%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20in%20the%20process%20of%20migrating%20our%20user%20base%20to%20Office365%2C%20so%20right%20now%20we%20are%20in%20a%20hybrid%20mode.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20user%2C%20her%20mailbox%20is%20still%20on-prem.%26nbsp%3B%20OnPrem%20we%20have%20Exchange%202016.%26nbsp%3B%20%26nbsp%3BShe%20was%20recently%20given%20Full%20Access%20and%20Send%20As%20permissions%20to%20a%20shared%20mailbox%20that%20was%20migrated%20to%20Exchange%20Online.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20she%20is%20unable%20to%20send%20from%20that%20mailbox%2C%26nbsp%3B%20or%20forward%20from%20that%20mailbox%20to%20hers.%26nbsp%3B%20We%20have%20seen%20this%20recently%20where%20the%20shared%20mailbox%20is%20on-prem%20and%20user%20mailbox%20migrated%20and%20we%20would%20run%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EAdd-ADPermission%26nbsp%3B-Identity%26nbsp%3BEXO1%26nbsp%3B-User%26nbsp%3BONPREM1%26nbsp%3B-AccessRights%26nbsp%3BExtendedRight%26nbsp%3B-ExtendedRights%26nbsp%3B%22Send%20As%22%20from%20On-Prem%20Exchange%20Powershell%20and%20then%20run%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3EAdd-RecipientPermission%20-Identity%20ILiketoSmile%20-Trustee%20smileyg%40chop.edu%20-AccessRights%20SendAs%20in%20Exchange%20Online%20PS.%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EWe%20have%20tried%20to%20have%20her%20go%20to%20on-prem%20webmail%2C%20login%20with%20shared%20mailbox%20credentials%2C%20click%20the%20redirect%20link%20and%20still%20did%20not%20work.%26nbsp%3B%20Had%20her%20login%20to%20a%20VDI%20with%20that%20account%2C%20still%20would%20not%20open.%20I%20believe%20we%20are%20going%20to%20migrate%20her%20account%2C%20but%20even%20at%20that%2C%20we%20are%20looking%20at%203-5%20day%20turnaround%20time.%26nbsp%3B%20%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EWas%20wondering%20if%20anyone%20might%20know%20of%20a%20workaround%20we%20can%20put%20into%20place.%26nbsp%3B%20or%20a%20script%20that%20we%20can%20try%20to%20run%20to%20keep%20her%20in%20business%20while%20we%20do%20the%20migration.%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EThank%20You%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3EBrian%20Dougherty%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1617403%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ehybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1624894%22%20slang%3D%22en-US%22%3ERe%3A%20Send%20As%20for%20Shared%20Mailbox%20in%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1624894%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F773846%22%20target%3D%22_blank%22%3E%40BrianDoc770%3C%2FA%3E%26nbsp%3BHi%2C%20on%20the%20run%20but%20see%20if%20this%20can%20assist%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fshared-mailboxes%2Fcannot-access-mailbox%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fshared-mailboxes%2Fcannot-access-mailbox%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1625039%22%20slang%3D%22en-US%22%3ERe%3A%20Send%20As%20for%20Shared%20Mailbox%20in%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1625039%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F551905%22%20target%3D%22_blank%22%3E%40bec064%3C%2FA%3E%26nbsp%3B-%20Good%20Morning%3C%2FP%3E%3CP%3EThank%20you%20for%20article%20link.%26nbsp%3B%20Spoke%20to%20my%20lead%20and%20we%20are%20just%20going%20to%20migrate%20her%20to%20Office365%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Good Afternoon, 

 

We are in the process of migrating our user base to Office365, so right now we are in a hybrid mode. 

I have a user, her mailbox is still on-prem.  OnPrem we have Exchange 2016.   She was recently given Full Access and Send As permissions to a shared mailbox that was migrated to Exchange Online.  

 

Now she is unable to send from that mailbox,  or forward from that mailbox to hers.  We have seen this recently where the shared mailbox is on-prem and user mailbox migrated and we would run 

Add-ADPermission -Identity EXO1 -User ONPREM1 -AccessRights ExtendedRight -ExtendedRights "Send As" from On-Prem Exchange Powershell and then run:

 

Add-RecipientPermission -Identity ILiketoSmile -Trustee smileyg@chop.edu -AccessRights SendAs in Exchange Online PS. 
 
We have tried to have her go to on-prem webmail, login with shared mailbox credentials, click the redirect link and still did not work.  Had her login to a VDI with that account, still would not open. I believe we are going to migrate her account, but even at that, we are looking at 3-5 day turnaround time.   
 
Was wondering if anyone might know of a workaround we can put into place.  or a script that we can try to run to keep her in business while we do the migration. 
 
Thank You

Brian Dougherty
2 Replies
Highlighted
Best Response confirmed by BrianDoc770 (New Contributor)
Highlighted

@bec064 - Good Morning

Thank you for article link.  Spoke to my lead and we are just going to migrate her to Office365