Custom Engine Agents in Microsoft 365 Copilot

on
Agents in BizChat has been available for some time already, but now there is an upcoming update to Agents. The introduction of “ custom engine agents ” in Microsoft 365 Copilot! These specialized agents can be built on any large language model (LLM), toolchain, or orchestration tool, tailored specifically for your domain or tenant workflows. Initially supported in Microsoft Teams, this feature will soon be available in Microsoft 365 Copilot Business Chat ( BizChat ).   The introduction of Custom engine agents enables your organization to create customized experiences using your own AI systems and orchestrators. You can design unique prompts, connect to any LLM, and integrate these custom agents with Microsoft 365 Copilot. After the rollout, users will be able to access these agents, provided they are enabled and deployed in the Microsoft 365 admin center under the Copilot tab.   You can read more about the feature on this page . Eligible users can create agents using Micros...

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.