Cannot add Teams meeting to a single occurrence of a series
We have a new issue - when a Delegate tries to convert a single occurrence in a series to a Teams meeting she gets a message telling her she must convert the entire series to a Teams meeting. (""This is one appointment in a series. To make it an online meeting, open the meeting series and try again.")
She does not want to change the entire series to a Teams meeting.
She states that she was able to do this until about a week ago. When opening a recurring meeting, she would get prompted and choose the single occurrence then proceed to add the Teams meeting to this single event only.
Same behavior as described in this locked & unanswered thread - except ours is a Win10 environment:
Any thoughts are appreciated.
Has anyone addressed the security issue here? If a meeting series has one Teams link and a person is invited to a single meeting in the recurring series, they then get access to the entire series' chats. You can remove them manually, but they still have access. Not cool.
Jeff W commented
I already posted this in another thread, but wanted to share my findings here as well.
I have similar issues with end users in my office. The OWA work around allows them a temporary fix, but I found updating my Office desktop application is what breaks it.
I thought it was due to a teams update, but after updating teams I was still able to change a single occurrence within a series.
I updated my Office from 'Version 2007 build 13029.20308 to 13029.20344' and started having the exact same issues my end users were reporting.
It seems as though there was an issue with the latest office update that breaks the teams plug-in ability to change a single occurrence of a meeting series to a teams meeting.
Following - this is an issue that for those of us who are delegates on multiple exec calendars and regularly are needing to change single occurrence within long standing series to online meetings due to COVID-19 and remote work (or office/remote hybrid as slow re-openings are happening). The fact that MS replied to someone who voiced this issue as connected to Outlook as being "by design" is ridiculous. If that is the case Microsoft took a functional tool and broke it just in time to make an already stressful situation for some due to the remote work/pandemic changes, even worse.
We have the same problem, it's not the versioning. It generates a lot of dissatisfaction in our end users who create regular meetings and add occasional TEAM meetings to the ones they need, it's a working model that is implemented and the failure is causing a lot of unrest.
Lisa Roebuck commented
Same issue we've been tracking here: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_win10-mso_o365b/cannot-add-teams-meeting-to-a-single-occurrence-of/fbf2db7e-e8b3-443f-bed9-ec1f9dd6ce31?messageId=3b874b75-1426-48a8-ab05-9f8fbbdfa199&page=4
This is a serious problem for our users who manage a lot of shared calendars with recurring events that are set up for clinical evaluations, but the attendees to each evaluation change. To protect PHI and maintain HIPAA compliance, a new Teams invite link is put into each occurrence of the series, to prevent the wrong clients from attending the wrong occurrence of the series. For our clinicians, its a series of events that recurs. For our clients, it's a single event. To set up these hundreds of events for our clinical team per week individually would be a nightmare.
The option to add a Teams meeting to a single occurrence still works in OWA, so that leads me to believe this is not functionality created on purpose but is something someone broke. Unfortunately, shared mailbox calendars that have logins disabled cannot be used in OWA this way so that is not a good workaround for us (or anyone that relies on the desktop app).