Lots happens in a month within Office 365. I can’t possibly write an article about every change in SharePoint, Teams, Exchange, etc. released by Microsoft,, so sometimes I need to publish a catch-up (or catch-up) post. Here are ten things that I think are interesting enough for you to know about.
Planner now supports guest user access to its plans. Office 365 tenants will celebrate this feature because they’ve been waiting for it to arrive. It’s curious that it has taken Microsoft so long to upgrade Planner for this feature given that Groups and Teams have had this capability for a while. But it’s here now, so enjoy.
Many Office 365 tenants use Planner for group-based task management. Generally, the application is OK and has been getting better. Now it can connect to Outlook to synchronize tasks into a user calendar, which then allows users to see tasks alongside their other commitments and print details off if needed. It’s an imperfect but acceptable solution to the lack of print capabilities within Planner.
Owners of Office 365 Groups can delete groups if they want. Some don’t like this as it means that SharePoint site collections, teams, and plans are removed. The simple membership model used by Office 365 Groups is the cause, and while you cannot stop owners deleting their groups, you can take action to detect and recover deleted groups if necessary.
Office 365 now supports external access to Teams for guests with any email address, a development that creates some questions in the minds of those who might want to add guests from non-Office 365 domains. In this article, I try and answer some common questions that you might have about guest access.
Office 365 keeps on changing, which makes it very hard to keep up with detail. The big stuff gets covered in articles but small changes might be overlooked. In this post, Tony looks at some of the changes that happened in the last week or so that you might have missed, including Teams, Planner, OneDrive, Yammer, and Exchange. And preparation for GDPR…
Microsoft has released some useful updates for the Office 365 Planner app, but external access is still not there, which is baffling. On the other hand, you now have an OWA-like schedule view, filters to suppress tasks that you don’t want to see, and better notifications to tell you when you must do some work. And an iCalendar feed is coming soon to allow you to clutter up your Outlook calendar with even more stuff.
One of the premium features for Office 365 Groups is the ability to use a naming policy so that all groups (and Teams) have a compliant name. The policy is a nice-to-have feature if you are concerned about having a well-organized directory with all your groups gathered in the same place. The question is whether enough business value is gained from a naming policy to make it worthwhile.
The Teams PowerShell module is flawed, but that does not mean that you cannot do work with it. Here’s a primer of the most important cmdlets, together with a link to a rather interesting approach to finding out what Office 365 Groups are team-enabled.
Office 365 Groups have been very good for SharePoint Online. Because many apps use Groups, they also use SharePoint, even if they don’t know it. Teams, Planner, Yammer, StaffHub, Stream, and Groups in Outlook (or whatever the name is this week) all drive SharePoint usage. SharePoint Online is Office 365 document management, and that’s a good thing.
Microsoft’s Compliance Manager is intended to help cloud tenants cope with regulations like ISO 27001 and GDPR. The Compliance Manager has a nice dashboard, but it is passive and offers very weak options in terms of organizing the work needed to achieve compliance. But Office 365 has Planner and Teams, and it is easy to create the necessary collaboration structure to allow people to work on GDPR controls.
Microsoft clarified what AAD features need premium licenses at Ignite. Tenants need many of those features to control Office 365 Groups and Teams, and some of the listed features are surprising. Did you know that the group creation policy is a premium feature? Or adding a default classification. The chosen set of features seems odd, but at least Microsoft is now clear about what you must license.
On August 9, Microsoft launched the Office 365 Groups expiration policy into preview. It expires groups after a set period and helps keep the spread of groups under control. All sounds good, but the new feature needs an Azure Active Directory Premium license, which isn’t so welcome.