Open ldpg-dev opened 6 months ago
To address the issue with Microsoft Teams meeting invitations not being created as online meetings and having an unprofessional description, it's essential to ensure that the meetings are created through the Microsoft Graph API as online meetings. This approach will enable Microsoft Teams to handle the invitation layout and details, ensuring a professional appearance.
Here's a more direct solution to implement:
Use Microsoft Graph API: Ensure your integration creates the meeting as an online Teams meeting directly through the Microsoft Graph API. This action will automatically set the meeting as an online event and allow Teams to manage the invitation details.
Customize Email Invitations: If you're sending additional emails through your application, use the AttendeeScheduledEmail
class as a reference for generating professional-looking email content. Include the joinWebUrl
prominently in your email template to make it easy for attendees to join the meeting.
Automate and Customize: Integrate the email sending functionality into your meeting creation workflow. After creating the meeting and obtaining the joinWebUrl
, generate a customized email invitation using your template and send it to all attendees.
Error Handling and Localization: Implement error handling for a smooth user experience and use localization and time zone information to ensure the email content is relevant and correctly formatted for all recipients.
By following these steps, you can improve the professionalism of your Microsoft Teams meeting invitations and ensure they are recognized as online meetings. This approach leverages the capabilities of the Microsoft Graph API and custom email templates to enhance the overall user experience.
To continue the conversation, mention @dosu.
@joeauyeung
Is this matter of permissions? Or bad implementation?
@buzzard10 This is a bad implementation of the MS Teams integration with Outlook/MS Calendar
@ldpg-dev, it was functioning for me a few weeks ago; I had a link to the meeting, but now it's not working. What has changed?
I honestly don't know, @milospuac and @joeauyeung have you been able to take a look at this? @ciaranha Not sure why it's not labeled as a bug anymore.
The Microsoft Graph API doesn't support suppressing invitation mails when creating an event
object.
The only way I see for solving the duplicate mail issue is disabling Cal.Com notification mails, if an event was created using the office365calendar
app.
This issue is the invalid email. If you look at the screenshots in the original post of this issue, you see there is an invalid email address. Cal.com keeps adding that "invalid email address" to the Microsoft Teams meetings. If that email is removed and the meeting updated. then it works just fine. But that would mean, after each meeting is created you have to go in and edit it, and when you do, it sends an update notification to the client which doesn't look professional. I had to switch to Calendly because of this issue. I'm waiting till it gets fixed to switch back to cal.com. I opened a ticket a long while ago, but it went nowhere.
Also the description is poorly formatted, you can see there are no line breaks. Again, I'm not sure why this is labeled as "Improvement" and not as "bug", this is certainly a bug.
Any updates on this? I really don't want to, but I'm going to have to migrate my entire team back to Calendly because of this issue. I work in Customer Onboardings, and we send an AI recorder into the meetings and give the video links to the customers to review later, but because the Online Meeting isn't checked, the recorder isn't scheduled to enter the meeting and we have to manually send it in, which also doesn't auto trigger the video to send to the customer later. It's becoming a major problem.
Yeah, Microsoft Teams become a really popular service in COVID, and we're using this every day. Unfortunately, based on my last tests i can say that:
How about adding an option not to provide Microsoft's API with the attendee's email addresses? We also don't like the current behavior (of MS, that is!), but couldn't find any other workaround yet.
Hi guys, are there any update on this? An opened PR? Priorities set? An investigation? Is it going to be fix in the next few months or should we migrate to another scheduling platform?
Hi guys, are there any update on this? An opened PR? Priorities set? An investigation? Is it going to be fix in the next few months or should we migrate to another scheduling platform?
Unfortunately we've already had to migrate to another platform. Looking forward to when this is resolved to possibly migrate back. But this issue has been here for a very long while and there have been no updates. It completely messes us anyone using teams & outlook. Which these days is a lot of people & companies, so idk why it's taking so long to even give an update.
+1 for priority on a resolution here. This is frustrating
Anyone have any workaround? I have to go to each meeting separately and switch this checkbox to make it an online meeting. Then it sends updates to all invited contacts. It's frustrating.
This is such a big problem, the bad implementation and the duplicate emails. I canโt recommend cal.com to my clients because of that. Workaround that I internally use right now to at least avoid duplicate emails is to add the event to a google calendar. Then I get automatically invited on my Outlook Calendar and the customer also just gets one email.
Issue Summary
Microsoft Teams + Microsoft Outlook Calendar Meetings are not being created as online meetings, and have unprofessional description.
Steps to Reproduce
Actual Results
Attendees will get 2 emails. 1 from Cal.com and 1 from MS Calendar
The one from MS Calendar looks like this:
When I go to MS Teams to check this is what I see:
Expected Results
This is what that email would normally look like when I create a meeting through Calendly or MS Teams directly:
Notice how the location is Not the Meeting Link but an arbitrary URL, in this case Calendly's event, and the "Online Meeting" switch is turned on, letting Microsoft handle the link creation, instead of creating a link and then attaching it to the calendar event