Sharing your Copilot notebooks - Is being rolled out

on
Microsoft is rolling a new update to Copilot Notebooks that make collaboration even easier: the ability to share Copilot Notebooks with your colleagues.  Personally, I like Notebooks because they feel almost like small, personal agents I don’t have to configure. They give me a safe space to collect notes and documents and then work on them over time. With this update, that personal space can become a shared space for a selected group of  colleagues, without compromising security or permissions. I think it is also important to note that your chat and chat history within the Notebook stays private. The web rollout began in late October and will finish by December, while mobile access starts in early November and are related to the Microsoft 365 Roadmap ( ID 506851 )  You can also read more about the Copilot Notebooks experience on the Microsoft website here . If you like this update and want to stay informed about similar improvements, feel free to follow me on LinkedIn!

What is Microsoft Teams Exploratory Experience and can you manage it?

on
Microsoft Teams Exploratory experience is a great feature for users without a Teams license to get to know Teams, and get involved with other organizations already migrated to Teams. The Microsoft Teams Exploratory Licence will replace the Commercial Cloud Trial license available today.
If a user has already been assigned a Teams license, the feature will not be available for that user (Also, the feature is not available for GCC, GCC High, DoD or EDU customers).

If, for some reason, you do not want your users to start playing with this experience (Let's say you are not ready to support the features, or you want an absolut controlled migration from SFBO to Teams, as many of my customers like), there are a couple of ways you can manage this.

The only way to turn this feature off completely, is to globally disable the use of trial apps and services. This can be done under the M365 admin center and "Services & add-ins", provided the organization is eligible in the first place.

If a user have already been playing around with the feature, the licence will have to be removed in M365 admin panel where all the user's licences are managed.

I highly recommend reading the documentation here if this is something you need to look into.