Teams meeting ID

Valued Contributor

Dear All,


Please i need your support on this issue.


I have reference the link which describes the problem I have : Teams create new meeting links with old IDs.


Several useful information:

(a) it looks to be related to the roaming profile and the information store for the TEAMS outlook add-in.

(b) this affects all the meetings that I create from outlook. If I create them from TEAMS then the issue is not there. This is a real issue as it means that people in my meeting see the chat of all the previous meetings.


And all the chats are "consolidated" in this "unique (re-used)" meeting. The first symptoms was that the meeting title was the one of a previous meeting. If I start the meeting from TEAMS then the title will be correct but the chat contains all the historic of the previous meeting.


According to what I've seen this affects all the meetings which have been created via outlook. So for the moment I will try to create meeting only from TEAMS but not always convenient especially when I use the "reply with meeting" option in outlook.


And despite I have cleaned the complete TEAMS cache according to the second url below it has not solved the problem.


Some persons have the same issue here:


Does any have an idea how to resolve this issue.


@Eric Marsi 



@Christopher Hoard

@Allen Xu_MSFT


@Steven Collier


@paul keijzers

@Bryan Nyce

@adam deltinger 

@Chris Webb


@Graham Walsh


Zhengqi Lou-MSFT

Vasil Michev

Nate Loback

Yuki Sun-MSFT

@Juan Carlos González Martín

@Satyendra Sharma



2 Replies

@IBN I can think of a couple workarounds. One would be to disable profile roaming, or to exclude that specific folder from being synced. Another would be to switch from the Outlook desktop app to Outlook on the web.


What I would not recommend, however, is to hold out any hope that this bug will ever be fixed. The issue where Teams meetings created from the Month view have start and end times of 12:00am was reported almost two years ago and still hasn't been addressed. It is clear that Microsoft is directing little or no effort toward the maintenance of this feature.

There IS an actual solution by Microsoft. We raised a ticket last year and they provided us with a simple RegKey to fix this issue but I can´t remember. Does anyone from MSFT please help in this case? Call was opened in the M365 admin center and addressed to the german support team in Romania I guess.