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

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

Lync owas windows 8_1 bug

** UPDATE **
The bug has been fixed in the following update: http://support.microsoft.com/kb/2837634
You might have to break the farm, and recreate it after the update.
**/UPDATE**

There is a known bug affecting windows 8.1 users when they try to present a PowerPoint presentation in any meeting. If you have installed any version of Windows 8.1 and tried it, you might have seen the all too familiar screen:


If you have tried to debug the error, you might be as frustrated as me, because there is (at least I was not able to find any) no visible error on any server or client component. Even a Fiddler trace revealed nothing but 200 OK messages.

This bug is not present in Lync Online, and I hope we'll see a bugfix for the onprem installations as well soon.

In the meantime, do as I did to correct the error. Join your meeting through the web browser, appending ?sl=2 to your meet url. At least I was able to run the presentation through my webapp.


Hope this helps, and that we see a bugfix soon :)