Here are three copilot updates coming our way, and this is what to make of them

Changes aimed at streamline workflows: As Microsoft continues to evolve its AI-powered productivity suite, three significant updates are rolling out across Microsoft 365 in June and July 2025. These changes are designed to streamline workflows, enhance research capabilities, and bring generative AI closer to users in their daily apps. Here is my summary of the three updates, and what you might want to be aware of. Access SharePoint agents in the Microsoft 365 Copilot app Some time ago, Microsoft introduced SharePoint Agents. These agents are integrated into the navigation, and users have to navigate to that specific site in order to access the agent. With this upcoming change, these agents can become available directly from the 365 Copilot App along other "recently used" agents list. This change will significantly reduce context-switching for users who rely on these agents for their daily tasks. Expect this rollout at the end of July . Researcher Agent Integrated into Copilot...

Installing OCS 2007 R2 (Still fighting a bit)

Once again, .NET 3.5 is a prerequisite for installing OCS 2007, and once again the installation for this failed. A tip for you might be to enable these things ahead of the installation of OCS. I do not remember having the same problem on OCS 2007 with Windows server 2003. It might be a 2008 issue as much as a R2 problem. If anyone do install this on Windows 2003, please let me know if you run into the same issues.

Now, off to the installation at hand. First of is the Back End server on which I just installed SQL.
If you are going to install everything on one box, you don't have to read much to install OCS (a basic understanding of the components involved is really helpful though). But if you are about to what I am, install an Enterprise installation with back ends, frontends and possibly balance loaders and several pools. Reading the docs is just for you! Also, make sure the right client tools are inplace, and server times are synchronized (I am using SQL 2008 on the back end, and the installation comes with 2005 client tools).

Installing BE is really just about "preparing" the environment. For those you who have not seen the wizard; This is a task of it's own. A few simple steps to complete.

Installing the FE is another matter. Again; If you are installing all on one box, there isn't too many pitfalls. But when you deploy to several servers, you need to keep your head straight when it comes to poolnames, servernames, sipdomains and certificates.... If you have a basic understanding, it should not be too hard, but still... whatch out for those pitfalls when assigning roles, names and certificates. My biggest obstacle was figuring out how to add the certificate to IIS. AS it turned out, the management tools were not installed (and are not by default).