Cannot add Teams meeting to a single occurrence of a series

Anonymous
2020-08-06T17:20:04+00:00

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:  

https://answers.microsoft.com/en-us/msoffice/forum/all/outlook-for-mac-change-single-occurrence-to-teams/296ae8c1-e293-40c1-baa0-7d5ac99590d6

Any thoughts are appreciated.

Thank you,

Brett

Outlook | Windows | Classic Outlook for Windows | For home

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.

0 comments
Answer accepted by question author
Anonymous
2020-09-15T03:51:33+00:00

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

Was this answer helpful?

4 people found this answer helpful.
0 comments

79 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-08-27T14:16:17+00:00

    I had the same problem with a user (not wide spread yet but I'm sure it will be soon). She was using Outlook 2016 and 1.3.00.21759. The last old manual executable I had was 1.3.00.13565. I installed that but it is just going to break again next time her client updates.

    Mine is at 1.3.00.19173 and it works fine.

    Nate

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-25T14:27:40+00:00

    That is the version ((1.3.00.21759 (64-bit)) with office 2016 ) i'm running and the problem is not there for me.

    I don't think it is a version problem. Plus there are reports of users on 2010 and 2013 with the same problem. 

    The issue is deeper then desktop software, i think this is a back-end issue.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-08-25T14:07:11+00:00

    Hello Betty (Microsoft)

    our users report the same issue - what is the solution?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-08-25T01:46:29+00:00

    Hi

    Wrote back to MS support and no word from them. The culprit seems to be MS Teams. Once I updated to the latest version of Teams (1.3.00.21759 (64-bit)), I got the same error too. As Teams randomly auto updates itself on client's machines, that might be the reasons why not everyone is getting the error.

    Was this answer helpful?

    0 comments