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!

Lync client may connect to a non federated partner, even if you though it should not.

on
Here is an "interesting" observation I did a couple of days ago. The customer has chosen not to allow DNS discovery of federated partners, but will allow federation with selected partners on the allow list. After a while with this configuration, the customer called me and told me they had mixed experiences with the solution. There were times when meetings with a partner (NOT on the allow list) actually would work, even if they expected the meeting to fail.

They asked me to verify the settings, and to investigate why some users reported they could connect to a meeting others couldn't.

This is what I saw on a client who failed to connect:




5 messages. And the interesting one would be the 504 message: "Can not route".



And then the client stops trying, as I would expect it to.

But here is an interesting twist. Log on with the same client from a remote connection (through edge), and then let's see what happens.



The client does not honor the 504 message "Can not route". It continues and connects to the meeting, unexpectedly. How can that be?

The interesting part is what happens after the 504 message. First the client acknowledges the rejection, but then it does something it didn't do on the inside. There is a new invite, trying to connect anonymously:



And this connection is allowed. Quite confusing for the end user, actually. But now they know.


It is important to note the user was allowed for federation in this scenario, but the domain in question was not in the allow list and DNS discovery was not allowed. Also, the organizer on the other side was allowing anonymous invites.