Teams meeting creation via Office app

Question

Good afternoon,

Yesterday one portion of our clients Team meeting scheduling started not appearing for other users in the same company.

If one of the Users creates Teams meeting via Outlook app in Organization and adds Required and Optional users to the meeting, that meeting won't reach the recipients.

We tried creating a teams meeting from Outlook app on a phone, from OWA, we even tried to change the internet connection to bypass the firewall (if its needed)

One thing is strange that Teams meeting scheduling from the Teams App works flawlessly. However same Meeting can't be scheduled and sent to the recipients from the Outlook app (nor from pc or phone)

The meeting itself creates correctly, but the meeting won't be sent to the other internal/external users. The problem is present on several accounts.

Answer 1

Hi @Ignas Grigulis | BTT Cloud ,

Welcome to our forum!

In order to further confirm your issue, please provide more information about your case:

but the meeting won't be sent to the other internal/external users.

Do you mean that the receivers didn't receive the Teams Meeting email? If so, can you sent other meetings successfully except Teams Meetings?
In addition, it's suggested that you could use message tracking to check if the message is sent via EAC>Message trace.

We tried creating a teams meeting from Outlook app on a phone, from OWA, we even tried to change the internet connection to bypass the firewall (if its needed)

The issue occurred in OWA and Outlook for mobile too, right? If so, it seems that the issue is not just related to the Outlook desktop client. And I notice that "The problem is present on several accounts", do you mean all users in your organization or only some specific users? If you mean some specific users, what do they have in common?

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

We found the coulprit.

In the Admin center, we did a message trace and found that one of the policies was blocking certain words in the message that was being sent.

When we removed that rule, everything started to work fine.