Collaborate on Invoice Example Excel for Administration with Ease Using airSlate SignNow

Invoice example excel for Administration

[Music] all right good morning everybody or good afternoon or good evening wherever you are from the world uh Welcome to our SharePoint embedded for Azure developer session we've got three speakers here today to walk you through all things SharePoint embedded oneon-one for Azure developers we've got Steve Plick yoga shap Parky and Reed carberg to walk you through our agenda today all right thanks kalissa uh hey everyone good morning good afternoon good evening uh I get the honor of kicking this off today so I'm going to walk you through a quick overview and demo we're going to talk about the core Innovation behind SharePoint embedded and then Steve is going to take over and uh teach you how to get started in 15 minutes or less yoges is going to come in and talk more about co-pilots and agents we have some really exciting news there uh Steve is going to come back and talk about security and compliance everybody's favorite subjects which are absolutely key to succeeding with an Enterprise app as we all know and then we'll uh talk about some next steps and handle some Q&A so with that I I really want to kick off with a very high level of why we're here because we have some new and interesting things to talk about first of all Azure today provides robust storage capabilities if you're an Azure developer you're used to working with these they're great options for you uh structured data typically goes into something like SQL Server this is something I'm sure you're all familiar with and unstructured data is usually going of course into Azure blob store and what we're here to talk about today is a new new storage option that's specifically designed for a different kind of data we call this data collaborative data and so typically these are files and documents that you would store inside an M365 tenant and SharePoint embedded is a new way for you to do that collaborative data has some very interesting characteristics when you look at it you know number one it tends to be active data as compared to data which is static so it's data that you're working on in some way it also tends to be interactive you know in addition to not being static it is data which is changing and you're modifying it usually with other people often in a multiplayer environment uh it needs to be co-pilot ready these are typically things that you want to do uh rag operations on or you want to use llm to inspect and understand and of course these need to be private trusted and compliant so this type of data is key to Enterprise apps of all kinds and often you're going to see this as Word Excel or PowerPoint files uh it can also be video it can be PDFs and of course it can be things like Json or jpeg now although I call out these file formats it's important to note that collaborative data is not limited to these kind of formats now when you think about use cases for something like SharePoint embedded uh there are a lot of different use cases that we're discovering as we talk to our customers we've been GA since May at build and I'll be talking more about that in just a second we're in use by companies around the world large and small for both line of business and isv apps governments are also turning out to be early adopters which uh if you have worked with governments in the past this might surprise you it also surprised me but uh people are seeing the opportunity here with this fully global Service now collaborative data requires the four seas and if you take one thing away from this session I want you to take away these four C's and so these are compliance collaboration co-pilot and core Enterprise storage and really what happens is SharePoint embedded makes it very easy for you to deliver these requirements as part of any app that you happen to be building so okay with that I want to do a quick demo so you can see this in action and get a a grounding on what it is that we're exactly talking about I'm just going to switch over to an app I have running you can see it's just running in local post I'm going to go ahead and sign in and when I sign in you'll see it's just popping up the regular Microsoft uh authentication going over to a regular tenant I'm going to Grant it some permissions and here I can do something called create a container now don't worry I'm going to get into more detail about what all this means in just a minute but if I say uh good morning Azure Developers right this will be my container name and then you can see a couple things that are happening so this is entirely apid driven there's no ux that's part of this and the API calls are just standard Microsoft graph API calls so I've gone ahead and create a container and now I can look and I can see it right here and there's a lot of things that I can do with this but I'm going to do something basic I'm going to go in and I'm going to upload a file and it's going to be something that I've created on Colorado mining history I live in Colorado I'm fascinated by mining so it's a great example you can see you get the same sort of feedback from how the API is working and if I want to now I can go ahead and edit this file so what you're seeing right here is the core magic of SharePoint embedded in action I've gone ahead and created a place to store files and documents as part of of any app I've built my own user experience for that app and now I'm using a standard Microsoft Word session in the web to go ahead and edit this so I can now say if I want to hello Azure developers right and just like word clients do everywhere it goes ahead and saves that real time okay so that's a very high level demo don't worry Steve's going to get into much more detail about how you can harness this but this is really what we're talking about here today so let me bring this back up and now we're going to talk about the core Innovation behind SharePoint embedded so if you think about SharePoint today SharePoint is already a partition service and so it lives inside the M365 storage subsystem and there's two partitions that are commonly available so these partitions are SharePoint online and one drive and so if you're used to working with these you know that there's a security boundary between them and you know that the user experiences is different and that they have different rules but at its core they're using the exact same storage subsystem and what we're introducing is this ability for you to create your own partition inside M365 and this is where a SharePoint embedded lives you interact with it just like you saw a second ago using the Microsoft graph API and it has all of the same characteristics that you're used to from anything that's stored inside the M365 stored subsystem so so SharePoint embedded is an API only headless version of SharePoint specifically designed for apps it lives inside that dedicated partition within your M365 tenant or if you're an isv it lives within your customer M365 tenant and it includes all of the M365 collaboration security and compliance capabilities that you're used to remember we were talking about those 4C's it has full integrated content management control through the SharePoint admin Center and it's also Microsoft 365 co-pilot ready it is all powered by Microsoft graph and is all delivered via consumptive apis Azure consumptive apis and of course it includes the M365 business continuity promises that you've come to expect now I did say that this was GA as of uh build so as of May and if you want to you can go ahead and uh Point your phone over at this QR code and read this later there is a fantastic FC two-minute explainer video on this that will uh help you understand at a very high level everything that SharePoint anded has to offer it's also a great way to introduce SharePoint embedded to your colleagues so I would encourage you to go ahead and bookmark this page and take a look at it now really important to note about SharePoint embedded is SharePoint embedded is the way that Microsoft is building our first-party apps today so if you think about first-party apps like designer or Loop or or co-pilot Pages those are all powered by SharePoint embedded and so when you're building with SharePoint embedded you're actually using the exact same system to build your apps that Microsoft uses to build our apps so it is all built on top of the M365 security and compliance capabilities and of course it's all living in the Microsoft cloud now I want to talk about this problem that's out there that uh I think you have probably run into over time when we started talking to people about file and document Centric apps we realized that these files and documents are actually all over the place inside a typical Enterprise so for example a finance app might have various uh accounts payable receipts or accounts receivable uh copies PDFs that kind of thing an HR app is typically going to have a bunch of information about employees maybe very sensitive personally identifying information the sales app often has customer information that's attached to it and a work management app might have any mix of this it might have a PowerPoint that people are collaborating on or it might have an Excel sheet that people are working through together and this differences all these all this uh variety of ways and places that files and documents are stored leads to tremendous complications for modern Enterprises these are fragmented and siloed systems they're very labor intensive to administer and they introduce security and compliance challenges and so what we have noticed as we start to talk to people is that there is this opportunity for a unified content platform where all of these different systems are actually storing their files and documents inside the same common system and this is where SharePoint Eda comes in and the advantage of this of course is it delivers a consistent footprint around security compliance and co-pilot capabilities and also all the content management uh different Administration and compliance requ requirements that you're going to have now one thing that's interesting and uh yoges is going to talk more about this here as he gets into co-pilot is that when you think about building an Enterprise AI app there's really you know kind of three easy steps to it you know step number one is you have to get all the data that you care about in the same place step number two is you have to make sure that that data is robustly secured via ACLS and compliance and rules and all the policies that an Enterprise need and step number three is you have to integrate that with a common set of tools that people are used to working with things like word excel and PowerPoint sound familiar it should this is where a SharePoint embedded really shines now when you think about M365 features uh I've talked about that at a very high level but this is much more detail about each one of these so the four C's are across the top co-pilot compliance collaboration core storage and if we take a look at just one of these collaboration what's really important to note is that you have full features that you would expect to have you can use both the web client and the desktop client you have full co-authoring and present support you can do full at mentions with people who have access to the document you get full sharing to internal external users and you have preview for more than 300 different file types as part of this so when I say that SharePoint embedded is a way for you to deliver robust M365 features for file and document Management in your app this is what talking about we're talking about this degree of full featured now Steve and yoges are going to go deeper on on each one of these so I'm not going to steal their Thunder but uh I do want you to really kind of take in and digest how complete this is our mission with SharePoint embedded is to enable you the app developer to build exactly the app that you want that your Enterprise customers Demand with all of the file and document F management features that you need so let's talk a little bit about how this comes together so you remember this uh slide from just a minute ago so this is uh how we're talking about the SharePoint embedded delivering a new uh partition within the M365 storage subsystem that you can interact with using Microsoft graph apis this actually gives you a new construct a completely new construct that we call SharePoint embedded containers this is a new file and document management primitive that you can now harness in your apps it's designed to be extremely lightweight quick to instantiate and highly scalable you can have more than a 100,000 of these per app and I should point out that this 100,000 limit is actually a default limit and really it's it's something that we can expand quite a bit uh and really what we mean is if you get more than 100,000 containers we want to talk to you and make sure that we're helping you architect it correctly the app has full control over the containers that it instantiates and the way to think about these containers is that you should map them to the business construct that your app is trying to address so for example uh you might have noticed on the use case wheel that we had there Professional Services is a big place where we're starting to see some early product Market fit and so for example in the Professional Services Arena specifically Legal Services most people there tend to map containers to a legal matter there's a very natural mapping that is able to OCC Ur in most of these problem domains so that a container represents a business challenge that is the focus of the app and so that's what you want to do with a container now these are also a scale unit and security boundary we'll talk more about those permissions in just a second and it's important to note that you can manage these in your SharePoint admin Center there's a new containers section uh with role-based access control and Steve's going to talk more about that as he gets into security and compliance so let's talk talk about containers for just another minute you should know that they're strongly typed they're strongly typed to whatever app has created them so if app one is out here using SharePoint embedded containers and app one has a stack of containers that it's working with only app one can access those containers by default I want to say that again only app one can access app one containers by default now it is of course possible for you to develop a microservices architecture where you maybe you have a common set of containers that are accessed by many apps but the default is that you could only have the app that created those containers managing those and so you can see that app one has its own stack app two has its own stack and app three has its own stack this is an important characteristic of SharePoint embedded uh so I want to make sure that people understand it now when you're talking about isv apps they have an additional construct which is really interesting and it's an addition way of operating really more than anything and so if you see the isv tenant over here on the left hand side of the slide they go ahead and strongly type a particular set of containers to work with their app and then when they're working with their customers whether it's customer one two or customer n there's no upper limit when they're working with their customers those customers can actually use that same strongly typed container within their M365 tenant so the core isv component that you want to take away from this is that when an isv is using SharePoint embedded it's actually interacting with containers that live in their customers M365 tenant and so they inherit their customers M365 configurations okay permissions very important now on the permissions front uh of course these apps can't just work inside any tenant the customer or the admin has to make sure to Grant each app ooth perms to work inside their tenant and this is true whether it's an isv app or an lob app we've introduced a new permission scope in graph to handle this and it's called file storage container. selected now our mission is to encapsulate all the permissions inside file storage container. selected uh there's still a couple things that we're working through so um generally speaking this works but there's a couple things that we want to do around search that are still work in progress so we should talk about that importantly you can have app only and app plus user uh permissions almost everything is uh available to app plus user and then there are several things which are available to app only construct uh when the user is sorry when the admin is actually uh granting permissions they're granting that app access to its containers and contents but it's a very narrow permission scope really it's really designed to be just for that app and its content and it's designed to not leak beyond that to be a least privileged situation now there are ways as we said before for you to Grant other apps permission to those containers and so if that's something you look you're looking for we have some rich documentation on how to do that now I want to talk for just a second about the permission model for users because one of the things that's different about SharePoint embedded is that you have a deterministic permissioning model that is doesn't inherit from anything else so at the container level you have this notion of permission roles so for example a user could be a reader a writer a manager or an owner at the container level and you can assign users or groups now likewise at a particular file or folder level you can also add permissions for users or groups there it's designed to be a very flexible sharing model so you can have uh a bunch of app specific settings including things like enabling external uh excuse me enabling external sharing or not and you can also uh make sure that you are restricting this to your app or the sharing could be outside of your app so you have a lot of flexibility there now one of the core interesting things about SharePoint embedded versus SharePoint online is that if you're used to working with SharePoint online you will probably have some experience with SharePoint online resource units and what we've done with SharePoint embedded is we've taken the highest number of uh resource units for SharePoint in online and then we've doubled them and so if you're thinking about what type of constraints you need to work within for this cloud service just like with any cloud service you actually have a substantially increased uh allocation of these resource units for every API call so again it's double the highest configuration on SharePoint online now we have two great articles on this and so if you're interested in diving in you can definitely find those and we can paste those into uh chat and comments for you as well now we often get asked this question is when to use which document management approach and uh you know it's a it's like any great architecture question you end up with this solid uh answer of it depends and so we just put three different approaches here so there's Azure blob store SharePoint online and SharePoint embedded and if you think about when Azure blob store is important uh first of all it's really important to know that it's a rock solid Cloud Object Store if you've used ABS you know this um it is outside of the M365 security and compliance boundary and so when you're thinking about what solution to choose that's a very important consideration when you're working with files and documents in an Enterprise context SharePoint online is a great option it does include the standard SharePoint online user experience it has Integrated Security say part of the SharePoint online system and it is inside the M365 security and compliance boundary it also delivers compliance for licensed M365 users so it gives you a lot of capabilities it also uh is restricts that to a license so it's a different kind of uh usage than you might have with SharePoint embedded so SharePoint embedded has partition security nothing has access to any SharePoint embedded containers unless you are specifically granting access you build your own user experience it does not include a user experience as part of it it's completely headless API only service it has very lightweight containers on the SharePoint online front there's a number of features in there that might be important to you so things like lists for example that's not something which is available as part of SharePoint embedded because SharePoint embedded is really focused on file and document management it has that dedicated resource allocation that I was talking about just a second ago so if you're building an intensive app SharePoint embedded gives you your own stack of resource units to work against and it's twice what the St the highest allocation is the highest shared allocation is across SharePoint online and this is also living inside the M365 security and compliance B boundary uh finally I want to call out that this is both separately metered and it includes collaboration capabilities for both M365 licensed users and unlicensed users people who might not have an M365 license but still need to be part of your um uh compliance capabilities sorry of your collaboration capabilities okay and I think that is it uh before we move on to Steve kalissa do we have any questions in the background that we should be answering or not yet not yet okay perfect uh well if you have questions go ahead and put them into the chat I'm going to take a pause I'm going to turn it over to my good friend Steve pelic who's going to walk you through how to get started in 15 minutes all right let me switch screens here excellent thank you Reed all right so what Reed set up is the or framed up for is the ability to create um SharePoint embedded containers and really what that is what we're going to do now for the next 15 minutes literally is I'm going to show you one slide and opposed to the 31 slides that Reed uh set us up for and then we're going to dive into specifically how to do that uh we are going to get into specifically what is the uh Visual Studio code plug-in how are we going to uh enable that within your environment and how do we use it so by the time that we're finished we will have a full fully functioning uh SharePoint embedded app registration in Azure we will have a container type that has been activated and visible in the SharePoint admin Center and we will create a container that is going to be used to upload files and interact with your applications we're going to also go through all the plumbing what was created so that from a governance perspective from an admin perspective you're comfortable and what is going to be included in that tenant and also we will uh get the postand collection and hit the container itself so that you can see that in action and how to um start to work with the API uh that we have okay so that is my one slide and I'm going to bail on the deck and we're going to get specifically into uh Visual Studio code so you'll notice that I am in Visual Studio code the first thing that we need to do is within the extensions uh simply type in SharePoint embedded and you're going to see we can't quite see your screen yet darn it I thought that oh I stopped sharing there you go and I should have just yep I got it demos everybody live demos live demos I love the live demo all right so back to the live demo uh again I am in Visual Studio code within Visual Studio code the extensions section is where we're going to focus simply search for SharePoint embedded and you will have the ability to that extension within Visual Studio code that will get you the icon on the side rail that will allow you to log into your environment so if you're playing along at home make sure that you do have that installed and it's really nothing more than just installing the the extension okay once you have the extension installed then you're going to log into your environment so this is where if your SharePoint online environment simply log in with the uh SharePoint admin or the SharePoint embedded admin so those are two roles that we're going to talk about here in a second once you're logged in you'll notice down at the bottom you're going to see the environments that we have created so I've got a number of environments that I've already created we'll dive into one of them here uh quickly so you can see the container type uh that I have created so that container type think of that as the uh collection of containers that we're going to use um for your applications So within that container type now we have the ability to see the containers now these are going to be a number of different containers that you can create to store your documents that's the heart and soul of SharePoint embedded is those containers the ability to store documents uh in those containers so that you can Surface those in your application and have users interact with those okay so what we're going to do is on the root of container types I'm going to collapse everything this is where we're going to create that trial container type uh so once we create that trial container type this is going to be active for 30 days and you can there's no subscription needed for this uh no consumption needed for this it's simply a way for you to start to kick the tires on what that needs to uh uh components that you need to create that so you notice that I clicked on that um create container type a trial container type and I'm going to type in what the name is so SP super session am and I'm going to hit go okay so now I want to create that Azure uh SharePoint embedded application app so once I click on that now was creating that ENT entra ID app so so you'll see the status of the creation progress happening uh down at the bottom right hand corner the next thing we want to do is we want to register that on our local tenant so yes we do it's opening up the consent link so this is where I'm going to grab this guy and pull it down on the window log in again with that Global administrator SharePoint administrator so that you can get access to to those permissions that were requested so Reed had mentioned that we need to get uh the file storage containers and the user profile information so this is what we're um accepting that permission or request to do have the ability to uh create that within your Azure environment and now we're going to go back to visual studio code and now it's going to continue on so now it's register ing that container type on our local tenant once that's registered again we're going to see what this has done for us automatically and it's uh successfully registered so now that we have that successfully registered I can go back to our container types I'm going to do a refresh there it's going to show up here in just a second but what happened is if we go into the SharePoint admin Center and I'm going to Gra grab that here so within the SharePoint admin Center you will notice that on the left hand side we have typical SharePoint sites and the uh uh archive sites and so forth there but we've also got that new vertical called containers and if we go into containers now we can start to see all of the containers that we have within our environment okay so right now the one that we've created not there yet but what we're going to do is we're going to go back to the container types that we have created and I'm going to expand this out and we should be seeing our demo tenant here in just a second oops okay so I am going to I'm delicately killing time here until the containers show up and let's see okay so I'm going to kill Visual Studio code really quick I'm going to fire that guy up again and we're going to reconnect just to make sure that we have no latency because of the screen sharing okay so back to my visual studio SharePoint Eda plugin going to go ahead and sign into my account so I'm going to get prompted for my credential so again this is where I'm going to have my username password there uh signing in as again that Global administrator or the um SharePoint admin okay great so now you can see that my new container type called s super session has been created but I don't have any containers in it yet so what I'm going to do is I'm going to right Mouse click on the containers and I'm going to hit that create container and again I'm going to go up to the visual studio code command bar type in what I want that name of the container to be and it's going to create that container for me automatically once that's created it's going to get refreshed and we're going to see that in our containers option within Visual Studio code but as I go back to SharePoint admin Center I'm going to do a Refresh on this guy now and within my active containers I'm going to see my SharePoint embedded app and here is my my SharePoint am session so now we have that been created once we have that created now we can start to interact with it but the first thing we need to do is create uh permission so that users can get access to that container so if I simply in the admin Center click on that container that I want to Grant permissions to you'll see we've got a bit of overview on what the metrics are for the container but I'm going to go in and I'm going to add an owner to that container so now I'm going to go into the gal the global access list or entra ID I'm going to find that person that has uh the ability to be the owner of that container and now I've been added there if I go back I can start to see and add more people based on what role they want to play Within the uh container itself also if I go to settings you'll notice that I can also set that sensitivity label so we can do that here in a minute from a compliance perspective on uh what sensitivity labels have been published in perview and how we can use that but then if I go back you can see that now I've got my um owner that's been assigned to that container and they have the ability again to add files do anything that they want to um for that container all right so that is the nuts bolts of creating that container and container type but you'll notice that if I go back back to the visual studio code we're going to refresh that and while that's refreshing what we're going to do is let's take a look at what it actually created so from a admin perspective yes we can see that it's in the SharePoint admin Center and all those fine and well there but if we go into Azure there's a few more things that we need to uh focus on when a container type is created under the hood it also creates the app registration in Azure so you'll notice that I'm going to sort this by today and here's the one that we just created so the SharePoint embedded app if I go into that app registration a few key things that we want to identify here from an authentication perspective this is where we are going to put in um any redirects that your application may use so when we get into Postman here in a second this is where it's going to authorize that call back and you'll be able to authenticate properly within your application certificates and secrets so this is the secret that you're going to use within your application so when you create that client secret and we haven't created one yet that is going to be critical so the client ID and the client secret are what you're going to use in your application to authenticate get that so that you can start to interact with that uh container and last but not least is the API permissions so Reed had touched on this a little bit this is where the file storage container that's selected is going to be uh a configured both with delegated and application permissions okay so we'll we'll dive into that here in just a bit also important to know that we need to Grant uh admin access for those and you'll notice that the Visual Studio code plugin did that for us as well okay all right so the last thing that we need to do is we need to create that client secret so you can go into the Azure app registration and do that or I'm going to go back to visual studio code and you'll notice that now within that container that we've created I can create that app registration okay so if I right Mouse click here I can go to credentials and I can generate that new client secret I can generate a new self-signed search and so forth so if I generate that secret it's created that secret so that's all fine and dandy now I can copy the secret okay so it's going to save it to your clipboard so if we copy that secret make sure that you store that safe place obviously because when we go into your application if you go into Postman we're going to need that client ID and the client secret to authenticate properly we're going to see that here in about 30 seconds okay the next thing you can do is you can set up that Postman collection so this is where you can download a preconfigured postman environment it has all the environment it has all the uh workspace that you need in there to um authenticate through so let's go there really quick and if I go into see Postman is here okay so when you download that Postman collection you're going to get an environment very similar to what we have here so in the environment you're going to have predefined variables on how you're going to authenticate into uh your app or your container type that we just created the most important ones are that client ID and that client secret again those are going to be in Visual Studio code that you can copy those once you have those copied into your environment you'll notice that we have that SharePoint embedded container first thing we want to do is authenticate through so you go to the authentication tab again client ID client secret you hit that generate new it's going to authenticate you with the global admin the SharePoint admin or the owner that you have put into that container type that's the that we're after okay so I'm going to use that it's going to store that in my environment and now I can simply start to work with the graph API and hit that container type so you'll notice that container type is going to be a variable that you're going to want to store but now you can start to see what are all the containers that are in there oh live demos Okay so one more time here and then I will call it yep I selected the wrong person proceed with that use that I'm going to go back I'm going to list that containers and the she blows okay so now I'm getting the graph response that lists all the containers that are in my environment for that container type that we created and now you know we won't exhaust all of the commands that are going be used within your application but those are um the ultimate where we want to be and how we get there easy enough within Visual Studio code use the plugin create that trial container type um when we get to creating a standard container type there's some other Powershell scripts and graph apis that we can use to do that but this gets you going within you know the last that probably took more than my 15 minutes here but now you have an environment that you can start start to create within your application upload the documents and start to get familiar with that API uh that will Propel your application to success okay all right so with that I'm going to hand it back over to Reed and we were going to continue on here hey this is great so you know Steve before we go on I have one question for you uh first of all uh I love live demos I love everything about live demos even when they go a little bit wrong so uh I was glad to see that uh you know the uh security worked if you log in as Microsoft you don't see it if you log in as the uh appropriate user you see everything just fine that's great now when you started off with this you made the choice to demo the SharePoint admin Center and add an owner that kind of thing is that something that every user always has to do or is that also available via API yeah excellent question so within the API you'll notice that I have the ability to create a new container does what you think it does right so if I create that container then in the body it's going to ask me two questions what's the display name and what's that description that's going to uh be used in the display within SharePoint admin Center okay um if we wanted to create permissions on that container again another API call you'll look at the body of that and now you have the ability to determine what role they want to play and that user principal name so remember um that person on microsoft.com or a tenant user is going to be used there or an M365 Group whatever preference you want there but again two ways of doing it if you're apid driven which this is an API application and platform great there's an API to do that know that from a SharePoint admin Center there's some functionality coming there um if you're an admin not quite comfortable with the API still ways of accomplishing it there excellent so this is really goes to show the depth of uh the capabilities for SharePoint embedded across both API services and more traditional admin Services um and it also shows the different ways that uh API permissions can work so we talked about app only or app plus delegated and in app only it does not automatically set the owner and app plus user the delegated it does automatically set the owner to whoever created it so it really is an interesting flexible system for Developers okay now that go ahead that that's going to be really important too Reed when we get to talking about purview in the audit log on why delegated permissions are going to be there I'll hold that little teaser for a few minutes how's that perfect foreshadowing the mark of a quality webinar a quality super session all right with that I want to invite yoges to the stage here yoges do you want to take over sharing and uh teach us a little bit about co-pilot and agents absolutely Reed so thank you for setting up the stage and building the context on how to build applications on SharePoint embedded so my name is yogesh and I will show you how you can bring the power of co-pilot within your SharePoint embedded applications we believe that every app will be an AI app and what we also believe that this is the opportunity for us to truly Empower our end users and our customers to do really really great things and Enterprise AI is that place where we can we can deliver real values to the end users so let's take an example of an Enterprise AI app contoso audit is a software as a service they have built their application on Sher embedded they've harnessed the power of Microsoft 365 with the collaborative compliant storage enabled with Shon embedded now they want to embed a smart agent that will help the audit professionals to serve their customers and clients more effectively so they need this agent to reason over the relevant knowledge and there are three things that an application developer needs to build such an agent the first thing is that the agent need to scope the responses from the AI to the client's case so the relevancy is really the key here the second thing is the cited information and knowledge must be scoped to what the user has access to so the responses need to be permission aware and and the third thing is as the models are working on this data the developer wants to make sure that this data does not go outside of the compliant boundaries right so the data needs to stay within the customer's tendency and we speak with a lot of customers and partners every day and we see this across all of our customers across different sectors whether it's legal audit finance and Healthcare the common theme we see here is the need to empower the end users by harnessing the power of co-pilot power of Agents but ground them on collaborative compliant data and make sure that the application AI promises the customers compliance needs so that's a common need to enable compliant AI to our customers and in users and what we believe is the next generation of AI apps require a new type of document management system Reed mentioned how there's a need to have a unified content platform and there is yet another need to make this work for AI scenarios so if you think about a typical Enterprise application they have three types of data one is the structured data this includes transactions and records and then there is unstructured data whether it's logs and images and other storage and then the third one which is the unstructured collaborative data this includes the files and documents we believe that we have a really strong solution within Azure for the structured data or unstructured non-collaborative data if you will for the unstructured collaborative data including office dogs the AI application have some unique needs they obviously need to be rag ready they needs to be enabled for retrieval augmented generation to make the AI responses contextual and relevant but they also need to be compliant as Reed mentioned the block storage is is a solid storage for your unstructured data but it stays outside the M365 compon compant boundaries so having not just the files but also the semantic index which is part of the knowledge now within the compliant boundary of the customer is really important the third thing is the application needs to have full scope over this knowledge that way it can make it relevant based on what the user is trying to seek with AI responses and last but not least these responses need to be permission aware we often see app developers building their own permission layer on top of their AI application and while that works great in the short term it's not really sustainable to keep up with all the compliant needs that are um that kind of grow as your application skills to different customers and that's where share embedder comes in as you build your applications you need a middle layer that checks all the boxes for building an Enterprise AI application as red mentioned the containers in SharePoint embedded are already part of the Microsoft 365 tency so you get all the foundational Enterprise AI needs including the compliant boundary the responsible AI but you get this amazing middle layer which is application scoped it is permission aware and it is semantical index and with her SDK which I'll show you through a quick demo you also get the uux part of it with an outof boox agent SDK you can plug a co-pilot like like chat experience within your application the thing is the same same data layer or or this middle layer is also enabling our first party agents so co-pilot Pages declarative agents Loop agents these are just some of the examples of how they were leveraging the power of a SharePoint embedded to enable compliant and collaborative AI within their applications that way they don't have to worry about about the underlying needs for a compliant AI whether it's your app or our first party app they can now focus on the user experience the custom skills the vertical knowledge and eventually even their own models so let's see this to a quick demo of how you can plug a co-pilot agent within your application with just a few lines of code so let me switch screens and bring you to the demo screen right making sure my application has not timed out okay it looks good all right so what you're looking at is a sample application I built on top of SharePoint embedded so this application is went for tax professionals to serve their Enterprise tax customers and this application is organized around a tax year so I created a container for 2024 tax year as a tax professional I'll be helping with my customers for this tax year and I have curated a set of documents and if you if you want to think about all the knowledge that is required for me to serve my customer whether it's the latest regulation s or the customer specific data that's all stays within this particular container it this gives me a secure uh security boundary for my application now this is a standard SharePoint embedded application but what you see on the right side is an agent this agent helps me to serve my clients even more effectively because now I can harness the power of co-pilot to reason over this knowledge you will not notice that it looks like co-pilot but it is rebranded to your application so you'll see that the title says tax agents there are certain starter prompts that help me get started and the tone of the chat is also said to being a tax professional which I can do through a few lines of code that I'll show so let me type uh a simple question here so summarize tax changes for employers so what it is doing here it is reasoning over data within this particular container because I have set the scope to be this application and this SDK lets you choose the scope you could narrow it down to a single file a folder a container or a set of container you could set the scope to all the containers within your application dynamically based on your need you will notice that the agent has summarized the response based on my query and it used the knowledge within this particular container so there is a citation here which is really key for Enterprise AI application because users need to know the evidence on where this data came from right so this is really powerful when delivering True Value to the end user like we discussed I can also use some Advanced skills here so I could say uh tabularize this these changes with respect to 2023 so I'm going to call with my client and I want to quickly inform them on what has changed this year versus the last one all right so uh looks like there is something wrong with my live demo but you can see that you can it can tabularize the responses here now enabling this agent Within your SharePoint embeded application is really easy so let me take you to take you to the visual studio code base on how easy it is to bring that so switching screens one more time then trying to find my visual studio code here so Steve showed you the extension for SharePoint embedded and once you have a container you can load a sample app and this sample app will let [Music] you get the SDK that you need to um I think my container yeah so when you load the sample app you also get an SDK here that can easily plug the agent that you just saw with just a few lines of code so this chat control lets you set a few basic properties so first thing you get to set a data uh so first you need to set the authorization context here and then you get to set the data control so remember that you need to provide the scope for your application all right now I get the right one so here you get to set the Au provider and then set all the notifications and events that you need for this Au and then you get to set the data sources for your uh chat control so that you can hone the responses based on a particular file or a set of containers okay Switching back to the the content here it's really easy for you to enable this uh control within your application right uh you get to set the zero prompts you can set the data sources and then you are ready to enable this Scope Pilot experience within your application so how does this really work so if you think about Microsoft 365 go pilot there are really three steps that go into responding to the users's query the first step is to pre-process the query that we get from the user to make sure that this query is appropriate for the user and the user has access to even asking this kind of question so there's kind of a pre-processing that goes here then you send this query to the llm where there is also an REI check that happens and and then the third step is where it does the grounding so the citation that you saw during the demo this is where it checks if the user has access to this particular data and it uses graph to make sure uh the access rights here and this is where SharePoint embedded comes in because SharePoint embedded is already part of that graph so all the vector embeddings and the security trimming is done for the SharePoint embedded just like it is done for SharePoint as well and you can utilize this functionality today it's in preview you can enable this control with the SDK that you just show that you just saw and you can dynamically contextualize your co-pilot agent responses within your application so there is a link that you can use to start learning about this control and has all the instructions to get started now what you saw is is a part of our MVP so this is a procode SDK that lets you plug an agent within your application as we expand we see a world where you get a full spectrum of this agent experience so we believe in enabling a low code experience as well where you could use copilot Studio to choose shareon embedded as your knowledge source and publish it to your application which could work for many scenarios where you don't need a dynamic setting of your scope and on the right side we we envision a proc code more advanced configuration using co-pilot SDK or agent SDK where you can use multiple sources not just SharePoint embedded for your unstructured collaborate data but also blend that with structured data and metadata and many other sources that make a meaningful experience for your end user and all of these will be offered through a consumptive billing model just like we do for the core share point embedded uh platform so today we are in public preview uh we are in private preview and we are targeting to go to public preview next year with apis and consumptive billing and then we plan to go ga towards the uh towards the later half of next uh semester and then later half of the year we plan to extend this functionality with with Advanced functionalities using co-pilot studio and Azure AI Studio so to wrap this what what we advise our customers or developers who are exploring this is to make it real to use this SDK to build something show it to your customers stakeholders and seek to add real value experimentation is the key when building this AI application so build something but also take the feedback to iterate your road map and lastly we are here to help you we want to collaborate with you to build truly amazing AI applications to get started today here's the link and reach out to us if you have any questions hey y g that's great thank you so much for uh walking us through all that you know one of the things that really stands out to me and I'm curious your experience because you've talked to so many customers about this at this point is as you look at the complexity of doing all this from scratch the vector database trying to figure out compliance trying to make sure the stuff isn't you know like overly broad what kind of what kind of feedback do you get from customers when they hear that you can actually just kind of do this integrated with SharePoint embedded yeah so that's a really good question uh first thing is the the scoping of it right that the scoping as I mentioned is one of the most important part of it and when they learned that the user can only access the data that they have access to I think that relieves them a lot I think that that's one of the feedback or question we get the second part is about the billing so I talked about the consumptive billing that's something that we are planning to launch next year and that is a big big part of their application uh design because they need to build such that they optimize the s and you know what the cost of it is if it's an isv then you know who they should send the bill to should they take the cost and include it as part of their subscription and if it is a line of business you know is it going to be part of the co-pilot licenses or you know if it is consumed to you you know what kind of consumptive billing it is going to be so those are kind of the other next set of questions that we get and the next the third one which is more common is around programmatic access so what we have today is a chat-based experience and many of our customers need a more flexible access to co-pilot so the API part is another thing and that has all all informed our road map as you saw earlier right yeah got it okay that's great so I'm hearing that you know customers love the convenience of having everything together and they look forward to us being able to provide the same flexibility around uh co-pilot with SP as we do with the rest of SP and the Microsoft graph apis that's what I'm hearing is that sound about right that's exactly right that's awesome well this is great to see and I'm excited now to turn it back over to uh my good friend Steve to talk about uh collaboration security compliance all of these things which really help make this real uh Steve you ready to walk us through this next step yes sir all right so I'm going to reshare and we should have my deck now and let me get these fun faces out of the way great all right so what we're going to focus on now darn it I hit that wrong button again okay that delete button and the maximize button are just too close right okay all right so what we're going to focus on is uh collaboration and compliance and we're going to break that down into a number of different aspects first of all is the collaboration aspects that you get within the SharePoint embedded uh environment and Reed alluded to this um pretty early on with regards to within your application focus on the business logic of your application right don't focus on the storage of documents yes we need to store the documents we're going to store those in containers that we talked about earlier but this office integration this is what customers this is what users expect is when I open up an Office document I want the full office experience and getting that is oh it could be a little challenging if you're um using some addin components or um other uh third-party application uh plugins and so forth but it doesn't really meet the need of what users are looking for again what is that full uh office experience in your application and that's what we're going to dive into now is what we're talking about is true collaboration co-authoring the ability to at mention people comments Version Control sharing all the good stuff that is in that office experience that you get within the application and it's going to be super simple uh for you as developers to incorporate that all right so I'm going to uh bail out of the deck quickly and we are going to get into what does that look like all righty what I have created is a power app that will allow us to interact with the uh SharePoint embedded environment so you'll notice a reed had a react or an application that he created you had a react component um I've got a power app all of the again bring your own interface into the uh solution that you want to use is fantastic you'll see the containers that I have created but if I go to the files portion now you can see I have the ability to select what container I want to use and I see the documents that are in that container from a development perspective the only thing that the user is going to do is click on that link so when I click on that link it's going to open that document in the office experience um so we're going to let that pop here in a second and a Word document is a Word document is a Word document and you'll notice that hey this is the full office experience we have uh the ability to um do at mentioning share the document if we wanted to open this in the client experience we can open it in the client's experience as well okay so from a user perspective that's all they're doing they're simply clicking on the document they're going about their collaboration needs as they normally would okay um so that is that that's huge um no configuration required on your part but let's take a deeper look into how that works so I'm going to go back to postman really quick and I'm going to go in and get some files so if I use the list items graph API call you'll notice that now I have to supply what's the container that I want to use and when I go and execute that call you'll notice that I'm going to get a laundry list of all the files and folders that are in that container but what I'm focusing on is this web URL attribute okay so you'll notice that the web Ur URL attribute is everything that you as a developer needs to uh incorporate that into your application okay so just wrap that through a hyperlink put it on the page and all is well okay so that is the um focus that you're going to want to use to incorporate that in from the collaboration experience okay you also have the ability there's another API call that you can go and call for the Version Control so here I've got version history that I've included in the application a simple graph response pulls that back and includes that into um your application so use that as you need to when you save that documents so I'm going to go back in here really quick and collaborate on the document invite you know 100 of your best friends to do the same thing all is well you'll notice that there's Autos saving happening just as you would suspect so that's going to save it back to the container uh create those versions if it's a version uh event but if I go to the location so some people are going to get smart and they're going to say well wait a second I can go in the back door and I can see the content of that library right well if I click on that particular item you'll see that now I have an access Deni error uh so again no direct access to the container or the contents it's all sealed meaning that you need to interact with that through the graph calls that you're going to use in your application but know that all of the functionality of saving that back to U the container versioning all that happens automatically as well okay all right so I'm going to proceed on a little bit further and talk about sensitivity labels So within this document so now we're getting into the purview in the compliance portion of it meaning that you have the uh Co governance set up within your environment you've got sensitivity labels deployed you've got the configuration that you're using with multiple data sources so this could include SharePoint one drive uh teams anywhere that you can apply sensitivity label there's some governance folks that have determined what those sensitivity labels are um what the configuration should be and how they should be applied uh we have a white paper that Microsoft has published on how we deployed those we'll make sure that you have that but from our perspective notice that if I go to that sensitivity label icon within word I have that highly confidential sensitivity label that's been applied okay so SharePoint embedded again respects the document respects that sensitivity label and allows you to apply it um to that particular document all right so let's back into this really quick and I'm not going to drain everything within sensitivity labels but what I want to do is I want to show you when I created that sensitivity label and I hit the edit button here we are going to go in and we have the ability to control a lot of different aspects one of those aspects is how do we want people to share and collaborate with that document so when I create that sensitivity label the one thing that I want to make sure that I enable is that files and other data assets so that includes SharePoint and SharePoint embedded okay and you'll also see that the group and sites SharePoint sites and if we look really close at what that URL was when we pulled it out of that Postman response kind of looks and feels like a SharePoint URL so which it kind of is okay so that's where we are starting to focus on SharePoint sites in this case and this is going to be relevant here for a couple other examples that we talk about in a second just for clearity I put on some uh controlling access who can view the labels and content marking uh so on content marking uh we can put highly classified on the watermarks or header of the document whatever the case is there but now comes the important part which is where I can assign permissions to this particular uh sensitivity label that we're going to apply in this case the permissions that I have configured and I can choose which users and groups and all the fun stuff that have within your organization um but in this case I kept it pretty simple but I assigned that viewer permissions okay so if I am in a specific group then those viewer permissions are going to apply and we're going to see that work here in just a second okay so that is um how you would start to configure what the uh permissions are for that particular sensitivity label and again I added some water marking on top of the header here so that it's very visible to what that looks like so it stands out gets some people noticed right that's all I've done with this sensitivity label I published that and if I go back into another user okay so here's another user that has diminished privileges so I've logged in in a private browser with another user I'm back to my files uh container or by project documents container and if I click on that project governance template now it's going to take a little different look and feel words going to come up as we would suspect but what I have the ability to do is severely limited I put in viewer permissions that's what I expect the user to do is view that document so you'll see my highly confidential sensitivity label highly confidential based on what I had put in for a watermark in that sensitivity label um appears on the document great I'm going to go and I'm going to try and share this um so I'm going to put in an external email address right it's going to resolve all is good but hey I can't send that okay so now it's using the configuration of that sensitivity label and saying wait a second This is highly confidential that this can't go out to external folks okay again demonst ating that SharePoint embedded honors the content of the document it honors the settings of the document as we can see from that sensitivity label so another