Cli-microsoft365: Bug report: isValidTeamsChannelId is out of date

[balbany]

Description

As per my comment on #909 Teams is now spitting out a new Channel ID format (ending in @thread.tacv2) which is breaking the validation in isValidTeamsChannelId.

Steps to reproduce

• Create a new Team
• Call o365 teams message list against the General channel

Expected result

Get the messages from the channel

Actual result

Something like '19:[email protected] is not a valid Teams ChannelId'

Environment

Win10 Enterprise, PowerShell

[garrytrinder]

Thank you for reporting this @balbany 👍🏻

[garrytrinder]

Is the change in ID a global change?

For example, if I already have messages created in channels prior to the ID change, do they still return in the @thread.skype format?

[waldekmastykarz]

In my understanding both IDs are being in use so for the time being we should allow them both.

[balbany]

Correct - both are used. Existing channels haven't changed id.