This post will be updated throughout the month as new items are added to the tag.
Be sure to subscribe to my M365 Newsletter for more M365 expertise and news.
Apparently, instead of purchasing M365 licenses and then additional Teams licenses, your M365 licenses will come in with or without Teams flavors.
Forgive me for picturing your MS partner with a headset asking, “Do you want Teams with that?”
That seems to be how we’ll be ordering our licensing in the future, though.
Hosting the meeting yourself and using Copilot is safer. It is also more expensive. Blocking external attendees from adding a note-taking application might also be a good idea, which might seem rude.
I’d argue that adding an app to a meeting you’re not hosting without asking is also rude, but that’s just my opinion.
Microsoft has made efforts to make it clearer when a call is from outside the tenant, and I think that helps. Still, it might now be a good idea to review the proper procedures with your users, and for larger organizations where users may not recognize the support team, an identity verification step might also be worth considering.
The first paragraph makes it obvious that you can’t be an unnamed guest in a Zoom meeting and invite your AI to take notes. That makes sense.
The second adds a requirement: you must also attend the meeting. No more sending your AI to take notes for you while you spend your time elsewhere.
This post will be updated throughout the month as new items are added to the tag.
Be sure to subscribe to my M365 Newsletter for more M365 expertise and news.
Everything about Teams—security, retention, eDiscovery, privacy, and so on— starts with understanding the data involved. To understand the data involved, you need to be familiar with all the details of this chain reaction. You’re not protecting and investigating data in a Teams channel; you’re dealing with data in Exchange, SharePoint, and potentially in various other locations, depending on the apps used in the channel.
