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...

Important certificate note to self

on
I've been having issues on a server, where I was supposed to create a secure channel (tls) to a remote server for synchronizing the exchange free/busy information on users. I long suspected it to be certificate related, but I always ended up by turning ssl of (thus running unencrypted). I thought I had it all done right, when importing the root certificate of the CA to the trusted root. But it never solved my problem. 

Thanks to my OCS course, a bright light dawned on me. The reason why the TLS failed could be several. First of all, if you are running the sync service as a service on the server, the certificate must be in the trusted root of the computer, not the administrator (or other account which you are installing as). Second, if the service is set up to "run as" a separate user. It is a good idea to log on as that particular user, and import the certificate as that user. Quite simple when you think about it, but not always intuitive..... :P