Copilot in Teams will be available for multitenant organizations (B2B)

Microsoft has announced that Copilot will be accessible to Business-to-Business (B2B) members within Multi-Tenant Organizations (MTO). This update allows users with B2B (shadow) identities to utilize Copilot during Teams meetings, provided they have a license in their host tenant. This will help organizations boost collaboration and productivity when working with different organizations. There will be a new policy setting in the Teams Admin Center (TAC) enabling IT administrators to manage and control Copilot access specifically for B2B members. According to the  Roadmap ID 423474 , we can expect this feature to be rolling to the first customers at the end of this month. Keep an eye out on the messeage center, and in the Teams Admin Center for these changes.  I know a lot of users and customers are asking for this feature, but organizations should make sure such access is aligned with their own security and access policies. And users should be informed that when the feature is...

Lync 2013 Documentation script

I have been looking for a good way to document my Lync environment in a way others can understand what has been done to the system. I have not been able to find a solution to suit my needs, and decided to create a new script for my self.

I have stumbled upon these great tools from "Empty Message" at his site: http://emptymessage.com/?p=149, but it didn't quite get all the settings and polices I wanted to incorporate.

My new script is configures to run almost all of the different get-commands I thought useful. some might find it over the top, but I find it very useful when I need to troubleshoot something later. And if I find polices or settings have been changed, it is easy to compare the now and then, and correct erroneous configurations.

I am not going to bore you with the details of how the script is built. And I'll just go over the obvious:

The script creates a folder at c:\LyncDoc\ and will use this as a base for all the out put.
The complete file set should look something like this:

8 HTML files (I have tried to make logical files for separate sections)
7 XML files containing actual configuration backup
1 bak fil for the LIS set
1 zipfile as a result of export-csconfiguration
1 zipfile with all the other files inside

- The Script must be run on a computer with Lync PS module available, and it must be able to reach the backend databases.
- The script has only been tested in a single site, single pool topology.
- Script has been signed for the ease of use.
- As before, run this only in your labs at you own risk and caution.

And finally, The script can be found at the Technet Gallery: http://gallery.technet.microsoft.com/lync/Document-you-Lync-2013-154f4050