Due to the impact of the Covid-19 virus, there’s been a huge upsurge of interest in using Microsoft Teams to work from home, especially for online meetings. Here’s a collection of practical tips about setting your company and personal network up for Office 365 and how to use Teams to run effective meetings collected from a March 18 gathering to discuss best practice about working from home with Teams.
Office 365 licenses can seem complex, especially when you descend to the level of multi-product license plans. PowerShell makes it easy to generate a quick and simple report of who’s been assigned which license. And best of all, because the code is PowerShell, you can amend it to your heart’s content.
You might consider Stream to be a kind of corporate video portal, but the ability of Stream mobile clients to record, edit, and upload videos makes the application much more useful. People can file video reports from trips, do product reviews, and share all sorts of interesting information with co-workers by using their mobile device as a production platform.
Exchange Online makes it easy to assign delegated permissions for user and shared mailboxes. But permissions assigned to people might not be still necessary, so it’s good to do a periodic check. In this post, we describe a script to scan for permissions on Exchange Online user and shared mailboxes and highlight non-standard permissions in a report generated as a CSV file.
Exchange Online enables mailbox auditing by default, which should mean that audit events get to the Office 365 audit log for all E3 and E5 mailboxes. Well, that’s what you might thing but that’s not what happens. Mailbox events for E5 mailboxes arrive just fine, but you must reenable E3 mailboxes for auditing before their events flow. It’s a bizarre situation.
Microsoft released Version 1.0.4 of the Teams PowerShell module on March 9. The new module comes with some useful updates and is recommended for anyone working with Teams through PowerShell. And if cmdlets don’t do the job for you, there’s always the Microsoft Graph as you can combine PowerShell and the Graph to solve even more problems.
Teams and Skype consumer users can now chat together if the Office 365 tenant configuration allows. Text-only chats and VOIP calls are supported. Teams users have the opportunity to see what Skype consumers have to say before they accept a connection. It’s all part of making sure that Skype for Business Online users can move to Teams without losing connections.
Microsoft has announced the retirement of the Twitter connector for Teams. The news is disappointing because the Power Automate alternative doesn’t do as good a job at injecting tweets into Teams. It’s a mystery why Microsoft is retiring a working component that does a good job, but no doubt a good reason is known to some and they’re saying nothing.
Microsoft has released information about high-value Office 365 audit events and audit event retention policies. Both are part of a Microsoft 365 Advanced Audit offering. The MailItemsAccessed event is the first high-value audit event (we can expect more) and the retention policies are used to purge unneeded events from the Office 365 audit log.
Large Office 365 tenants with more than 10,000 seats can now use the SharePoint Online site swap feature to replace an old root site with a new communications site. The site swap must be done with PowerShell and needs a new version of the Invoke-SPOSiteSwap cmdlet. Once you prepare your new site for swapping, everything goes smoothly.