Microsoft has improved upon and added some new enhancements to the EOP service:
- Directory-based edge blocking
- Office 365 domain limit increased
- View message traces up to 90 days
- Remote PowerShell
- OWA Junk mail reporting
- Spam quarantine access for users
- DomainKeys Identified Mail support
- Enhanced IPv6 support
- Match subdomains feature
- Geocentric affinity
Highlights from the article:
Spam quarantine access for users
In previous versions of EOP quarantine access was only available at the administrator level. Now individual mail users will be able to access their own quarantine to manage spam via the EAC web interface. Users must have a valid Office 365 user ID and password in order to access the spam quarantine page. For current Exchange online subscribers, users should already be able to access their spam quarantine with their current user ID and password. EOP only subscribers can utilize Directory Synchronization and password sync to automate access for their end users.
Directory-based edge blocking
DBEB allows organizations to reject messages for invalid recipients at the network perimeter. DBEB will block all messages sent to an email address that isn’t present in the Azure Active Directory.
View message traces up to 90 days
Admins can now request message trace information for up to 90 days. Message traces for the past seven days can be viewed immediately.
EOP customers now have the ability to use remote PowerShell to manage Exchange Online Protection settings and use PowerShell scripting to automate a variety of management tasks.
OWA Junk mail reporting
Easily report junk mail back to Microsoft EOP team. Users can report a false negative or positive back to Microsoft by right-clicking within the mail message and selecting ‘mark as junk’ or ‘mark as not junk’. This will help improve the spam filtering capabilities of Exchange Online Protection.
To understand how EOP works, click this link:
About the author
Welcome to the Interlink Cloud Blog
All content provided on this blog is for informational purposes only. The owner of this blog makes no representations or warranties regarding the information from our partners or other external sources.