11th MVP Award Rewarded

I am actually on vacation, but as I sit here under the summer sun, toes in the pool and a cold drink within reach, I have been waiting for that email confirming that I’ve been awarded my 11th Microsoft MVP Award! As last year, I am being awarded in both the Teams and Copilot category. To say I’m humbled would be an understatement. Being part of the global Microsoft MVP community for over a decade now has been an incredible journey, filled with learning, sharing, speaking, and connecting with passionate technologists from every corner of the world. What is the Microsoft MVP Award? The Microsoft Most Valuable Professional (MVP) award is given to technology experts who share their knowledge and real-world expertise with communities. With fewer than 4,000 MVPs worldwide, it’s an honor to be part of such a vibrant and dedicated group. MVPs contribute through speaking engagements, writing, open-source contributions, and helping others online and offline. You can learn more about the progra...

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

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.