Proper invation e-mail template for Teams meeting created by Graph API

Jan Pěček 1 Reputation point

Hello all,
we're developping a calendar managging app. You can create a new meeting there using Teams and we use Graph API and event.onlineMeetingProvider attribute set up to 'teamsForBusiness'. That means it creates a Teams meeting. The problem is that in invitation of this meeting, there's no data filled in Meeting settings in Teams administration ( or they are displayed incorrectly.

Is there any issue with this or how we can achieve that the meeting invitation (coming to e-mail) created via GraphAPI will contain our logo and all footer and design details set in the Teams Administration?

Thanks for any hints.

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,223 questions
Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
10,795 questions
Microsoft Teams Development
Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
2,907 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Gopinath Chennamadhavuni 2,431 Reputation points

    Hi @Jan Pěček

    Thanks for reaching out!

    As per my research and testing, I am able to send the meeting invitation with custom body (logo, footer etc.) using graph API- POST and I am receiving the invitation with customized body. However, I noticed that it is taking some time/delay to reflect changes into the system.

    Below are the screenshots for your reference.



    Hope this helps.

    If the answer is helpful, please click Accept Answer and kindly upvote. If you have any further questions about this answer, please click Comment.

    0 comments No comments

  2. Leo Lukáš 0 Reputation points

    Hello @Gopinath Chennamadhavuni

    thank you for your reply. Could you please provide more technical details on this? I can see, that it works for you properly and that is great! We are not sure how to proceed on our end - it still seems to us, that problem is on the Graph API side and the footer is somehow not generated properly.

    Thank you for your reply in advance - our customer is quite concerned about this. Because the footer is not displayed correctly, emails generated automatically by Graph API look a bit like some kind of online scam.

    Thank you in advance for your help.

    Best regards