Home

Recipient SendAs:You can't use the domain because it's not an accepted domain for your organization

%3CLINGO-SUB%20id%3D%22lingo-sub-130537%22%20slang%3D%22en-US%22%3ERecipient%20SendAs%3AYou%20can't%20use%20the%20domain%20because%20it's%20not%20an%20accepted%20domain%20for%20your%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130537%22%20slang%3D%22en-US%22%3E%3CP%3EIssue%3A%26nbsp%3B%20%26nbsp%3BWhile%20Setting%20Up%20Send%20As%20Permission%20for%20an%20Office%20365%20User%20on%20On-Prem%20Exchange%202013%26nbsp%3BMail%20Enabled%20Public%20Folder%2C%20I%20am%20getting%20the%20following%20error%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20851px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F24585i5FAE720CDFB9C5F6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Sendas%20Issue.PNG%22%20title%3D%22Sendas%20Issue.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EVerified%20Information%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%26nbsp%3B%20%26nbsp%3BVerified%20accepted%20domain%20on%20both%20the%20ECP%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3B%20%26nbsp%3BRemoved%20invalid%20domain%20(domain.local)%20entries%20from%20Mail%20Enabled%20Public%20folder%20and%20also%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%20verified%20users%20from%20O365%20has%20the%20same%20entry.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3B%20%26nbsp%3BMail%20Enabled%20Public%20Folder%20Contacts%20are%20synced%20almost%20everyday%20using%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B(%3CSPAN%3ESyncMailPublicFolders.ps1)%20script%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20(%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fundocumentedfeatures%2F2017%2F04%2F08%2Fmigrating-hybrid-%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fundocumentedfeatures%2F2017%2F04%2F08%2Fmigrating-hybrid-%26nbsp%3B%3C%2FA%3E%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20public-folders-to-office-365%2F)%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3BVerified%20the%20Mail%20Enabled%20Public%20Folder%20Contacts%20in%20Office%20365%20and%20the%20Email%20address%20entries%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EReferences%20Related%20to%20the%20Issue%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3067179%2F-hybrid-domain-domain-isn-t-an-accepted-domain-for-the-cloud-organizat%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3067179%2F-hybrid-domain-domain-isn-t-an-accepted-domain-for-the-cloud-organizat%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EPlease%20Assist%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-130537%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eaccepted%20domain%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDomain%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ERecipient%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESendAs%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297905%22%20slang%3D%22en-US%22%3ERe%3A%20Recipient%20SendAs%3AYou%20can't%20use%20the%20domain%20because%20it's%20not%20an%20accepted%20domain%20for%20your%20organizat%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297905%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F97181%22%20target%3D%22_blank%22%3E%40Sujith%20Suriya%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20might%20have%20already%20resolve%20this%20issue%2C%20however%20just%20wanted%20to%20check%20what%20was%20the%20resolution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20been%20able%20to%20resolve%20similar%20issue%20using%20the%20below%20mentioned%20action%20plan.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3ECheck%20the%20UPN%20and%20Email%20Addresses%20of%20the%20users%20that%20you%20are%20having%20problems%20with.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EChances%20are%20they%20have%20an%20email%20address%20on%20a%20domain%20that%20is%20not%20verified%20against%20your%20Office%20365%20tenant.%20%26nbsp%3BUsually%20something%20like%20%3CA%20href%3D%22mailto%3Auser%40domain.local%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euser%40domain.local%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSTRONG%3EOne%20can%20use%20the%20below%20commands%20to%20check%20the%20proxy%20address%20and%20domain.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fpowershell%2Fconnect-to-office-365-powershell%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EConnect%20to%20Office%20365%20PowerShell%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EGet-MsolDomain%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EGet-MsolUser%20-UserPrincipalName%20user%40domain.com%20%7C%20FL%20*ProxyAddresses*%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3EConnect%20to%20Exchange%20Online%20PowerShell%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EGet-AcceptedDomain%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EGet-Mailbox%20user%40domain.com%20%7C%20select%20-ExpandProperty%20EmailAddresses%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3ELaunch%20Exchange%20Management%20Shell%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EGet-AcceptedDomain%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EGet-Mailbox%20user%40domain.com%20%7C%20select%20-ExpandProperty%20EmailAddresses%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERef%20link%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fx500.co.uk%2F2018%2F04%2F03%2Fsend-as-you-cant-use-the-domain-because-its-not-an-accepted-domain-for-your-organization%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fx500.co.uk%2F2018%2F04%2F03%2Fsend-as-you-cant-use-the-domain-because-its-not-an-accepted-domain-for-your-organization%2F%3C%2FA%3E%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3E%3CA%20href%3D%22http%3A%2F%2Fkevinongkl.blogspot.com%2F2016%2F09%2Fyou-cant-use-domain-because-its-not.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fkevinongkl.blogspot.com%2F2016%2F09%2Fyou-cant-use-domain-because-its-not.html%3C%2FA%3E%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.spiceworks.com%2Ftopic%2F337146-you-can-t-use-the-domain%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcommunity.spiceworks.com%2Ftopic%2F337146-you-can-t-use-the-domain%3C%2FA%3E%20%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERegards%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EMukesh%20Rawat%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130692%22%20slang%3D%22en-US%22%3ERe%3A%20Recipient%20SendAs%3AYou%20can't%20use%20the%20domain%20because%20it's%20not%20an%20accepted%20domain%20for%20your%20organizat%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130692%22%20slang%3D%22en-US%22%3E%3CP%3Eyou%20are%20right%2C%20but%20i%20am%20referring%20to%20syncing%20but%20not%20migration.%20even%20in%20AD%20Connect%20newer%20version%20we%20have%20this%20option%20for%20syncing%20mail%20enabled%20public%20folder%20exchange.%3C%2FP%3E%0A%3CP%3Ehope%20you%20understand%20my%20issue%20from%20my%20previous%20post%20and%20this%20one%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eplease%20assist.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130662%22%20slang%3D%22en-US%22%3ERe%3A%20Recipient%20SendAs%3AYou%20can't%20use%20the%20domain%20because%20it's%20not%20an%20accepted%20domain%20for%20your%20organizat%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130662%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20Necessarily%2C%26nbsp%3B%20See%20we%20have%20our%20users%20in%20our%20on-prem%20exchange%20server%20and%20Exchange%20online%20as%20well%2C%20we%20are%20not%20migrating%20our%20public%20folders%20to%20exchange%20online%26nbsp%3Bfor%20now%26nbsp%3Bbut%20instead%20we%26nbsp%3Bare%20syncing%20public%20folder%20AD%20objects%20to%20exchange%20online%20so%20that%20users%20from%20Office%20365%20can%20identity%20mail%20enabled%20public%20folder.%20This%20is%20how%20been%20set%20up%20in%20our%20environment%20and%20now%20we%20are%20facing%20issue%20with%20one%20public%20folder.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESee%20the%20below%20screenshot%20for%20reference%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20752px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F24605iB9760E39BC5EB929%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22123434.PNG%22%20title%3D%22123434.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ethe%20above%20script%20is%20to%20give%20send%20as%20permission%20mail%20enabled%20public%20folder%20for%20an%20Office%20365%20user%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130653%22%20slang%3D%22en-US%22%3ERe%3A%20Recipient%20SendAs%3AYou%20can't%20use%20the%20domain%20because%20it's%20not%20an%20accepted%20domain%20for%20your%20organizat%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130653%22%20slang%3D%22en-US%22%3E%3CP%3ESyncing%20the%20(ME)PFs%20is%20very%20different%20from%20migrating%20them%2C%20actually%20is%20just%20one%20of%20the%20many%20steps%20you%20need%20to%20perform%20for%20the%20actual%20migration.%20As%20you%20can%20see%20in%20the%20article%2C%20those%20permissions%20are%20added%20only%20after%20the%20PF%20are%20migrated.%20Not%20synced%2C%20migrated.%20So%20perhaps%20you%20want%20to%20clarify%20on%20your%20current%26nbsp%3Bsetup%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130643%22%20slang%3D%22en-US%22%3ERe%3A%20Recipient%20SendAs%3AYou%20can't%20use%20the%20domain%20because%20it's%20not%20an%20accepted%20domain%20for%20your%20organizat%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130643%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20refer%20the%20below%20article%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-in%2Flibrary%2Fdn249373(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-in%2Flibrary%2Fdn249373(v%3Dexchg.150).aspx%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EUsing%20the%20above%20article%20we%20have%20already%20implemented%20and%20also%20we%20are%20syncing%20the%20mail%20enabled%20public%20folder%20to%20exchange%20online%20using%20the%20below%20link%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fundocumentedfeatures%2F2017%2F04%2F08%2Fmigrating-hybrid-public-folders-to-office-365%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fundocumentedfeatures%2F2017%2F04%2F08%2Fmigrating-hybrid-public-folders-to-office-365%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EAfter%20the%20above%20setup%2C%20we%20are%20able%20to%20give%20send%20as%20permission%20on%20mail%20public%20folders%20to%20the%20users%2C%20but%20now%20we%20are%20facing%20issue%20only%20on%20a%20particular%20mail%20enabled%20public%20folder%20and%20the%20error%20is%20quite%20irrelevant%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130638%22%20slang%3D%22en-US%22%3ERe%3A%20Recipient%20SendAs%3AYou%20can't%20use%20the%20domain%20because%20it's%20not%20an%20accepted%20domain%20for%20your%20organizat%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130638%22%20slang%3D%22en-US%22%3E%3CP%3ECross-premises%20Send%20As%20permissions%20are%20NOT%20supported.%20Yet.%20And%20you%20cannot%20use%20the%20contact%20object%20representation%20in%20O365%20for%20permissions.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Sujith Suriya
New Contributor

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

 

 

Sendas Issue.PNG

 

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-...

 

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-...

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

 

123434.PNG

 

the above script is to give send as permission mail enabled public folder for an Office 365 user

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.

@Sujith Suriya

 

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.

 

  • Check the UPN and Email Addresses of the users that you are having problems with.
  • Chances are they have an email address on a domain that is not verified against your Office 365 tenant.  Usually something like user@domain.local.

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

https://x500.co.uk/2018/04/03/send-as-you-cant-use-the-domain-because-its-not-an-accepted-domain-for...

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

Related Conversations
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
2 Replies
*Updated 9/3* Syncing in Microsoft Edge Preview Channels
Elliot Kirk in Articles on
202 Replies
Early preview of Microsoft Edge group policies
Sean Lyndersay in Discussions on
65 Replies