Exchange Online reads inbound email to know when messages contain events that should end up in user calendars. OWA is the only client that exposes the settings to control what events are processed, but all clients can display the events Exchange creates. Some new cmdlets are available to support controlling the settings centrally.
Exchange transport rules are a powerful way to apply different conditions to messages as they pass through the transport service. In this case, we add a disclaimer to calendar meeting requests with a pretty simple rule that works on the basis that it detects a special x-header in meeting requests and applies the disclaimer when the x-header exists.
After a long delay, Microsoft has started to deploy the new Teams Files channel tab experience to Office 365 tenants. The new experience is more functional than the old, even if it doesn’t offer the complete set of features available in the SharePoint Online browser interface. You should see the new tab interface very soon if it’s not already in your tenant.
A question asked what the best way is to add a mailbox to multiple distribution lists. The admin UIs do the job for a few lists, but PowerShell is the way to go when you have lots of lists to process. Two approaches are discussed here: one uses an array as the input, the other uses a CSV file.
OWA now includes Files in its “module switcher”). The new module allows fast access to attachments stored in any folder in an Exchange Online mailbox. It’s a neat feature that will please many people simply because it makes finding often-elusive attachments just that bit easier.
The email addresses for Teams channels are interesting objects. Messages sent to channels start conversations in the target channel and are also captured in SharePoint. Any team member can enable or disable the ability of a channel to receive email by creating or removing email addresses and no admin control exists to stop this happening. Events captured in the Office 365 audit log reveal when email addresses are created or removed, meaning that you can at least know what’s going on.
The Office 365 compliance framework can now to place holds on Teams compliance records created for conversations in private channels. You simply have to place holds on the mailboxes of members of the private channels and hope that no one removes the members from the tenant. If they do, the hold lapses, which seems like a pity.
Teams App Security policies now include an Allow user pinning setting, which controls the ability ot users to pin apps to the left-hand navigation rail. The setting is enabled by default and probably can stay that way in most circumstances. Guest users don’t get to pin anything because their accounts are not policy-controlled.
Subscribers to the Office 365 for IT Pros eBook can download the February update now. This release updates 18 of the 24 content chapters, so it’s a pretty big update overall. No other eBook (or printed book) attempts to update as often as we do, which means that our content is the most up-to-date available to read about Office 365 and associated technologies. That’s a nice position to be in.
The Microsoft 365 Compliance and Security centers are roling out to Office 365 tenants where they’ll replace the old Security and Compliance Center over time. The new centers look fresher than the SCC, but looks can deceive and it’s much more important that the functionality exposed in the new portals work reliably all the time.