Many Office 365 applications (Teams, Groups, Planner, SharePoint, etc.) now support external guest access. you might end up with a lot of guests, and like any good accommodation, some management is needed. In this article, we look at how to manage the guests created by Office 365.
With Ignite happening last month, there was a lot of Office 365 news and Shane distills it down into an easy to read format.
Microsoft announced at Ignite that you can soon manage Teams through the Teams and Skype for Business Online Admin Center. Office 365 administrators will welcome this because it means that they can manage teams without being a member of those teams. And they can avoid PowerShell, which is a pity.
In news gently leaking out, Microsoft says that new Office 365 tenants with 500 or fewer licensed seats will have to use Teams. These tenants won’t have the option to use Skype for Business Online. Then again, you have to ask the question whether they want or need to use Skype for Business Online? Existing tenants aren’t affected by the news.
To make things easier for Office 365 tenant administrators, Microsoft has released four new administrative role for Teams. You can now assign these roles to other people and have them take care of areas like Teams general admin or the more complicated area of voice and audio meetings and calling. It’s a sign of increased maturity in the Teams product.
Microsoft has scheduled 1,500+ sessions for the Ignite 2018 conference in Orlando next week. What’s happening for Office 365? Well, there are many sessions to attend, but the interesting thing is the huge number of sessions assigned to Teams compared to other workloads. SharePoint does OK, but Exchange is low, and Yammer gets a surprising allocation.
When someone leaves your company, you might need to preserve their Office 365 data. Email, OneDrive, and SharePoint are straightforward, but what about Teams? As it turns out, a content search or an Office 365 DSR is a good way to retrieve information about Teams messages and information about their activities can be found in the audit log.
SharePoint Online makes it easy to publish news items, but people might miss the news if it only exists there. Publishing to Teams spreads your message and there’s three ways to get the job done. Choose from email, a connector, or linking to news with a tab.
You can create an Office 365 retention policy to process Teams channel conversations and personal chats, but how do you prove that the policy is working? As it turns out, the only way is by checking the mailboxes where Teams stores compliance items and the statistics generated by the Exchange Online Managed Folder Assistant.
Teams and Skype for Business Online both capture IM conversation records that can be found by Office 365 eDiscovery (content) searches. All of which is good, but if you ever get around to performing eDiscovery and need this information, you’ll find that Skype for Business Online conversation transcripts are easier to use than the individual copies of conversation contributions captured by Teams.
Microsoft has recently rolled out an update to Teams that fixes one of the most annoying issues with the application.
Microsoft says that Teams now matches Skype for Business Online’s feature set but the company still won’t say when they will decommission Skype.
The licensing model for Teams is now per-user instead of tenant-wide. That’s fine if you leave everyone enabled for Teams, but removing licenses one at a time for a set of users through the Office 365 Admin Center is a tiresome and boring operation. PowerShell can help ease the pain, and here’s a script to do the job.