Saying that Teams will reduce the amount of email traffic is one thing; proving it is another. After making the case that Teams reduces email traffic, I set out to prove the case by looking at data in the Office 365 usage reports, Office 365 content pack for Power BI, and third-party reporting software.
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?
Office 365 has given its rights management capabilities a complete refresh. Clients deal with protected email better and it’s easy to send protected email to people inside and outside your organization, including coverage of consumer email systems like Gmail and Outlook.com. And protected email works on mobile devices too.
OWA now boasts a useful mailbox option, which is helpful if you feel that you need to remove some old and lingering email. The funny thing is that Microsoft doesn’t seem to have told anyone about the feature – or my search-karma is failing me in finding any information about it.
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.
A UK-based leak revealed a plan to require Office 365 inactive mailboxes to have licenses. Storage costs, but because Microsoft told people to use inactive mailboxes for purposes such as keeping content for ex-employees, it wasn’t a good idea to suddenly demand licenses. Good sense prevailed and the plan isn’t going ahead.
Microsoft will release Office 365 multi-geo tenants to general availability in early 2018. You can then deploy Exchange Online, OneDrive for Business, and (later) SharePoint Online across multiple Office 365 datacenter regions. It’s good for data sovereignty, but won’t solve network problems.
Day 2 at Ignite featured news about SharePoint, Exchange, Office 365 Groups, and Teams, And on a personal note, I had the chance to speak twice. That was nice, but I’m exhausted and there’s still three days to go.
Office 365 audit logging generates a lot of data – sometimes too much. The trick is to know what events are recorded and what applications capture. Some pretty strange audit events turn up in the log, but everyone should relax because they are just traces of the system doing its own thing.
Apple released iOS 11 and found that the mail app cannot connect to Exchange Online or Exchange 2016. It’s all to do with HTTP2 connections. Apple tries to connect via ActiveSync but doesn’t do so the way that Exchange likes, or something like that. In any case, maybe now’s the time to consider Outlook for iOS.
Office 365 allows you to block a user when necessary, as when someone is leaving the organization. You can also initiate a forced sign-out, but the option to do so is buried in the user’s OneDrive for Business settings, which seems like a logical place to find it!