This month’s updates cover some GDPR stuff, Teams reminding me that it is important, and some other fun tidbits. Good news for you? I kept the snark to a minimum. You are welcome.
Microsoft has updated the Hybrid Configuration Wizard (HCW) to transfer some Exchange on-premises configuration settings. That’s nice, but possibly too little and too late to make any real difference. Office 365 has moved on, most people who wanted to configure hybrid connections are now in the cloud, and the settings aren’t all that exciting.
Companies that move to Office 365 have to decide what mobile email client to use. A native client that uses Exchange ActiveSync (EAS) or Outlook? In the past, the best choice was probably something like the iOS mail app. Now, Outlook is the focus of Microsoft’s mobile efforts and it’s where all the new functionality appears. EAS is still valuable, just less so than it was before.
The Meltdown vulnerability is clearly serious, especially if you run on-premises servers. But if you use Office 365, should you be worried? Well, maybe, but when you sign up for a cloud service, you transfer responsibility for understanding and responding to threat to the service provider. Over to Microsoft…
Microsoft has a new Information Protection guide to help Office 365 tenants prepare for GDPR. The guide is incomplete because it focuses on SharePoint Online and OneDrive for Business, but it contains some good information that will help companies figure out what they need to do to prepare for the May 25, 2018 deadline. Expect more guides of this type to appear in the future.
Some observers say that Teams will replace email. Well, Teams won’t because email still has so many advantages over what Teams offers. But Teams has its own capabilities that will lead it to take some of the traffic currently carried by email. Because of its internal focus, the traffic that moves to Teams is in-house chats, and Teams is a good place for those conversations to be.
Microsoft Workplace Analytics is not a “Fitbit for the enterprise” that you can deploy off-the-shelf to get instantly usable information. Expect to invest considerable time or spend some consulting dollars to make sense of organization dynamics, office politics, and internal friction. All the stuff that makes working in large companies so worthwhile!
Recent developments show that a fully-populated Azure Active Directory is considered by Microsoft to be a core part of the overall Office 365 “experience.” Yet many tenants have partly-populated directories. Is that a problem? Or might it be a future problem?
In today’s Ask the Admin, Russell Smith shows you how to create and use conference rooms in Office 365.
Further signs of Microsoft discarding the on-premises roots of Office 365 in favor of consistent cross-workload functionality comes when the Security and Compliance Center takes center stage for eDiscovery from July 1.
The U.S. patent office granted IBM a patent in January that seems to cover email auto-reply. The only problem is that auto-replies existed a long time before IBM claimed to have invented them. But it’s all good now.
Microsoft set out to rename OWA as Outlook on the web last year. That effort never gained real acceptance in the Exchange community, but in fact the project isn’t to rebrand OWA. Instead, it’s all about preserving and building out the Outlook brand across multiple clients and different experiences. Microsoft is struggling against the weight of history here, so don’t expect any great success anytime soon.
This week’s snippets span the tenth anniversary of PowerShell, a survey indicating that Office 365 has a solid lead in deployments over G Suite, Windows 10 Mobile finally gets the new authenticator app, Outlook starts to look like mini-CRM, why dynamic groups don’t work for Teams and Planner, and an interesting document from Microsoft describing Office 365 tenant isolation.