“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...

Issue with enable-csuer when the user first name contain spaces

on
I have run into an issue with the set-csuser command in a few deployments. The error occurs when I try to use set-csuser with the "-sipaddresstype firstlastname" switch.


If I changed the -sipaddresstype from "firstlastname" to "emailaddress", I was able to use the script to enable the same user.

It turned out this user had two first names (with a space between) in the fname property in AD (fname="First Name"). If I removed one of them (fname="First"), or used a hyphen between them (fname="First-Name"), the script started working again.