Nov 22 2017
07:23 AM
- last edited on
Feb 06 2023
04:03 AM
by
TechCommunityAP
Nov 22 2017
07:23 AM
- last edited on
Feb 06 2023
04:03 AM
by
TechCommunityAP
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:
References Related to the Issue: https://support.microsoft.com/en-us/help/3067179/-hybrid-domain-domain-isn-t-an-accepted-domain-for-...
Please Assist
Nov 22 2017 10:16 AM
Cross-premises Send As permissions are NOT supported. Yet. And you cannot use the contact object representation in O365 for permissions.
Nov 22 2017 10:24 AM
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
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
Nov 22 2017 10:32 AM
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?
Nov 22 2017 10:50 AM - edited Nov 22 2017 10:52 AM
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
Nov 22 2017 12:21 PM
you are right, but i am referring to syncing but not migration. even in AD Connect newer version we have this option for syncing mail enabled public folder exchange.
hope you understand my issue from my previous post and this one
please assist.
Dec 08 2018 06:30 PM - edited Dec 08 2018 06:31 PM
You might have already resolve this issue, however just wanted to check what was the resolution.
I have been able to resolve similar issue using the below mentioned action plan.
One can use the below commands to check the proxy address and domain.
Connect to Office 365 PowerShell
Get-MsolDomain
Get-MsolUser -UserPrincipalName user@domain.com | FL *ProxyAddresses*
Connect to Exchange Online PowerShell
Get-AcceptedDomain
Get-Mailbox user@domain.com | select -ExpandProperty EmailAddresses
Launch Exchange Management Shell
Get-AcceptedDomain
Get-Mailbox user@domain.com | select -ExpandProperty EmailAddresses
Ref link
http://kevinongkl.blogspot.com/2016/09/you-cant-use-domain-because-its-not.html
https://community.spiceworks.com/topic/337146-you-can-t-use-the-domain
Regards
Mukesh Rawat