Closed RichieMcCaff closed 1 month ago
Hi RichieMcCaff! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.
Best regards, Teams Platform
@RichieMcCaff This seems to be a problem in Outlook itself. Let me reach out to the Outlook team and get back to you.
Hi @RichieMcCaff - my team and I are responsible for these APIs in Outlook. We're looking into it and as @AE-MS mentioned we do have a repro. Please give us a few days into next week and i'll see if I can share any details then.
Thanks.
Update from our end, Classic Outlook for Windows was incorrectly expecting that startTime and endTime were required while the TeamsJS API lists them as optional. We have a PR out to fix this and with all things rolling out smoothly, the fix should be available in Insiders Beta channel in a few weeks.
Given that slower forks of Classic Outlook can take several months to receive updates, I would suggest adding some placeholder startTime and endTimes in composeMeeting to ensure CC, MEC, and SAC users don't face this error in the mean time.
Probably would have helped if I included the parameters I was using in the issue! Thanks for the workaround, I'll add it and close this out.
Hi RichieMcCaff! We have closed this issue in our system, but we would love to hear your feedback. To let us know how we did, simply use one of the following emoji icons: :thumbsup: for resolved, :thumbsdown: for unresolved, or :heart: for a great experience on this message. Please use the link for more detailed feedback.
Best regards, Teams Platform
When using the calendar module in the Outlook desktop app we get the following error when trying to compose a meeting:
This is after confirming the module is supported and confirmed working on outlook web and mobile apps.