This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello,
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.
We are also in the process of moving users from Islands to Teams-only mode and I'm not sure if she was recently moved to TeamsOnly.
Same behavior as described in this locked & unanswered thread - except ours is a Win10 environment:
Any thoughts are appreciated.
Thank you,
Brett
Using Classic Outlook on Windows for personal email, calendar, and contact management
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Just received an update from Microsoft:
Due to the popular demand Teams engineering team decided to re-enable this feature. According to Teams engineering team that they have reverted this feature on Sep 14th.
Restart Outlook/Teams apps and check if there's any difference
Today, five of the eight users reporting the issue now say it's working again. I'm still waiting to hear from the other three.
It seems to have resolved after the latest round of Windows Updates. Users who have it working are on "Microsoft Outlook 2016 (16.0.5071.1000) MSO (16.0.5056.1000) 32-bit." The issue was occurring when users were on "Microsoft Outlook 2016 MSO (16.0.4849.1000) 32-bit," so perhaps it was an update to Outlook that resolved it. As was the case before, Microsoft Support has no idea how it was broken or how it has been fixed.
I am also seeing this issue again. It was fixed for a while but it is giving me the same error message.
Yes, we are also seeing issues again with the same error message.
We now have seven users reporting this issue.