Here are three copilot updates coming our way, and this is what to make of them

on
Changes aimed at streamline workflows: As Microsoft continues to evolve its AI-powered productivity suite, three significant updates are rolling out across Microsoft 365 in June and July 2025. These changes are designed to streamline workflows, enhance research capabilities, and bring generative AI closer to users in their daily apps. Here is my summary of the three updates, and what you might want to be aware of. Access SharePoint agents in the Microsoft 365 Copilot app Some time ago, Microsoft introduced SharePoint Agents. These agents are integrated into the navigation, and users have to navigate to that specific site in order to access the agent. With this upcoming change, these agents can become available directly from the 365 Copilot App along other "recently used" agents list. This change will significantly reduce context-switching for users who rely on these agents for their daily tasks. Expect this rollout at the end of July . Researcher Agent Integrated into Copilot...

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