Hi @Max Bongaerts ,
Issue is resolved.
Glad to know that the issue is resolved!
Noticed that a same question has been posted in the other forum and was finally resolved by manually applying the URL Rewrite rule (EEMS M1.1 Powershell - inbound). Is this also the solution in your case?
If yes, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost the solution in case you'd like to "Accept" the answer. If I have misunderstood anything or your solution is not this one, feel free to post back.
[How do you stop Teams putting all users on hold when accessing documents?]
Issue Symptom:
"We are facing an problem with an Exchange server which has both KB5019758 and KB5022193 installed but still our vulnerability tool says the Exchange server is vulnerable."
Solution:
"For some reason there was nu URL Rewrite rule (EEMS M1.1 Powershell - inbound), but other exchange servers we manage do have this rule.
After manually applying the rule I ran an vulnerability scan with our tool and it says it isn't vulnerable anymore. "