Forum Discussion
Recipient SendAs:You can't use the domain because it's not an accepted domain for your organization
Cross-premises Send As permissions are NOT supported. Yet. And you cannot use the contact object representation in O365 for permissions.
Please refer the below article
https://technet.microsoft.com/en-in/library/dn249373(v=exchg.150).aspx
Using the above article we have already implemented and also we are syncing the mail enabled public folder to exchange online using the below link
https://blogs.technet.microsoft.com/undocumentedfeatures/2017/04/08/migrating-hybrid-public-folders-to-office-365/
After the above setup, we are able to give send as permission on mail public folders to the users, but now we are facing issue only on a particular mail enabled public folder and the error is quite irrelevant
Syncing the (ME)PFs is very different from migrating them, actually is just one of the many steps you need to perform for the actual migration. As you can see in the article, those permissions are added only after the PF are migrated. Not synced, migrated. So perhaps you want to clarify on your current setup?
Not Necessarily, See we have our users in our on-prem exchange server and Exchange online as well, we are not migrating our public folders to exchange online for now but instead we are syncing public folder AD objects to exchange online so that users from Office 365 can identity mail enabled public folder. This is how been set up in our environment and now we are facing issue with one public folder.
See the below screenshot for reference
the above script is to give send as permission mail enabled public folder for an Office 365 user
