Microsoft says that Office 365 will support internationalized email addresses (EAI) in Q1 2018. Support is limited to inbound and outbound email and you will not be able to assign email addresses with non-Latin characters to Office 365 accounts until all the heavy lifting is done to make sure that nothing breaks, including in hybrid organizations.
Exchange Online Protection now highlights unauthenticated users – or messages that come from people who cannot prove their identity. Instead of a nice picture (or avatar), you see a question mark for the user. Maybe this might make people think twice about the opportunity to send money to someone to liberate funds held in a bank. Just maybe.
A year ago, Microsoft said RPC over HTTP was dead from Oct 31, 2017 and that Outlook clients must use MAPI over HTTP to connect to Exchange Online. The protocol is still dead, but it will persist in a zombie-like unsupported mode. The question is for how long?
You can capture Exchange mailbox events in the Office 365 audit log, but only if you remember to enable auditing for target mailboxes. Exchange Online doesn’t enable new mailboxes for auditing by default, so administrators must remember to enable the mailboxes manually – and check for new mailboxes periodically. If you don’t, nothing is recorded and your audit log will be empty.
After returning from the Ignite conference, I have pages of notes to pour over. Here are some of the more interesting things i learned about Office 365, including who should be in my “inner loop” and “outer loop”, why Microsoft talks about Microsoft 365 when they really mean Office 365, and some Exchange Online cmdlets I had not heard about before.
Revealed at the Ignite conference, Microsoft plans to make some changes relatively soon to relieve the complexity and overhead of deploying and managing hybrid Exchange organizations. Microsoft also showed how to move mailboxes between tenants. It’s a small part of the tenant-to-tenant migration scenario, but it’s good to see it happening.
Microsoft has new tools to migrate public folders (the “cockroaches of Exchange”) to Office 365 Groups. Sounds good. The good news is that the tools work, even if they need a lot of manual oversight. ISVs offer tools to do the same job with more automation. The choice is yours!
Surprisingly, Microsoft has never included a central method to manage user autosignatures within the cloud or on-premises versions of Exchange. Which means that you must let users manage their signatures, build your own tools, or deploy a commercial solution.
Microsoft told us some months ago that they would block the creation of new eDiscovery cases in Exchange and SharePoint. A course reversal has happened because of the humble discovery mailbox, which Exchange uses as a target for eDiscovery results. The block has lifted for Exchange but remains for SharePoint. It will eventually happen for Exchange but Office 365-wide functionality is better than workload-specific features.
Microsoft now supports the migration of modern public folders to Exchange Online. ISV solutions allow you to migrate public folders to other places, like Office 365 Groups and shared mailboxes, which seems like a lot more interesting.
The IT world often focuses on big changes and announcements instead of looking at how small changes can really make a difference. One example is how Microsoft has changed what happens when users recover deleted items to allow items go back to where they came. It’s a great change, even if it is seven years overdue.
Microsoft is obviously putting a lot of effort into improving the functionality available in the OWA and Outlook clients, but only for Office 365 users. It’s now got to the point where on-premises customers must be wondering where their next update will arrive. The answer may be “Never”.
As part of the Office 365 data governance framework, tenants can now create retention policies that apply to the mailbox and team site belonging to Office 365 Groups. The process is quite straightforward, but some gotchas exist that you need to think about!