Andrew Clear

We've identified the root cause for why this is happening, and are currently working to determine what the default behavior should be for users from ACS clients. No ETA yet...

I've reached out to them. @RobinVds for future reference please use one of the methods outlined here for Teams-specific issues: https://docs.microsoft.com/en-us/microsoftteams/platform/feedback

The Teams group is currently investigating - either they or I will follow up on this thread when we have a more concrete answer.

The Teams group have repro'd the issue, and are working on solutions. I can only provide a rough estimate for a fix currently - the global roll-out of a solution...

For the booking a meeting scenario, you could have your bot return a Task Module and embed your existing web service as a web view in the task module. Essentially...

I get the same problem.

Hi - We just released Teams as a first class channel on the Bot Framework with the release of the 4.6 SDK. Can you please try this sample: https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/csharp_dotnetcore/50.teams-messaging-extensions-search

Hi - we've got a PR with an example of this using the vNext of the Bot Framework SDK. You can check it out here: https://github.com/microsoft/botbuilder-dotnet/pull/2646

Then how do you populate the rest of the Teams properties in resulting TeamsChannelAccount object?

Doing something like: ``` var roster = teamsContext.GetConversationParametersForCreateOrGetDirectConversation(turnContext.Activity.From).Members; List rosterTC = roster.ToList().ConvertAll(member => { return teamsContext.AsTeamsChannelAccount(member); }); ``` Also results in nulls