New Copilot Updates for Outlook Scheduling, Word Agent Mode, and PowerPoint Agent Mode

on
Microsoft has announced Copilot enhancements across Outlook, Word, and PowerPoint that improve scheduling, document creation, and presentation building. Here is a summary of some of the features I think can come in handy. Be aware that timelines may change as deployments progress, some of these have already been pushed back a couple of months. All of the following features requires a Microsoft 365 Copilot license, and will be enabled by default for users with such a license. Automatic rescheduling of 1:1 meetings Automatic rescheduling of flexible 1:1 meetings and personal events in Outlook with Copilot, helping users resolve conflicts with minimal manual effort is coming soon. This will be in addition to the already released auto rescheduling of meeting rooms. Originally this feature was planned for mid‑November 2025 to mid‑January 2026, but is now hopefully coming between to mid‑February 2026 and the end of February 2026. A Microsoft Copilot license is required to use the capability....

Enable or edit Lync users based on AdGroupMembership

on
In my previous blogposts on Lync user management using PowerShell, I have demonstrated how you can edit  by using an OU search string, or import a csv file. I thought maybe it would be nice to show how to add/manage Lync users by searching for a AD Group. It might be a bit tricky, but it is possible.

I have created a tiny script to prompt the admin for the group name, find users within that group, enable them for Lync and finally enabling the user for Enterprise voice (Presuming the phone attribute in AD is populated in the correct E.164 format, or the script might need adjustment) and setting a specific policy (just because I can, not because I have to).

Something worth mentioning, the set-csuser doesn't seem to like being pipelined to, which is why the get-adgroup is run twice.

The first part of the script is not doing anything, it's just a reminder to import the ad module. The first thing you have to do, is to enter the ADGroup Name (the display name of the group).


When the ADGroup is known to the script, we move on to enabling those users for Lync (skip this part if they are already enabled, but you want to edit users). This is quite straight forward.


But I'm not done yet. I also want to enable the user for voice, and grant him a client policy (These are just examples. Your imagination of PS command combinations is your only limitation).

Doing all I wanted to gave me an unexpected problem. As it turns out, the "get-adgroupmember" will not return the phone property of the user, and it became a challenge to figure out a way to get that property. That is why there are two foreach statements with in this last section. After we get hold of the adgroupmemner name, we can run the get-csaduser with that name (A bit dirty? I know, but it works).


As you can see, the script is fetching the $_.phone attrib of the user, and uses it to create the LineURI after adding the "tel:" prefix.

If you want to take a closer look at the actual script, it can be found right here. Have fun playing with it :)