Differences in returned value type between Botbuilder v3/v4 and Microsoft 365 Agents SDK

[PjPraveenkumar]

Cx is migrating from BotBuilder v3 to the Microsoft 365 Agents SDK using JavaScript and noticed a change in the handling of the composeExtension/querySettingUrl invoke event.

In BotBuilder v3, the handler registered via TeamsChatConnector.onQuerySettingsUrl must return an IComposeExtensionResponse through the SDK callback:
https://github.com/OfficeDev/BotBuilder-MicrosoftTeams/blob/6a71ca74e9a878551730dbf19a119cab5f03a788/Node/src/TeamsChatConnector.ts#L371

In BotBuilder v4, handleTeamsMessagingExtensionConfigurationQuerySettingUrl expects a MessagingExtensionResponse:
https://github.com/microsoft/botbuilder-js/blob/dc9464ec79a30bf6dd4f1f86bb3e3fa7b3db999a/libraries/botbuilder/src/teamsActivityHandler.ts#L563

However, in the Microsoft 365 Agents SDK, the corresponding handler does not expect a response payload and always returns HTTP 200, even though ConfigureSettingsHandler still returns a Promise:

Agents-for-js/packages/agents-hosting-extensions-teams/src/messageExtension/messageExtension.ts

Line 255 in dd45e8a

onConfigurationQuerySettingUrl (handler: ConfigureSettingsHandler<TurnState>) {

Why was the expected return type for the composeExtension/querySettingUrl handler changed in the Microsoft 365 Agents SDK? I couldn’t find any migration documentation covering this difference.

Question is: What would be the right way to migrate such handler linked above from botbuilder v4 to Microsoft 365 Agents SDK so that it takes the same effect?

[PjPraveenkumar]

@tracyboehrer / @MattB-msft would you be able to confirm on this please ? Cx waiting for the confirmation.

[PjPraveenkumar]

@tracyboehrer / @MattB-msft Could you please shed some light on the above query?

[benbrown]

There is currently a gap in some of the teams extension methods that do not properly return the handler as part of the invoke. We are going to correct this in an upcoming version. I will post here.