Follow-up Q's to GA ANN from Build 2025: Teams AI Library, ETA on JS Docs, roadmap #184
Replies: 2 comments 8 replies
-
|
Thanks for reaching out, let me try to explain where we are with the Agents SDK for JS:
yes, you are on the right track
Curious to understand which samples are missing or incomplete. We are maintaining curated samples (with READMEs) in this repo, and also have a more samples in the JS repo. We are planning to make the JS SDK GA soon (like in a few weeks)
You are totally right and probably caught you in the middle of a refactoring. The idea is to expose Teams specific APIs in an extension package: https://www.npmjs.com/package/@microsoft/agents-hosting-extensions-teams , this one is based on the Application object instead of the We will update migration doc by GA to cover migration of JS bots. I'm adding @MattB-msft to comment on the relationship with the TeamsAI library. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the clarification & replies @rido-min!
Looking back at the JS SDK repo, that seems to be the case as I can't find what triggered me to write that original comment about a mix of old & new.
For context, I was looking for examples to update my Teams samples that currently use the BFv4 to use the Agents JS SDK. I found this, but there are just a few samples. The Teams DEVX group has a few different repos that contain tons of samples, which in the past seemed to be the quintessential samples, like:
Those hadn't been updated so I was just looking for things to reference. Looking through the current state of the JS SDK, it does look like a lot of progress has been made lately. I'll keep an eye out for the JS SDK GA drop. Thanks!
Thanks... that's exactly who I was hoping would chime in on that question... appreciate you @mentioning him as the handle I was going to use (and you just confirmed) didn't seem correct. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Are there any specific scenarios or APIs missing from the current teams samples? we have samples for TaskModules, MessagingExtensions, Meetings and AdaptiveCards. From the repos you linked:
|
Beta Was this translation helpful? Give feedback.
-
|
I see the team has made a lot of progress on the samples in the JS SDK repo since I originally looked at it... these help. I'll dig in and work to start porting my samples that used the BFv4 ▶︎ M365 Agents SDK. Agreed on those other repos... wasn't sure if you were going to have any influence on the MSFT owned ones since they're filled with tons of good resources for different scenarios. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @andrewconnell thanks for your feedback. Rido has responded to your specific JS questions, and @MattB-msft and I chatted, we wanted to provide feedback/comments/input on some of the broader questions you asked too.
We work closely with the Teams AI Library team, and the best way to see the Teams AI Library v2 release is a landing off point for the investments that that team are working on, which are focused on providing depth experiences for the teams client. We have been working with them closely so that we are aligned on the fact you should start with the Agents SDK, and for depth experiences, the teams extension IN the Agents SDK, which we have designed into the Agents SDK can be used to double click into those experiences (without locking you in)
We should share our roadmap :) thank you for the nudge. We are working on preparing something here which we can share externally as we do have lots of plans, and we do want feedback. We are also working with the Microsoft 365 & Power Platform community programs to be regulars, sharing the Agents SDK capabilities and also provide access for Q&A + input on our roadmap. Let me know if you have any other questions |
Beta Was this translation helpful? Give feedback.
-
|
Been a while since this reply, but with the Teams AI v2 GA recent release, I'm having a hard time reconciling this part of your response @sarahcritchley:
From what I've tried, it isn't obvious how to leverage the two SDKs together. I expected there would be something once your JS SDK was published and/or closer to their GA or, over time, something that would clear this up. So far, I'm coming up empty... Fundamentally, the two SDKs seem to take very different approaches, and it's not clear how I'd incorporate the Teams AI SDK v2 into an agent that I've started with the M365 Agents SDK. At this point, it seems like my decision tree is something like the following: ---
title: Where will your agent be used?
---
flowchart TD
A@{shape: diamond, label: "Only in MS Teams?"}
A -->|yes|B[Use Teams AI SDK v2]
A -->|no|C[Use M365 Agents SDK]
I get using one or the other when you start a project, but starting with one (M365 Agents SDK) and then adding the other (Teams AI SDK v2), that's not clear how to do that... Do you have examples of using two of these together? Looking at this repo, as well as the JS SDK one, I'm not seeing any examples using the Teams AI SDK v2 or any of its packages for that matter. |
Beta Was this translation helpful? Give feedback.
-
|
Keep in mind that Teams Bot applications use the same Azure Bot Service, so Agents created with the Teams AI libraries will also work in other channels, as long the agent does not use Teams specific features, such as meetings or group chats. Can you help me to understand the use case to use both SDKs together? (apologies, from my previous reply from the wrong account) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @andrewconnell - the two SDKs work together with C# & JS right now by registering the Teams extension e.g. here. This is targeting Teams AI Lib v1, and we are working with the groups to align on having this same pattern work for v2. Your diagram is correct - this is the high-level messaging we share across our groups where the recommendation is to begin with Microsoft 365 Agents SDK for broad usage (including Microsoft Teams), unless you are specifically focusing on Teams experiences and do not expect to be using other clients. |
Beta Was this translation helpful? Give feedback.
-
|
@rido-min said:
Honestly, I can't... in my discussions with the Teams AI group that came up which confused me as to why I'd do that. They echo'd what @sarahcritchley said in her reply above: @sarahcritchley said:
That implied I woudl have those scenarios, but I'm struggling to see when I'd do that... hence the question to better understand the scenario myself. |
Beta Was this translation helpful? Give feedback.
-
|
Scenarios where you will want to use both will include where you want to include teams client functionality like message extensions, anything to do with meetings etc |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hope this is the right place to ask these questions... I've been looking for the right people & place... if this isn't the right place, please feel free to guide me to the correct one.
ETA on JS SDK & Docs?
I'm working to update a lot of samples I've created for Teams apps over the years using the BF v4 & Teams AI Library v1, all written in Node.js. My understanding is that only the .NET SDK is documented...
🙋♂️ What's the ETA on the JS SDK docs?
Right now, I'm using the JS SDK source to figure things out, but not sure if I'm on the right track. Lack of updated samples is also making it tricky... I get it's early, but curious what the expected timeline is.
For example, there are parts (such as Teams Message Extensions) that feel like the classes were copied from BF v4, but other places in the source appear to use a more modern (btw, I like) way of handling the messages received from the Azure AI Bot Service... so it's unclear which I should use (or if the modern one isn't finished, or if I'm just missing something).
Further... the migration guide doc is very .NET SDK focused.
🙋♂️ When the JS SDK is available, will this be updated to reflect that or...?
Relationship/positioning [with|vs] the Teams AI Library
My understanding from the initial announcement/tease at Ingite 2024 was that the M365 Agents SDK would be the replacement for both the BFv 4 & Tems AI Library. Cool... makes perfect sense.
But then the Teams AI Library team released a v2 SDK out of the blue 2w prior to Build. I get the impression, in talking to others at MSFT that this caught people (inside Redmond) by surprise. The new v2 SDK preview is also a big expansion on its role... but it feels like it's trying to compete with the M365 Agents SDK & the M365 Agents Toolkit VSCode extension. I'm trying to get a better understanding of it, but I'm just getting more confused by their approach.
This page in your docs does a good job positioning the M365 Agents SDK to similar things (AI Foundry, Semantic Kernel, etc), but it doesn't address the Teams AI Library. It seems to me in that project shouldn't exist... everything I'd do with it would be done with your SDK... or not?
🙋♂️ Can you comment on the relationship with the Agents SDK & the Teams AI Library?
Roadmap?
Is there a public roadmap? I see things like #174, #156, and others that, frankly, give the impression while Build 2025 was the GA release, this is still very much a work in progress.
Is that fair?
🙋♂️ if so, is there a roadmap that not only explains what's been implemented (from BF4) in the Agents & what's coming?
Beta Was this translation helpful? Give feedback.
All reactions