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

More OCS challenges

on
Ok, So I have the basics up and running, but is it working? Aperantly, yes.
Front end and backend now run without errormessages, and I can chat, call and use livemeeting on all the clients.

I decided not spend to much time on running around, installing applications, so I am using AD Group policies to deploy the applications. Here is a quick rundown of what I did:

Livemeeting:
  • Download software from www.livemeeting.com (Remember to download both client and outlook plugin)
  • Convert exe files to .msi files by running "LMsetup.exe -out c:\temp" (presuming c:\temp exists)
  • Create a GPO for distribution (Assign or publish, Computer or User - It depends on your preference)
  • Create Groups for filtering of the GPO
  • Add objects to the groups
  • Remove "authenticated users" from the filtering, add the desired group.
Attendant:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.

Office Communicator:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.