New Year, New Momentum: Here are three Copilot updates to get you started into 2026

on
It's a new year, so I thought I'd start the year by mentioning three features already released, or soon going to be released. One of the features improves the workflow of sharing files with comments, the other improves the application specific Copilot, and the last feature makes it easer to find the nest available timeslot for a 1:1 meeting. As with all of my other posts, timelines can shift, and the timelines in this post is as written in the Message Center at the time of posting. AI-Summary experience when sharing files. With this new feature, copilot intent to help users share files with clearer context in just a few steps. Users will get the capability to generate a concise summary of a file and include it when sharing from the File Explorer share dialog or the OneDrive activity center. This will make it easier to share the context of a file and giving the receiver a faster understanding of what a document or file contains before they open it. General Availability announced...

Searching for that LineURI

on
Organizing and maintaining your entire dial-plan in Lync can at times be tough work. Easy enough when you're a small company, but try keeping score when reach 3-4000 DID's in your system.

I've been working closely with a customer of that size lately, and they asked me if there was anything I could do to help them when they had to allocate a new number (or move) to one of their employees. 

It turned out they were not able to keep score of available numbers, or where certain numbers were assigned. 

The first task was simple enough. I showed them Ståle Hansen's (http://msunified.net) script for identifying unused numbers. Big hit! 

However, the customer also wanted a quick way of identifying where a number was assigned, and if possible, to do the search with a wildcard (the lync client only returns an identity when a normalization rule has been matched).

I gave it a thought and created the following script to do a search through powershell. (download and rename to .ps1 to run).

The script asks for an input, then adds * to the input to make it a "wildcard" search.
It will then run several "get-" commands to see if any matches can be found within a known user, device, service or application.


The screen shot above is only the beginning of the script, but it should give you an idea of what it's doing.

When the script is run in a live environment, it's output could look like this:


In my demo environment the search only returned 1 user, but if there were more matches to the 4 digits entered in the search, there would be more hits.

I hope you find this script useful, as I did. In one my upcoming posts, I will post a script to export all used numbers to a searchable html file.