Support of agents-hosting-extensions-teams package

[lilianmisser]

Hi, I am working on a Teams bot for my organization that sends notification to users from different tenants when we call an endpoint with a list of emails through an azure function.

We decided to update from teamsfx and I am trying to implement a way to save the email in our implementation of the storage because our goal is to notify users through azure functions based on their emails.

I made this snippet of code in the write function of my storage so I can save user email with their conversation reference:

let email;
await adapter.continueConversation(
    conversationReference as ConversationReference,
    async (turnContext) => {
        try {
            if (
                turnContext.turnState.get('connectorClient') ===
                undefined
            ) {
                turnContext.turnState.set(
                    'connectorClient',
                    adapter.connectorClient,
                );
            }

            turnContext.activity.channelData =
                turnContext.activity.channelData ?? {};

            const result = await TeamsInfo.getPagedMembers(
                turnContext,
                1,
                undefined,
            );
            email = result.members[0].email;
        } catch (error) {
            throw error;
        }
    },
);

I have couple of issues here, I had to directly set the connectorClient in the context because sometimes it was not defined (same for the activity channel data). At the moment I am using @microsoft/agents-hosting-extensions-teams, @microsoft/agents-hosting, @microsoft/agents-activity v0.6.18 but I noticed that some pull requests were merged with updates to the two last packages but not the @microsoft/agents-hosting-extensions-teams.

Updating @microsoft/agents-hosting to version 1.0.0 creates types mismatches with agents-hosting-extensions-teams on TurnContext.

Furthermore I noticed that agents-hosting-extensions-teams has been removed for version 1.0.0 : #469.

Do you have any way of doing to succeed retrieving user email in a Teams notification bot with azure functions.

[rido-min]

Hi @lilianmisser

Yes, we are in the processing of publishing a compatible version of the teams-extensions.

@Stevenic can provide more details on the timing.

In the meantime, I'm curious to understand the type mismatches you see.

[lilianmisser]

With this package.json configuration

And this same code

I get type mismatch on turn context from @microsoft/agents-hosting and @microsoft/agents-hosting-extensions-teams

Here is my adapter declaration

import { CloudAdapter } from '@microsoft/agents-hosting';
import config from './config';

export const adapter = new CloudAdapter(config.authConfig);

I was talking of type mismatches because I guess the TurnContext has evolved in version 1.0.0 but having @microsoft/agents-hosting-extensions-teams in the version 0.6.18 creates differences. I want to update the version of agents-hosting because I think some bugs about connectorClient has been solved if I am not wrong

[sarahcritchley]

Hey @Stevenic could you take a look at this please?

[jamesbirtles]

Teams support seems to have been removed? #469

Which is confusing as its listed in the first sentence of the readme

We were building on top of this, would be good to know what we're supposed to use going forwards

[MattB-msft]

@jamesbirtles
This is a work in progress with the Teams AI Lib folks.
Teams is moving their bits out of this repo and to another with the intent to merge with the AI lib bits, they will take over publishing separately, as part of that they asked us to remove the teams extensions for JS until they are ready to drop their bits.

@Stevenic would need to answer more on this.

[neotrow]

I'm having the same issue and would appreciate a quick solution.

We need to run @microsoft/agents-hosting on the latest version because 0.6.18 has another bug that we cannot live with.

Overall I have to say the developer experience on developing a teams bot has been very frustrating.
So many different packages with unclear guidlines on which to use, broken and outdated documentation as well as samples.

The push from MSFT seems to be to provide a very easy platform to get a bot up and running in no time but they are failing misreably right now.

@Stevenic do you have an update on how we can fix this?

[Dextaa]

To echo @neotrow, trying to make progress on Teams bot development is impossible at the moment.

@MattB-msft

This frustration is doubled because the Agents Toolkit Teams template/scaffolding presents Teams bot dev as a solved problem, with a solution accessible using a few toolkit commands. There is no path to a useful production app from the Agents Toolkit unless all you want to do is push notifications to the default channel of a team.

I've spent many hours working from that scaffolding to a production app, only to discover that even solving for all the bugs in the templated code/infra, the required solution is impossible without using dead SDK versions.

It's fine to be honest and say it's simply not ready. In fact, I'd say it's unfair to clients/users to send them down a dead-end.

I recommend that this templating (aka marketing) all be removed until there is order in the ecosystem.

[rido-min]

The teams extension package has been restored and it's available in NPM https://www.npmjs.com/package/@microsoft/agents-hosting-extensions-teams