This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 50%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBP%3C/text%3E%3C/svg%3E)
I am having an issue with any new mailbox that is created in directly EXO or o365, any message it sends to any Hotmail or Outlook.com mailbox ends up in the junk folder.
We do not have this issue with accounts that are created in our on-prem AD and the mailbox is activated by way of executing the "Enable-RemoteMailbox" PS cmd.
All our mail flows out the same path and all mail is SPF/DMARC pass, the only difference is how the account are created. I've had a premier suppport case open about this, but support has been useless.
Any suggestions why the email from mailbox created in cloud are always junked in outlook.com recipients?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 18%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
Hi @Bob Pants ,
Thank you for posting to Microsoft Community. We are happy to help you.
Based on your description, I understand the issue is the mails from new mailbox created in EXO would ends up in the junk folder and you may want to seek some suggestions.
May I know this issue happen with only Outlook mail system? If so, it could be related to the email system provider since only Outlook identify all emails from your organization as spam.
As the question why the accounts are created in on-prem AD works fine, you should notice the email headers for cloud-created mailboxes might differ slightly from those created through "Enable-RemoteMailbox" command. Please compare the headers from emails sent from cloud-created mailboxes against those from on-prem AD-created mailboxes.
If there are anything else I can do for you, please let me know.
The issue is only with Outlook.com recipients. o365, Gmail etc are all fine.
Sure, I can check the headers, how does this help me though, what am I looking for?
in either case, both scenarios are DMARC pass
Hi,
Since email headers for cloud-created mailboxes might differ slightly from those created through "Enable-RemoteMailbox" command. It is possible to compare the differences between the emails to determine possible reason why they are being treated differently.
As you said the issue is only with Outlook.com, but other mail systems work fine. This is most likely related to the way Outlook.com recognizing your organization. You could fill in the relevant information through the following link trying to fix the issue New support request (office.com).
If there is anything else we can do for you, please feel free to inform us.
Just checking in to see if above information was helpful.
If the issue has been resolved, please mark the helpful replies as answers.
it's still unresolved. I had already tried that support request for office.com, they said "can't see any issue"
Hi,
Based on your description above, looks like the issue is more related to Outlook.com, please kindly understand that the Exchange tag here we mainly focus on general issues about Exchange Server. It's suggested that you could post your case in dedicated forum for Outlook.com for more professional advice. Thanks for your understanding.
Just checking in to see if above information was helpful.
If the issue has been resolved, please mark the helpful replies as answers.