Smarter AI Workflows in Microsoft 365 Copilot has been announced on the roadmap: Tools, Source Control, and Agents

Tool Selection in Copilot Chat: Making AI Features More Discoverable One of the most helpful updates in my opinion, is the introduction of the new “Tools” button in Copilot Chat. Users will soon see this button directly in the chat prompt box, offering quick access to a curated set of Copilot features such as Researcher, Analyst, Pages, and image generation.  This will hopefully help users with an easier path to the different tools at their disposal. The feature is turned on by default, with no admin configuration required. This feature is associated with Roadmap ID 497298 , and is expected to roll out in the last weeks of August. Source Control in Copilot Chat: Scoped Responses for Greater Relevance Another user-friendly enhancement coming up, is the ability to scope Copilot Chat responses to specific content sources. This feature will allow users to define exactly which documents, folders, or repositories Copilot should reference when generating responses. It’s a subtle but power...

Signing scripts, from now 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