Forum Discussion
PJR_CDF
Apr 06, 2020Iron Contributor
O365 ATP - Ensuring Junk Email settings on Exchange Mailboxes are enabled for ZAP and Anti-spam
Hi All, I am looking at best practices for O365 ATP deployment and have reviewed a ton of documentation and presentations, and understand the need to ensure that Junk Email Settings are enabled f...
- May 11, 2020End users can disable junk folder in OWA
Click on the Options tool at the top right of the OWA page.
Click on See All Options...
Click on Block or Allow in the column on the left.
Click to select the Don't move e-mail to my Junk E-Mail folder option, which is at the top.
And the more techie end-users can connect to Exchange Online PowerShell and they can run this command against their own user mailbox.
You can prevent end-users from doing this by creating a custom policy, and you can also disable them from launching Exchange remote PowerShell:
for a single user: Set-User -Identity david@contoso.com -RemotePowerShellEnabled $false
for all users: get-user -resultsize unlimited | set-user -RemotePowerShellEnabled $false
(just be sure to exclude yourself and other global admins otherwise you'll lock yourself out.)
You can enable junk mail folder on all mailboxes with this one commnad:
$All = Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited; $All | foreach {Set-MailboxJunkEmailConfiguration $_.Name -Enabled $true}
If this was helpful, please mark as best answer. thanks!
-Joe
Joe Stocker
May 11, 2020Bronze Contributor
End users can disable junk folder in OWA
Click on the Options tool at the top right of the OWA page.
Click on See All Options...
Click on Block or Allow in the column on the left.
Click to select the Don't move e-mail to my Junk E-Mail folder option, which is at the top.
And the more techie end-users can connect to Exchange Online PowerShell and they can run this command against their own user mailbox.
You can prevent end-users from doing this by creating a custom policy, and you can also disable them from launching Exchange remote PowerShell:
for a single user: Set-User -Identity david@contoso.com -RemotePowerShellEnabled $false
for all users: get-user -resultsize unlimited | set-user -RemotePowerShellEnabled $false
(just be sure to exclude yourself and other global admins otherwise you'll lock yourself out.)
You can enable junk mail folder on all mailboxes with this one commnad:
$All = Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited; $All | foreach {Set-MailboxJunkEmailConfiguration $_.Name -Enabled $true}
If this was helpful, please mark as best answer. thanks!
-Joe
Click on the Options tool at the top right of the OWA page.
Click on See All Options...
Click on Block or Allow in the column on the left.
Click to select the Don't move e-mail to my Junk E-Mail folder option, which is at the top.
And the more techie end-users can connect to Exchange Online PowerShell and they can run this command against their own user mailbox.
You can prevent end-users from doing this by creating a custom policy, and you can also disable them from launching Exchange remote PowerShell:
for a single user: Set-User -Identity david@contoso.com -RemotePowerShellEnabled $false
for all users: get-user -resultsize unlimited | set-user -RemotePowerShellEnabled $false
(just be sure to exclude yourself and other global admins otherwise you'll lock yourself out.)
You can enable junk mail folder on all mailboxes with this one commnad:
$All = Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited; $All | foreach {Set-MailboxJunkEmailConfiguration $_.Name -Enabled $true}
If this was helpful, please mark as best answer. thanks!
-Joe
John_Weiss
Aug 19, 2021Copper Contributor
seems unavailable in OWA now.
i created a rule to move all messages to Inbox. I don't know yet if it will work.
i created a rule to move all messages to Inbox. I don't know yet if it will work.
- Marc MönnikesSep 28, 2021Brass ContributorHello,
yes, the option is only in the old Classic view available. . .
New OWA and outlook = no option available to disable this completly.
Maybe an automated job would be nice to disable this for all users...
Regards
Marc