Microsoft 365 Community Office Add-ins, 9 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Office Add-ins community call-July 2020

Description

July’s call, hosted by Alex Jerabek, featured a new developer tool: the Web View Switcher for Office Add-ins; API improvements for Office Scripts and survey information about the programming languages and frameworks for developers.

Speakers: Artur Tarasenko, Sudhi Ramamurthy, Michelle Scharlock

Resources:
WebView Switcher tool https://aka.ms/AA8xhut
Office Scripts https://aka.ms/office-scripts
Take the survey https://aka.ms/oadevsurvey

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

A

Welcome everyone to the office evidence community call for July. Today, we're gonna be sharing a new developer experience tool, the web view switcher we're going to be going over. Some improvements, we've been making to the office scripts API and at the end of the call Michelle, is going to present a survey that will help us with our developer, documentation and learning experiences around office add-ins our first.

A

We received a lot of questions through our Q&A forum about the new chromium based edge webview too, so we thought we'd invite Sudhir back from last month's call to kind of go over that information real quickly to help out everyone answer those questions about when is it coming out and how they can help support the tool and test in preview, so we'll be doing that first and then we'll be going through our new web views switching tool and then the simplified model VNA in the survey.

A

We also have time for questions at the end of this presentation, or this community call we'll be answering them, but please type your questions in the chat as we go along we'll be trying to answer them as we go along and yeah. So if we do that, also keep in mind, uh please mute your microphones unless you are presenting. We are recording. This call so try to keep the audio clean for everyone all right so about further ado. I'll turn it over to two Sudhir to talk about the edge webview runtime, so Sudhir you're.

A

B

Alex yeah I'm here, okay, so just a quick recap: I talked about this last month, so we've got the new chromium based edge, webview control available with office add-ins in insiders fast. So just here are some very quick highlights about webview. It's it's based on the open source communities gonna be consistently supported across all the Windows versions. It's gonna be available for both win32 and UWP. Of course, the things that we're going that we're talking about over here is the win32 office app.

B

If you will and most importantly, this control is going to be always up to date. So that's sort of the default setting that all users who get this this control and the browser are gonna experience is that this is always up to date. It's similar to how you you'd, update, for example, chrome or other browsers out there that are available, so just a quick call to action again, based on just similar to what we did last month. So you've got that version of Office, starting with that version of Office that you see on your screen.

B

Office is gonna be using that new, but for you to control is the default run time for our add-ins in insiders fast? You will need to be part of the insiders fast channel to get this to get this build and this integration you also need to install the dev or the canary channel of the browser. So that's super super important make sure that you get that dev or canary channel.

B

Otherwise you will not get the webview control but most importantly test and validate your ad and again using webview to let us know if you have any feedback or questions or encounter or any sort of issues do. Let us know one easy and quick way to know that you're running webview is if you're running the Adhan again using webview. You should be able to right-click in the task pane or within your atom, and then you should see an option right there, the debug command that should open up the new edge web.

B

You debugging tools, so super easy to debug as well. Definitely do test that scenario as well the debugging scenario using that new debugger tool. But again, as I said, let us know if you have any feedback at all. Github is a great place to to post your questions. I'm happy to hang out over here for a few minutes as well. A few folks have any any questions. I know last community call there was a question when this would get to production.

B

You know again, we right now we're an insider's fast, we're looking to get this to production later in the fall, but but more importantly, before we get there. I want to make sure that the control is tested. All of your add-ins and scenarios are working as expected. Only then will will sort of get to get to production. Awesome.

A

Thank you so much this year and yeah just to echo that a lot of our products and our features rely on usage data before we can roll them out to general availability. So please yeah test this out, give us your feedback, we're listening, and we want to make this want to make sure you're adding to work with the new web view controller. So yeah thank everyone and Sudhir I'll be hanging out in the chat.

A

So please type any remaining questions you have there as we proceed, but for now let's go to the new web view switching tool. So our tour are you on the call? Yes.

C

I am can hear me yeah.

A

Again, thank you so much.

C

I'm, a software engineer specifically with an office platform experience and, more specifically, within the developer, experience team. You guys remember Courtney from last month, we actually work on the same team, so finally, there's an easy way to switch web views for office at in testing, which is fantastic, we're gonna jump into a demo, but these are just some simple instructions to follow along with later on. But let me go ahead and share my screen.

C

We can just start up with a pretty simple CLI and we can build up an add-in pretty quickly. You know, office I have a clicky keyword, so I apologize for that ahead of time. Let's call it demo.

C

And then we see the into here and then NPM starts and that's the sort of typical side loading steps for an added and when we open it up, I'm running I have the edge chromium installed. So when I right-click here you can see, there's the chromium drop down menu here when we close out of here and then run office, Adam.

C

Settings what you manifest.xml and adds we're able to set the webview to edge. So when we open this up, if I try right-clicking again, there's no drop-down menu. That opens up by going to here edge dev tools, I'm able to attach to this added and then, if we close out of here again, I'm going to come back into here and I run the same instruction, but instead of edge I use.

C

Ie, then we're able to come into here- and this is running with an IE if I right click here, there's the Internet Explorer drop down menu. So we're able to switch pretty fluidly between these different web views and it's a nice handy tool for testing. And then we can check the current webview setting that we have here by just running the same instruction without edge IE or any other setting.

C

And so it just tells us what we currently have and if we want to send back to whatever Depot meow you just use default and that's it.

A

Awesome, thank you, sir. So we had this slide that had the steps for is there documentation for this tool yet or is that forthcoming.

C

There actually is documentation, it's bundled together with an office added scripts. So if you go into the office, I didn't scrape Sri PO within packages and then specifically within office, I haven't added dev settings. There should be it's included within that readme I can go ahead and post a link to it in the chat, yeah.

A

That would be lovely, yeah awesome. Thank you so much art or anything else or that's it sweet. Alright, thank you and yeah. If anyone has any questions for our tour, yeah hop in the chat and we'll post a link to all the documentation, so you can try this out today and get more testing on different runtimes, alright and then we'll hand it over to so sudhi's gonna talk about the new office scripts API model, the sink API. So Sydney are you there.

D

Okay, yes hi all it's awesome, so hello, everyone, my name is sudhi I'm, a program manager in the office platform team, so today I'm very excited to talk about some new developments in office scripts for excel on the web. So in today's session, I'll be covering a very high-level recap of office scripts, which is a topic that has been covered in in this forum before and mainly walk through the improvements we have done for office scripts API in much greater detail, I'll show and run some office scripts chord and talk about office.

D

Scripts API in relation to office chair so I'm sure that that might be some question. That's that's on your mind and at the end, I'll leave you with some links for further learning in this slide, so we kind of just recapping what office crypsis office scripts, as you might know, is a new feature within Excel for web. You can now automate tasks and workflows easily and eliminate the need for repetitive steps as you create and manage Excel workbooks.

D

On your day to day basis, it gives greater control for administrators to determine, what's safe or what's not, and yet allow organizations to share and collaborate very easily. So in terms of the features you know, you can record actions that converts your interactions and changes in the workbook two types: kambei syntax, as as a script. You can then edit that scribe add your customizations or just simply run the script. You can also create a brand new script from the scratch.

D

If that's that's what you intend to do and then add your own code on top so I described in the last month demo, the script you recorded create can be also connected to other collaborative applications such as teams or email services or SharePoint using the power automation flow. So so that's really like a cool new feature that allows you to interact with other services within your organization and, finally, you can use wide array of programming features offered by the office scripts API.

D

Now, we've always strived to get the users to learn and use the programming features offered by the api's to manage their day-to-day tasks and automate. One of the keys to achieve this goal, as we think, is to make it easy to learn and and grow user skills, though the previous version which allowed users to use office shares in office scripts. You know that offered a whole range of capabilities.

D

It was bit difficult to get started with, so you needed to understand some of the advanced topics, such as how asynchronous programming works, even for basic editing capabilities. So even simple scenarios may include things like reading values or performing whether a value exists, an art or iterate over collections of things like tables or charts check if an object exists or do some error handling. So such scenarios shouldn't be hard to achieve and shouldn't require advanced knowledge for those who are closest to the business processes and workbooks and those who wish to automate manual tasks.

D

So we felt we can do better and make office scripts API easier to understand and use for those who are moving up from just recording actions to actually editing and making changes. So we wanted to make that journey of, discovering and and beginning your automation journey and be able to feel comfortable with the process much more smoother than what was so goal was really to lower the barrier for entry and get the programming interface to match the natural flow of how users think and interact with the Excel workbook.

D

So in that regard, based on our research and development, we are now introducing a simplified API version for office scripts. So it is now easier to get started and automate your tasks in office scripts by using a simplified API surface, and we go over the details of what that means, and you still get the same benefits of the previous model in terms of recording actions and using the full breadth of the api's and yet use a much simpler and modified model designed to suit both all the beginners as well as for experienced users.

D

So as with office scripts, it is now available as the primary API surface and it is available in public preview. So the main thing is the office. Clips API is, and now synchronous in nature, which means you can invoke them in a synchronous manner without having to worry about promises or callbacks. The API offers simple constructs. For instance, it has synchronous, API, getter and setters for things like property access getting and setting properties.

D

You can also invoke methods in a synchronous fashion if you are familiar with the the the object collections in the office years, so it comes with somewhat of a fairly complex structure, but here in this mode will be simplified. It so object collections are just regular, arrays and, and now we can do better error handling, because it's much easier to check if an object exists in art and so on.

D

We also added few api's that offers improved interaction. Capabilities with common excel objects that you might use, such as excel range table row and column mainly to match the dimensionality. So if you're, interacting with a cell now, we can read and set its values and formats and number formats, just as if it's a single value and the same thing with columns and and rows, and all this you'll get with the benefit of having the static type check offered by type script.

D

So we've heavily leaning on type script with this model and with that comes for a better validation and we've also worked on optimizing performance for select scenarios and then in the future. We will continue to do so to match the expectation that you interact with and if you're familiar with office jazz, you can carry forward your knowledge, which means the object model Araki matches very closely with office chairs. So in terms of the video naming conventions and and object model matches very closely and I'll talk about this towards the end of the presentation.

D

A little bit more and just to clarify before I show what the code looks like. So this simplified API model is only available in office scripts and it is not part of the add-in surface so with that and so case, the actual the scripts. So, let's look at how the actual API surface looks like so I'm going to switch over to excel on the web, and you might be familiar with the the place where you find office scripts, that is on the automate tab.

D

It comes with the record actions as well as the the code editor using, which you can now. You know browse through your existing scripts. So the simplest way to start is to just you know, start recording. So that way you have a base to start with. So here you know, let me just set the value to and I'll stop recording and I'll be able to save the scripts edited and you know either run it as is or I can improve on top of it.

D

So here, as you can see, the rapier surface has the the main function that is called when you actually run and it gets the workbook object. So workbook object is the top-level object and it has other sets of relations and hierarchy using which you can access the the rest of the object model and what the script is doing here is simply getting the active worksheet and then setting the value of range. B3 was the address and just setting its value to test. So, as you can see, the the APS are synchronous in oh.

D

That means you don't really need to handle promises or call back. So you can simply start to read and write with the objects that you're interested in. So let me do something so here: I'm, actually setting the value, the interesting scenario, so when you can actually read so, let's see if I can get to the the cell instead of setting it directly.

D

Let me just get the actual cell variable called cell and I'm gonna just set its value now like what, if I, want to get to the next cell and and set its value or check its value. So I can do that simply by calling the API is that is associated with the cell. So, let's get the offset range, I'm gonna, get keep the same row maybe go to the next column, and now I can simply leave values off of the next cell and then just use it directly.

D

So, for instance, if I want to check hey, that's the next cell actually have any value in it. So I can use that directly. In my if statement, and then I can say: okay, yes, it does have a value and I can print that value.

D

So, let's see and if not maybe I want to set its values, so I can do set value. So, as you can see, the the functions are available directly. The methods are directly available and the function is getters and setters. If you're dealing with the properties, so I can set its value to say, I'll call it next values, so I'm gonna just run this.

D

It's gonna set it to next value, so the next time it runs. Obviously you find the value and it should display the information in the output area, so the console gets displayed in the next next value gets displayed in the console. So here what I demonstrated is just the the ease with which you can get and set values without really having to worry about any asynchronous nature of api's. Next I want to showcase another script using next I wanna showcase.

D

How you can check if an object exists, an art and take actions based on that, so I'll start a new scripts as if you start a new script, you get you know a blank script and using which you can begin to just write your code. So, let's say I want to add a worksheet called index if it doesn't exist.

D

So the way to do that would be so I'm going to just get the worksheet directly off of workbook, so I'll say get worksheet, and this takes in the parameter and I'm interested in the worksheet by the name of index. So at the end of this, I should have this object and I can check if this object exists or not so I'm doing. That is as simple as saying hey does this object exist and if so I can say you know, let's say console.log.

D

Yes, the the worksheet exists, and else I can just go ahead and create it, so I can do workbook and, as I mentioned, we also have methods that performs actions like reading so such as writing up doing some updates in the document. So I'll add a worksheet the name of index and then and I I can get you sheet so once like it. So this returns the actual sheet now I can take that object and perform other methods on it.

D

So maybe you want to set its position to zero, so it shows up at the at the top of the worksheet and then I'll also.

D

I will all activated so all right, so if I run the script, obviously the first time it's gonna say yes like it exists because I do have this. So let me go ahead and remove this.

D

And I can run this again and it will create that index sheet and it'll activate and move it to position one. So with this things like object, validation and whether object exists, an art or even doing error validation becomes a lot smoother okay. So the next thing I want to show is my favorite feature, which is the ability to interact with collections with a lot of ease. So collections are things like anything that can have?

D

You know exist more than once like worksheets, they can have tables and charts and rows and columns within a table or arrange in the earlier model. Managing collections was a little bit hard because you needed to understand some of the intricacies of how the collection is organized and loading properties are acting on. It required a little bit of advanced skills. So what we made is made. We made the Excel object, collections, plain, simple arrays, so what I'm gonna do is start a new script again and in this script, I wanna achieve a couple of things.

D

So I want to first go through each of the worksheets and collect its names, and maybe I want to reorder the worksheets in the inner in the ascending order of the the sheet names. So in order to do so, office want to get the worksheet collections, so let's say I begin with: let's sheets and then workbook get worksheets. So what this returns as I can see in in the typescript intelligence is just a collection of plain worksheets. So this is just a plain array of worksheet object and because this is an array, I can do.

D

I can call the array functions or are a method such as I can map or it I can do a forage on it or I can just read its length. So let's go ahead and do that so let's say a console.log I want to just read: okay, how how many worksheets are here so I can do worksheets lengths, so I want to collect next. The names of each of the sheets, so doing so is pretty simple.

D

So, let's read names: I'm gonna be straight over sheets, so I'm gonna use map function and then for each of the sheet. I'm just gonna return its name right. So on.

D

So at the end of this, I should have I'm gonna display the names and the lint.

D

Let me make sure it works correctly: oh I'm already displaying glint.

D

So let me run this so it should display hey. You know it has four worksheets and here are the names of the worksheet and let's see if I can go ahead and reorder the worksheets in a way that suits me. So, let's shuffle this up a little bit.

D

What I'm gonna do now is take the name, so the worksheets that I have and because this is just an array, I'm gonna sort. This and I'm gonna do a for each on it. I'm gonna get the name.

D

And it's index and and then what I'm gonna do is get the workbook.

D

Of that name and so and because it's in the order so I can set the position to be the I. So.

D

I'll set the position to be I, so when I run this crib, all its gonna do is again sort this based on its name and it's gonna reorder the worksheet as you can see. So this is an example of how you can use collections. You can simply fetch. As a plain array, you can read properties off of collection using just plain regular array functions such as map of our each and then you can also call methods on the objects by simply invoking it within within the array. So this makes the collection.

D

Having you know, navigation of collection are dealing with object. Collections are much more straightforward in simpler process, so the last thing I will show is that, in addition to making it easy, we were also working on making it more performant performant optimal, and so this is. This is a work in progress, but what we have done is in cases where we are doing multiple writes and now we can perform that in a single operation and reduce the chattiness, so here's an example of a script that sets just random colors in each of the cells.

D

So if I run this, it's gonna just set each of the cells with a random color, so the name invoked wrong script.

D

Alright. So this is someone I wanted to showcase. So, as you can see, it's doing a cell level operation, it's performing cell level, but you'll see that it completed pretty fast. So, regardless of how big a range- that's a select, so let's say you know, select a much bigger range here, so this is kind of run and complete all in a single operation.

D

So this is part of our journey to make the API surface font performant by optimizing as much as we can, when you run the script, there are certain best practices that we have documented in the in our documentation site. So you can go and see beginning with the overview. There are samples that are included. There are many. A couple of detailed scenarios that you can walk through. They'll go into a lot more details and as part of this, we also have some of the things you know do's and don'ts of making your court more performant.

D

So that is just a brief introduction into what the API surface looks like and some of its core capabilities and the fact that we will continue to iterate over it and an improve it, and because this is in the previous stage. So we are very curious to hear from you and what you think of the model. So you can actually go try this out today and you can use Excel for web and show that your admin has enabled office scripts. You can go to these automated tab. I can try, recording actions, editing and running.

D

You can check out sample scripts and I'm. Gonna show you so as far as the the office scripts experience itself within the code editor, we have in build samples and we will continue to add more samples to it. But here are a couple that you can also get started with in addition to what we have in our documentation and then, if you search office, scripts you'll find our the site also available at a kms office scripts.

D

So if you have any feedback or suggestions for the new office scripts feature, please let us know we are either user voice or it can head to Stack Overflow and use the office scripts tag to ask any technical questions that you may have. If you have any, if you run into any problems, you can, you can ask questions there as well. We also have the within Excel itself.

D

There is the help improve office link and if you click and tell us what you feel or if you have any feedback or running into an issue, we'll also get to hear that as well. So we really looking forward to hearing your feedback and so because we are in public preview phase, so we want to get as much feedback and and usage as possible and make sure that we make any revisions or enhancements that that is needed while we're in the public preview.

D

So the last thing I want to mention is a let's talk about some of the questions that you may hand you in your mind, which is sort of what is the relation of the API model. The ratio case with respect to office, yes, which is the primary API surface that drives our office add-ins. So what I want to say is that office yes and office.

D

Goods have a lot of things in common, so they shared essentially the same object, hierarchy, naming conventions and error scenarios in error conditions, they're all basically the same so office just gonna drives the office scripts behind the scene. So if you're familiar with office years that familiarity and knowledge, you can use that to learn off the scripts pretty quickly because you'll be familiar with the whole structure. If you're used to using add-in development transitioning to office scripts is going to be a fairly simple process.

D

There are key differences as I described earlier, and we made those enhancements to really help with learning and development of office. Scripts users and any new API is related to excel, will surface in both the models and an office. Yes, which is an asynchronous model which gives kind of much more finer level. Control over over. Your logic will continue to drive the ad in development. So a common question that we've heard in the past when we showcase this is you know, will this be available on on the add-ins for add-in development?

D

So, right now we focused on improving the scripting experience for office scripts users. So there is no plan for taking the simplified of scripts API for office add-ins.

D

You know we would love to hear your feedback and what you, what you think this strategy might be like or if you have any kind of strong inclination of one versus the other. Let us know as part of your feedback- and we are curious to you- know, hear hear from you and once again, so the way to reach us would be through user voice.

D

You can ask questions on Stack Overflow and we do go over all the feedback that you send right from Excel online, using the help improve office link, so that I think concludes the topics that I want to cover and I'll be available for rest of the the presentation to address any other questions that you may have and if you have any time at the end, we can kind of go into the queue a more as well, but continue to ask your questions here and I'll also address offline.

C

A

Awesome, thank you see. Actually there are a couple questions that came up that might as well ask now, if you're really so there are a few questions around the relations between office, scripts and office. Add-Ins specifically, could you call one from the other and I know, that's not yet available. But what is the timeline looking like for that? But.

D

uh You mean calling the the scripts from an add-in.

A

Yeah, or vice versa, calling an add-in function from a script right.

D

Yeah, so it is something that has come up in the past as well, so it is an hour backlog or it is something we are interested in, but we don't have a timeline for it yet, so we are working on a set of features right now that are in public preview. We are iterating it and we are improving the quality, and so so it is going to be definitely beyond our kind of initial GA period. Awesome.

A

Yeah and I think for everyone who is interested in this sort of feature not only requesting it through user voice in the channel Sudi shared, but also sharing your scenario and the context for why you're looking through that really helps us, because in a lot of cases, there might be something similar you could do instead that we could help you build out that work instead of creating a whole new feature, so yeah share share your needs and your apps with us and we'll we'd love to help you design, yeah I, think that's it.

A

There were also some questions around like external calls and using REST API, and so you don't know if you know the current status of that with office scripts.

D

So the office clips right now we don't yet support the rest. Api calls so it it is something that's on our backlog. We are working through how the permission model might fit in and what sort of controls are the admins might want to have over the scripts. That is accessing external data, so the things kind of that we are interested in is hey. What does the API call to properties such as Microsoft graph would look like and how we can provide it in an integrated fashion?

D

What the authorization model would look like and how the permission model would work, so we'd still have some work to do there, both in terms of design, as well as actual engineering work. So as of now, we don't support access to things like graph.

D

But it is something we are actively looking into.

A

Wonderful, thank you, city, appreciate your time and yes, you'll be hanging out in the chat. If anyone else has any questions cool. Alright, thank you very much. So next up I'm going to share my screen again and to kind of close up the call Michelle is going to talk about a survey that we're doing to help with our documentation. So Michelle are you on the call?

A

E

I am hearing all.

A

Right, take it away very.

E

um Yeah I don't have too much to say here, but as I'm on the docs team, as Alex may have mentioned, and we're trying to uncover what tools and languages and other you know what kind of frameworks you might be using we're. Looking at our samples and snippets that we provide and we're just trying to figure out what might be the you know the best languages and frameworks, and you know, tools that we can. We can support for you to to make our Doc's even better. So it's a five question survey.

E

It shouldn't take very long just go ahead and go to a kms dev survey and you should be able to fill it out there. It's just a simple forum of five questions.

A

These sort of surveys really do help us Wever documentation and tailor to your needs that you know like the the tech role it's constantly evolving and growing, so it helps us get a pulse of where our developers are and what sort of stuff you're using whether it's you know JavaScript versus typescript or yeah, jQuery versus react or angular all that stuff. It helps us know where you're at and so much more yeah anything else. Michele, no.

E

That is it, but I think you summed it up perfectly. There.

A

Cool, thank you, flattery, all right, so that is gonna it for the heart of the call so yeah. Please take the time to fill out. That survey will repay Stu link in the chat, so it's clickable we're going to the Q&A. We've had a lot of the some great questions in the chat and we'll go over them more at throughout. We always post all the questions and answers in the follow-up blog post to this call on the developer blog, so we'll put a link to that as well.

A

These questions came in through our web forum and a lot of more around the chromium version. Imagine the new runtime webview to that. We had Sudhir talk about at the top of the call like we said we are planning to GA the new runtime later this year, but a lot of that depends on your usage and adoption. We also had questions around new PowerPoint api's and we are actively working on a new PowerPoint API set, but we don't have a release date so again, like head over to user voice.

A

Request features upload what's there and and share your scenarios with us of what you need to do and we can make this API set tailored towards your immediate needs. And then you know we have some questions about the the nuance end feature just some details about it: like can you disable male editing mode without displaying a dialogue? And today you can't, but if that is a feature, you need again request it.

A

If you would like to engage with us, if you'd like to present on an upcoming call or give us feedback on the call or a documentation, the platform anything like that, please, head over to a kms office, add-ins, engage and give us your your contact, information, your feedback, and if you want to share with us, if you're working on an add-in and want to share the details of it, your implementation, your cooling, the features and you let us know and we'd, be happy to have you on the call.

A

And if you are new to office at ins, there were some people in the chat who yeah. This is their first introduction to it. Please head over to our Doc's a tech MS office at in stocks. There we have some quick starts that'll, get you up and running with an office add-in in five minutes or less. You can also use the add-in script lab to explore these api's and how they work with the host. So you can open up Excel and have a little mini add-in that edits the workbook.

A

You can also start using office scripts that is in public preview today and I believe the new API improvements that Sue you were talking about are 100% rolled out to everyone or coming soon so head over to ms-office script stocks and take the tutorials there to start recording and using scripts. Today he will post them these links than chat or we'll post the slides after this as well. If you're looking to learn, we have our script lab the documentation.

A

We also have the Developer Program, so you can get an office, 365, Pro, sorry, Microsoft, 365, tenet and start testing out on a build of office. Your add-ins, your development needs start using power automate with office scripts and please engage with us on Stack, Overflow and github user voice. All that stuff. You know we're.

A

Looking there we're happy to answer all your questions so yeah, and then we also have other mt 365 developer community calls across the board, so four teams graph sharepoint all that again these links will be sharing the blog but head over to the other calls this month for whatever your developer interests are, and that will end the call. So thank you so much for joining us. Our next call is august 12th at 8 a.m. Pacific, Daylight Time join us next month. Submit your questions ahead of time, we'll get them answered for the call.

A

Thank you so much. Everyone have a great rest of your day.