“Bring your AI to work” is here: Microsoft edition - What Multiple Account Access to Copilot means

on
Multiple Account Access to Copilot On October 1. 2025 Microsoft released a blog post explaining how employees now can use Copilot from their personal 365 plans to work on organizational data. This is of course, an extension of the already existing "Multi account" feature that was released for corporate accounts a "couple of months" ago. In other words, “bring your own Copilot” is now a real thing in Word, Excel, PowerPoint, Outlook, and OneNote on desktop and mobile, with enterprise protections intact. “Bring your AI to work” is an important topic, and banning AI altogether might not be the answer. Whether sanctioned or shadow, AI has already entered everyday knowledge work. Microsoft’s new multi‑account access offers a safer path where employees can use Copilot from their personal Microsoft 365 subscriptions on work files, while the file’s access, auditing, and compliance still flow through the work identity and tenant. That’s better than users copy‑pasting sensit...

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.