Forum Discussion
Recipient SendAs:You can't use the domain because it's not an accepted domain for your organization
Issue: While Setting Up Send As Permission for an Office 365 User on On-Prem Exchange 2013 Mail Enabled Public Folder, I am getting the following error
Verified Information:
- Verified accepted domain on both the ECP
- Removed invalid domain (domain.local) entries from Mail Enabled Public folder and also verified users from O365 has the same entry.
- Mail Enabled Public Folder Contacts are synced almost everyday using (SyncMailPublicFolders.ps1) script (https://blogs.technet.microsoft.com/undocumentedfeatures/2017/04/08/migrating-hybrid- public-folders-to-office-365/)
- Verified the Mail Enabled Public Folder Contacts in Office 365 and the Email address entries
References Related to the Issue: https://support.microsoft.com/en-us/help/3067179/-hybrid-domain-domain-isn-t-an-accepted-domain-for-the-cloud-organizat
Please Assist
6 Replies
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?
