Two Major Admin Control Updates for Copilot and Agent Management

on
At Ignite Microsoft showcased and talked about two new admin controls for Copilot and Agents. These controls drew a significant amount of attention for their potential to simplify management and strengthen governance across Copilot experiences and AI agents. These capabilities are now emerging in preview, offering administrators early access to improved insights, expanded control surfaces, and more secure operational foundations. Copilot Overview Page Refresh in Microsoft 365 Admin Center First off is the redesigned landing page for Copilot in the Microsoft 365 Admin Center (MAC), giving admins an at-a-glance view of the Copilot journey across Chat, Agents, and M365 Copilot. This update  centralizes critical insights and success metrics, helping organizations accelerate adoption and maintain security posture. The refreshed page introduces success metrics such as Chat active users, assisted hours for licensed users, and satisfaction rate. Each Copilot pillar now includes multi‑...

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