Meet your new Copilot 365 assistants: Skills agent, Interpreter agent, Project agent and the facilitator

Making your tasks easier for you: The other day I wrote about the new Skills feature coming to Microsoft 365 in the following weeks. But the Advanced tier os the new skills feature is just one of three out-of-the-box agents already in place or coming the next weeks and months (and many more in the future, I'm sure). This agents are designed to handle "everything" from simple tasks to complex multi-step processes where you choose to implement them. In this rather length post, I’ll try to break down each agent’s capabilities, why they’re useful, and how you can prepare to make the most of them. Skill Discovery (Skills Agent – Powered by People Skills) Let's start with the skills agent. In my previous post, I mentioned the release of the "skills feature" that will be released in two tiers. One basic, and one advanced. The advanced tier is driven by AI, more specific the "Skills agent". This agent is all about connecting people and expertise. The agent...

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