Copilot in Outlook: Prioritize my inbox

on
Microsoft is releasing a new feature for Copilot in Outlook: "Prioritize my inbox by Copilot". The feature can go through your inbox and analyse the content for you. it will then mark them as high and low priority and help you focus on the tasks that are important to you. When the feature rolls out, it will be implemented as an opt-in feature for users, and it will be a "limited seating" until there is enough capacity for all within the organization. When available and enabled, there will be ways to tell Copilot what is important to you. You can read more about this on the support pages for the feature. A couple of notes: It will only prioritize in your main inbox (Not subfolders) It will not work on shared mailboxes or groups This feature is associated with Microsoft 365 Roadmap ID 411302  and will start rolling out in April 2025

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