Sharing your Copilot notebooks - Is being rolled out

on
Microsoft is rolling a new update to Copilot Notebooks that make collaboration even easier: the ability to share Copilot Notebooks with your colleagues.  Personally, I like Notebooks because they feel almost like small, personal agents I don’t have to configure. They give me a safe space to collect notes and documents and then work on them over time. With this update, that personal space can become a shared space for a selected group of  colleagues, without compromising security or permissions. I think it is also important to note that your chat and chat history within the Notebook stays private. The web rollout began in late October and will finish by December, while mobile access starts in early November and are related to the Microsoft 365 Roadmap ( ID 506851 )  You can also read more about the Copilot Notebooks experience on the Microsoft website here . If you like this update and want to stay informed about similar improvements, feel free to follow me on LinkedIn!

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