Exchange Online

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!

Changing from one mobile platform to another can be interesting. I went from Windows 10 Mobile to iOS and so far, no major damage is done. Some interesting differences exist in how Outlook for iOS and Outlook mobile synchronize email to devices. I wanted to learn more, so I poked and found out why the differences exist.

Microsoft has moved 400 million Outlook.com mailboxes to an Office 365 infrastructure. Outlook.com mailboxes are now powered by Exchange Online and exploit other parts of the infrastructure like EOP. It’s a good change from a engineering and economic perspective.

On January 20, Microsoft unexpectedly updated their original blog post from July announcing the Focused Inbox with information about client updates to support the feature. The update contains some answers to questions why people have not been able to use the much-trumpeted feature.

Microsoft has finally provided an effective method to allow users to recall messages. Outlook’s Recall Message function usually doesn’t work, but OWA’s new Undo Send will stop messages that should never be sent. Five seconds might be too short to realize that you have made a mistake and should stop an outbound message, but ten seconds is about right. And if you are really indecisive, you can take up to 30 seconds to decide whether a message should go.