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

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

Signing scripts, from now on

on
During the Lyncconf13, I was lucky enough to win a certificate from digicert in give away competition from the The UC Architects. It didn't take long to decide what to do with the gift. I decided to get a code signing certificate for my online scripts.

Now, you should be able to run the scripts directly by downloading them to your labs, without tampering with the script, it's security settings or your power shell security setting.

A benefit for me, is to see if the script has been tampered with if it does not work on a tested system. I decided to sign all my backup scripts, and I will also sign every new script I post on my blog.

As a side note: I was wondering if signing a lot of certificates was going to take a long time. I turned to power shell  and scripted it. What else "could" I do? It turned out to be quite easy, and done in a few minutes (writing the code, signing took seconds)


param ([Parameter(Mandatory=$true)][string]$folder,[string]$certvalue)

cd $folder

$cert = @(gci cert:\currentuser\my -codesigning)[$certvalue]
foreach ($scripts in (Get-ChildItem)){
Set-AuthenticodeSignature $scripts $cert}

All my backup scripts have been updated, so if you download these scripts now, they will be signed. (If your machine trusts Digicert, you should be in good shape.)

Here are two posts I used as reference:
http://technet.microsoft.com/nb-no/magazine/2008.04.powershell(en-us).aspx
http://tfl09.blogspot.no/2010/06/signing-powershell-scripts.html