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

Lync owas windows 8_1 bug

on
** 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 :)