Microsoft 365 Community Teams, 22 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Microsoft Teams community call-October 2020

Description

This month's agenda featured Microsoft Teams meeting extensibility and two community demos including HTTP Status Cats Messaging Extension
and calling the Microsoft Graph API from a messaging extension.
Speakers: Rajest Rangarajan, Tomomi Imura and Markus Moeller (Avanade)

Resources:
HTTP Status Cats sample https://github.com/pnp/teams-dev-samples
Microsoft Graph API blog https://mmsharepoint.wordpress.com
Meetings extensibility https://aka.ms/create_apps_in_meetings

Stay connected
Twitter https://twitter.com/microsoft365dev
YouTube https://aka.ms/M365DevYouTube
Blogs https://aka.ms/M365DevBlog

A

Thank you all for joining the october teams, developer community call. You know, we've got an awesome agenda for you guys today. So we'll start off by you know doing a brief recap of last month's ignite and then we're super excited to do our very first community showcase, where we have two members of the team's developer community to mommy and marcus today, who will be presenting and showing some amazing things that they've built? You know, I'm personally super excited about starting this and it's something that we'll be incorporating into our calls going forward.

A

You know the word community isn't lost on me and I want the members of our team's developer community to come together and learn together and support each other. So it's not just about us.

A

You know bringing microsoft speakers, but it's also giving members of the community the opportunity to come up and spotlight some of the great things that they've been doing with teams and then, lastly, we'll we'll wrap up with a good session on a huge teams, platform, focus area teams, meetings, extensibility with apps from meetings and if time permits we'll have some q a so with that said, let me kind of move on so microsoft, ignite 2020..

A

So last month we held our annual microsoft conference from the 22nd through the 24th of october or of september sorry, and that was fully digital. So we hosted hundreds of sessions on a 48 hour cycle across multiple time zones and then, specifically for microsoft. For the microsoft teams platform, we had 12 dedicated sessions across the main ignite website in our virtual hub.

A

You know, and some of the main platform themes that you know we covered during ignite from a team's platform standpoint was building deeper teams integrations with teams meetings which will get an awesome overview today by rejection. Also co-presented on this topic at ignite, the other being you know, accelerating digital transformation, with loco teams plus power platform, where you know, we've made significant enhancements to our low code and citizen developer uh capabilities and then, lastly, just continuous enhancements to teams, platform and learning.

A

You know where we've covered many of the amazing improvements to the platform over the past several months that we've made and where we're going forward. So you know in case you guys didn't, have a chance to attend ignite. You know I'd say, don't worry! You know. All of the sessions are now fully available on demand across the ignite website and virtual hub and I've got all of the teams platform sessions loaded here and where you can find them.

A

So you know if you want, you can go ahead and take a screenshot of this slide, but we'll also be providing out this page in our in our blog. That follows the call um just so you have um easy access to these sessions, so you know I definitely highly recommend you know taking some time when you have some free time to watch some of these sessions. We've got some great content on here. You know kind of keep you up to date on all the the latest happenings from a team's platform standpoint.

A

So enough about ignite, you know now I am super excited to kick off our community showcase today with our guest, presenters, tomomian and marcus. So you know I'll have to mommy present first followed by marcus. So with that being said, you know I will let tamomi take the reins.

B

All right, hello, this is tomomi and I'm doing a cloud advocacy for m365 and I'm focusing on teams. Ms teams and I actually joined the company this summer, so I've been here only like three and a half months, so I'm relatively new, so the one of my tasks is something like you know. I wanted to create some tutorial and a code sample that is like step by step like easy to follow tutorial for everybody who wants to create teams and the apps for ms teams.

B

I would say so it's early in the morning, so my brain is still kind of fuzzy but anyways. So this is my toy app. It's called http status, cats. I have a and they have ripple here. I mean this code sample, it's a hosting ripple, it's on pmp, and this is called this hp status. Cats app for microsoft teams. What it does is it lets.

B

You look up, uh http status code, so you know if your developers, especially working on some apis, you have occasionally you know you occasionally get the time that you need to look up some status quo right. So it does that and let's see something like four four: I guess everybody probably no not found so yeah. So I'm using the message and extension feature for ms teams api and uh you can use this app. So basically you can look at the status quo in two different places.

B

So one is like I show you you know from this uh command bar on the top. So let's try another one, something I like yes, 301 means move permanently and it comes with cat. Folders and I'll. Show you another location here, so you can do the same operation from here and compose message compose window.

B

I mean the input bar and here's. I need to make a better. I go because it's kind of hard to see click here. uh What I want like 500.

B

Internal software, let me try something else, something I don't know 501 not implemented. Okay, let me see, oh something, you know what I'm going to show you my favorite 4 18 oops. I did.

B

B

I wonder if you knew about this 418, I'm a teapot so yeah. This is a message window. So if you feel like uh sending a message, let me see you can still. This is how it works. So, historical, it's not really historically, but you know, internet age goes fast, so I created this like almost nine years ago. So it's been quite a long time ago I created this original http status cat.

B

That was just uh nothing more than the collection of cat photos with corresponding http status code and that actually gave me 15 minutes of pain, and the great thing is about this was a community. You know, developed community have reacted, so everybody have created something like api, um apache, config file, webpages and all kind of cool stuff, and someone in europe even created this um hd http dot cat domain like daca, catalan domain and web page. You can take a look at actually.

B

I have it here: oh not that one and yeah this is, you can see it's yeah, pretty cool, so yeah, so yeah. Why not? I created my own stuff too. Like again, I wanted to show you how to create. You know: teams app and uh well. I created this really quick, so I'm not super proud of the whole code. If you take a look at, I didn't really do all the error, handling and stuff, but you know just the purposes I wanted to show you.

B

You know in easy to digest code sample and see what you can do so that it's pretty much it.

A

Awesome, thank you so much to mommy, and I just present this on the screen real quick. So this is what tomomi just covered. You know, if you guys want to, you know, get some more information on this. You know here's kind of a a slide that kind of covers. You know what the related article is, where you can kind of locate this on github but yeah. This is super awesome. You know this kind of hits me in the in defeat all that gives me all the feel since I'm a cat man, so this was awesome.

A

Seeing so thank you to momi and then next we have marcus presenting today as well, so marcus. I will go off screen and we'll. Let you take it over.

C

Yeah thanks: okay, hello, my name is mark smaller, I'm a microsoft, 365 developer and I work for abernath in germany. You can reach me on twitter or where my blog and the last line is only a warning just in case of unpredictable background noise here in a small flat and stay home times. It can happen that my little daughter cries today. I want to show you um about a microsoft teams, messaging extension, which is uh search based impact and the authentication method to access microsoft graph in the back.

C

My scenario is uh that I'm talking about some documents that need a review. We can see this here in my small little document library. So I have some documents here that need a review and those documents. I want to communicate inside teams and enable the review from that perspective.

C

How does this work in teams? I created a messaging extension as mentioned you can fire it up here. This is a search-based scenario, I said so it's quite a simple display. We can pick up now either a document or what we can also do return back and also do some filtering here.

C

So that we only in and assuming we have lots of documents here, we can also intercept and do some search-based stuff here and again paste this in teams. Now we have this adaptive card shirt in our team's channel and everyone having access to it would be able to either view our document or even put this on review.

C

It can adapt this by a small date and put this on review directly and when we go in our document library, we can see that our document just got reviewed and also the next review is set to a date in the future.

C

What we can additionally do um is because you might ask how to access these documents, I'm doing this with uh the graph api, but with cyberpoint access. So I need some information from where I get these documents, um so such a messaging extension can also be configured with some settings and in my case here I have the site id and the list id that point to that.

C

This was just demonstration. Now, let's check, how does this work? First? Is the injection. So how uh does this code get fired? This is done in the team's manifest with the so-called compose extension.

C

um What we have here um is, on the one hand, we have a bot id that will be inserted and two other things are interesting, so the setting can update configuration and initial true says that this automatically executed. So this is what we have seen already once we click on the extension. We already get documents, not only when we search for something um this is we see this in the code later how this is detected.

C

The next thing is, of course, how to get the initial documents.

C

This is executed in the so-called middleware in the teams in the teams app and this middleware, this imessaging extension middleware processor in the on query method, is uh communicating with the bot in the background and here what we first try to do. Is we try to get a user token? In my case, this was successful and I will just uh so that I forget to demonstrate how, when it's not successful, I will catch this up in a minute.

C

So uh here we have a token. This is why I shortened the negative token response here. I directly jump to where we get our documents and then we instantiate the graph controller, get our settings. What I've shown you.

C

I do this in a really simple way: an adjacent db option, of course, in a productive scenario, you might do this different, but just to show you how configuration is done and just retrieving the parameters and finally, at the very end, in the second last line, my controller retrieves, the documents with, in the background, the simple graph call, and then we have the documents.

C

Alternatively, um we had the search, uh the filtering, in my case, it's more filtering, because when you look in my code, you see that I'm taking the documents from the initial run in this document, so I'm not doing another server request. In my case, of course, I could do this, but just for simplicity reasons, I take the original request and simply filter it by the string that I'm retrieving from search parameters.

C

And, finally, I will also use the documents, the items that I have and then iterate them and transform them in right. On the one hand, on the left side, you see the so-called preview visualization.

C

This is in the in the overall result and on the right side, you see the single adaptive card representation once I select one and how this is achieved.

C

This is by simply returning an adaptive card and on the right hand, you see a bit shortened my adaptive card um consisting of a body and actions and on the left hand you can see um the preview which is quite similar, but here in the search based scenario, you cannot modify this uh in a real way.

C

I'll show you some other examples at the end break how you can do this different um and, finally, I will put the pieces together in in an attachments uh object, and this is, I will return as a result to my messaging extension where it will arise the settings um you have seen. It's also quite simple. Therefore, we need two methods. um This is, on the one hand, on query settings url. This is just returning.

C

Finally, the url to my settings, page with a small html page inside my solution, but I also have to return, of course, existing parameters like if you already have configured values you need to return them. This is what I'm doing here in most of the parts of the code and the second method, the on settings method. This is executed once the configuration is done and returned back, and in that case I'm just simply saving all my parameters to my json dp, simple configuration storage, the reviewed action. Finally, um we can make this quite short.

C

This is what we also again need to check for the authentication and then we will finally take some parameters. First, the configuration again in a short way, and then we will only execute the update item method of my controller and what I'm finally doing- and this is now I can jump back to my demo- because this is what I missed to show you is that I'm signing out the user. This is no production scenario.

C

Of course, this is just for demonstration purposes and when we go back and try this again, I just want to show you how this looks like when I have no token when I'm not signed in then I will get this and once I just set this up, then I'm signed in again and now we see that we only retrieved two documents, because one was already reviewed yeah. This is quite clear and to show uh how this authentication works.

C

My last two slides or demos, is first um what I just showed uh yeah. I hided this in the last screenshots of my code. Here I have the negative check of my token response. So if I don't have a token, then I will simply retrieve from my bot adapter and get signed in link and return this as a messaging extension result, and this is how I retrieve this window, what you this pop-up window, what you have just seen now, the final question how this is configured.

C

This is configured, um of course, what you need. I showed this in the manifest already that you need an id of your bot, and this is a dot adapter. You need to configure in azure. This is on the left side, um where you also have to put a messaging extension endpoint.

C

This is a debug scenario here, where I'm using android for this, I o, but you can also deploy this, of course, to an azure web app for production scenarios and at the very bottom you can see the out connection settings and this connection setting you see on the right is here I put in my app registration value, so my client id my client secret and the scope and uh behind the scenes.

C

Of course, I have requested the right graph permissions to write to sharepoint and that's all how the authentication works together this um this app now only some simple screenshots. um With this I've seen, I told you that it's not uh you cannot massively configure the ui in the search based alternative.

C

Therefore, it's quite easy to implement, as you have seen, but you can also create an action based alternative and what I've done here is I'm presenting a grid, and I was also, for instance, highlighting a document that is much longer due for review and also I can get input parameters what you can see at the bottom that I could also request, for instance, some additional parameters, some comments for this specific review case- and I could also point this out in the adaptive cart as an additional parameter, not coming directly from the document and another option I recently presented in the sharepoint framework call is also quite similar in this action-based scenarios, for instance developed with spf x as an alternative to the yeoman team's generator, which I was using here last, not least, some resources.

C

I've created a blog series on all on several authentication scenarios, all around messaging extensions um here you can see the link and then uh the whole code of this example, and also of the other ones, uh is available on my github and also on the team's dev samples, github repository, that's from my site, thanks so much.

A

Awesome, thank you so much marcus for for walking us through that, and thank you to momia as well. You know for spotlight, spotlighting. You know both of your guys's amazing demos and samples that you've created so now on to our next topic. You know I'd like to hand it over to my buddy rajesh. You will be walking us through one of the biggest upcoming platform features and meetings extensibility through app teams, apps for meetings. So rajesh do you want to share your screen and kind of kick us off on this awesome.

D

um Hey, thank you all so much for joining this community call. I am personally so excited to be presenting this. uh My name is rajesh. You know if you watch the big bang theory, I am rajesh and I am currently a product manager in microsoft teams and specifically, I am the pm for meetings extensibility uh apart from my time at microsoft, which has been now three years. I am a proud penn state alum um and you know, uh love to watch college football.

D

So with with that introduction, I kind of want to dive into the team's platform and how the team's platform has evolved um and specifically talk about meetings extensibility.

D

When you look at the team's platform overall at the very bottom, at the very foundation of the platform, there are services like craft and sharepoint and power platform that then start working across different app capabilities like tabs, bots and message extensions and these capabilities of an app along with the backend services that we offer work in different surfaces within teams. You must be familiar with personal scope, channel and group chat, and for the first time we are introducing meetings as a surface as well.

D

So uh this is, uh you know, a million user billion minutes kind of an opportunity, and we are. We strongly encourage you to partner with us and start building some applications.

D

So when we think about the meetings, life cycle meetings is a very, very interesting space in that it's not just about the meeting, but it starts way before the meeting even begins.

D

So when we think about the life cycle, it's things that happen before the meeting during the meeting and after the meeting and before the meeting there are things that the users try to accomplish, specifically organizers, who send out the meeting invitation they would like to prepare ahead of time and when they actually go to the meeting, they want a collaborative and productive environment and when they actually finish the meeting, they want actionable next steps and they want something that something a place where they can store all the information and notes that they have pertaining to that particular meeting.

D

So we have thought through the entire life cycle, just the way you see in in this particular slide and in the course of this presentation. What I'm going to talk to you about is how to actually build your application so that it fits across this.

D

This meeting life cycle, if you go to the next slide I'll, be talking about a few things I'll be talking about how to attach your application to the meeting life cycle before during and after the second thing is I'll, be talking about ways you can make your app more meeting aware and I'll explain what that means in just a bit and then finally I'll be talking a little bit about the new ux services and places where your customers and your users can engage with your application.

D

But before I even get into the nitty gritties, uh we already have a handful of partners. Who've been um closely working with us, and pagerduty is one of them.

D

A page of duty is an incident management platform that provides a real-time collaborative and productive environment, so that customers are being served well uh by their service provider, such that when an incident comes through, a group of people can actually come together, get on a call, see make decisions and actually have a discussion all with the context of that incident ticket that was raised.

D

So if you see in the next few slides like page of duty, the the experience that they're building is before the meeting, the organizer is able to set context in the meeting chat by sending a message extension um with an adaptive card. That explains what the incident is um and essentially building that context and when they actually get into the meeting notice that there is a side panel experience where the context that the organizer created follows them, and so that everybody in the meeting can grab the context.

D

While they are in the meeting having that discussion and making those decisions and then, finally, after the meeting they can actually assign tasks. They can actually say that hey you're, you're responsible for these things- and these are the notes from the meeting itself, so page of duty- has intelligently gone through the entire meeting life cycle and they've used.

D

The the new ux surfaces that we introduced and also some of the existing capabilities, like message: extensions to kind of complete their story just like pagerduty, you all can also create some phenomenal experiences and I'm going to kind of take you through each part of the meeting life cycle and tell you how to go and build your application.

D

So before the meeting. How does your app actually appear in the fly out that you see here and particularly you're, probably wondering what does optimized for meetings even mean I'll get to that in just a bit? But in this scenario, you're trying to add your application um to the meeting before the meeting even starts, and how does your app actually be surfaced in this flyer?

D

The changes that we ask you to make is uh the the app manifest that you have. There are two fields that is the the scope field, and then there is the context field.

D

We would want you to have group chat, as the scope and context will be meeting chat tab and for those who are familiar with the platform already. Yes, we've made changes to the app manifest we've added a new field called context, and I highly encourage you to go. Read our documentation to understand more about what context actually means. The simplest way to think about it is context is mainly for where your app appears, whereas scope is for whom your app appears.

D

So just to recap for your app to be available before the meeting. Your context is meeting chat, tab and your scope is group chat. That is signal for us to showcase your application in the fly out that you see here in the next step. What happens during the meeting? There is, as you see like this in meeting site panel experience and for you to actually enable your application in the meeting.

D

As I said earlier, the context that we need is the in meeting site panel. So the context here is meeting site panel and the scope still remains group chat. That is when your app becomes meeting optimized. So if you're wondering what does optimized for meetings mean, it just means that your application functions before the meeting in the meeting chat and it functions during the meeting as well, and that signal for us to showcase your app in the meeting optimize section of the flyer.

D

In addition to the to the side panel, we we are also introducing a net new surface uh called the in meeting dialogue and the way you should think about the in meeting dialogue is the ability to showcase an actionable notification in the meeting stage itself.

D

One of the classic examples that we we've showcased here is how you send a poll and get users to actually participate in a poll. This is a way to get user engagement and to actually grab user attention for the most important thing. So this is something that is net new and it resembles a task module and if you do recognize that it is in a way a task module. The underlying infrastructure is the same, but the intent and the purpose is different. So we've documented this publicly.

D

I encourage you to read it and make sure that uh the the use of this surface is for the right reasons. Now, how do you actually create one of these in meeting dialogues?

D

We we've actually expanded our conversations api. So if you look um at the conversations api, it's something that works only when you have a bot registered and when you're able to generate a bot auth token. So that's the prerequisite and as part of the request, payload we've introduced a new field called external resource url, and that is the the url that we'll be hosting inside the in meeting dialog. So in a way, it's a web view that contains the notification that you would like to.

D

You would like to showcase to to your customers and to and to your users again I highly encourage you to read the design guidelines so that it feels native and it feels rich when, when users start interacting with us now the conversations api, the way it works is you'll need a few input parameters and, in the next few slides I'll kind of tell you how to get those input parameters.

D

I think so in the previous slide, it's finally wrapping up the meeting life cycle itself. So uh what happens after the meeting? So when you actually uh finish a meeting, users should be able to go back to the tab and and make updates or or change things based on what they learned from the meeting. As long as you've enabled your app in the pre-meeting space post meeting is exactly the same surface. There's no net new work that you have to do as long as you've done the work for enabling your app before the need.

D

With that, let me get into some of the let's say like different aspects that developers should know about about the meeting itself in a given meeting. There is like different roles, so on the left side you will see organizer, presenter and attendee. These are the roles that are available in a meeting and if you see the first row on top, there are different kinds of user types, guest users, anonymous users and in-tenant users.

D

Now these user types can assume any one of these roles: organizer, presenter and attendee, but the catch is that when you want to add, remove or uninstall an application in the meeting life cycle, attendees cannot do it and guest users and anonymous users, regardless of what role they have in the meeting cannot do it.

D

So it's one of those very interesting things that uh that have marked at that the very end of of the matrix here, and it also showcases the different roles as part of the whole meeting meeting life cycle and as part of meetings. Extensibility we've created an api called get participant api, and this api gives you the participant role.

D

So if you provide us with the participant id meeting, id and tenant id we'll be able to provide you the role of that user and that's a very powerful api, so that you can create experiences based on roles, and when I give you a closing example I'll tell you how some of the developers have been thinking about it, the way to now retrieve the information meeting id participant id and tenant id. There are a few ways to do this. The first is tab sso.

D

The next is the team's client sdk and the third way to get this is through bottom work when I say bought in work message. Extensions are also using bots, the underlying infrastructure. So it applies to both message, extensions and bots.

D

You can get up the participant, id and tenant id through any one of these methods, but we highly recommend you to use tab sso and, as far as meeting id is concerned, you can either use the client-side sdk or you can use the board involved and below. Are the links uh we'll also share this out with you to kind of help you get up to speed on on these concepts, in addition to the get participant api, the next slide of the the last line will be something called as frame contact earlier.

D

I said that your app can be aware of the meeting itself. What frame context does is that it gives you knowledge on where the user is and from where they have invoked your app invoking an app from the in meeting window versus invoking the app from say, pre-meeting or post meeting is different and your experience or the content that you want to generate could change based on where the user is frame.

D

Context is that is, is that tool for you to determine where the user has invoked your app from so that you can render appropriate experiences.

D

So with that, uh there's always the the more admin oriented aspect so in the next few slides I'll kind of quickly gloss over the different admin experiences, so that you are aware of how your app is being treated admins and organizer controls for the very first time anonymous users are able to not just join a call, but they can also interact with amps and, like I said earlier, they cannot and remove or uninstall applications.

D

But if you send an adaptive card to the meeting chat, they can actually participate in it anonymous users. But if admins are not happy about it, they can actually use the new control that we've provided, which is the ability to turn off anonymous users from interacting with applications. If you go to admin.teams.microsoft.com into meeting settings, you will see a toggle that says, allow anonymous users to interact with applications it's default on, but we, like, I said you know, we've given uh admins the ability to go and turn it off.

D

If uh they don't want this to happen. In addition to this, uh you must already be familiar with permission policies. It's it's. It's a feature that we announced last year, where admins can actually selectively, go and enable or disable applications for users and for the tenant itself and with introducing meeting applications or meetings extensibility we'll continue to honor any permission policy. So let's say that your organization or your customer has blocked or has enabled a handful of apps, and let's say that your app now has meetings extensibility, nothing changes in terms of their policy.

D

If, if it's blocked it remains blocked, if it's allowed, it will be, it will continue to be allowed.

D

In addition to this, I think a few things are, like I said earlier, an organizer or a presenter are the only ones who can add or remove applications or install applications or uninstall applications.

D

So in the meeting window, when you right click, only organizers and presenters will be able to perform these these operations and not attendees are not anonymous users or cat users. I think that kind of brings me to to the end of this presentation and I'll kind of wrap it up with with one example, which is poly. So the way paulie has done.

D

This whole thing is before and after the meeting experience, they have added meeting chat tab to their manifest as a context now, because of that they are able to operate as a tab in the meeting chat before and after the meeting when you go to during the meeting they've enabled meeting site panel as the manifest context, which is why they are able to render the in meeting site panel and if you notice uh there is a button, called create, create a poll.

D

They've used the get participant api to determine whether the participant is a presenter or organizer or attendee, and they are rendering experiences in that site panel according to the role of of the user who's using the application and then during the meeting they are also they have also integrated. With in meeting in meeting dialogue.

D

To my earlier point, they've used the conversations, api and they've, given us an external external resource url, to help us render render this experience during the meeting so that users can create polls and get responses from all meeting participants and then, even even in here, you'll notice. The fact that they've used the participant role api to see like who gets to see the results versus attendees, who probably shouldn't, be seeing the results just yet yet they should just be participating in the poll.

D

But then it depends on the role so that they can determine whether they show the results or not. On on the side panel, I think yeah. So with that, you know, that's paulie's experience the way, they've wrapped things together, and some of the resources um are here for you to get started and build similar experiences or even even better experiences through your customer needs and also through your creativity.

D

A

Awesome, no thank you rajesh, for you know taking time to to walk us through all of this. This is a super, exciting area and we're looking forward to all the amazing. You know meeting apps that are going to be created using these, so you know to all the to the devs on this call. You know start playing around with this see.

A

You know we definitely want to see all of the you know the awesome apps that you can create with this all right, so we are kind of at the end of our presentation now, um so I would love to open it up for for any q a so if anyone on the call has any questions for you know either tomomi or marcus on on some of the samples or demos that they've created or any questions for rajesh, please, you know feel free to you know, write your questions in the chat, pane and we'll kind of cover them, as we can.

E

Mike had a question for rajesh about the time frame that this was going to be released.

D

Yeah, absolutely, I cannot commit to any public timeline just yet, but this is in developer free view, so you should be able to go and play play with it. You should uh public docs are already published it's again in preview, uh so it's all publicly available. So it should. You should be able to go and start building your applications in terms of the ga date. um I I just cannot comment on it at this point.

E

There was a question a little bit ago from tim about do apps like pager duty require the advanced communications add-on, license.

D

What does advanced communication license uh entail up? I'm not sure.

A

I think it's one of the premium skus for I don't. I can't recall the specifics on there as well, but you know I don't think you know the pagerduty app or any of these bdm's required. The the advanced communication skus.

E

And then is it possible to have a meeting application trigger meeting recording understanding it may have to initiate, as a user.

D

Yeah, so uh that's a great question. uh The short answer is no, but it's something that we are aware of. You know, like developers, have been asking us about this, so we are aware we are aware of this. Ask it's not available as part of this. This initial launch.

E

Is there any app already available.

D

Yeah, so um I believe you you can try, like, I think uh in the developer ring you should be able to play with forms. uh One note and I believe poly as well.

E

Okay, great and then will the whole process be able to be edited and formatted to a presentation formatted to a presentation to store the meeting and share it.

D

Oh like when, okay so formatted to store the meeting and share it. No, that's that's not available. uh Well, there may be some graph apis that could possibly give you that, uh but it's something that I'm not privy to, um and it's not part of this offering or rather this presentation that I have.

E

Okay, great and then um mike asked another question: is there a way of interacting from powerpoint or other presentation apps within a team's meeting app.

D

So if I, if I get the question you're asking if your app can kind of interact with another app like powerpoint, is that the question or are you saying like when you share screen like to do powerpoint like uh some more clarification, would help.

E

um To present powerpoint slides and share requests, oh.

D

Okay, oh yeah, so I think I think he is talking about so I think they're talking about like the ability to like share a powerpoint presentation like we do today, except that they want it for like other applications, is, is what I understood uh it's. uh We are very well aware of this. Ask um it's something we do have a plan for it. I don't have timelines, um but it's something that we think is a very powerful scenario for us, so uh it should, it should be. It should be in our road map um again.

D

I cannot comment on on the timeline just yet.

E

Okay- and that was exactly what he was looking for, so that's perfect. um Another question, while scheduling meeting, is there any option to add this meeting apps.

D

Is the person talking about adding an app before the meeting starts, or are they talking about adding an app during scheduling.

E

Before, while you're scheduling the meeting.

D

Yeah yeah, so uh it's something that we've we've thought about it's without getting into too much. You know like uh the technical aspect, it's about a bit of an interesting space where we need to like. Let me put it this way, it's something that we've thought about and we want applications to be attached to a meeting. uh But at the time of scheduling a meeting, it's it's a feature that we do have in our roadmap.

D

It's not available as part of this launch. You will need to send out the meeting invitation and then add the application.

D

uh But the particular ask is something again: we are aware of it and we are working through it and should be. Should I should have some some kind of an update soon. I don't know how soon.

E

How about a timeline or schedule to keep the meeting in control.

D

To keep them meeting and control, so is he asking for, like things like muting unmuting start sharing, stop sharing things like that.

E

Yeah, are you asking for more meeting options, ricardo yeah.

D

Elements of the meeting that is, that is a good one. It's not available as part of we don't offer those controls as part of our v1 launch.

E

um Mike made a comment, I was thinking of a meeting apps using the new context area to show a countdown timer um sounds like a good app idea.

D

Totally yeah, I mean uh in fact it's it's one of the things that we anticipated when we did things meeting dialogue so in an inmating dialogue is persistent in nature. So let's say that you actually want to trigger a timer because say a bunch of students are taking a test uh totally yeah. You should like uh show an in-meeting dialogue to say if you have five months left or ten minutes left, I don't know your exact use case, but that you should be able to to power that, with the offering that we have today.

E

Okay- and I think that's what ricardo was actually talking about about keeping the meeting in control for the time allowance, so that was great. Thank you.

D

E

Yeah there was a question about teams apps in meetings and if that one will be available in forms for meeting polls.

A

Yeah, I believe forms is one of the one of our microsoft apps that will be available once uh meetings extensibility releases later.

E

Great, thank you.

E

We have a few minutes left for anyone who wants to say we still have time for more questions. Matt mentioned, there's a feature coming that has a five minute notification before the scheduled end correct. He read about it somewhere where you get, you know it's a half hour meeting and then five minutes before the end. There is a notification.

E

That's right! There's.

D

A banner on top yep.

E

D

So, what's the question.

E

So when is it coming? um Ga, I believe, is the question.

D

Well, uh so uh I don't know, uh but then like, if you want to like give notifications because of through through an application, the in meeting dialogue is where we are asking you to kind of go to uh versus versus like the banner kind of kind of experience. So if you want to like notify your user saying hey, you have only five minutes left then, and if, if that's your use case, then the in meeting dialogue is is what we recommend.

E

ah How will the behavior of meeting in teams client and in web client will they be similar.

D

uh There's gonna be some. Let me put it this way: it's not in 100 parity between desktop client and web client and in either in the next few months, we'll be working on getting parity across web and desktop, but desktop is is leading for now. Example is like anonymous user behavior, and things like that you'll see like anonymous. Users typically will join via web.

D

So there'll be some some improvements and also there'll be some and if you're, a regular user who's going to the web, there'll be some some gaps, uh but uh we, we will be eventually working on closing those gaps.

E

Okay and then what about for mobile the behavior on that? Will that be in a similar.

D

Yeah, so so mobile is also not up to parity, so in in the next few weeks or in the next yeah in the next few weeks or a couple of months, I would say there will be meeting meeting apps available on like mobile as well, but, like I said, there'll be some gap in terms of parity. So right now uh it's going to be like desktop, that's kind of coming forward and then we'll work through like parity across web and mobile. Soon.

E

All right, the recording for this will be available in the next 24 to 48 hours. We do have a series of developer community calls if you're not aware of them. You know.

A

E

Some on sharepoint powerapps, just across the whole platform, with a lot of information of crossover. um There's one last question about any plans for adding any kind of insights into the meeting. Experience that, like education, has to tell how much attendees have engaged.

D

There is thinking around it. um At least we started thinking about like providing those insights and making it like like a platform offering, but it's not available as part of our v1, offering. You should consider, like um just you know, keeping an eye out for updates via like craft apis um and then in general, like updates from like the meeting space. But it's not available as part of our v1, offering.

E

Okay, great, um I think that's it thank you to everyone for joining um and who stayed on and asked a whole bunch of questions that was awesome and to the presenters for sure. We really appreciate it. We're looking forward to sharing more community demos and samples in the coming months, and with that thanks again- and we will see you next month.

D

A

Thank you. Thank you. Everyone thank.

E