Block sending chat messages to users who are not granted the Microsoft Teams license
Currently we are able to send chat messages to users who are not granted the Microsoft Teams license because they are shown in the search result. In the result, a notification message will be sent to the unlicensed users and get them confused. So I would like you to block sending chat messages to unlicensed users.
Agree - very frustrating to think you have sent someone a message to find out later, when they have finally checked their emails, that they haven't received the message at all.
Brandon B commented
Please Fix this
Tasha C commented
Please fix this
Darren F commented
Please fix this
Sara C commented
Microsoft please address this - it is a really poor user experience!
I'm currently trying to block the chat to a Shared Mailbox by applying a custom no-chat TeamsMessagingPolicy, see: https://office365itpros.com/2020/07/07/disabling-chat-teams-users/
I'll report back here if it works.
edit: Turns out it's impossible to assign a TeamsMeetingPolicy to an unlicensed account.
43 votes? Is that all?
I too find it utterly bizarre that an account not licensed for Teams is available to send Teams messages to.
Like Nathan, we have an 'IT Support' mailbox which staff are welcome to email to as it's used by our helpdesk system to import new, and update existing, tickets. IM messages from Teams create a ticket but because the message comes from firstname.lastname@example.org the user doesn't get our system auto-replies, but the system then receives an NDR which creates a new ticket!
Of course what they're hoping for is a live chat with one of our IT staff, but in reality they'll never get a reply at all since there's no way to delegate a Teams account (and we don't operate like that anyway).
This also means that the Search function can return many more results than reflects the reality of how many carbon-based units (aka "staff") we have!
Matthias D.N. commented
It is really unacceptable that people can be chatted with who are not licensed. Hiding people from the address book is also not a solution, otherwise they will no longer be available as recipients for Exchange Online users.
Those who do not have a license should not be able to use a function.
Nathan Bicknell commented
Surprised there aren't more votes for this.
Our experience of this is with a full user account with EO2 license only that is used for a helpdesk mailbox due to interaction requirements rather than it being a shared mailbox.
Due to this setup it needs to be available in the GAL to be visible to users sending email to the helpdesk.
However we can't really accept jobs logging through teams since it just groups a summary of messages 'missed on teams' to the account.
There is no way to check the messages missed to educate all the users since the account is not actually licensed for teams.
Also due to the GAL for email requirement - I don't believe using Scoped Directory isn't an option to eliminate in our case but happy if someone can correct me on that.