Microsoft 365 Community Graph, 9 Nov 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Microsoft Graph community call-November 2020

Description

This month, we featured topics including a Microsoft Graph + gRPC.net sample and Microsoft Graph Toolkit updates.
Speakers: Christo Matskas, Elise Yang

For more information, visit https://graph.microsoft.com

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

A

Good morning, good afternoon, good evening, wherever you may be calling in from welcome everybody, this is the microsoft graph community call for november of 2020.. Today, we've got some great presentations that will be taking place first, one's going to be on microsoft, graph and grpc.net from our very own crystal semesters and second will be a microsoft graph toolkit from elise yang, so some great topics for us to cover today again our agenda for the items we have here.

A

One quick thing we do want to make a call out for before we actually get into our presentations.

A

If you are interested in presenting on the microsoft graph community call, we are looking for speakers always open to any kind of submissions. If you are looking to present a couple things just to kind of call out for things you can include in an email would be the solution that you're looking to present on or the topic area. What are the graph apis that you'll be calling and any other kind of platforms or services that might be involved in this?

A

Sometimes I see people mixing together graph with azure server lists or with power platform or other kind of things, I'm just going to get a good feel for what all has encompassed in the solution that you'd um like to talk about. So if you are interested feel free to reach out to myself, brian.jacket microsoft.com, as well as jeremy, fake, jeremy.fake microsoft.com feel free to write those down um shoot us over any kind of submissions, we'll review them and get back in touch with you.

A

If it's something that sounds like a uh a good inclusion for our community calls, and with that, I will turn it over to christos, and you can present on jp with microsoft graph.

B

Sure, thank you. So I work as a developer advocate for the microsoft identity. So we sit inside at nt and we talk.

A

About all things, identity, identity,.

B

And this includes btc azrae d and also graph. We tend to uh to do more end-to-end scenarios as possible. So rather than just talking about the identity component or the health component, we try to educate people about how they can build end-to-end solutions, which is usually something that we lack across documentation and samples. So if you find gaps feel free to reach out to us, I also host with uh jp my partner in crime at twitch stream. Every monday and friday we go on the four to five show for two or three hours.

B

Every time we have guests sometimes and we build things live. So if you are a developer interested in how you can indicate identity in your solutions, whether you're, using azure or aws, or on-prem or google cloud, as long as there's an identity component as long as it's a graph component, we're more than happy to show that so we built lots of different things, uh feel free to check us out. It's usually around 8 a.m, pacific time and we love talking developers having you as well.

B

So if you have something interesting that you build graph or azure id or b2c, then reach out to us, we love to showcase your solutions and see what exciting stuff you're building. So today, I'm going to be uh covering identity for developers. um The the latest stuff that we I'm going to be covering is around.net, and we had two major announcements in that space.

B

First of all, it's the adel to amsel uh change. So uh I don't know if you heard the news but adel the older library that we used to have for the microsoft identity platform is being deprecated, so, as of june 30th, 2022 adele will be out of support. So one of the things that we always talk about- and we want to highlight- is that if you are using the microsoft platform today to grab tokens and speak to other services like graph and what have you you need to make sure that you start the migration process.

B

If you have any issues or if you need support, please feel free to reach out to us to help you with the migration to amsoil, because amstel comes with all the goodness of the v2 endpoints and it's a lot more advanced than ada, and we want to make sure that you're compliant and up to date, the second big announcement in the dot net space is around the microsoft identity.web, which is the new library designed for asp.net core apps and wraps around through the amstel library, and helps you with all the things that have to do with authenticating users grabbing their tokens and speaking to other services.

B

So in the past there were multiple libraries, especially if you were in the asmr space you had to authenticate users and that was usually using the es net identity system. So, even though you were using azure id behind the scenes, there was a different system to authenticate users and then, if you wanted to speak to other services like graph or your azure, storage or other other services or other apis, you had to go and download amsoil, which made things a little bit confusing.

B

uh It was also defaulting to azure id v1 endpoints, which was also uh something that we wanted to avoid and getting tokens monitoring tokens was always confusing. Now, if you were creating apis, there was an additional complexity. On top of that, because you had to manage the middleware for the your jwt tokens had to also work out how to do on behalf of so it was always complex.

B

So what we try to do is create a a single library that abstracts all the complexities, gives you one line: solutions to integrate, authentication, one line, solutions to a pool graph, one line, solutions to implement cases, and it hides all the complexity.

B

You still have the capacity to obviously look into, or hook into, specific events in the middleware if you want to, but for most part and for most developers the 90 of those developers out there, they just want to integrate with the identity solution and move on. So with that microsoft attended web is a great solution so for people that are wondering where that library sits.

B

Obviously, microsoft android web is the new solution it gave back in september, so you can go and download the latest and you get packages and add them to your ace and the core solutions and, as you can see, all the individual components that you had to work in the past are still there are still hidden behind the scenes. So you don't have to worry about that, uh but also surface them.

B

So if, if but if the default settings or if the default functionality in identical web does not fit your needs, you can always go and look into how you can create custom, cookie, authentication or extended jwt barrier authentication. And what have you so from our perspective we're up around themselves? We hide the complexities in the dotnet space and we make working with the identity system and graph super straight straightforward.

B

So, in the uh on the left-hand side, you can see how the old code used to be for asp.net. I don't know how many dot net developers we have on the call and apologies if you're, not a dot net developer. But the good news is that if you like what you see here, especially on the right hand, side, then you can let us know, and we can start working on making java and javascript and python libraries that we have for amsoil work in a very similar manner where we abstract a lot of the complexities.

B

So if you find this exciting every time I speak to dotnet developers, they jump with joy at the end of the presentation, because we take away a lot of the code. We hide it behind the scenes, so you don't have to worry about these things. So if you like it- and you say- oh my god- I wish I could do the same with javascript or typescript or java. Then this is the the opportunity for you to speak out and let us know we're always open to feedback.

B

So in the left-hand side, there's a little bit more code, there's uh there. There are specific events that you need to tap in, especially for classes or have you and on the right-hand side you can see we abstracted everything behind a single line of code for most of the components.

B

So you can easily add authentication, you can easily add the ability to acquire tokens and call other apis and we're following best practices around.net. So everything is happening in the middleware. Everything is happening through the the standard injection of services and registering those services and injecting them into controllers. So you don't have to you know, follow a different pattern than everything else. So authentication becomes one of these components that should be fairly easy to implement securely and correctly using the new library- and I think talking- is cheap and showing actual demos.

B

It adds a lot more value. So since I'm in the developer advocacy team I like to play around with different solutions and since microsoft attended web has been a lot in the discussions lately. What better opportunity for me to try and test how I can use it with grpc. So if you haven't used grpc or if you don't know what grpc is it's a it's an open standard that allows for low level communication between services?

B

So it's a way for us to write very low level services with very low latency and super fast performance, and it is an open standard.

B

So we we thought: how can we integrate grpc with net so there's a grpc.net version that allows you to write grpc services using csrp and net, and since it's running on top of the asp.net core component, I was like well that's a great opportunity for me to see how I can break it and see if I can add microsoft ident.web there, because it would be great and then I didn't want just to do authentication since it's a service. I wanted to call into graph so on this demo today.

B

I will walk you through the process of how this uh this was implemented, and there are a few things I have changed since I I wrote the the the demo in particular the fact that one of the limitations of grpc is that it couldn't run as a web service. So it runs as a service that you can speak to directly via http 2, but you couldn't host it in inside a web app. Now we have the ability to actually host it inside azure web apps or you can host it as an actual asp.net service.

B

So, even though it was running on top of ace net, it was not accessible via a browser, but now we made it available via browser, so the demo I'm going to be using is uh is going to actually, let's let's reach the demo rather than me talking about it. Let me show you what it does so here.

B

Let me make this bigger, so everybody can see it and if you have any questions, feel free to interrupt me. I'm interruptible, while I'm discussing this, so we have two two components here: we have the grpc, client and grpc service.

B

So first, let's go to the grpc service.

B

We'll open this in your code, you can use visual studio as well. You don't have to use visually your code just because I'm using it anything that supports dot net, if I can do it in notepad, if you want to that's the beauty of face in the core, so let's open this one, let's go through uh the code implementation.

B

What did I have to do to add authentication to my grpc service? So every call that comes in needs to have a better token that calls the service. In fact, let's start with the necessary libraries, so we have the grpc asp.net core, which is the library that wraps around the grpc service and allows us to work in net. We have the microsoft ident.web, which provides the integration for the authentication and then down here, you'll notice. We have a new package called microsoft, identity, web microsoft graph.

B

This is a new new gear package that allows us to easily integrate graph into asp.net, it's not specific to to just grpc. So if you are, writing estimate core apps today, you can call you can add this library for graph and we made it a separate package because some people might say well, I don't use graph. I don't have all that overhead in my identity, library, which makes perfect sense, but if you want to use it, there's an extra packet so with these two packages here this is all we need for the authentication.

B

Now, if we go into uh program, there's nothing here. So that's the the vanilla asp.net core middleware! That starts the program and in here uh this is where the magic takes place, and let me just make this even a little bit bigger. uh So we have uh services at grpc, so this asp.net middleware only deals with grpc. We don't have any views or anything else that can show user or users can interact with. So it's a service, then we're adding the microsoft web api authentication, because this is a service.

B

So it's more like an api and because we want to call graph you'll see that we have a single line here. That says, enable token acquisition to call downstream apis. That means that any call that comes in has to be authenticated, and then the middleware will make sure that we also acquire the necessary tokens. So we can go and speak into our graph. So this is the graph over here.

B

This is the one that ejects the microsoft graph client into our middleware, and we can call it later and I'll show you how to do it and then, finally, down here we're adding a cast, because we don't because, since we're calling graph on behalf of the incoming call, we don't want to be going back to us ready every single time to validate our token. So it will cache it for us and then down here.

B

We need to ensure that we add our authentication, so an incoming call needs to go through the authentication pipeline and validate that the user is authenticated.

B

Now, a little bit of a side note here, for when you work with grpc, you need to define the contract.

B

Grpc has this kind of a strongly typed contract between the client and the service, and they both need to abide to the same contract. So if I change things here, I also need to change them in my client, and this is what what, in effect exposes the api interface to the clients and dot net core has built around this protofile. This is the the open standard. The grpc standard has built the the support for compiling services that can uh work around this grpc.

B

If you ever done, um I know um all the services like w uh like whistle. uh If you generate apis from json or from back in the day wcf, then this is a similar kind of functionality where we create clients at the back or services. At the back of the protofile, and here we have a calendar request, which means that uh well, this is pretty basic, but what I'm saying is that a call will come with a calendar request passing a name.

B

This is the name here and then the response will include a calendar reply which will have the subject body start and end dates of the of my calendar item from graph. So this is very basic and just builds around the calendar api on the graph. So I have a service which wraps around the functionality.

B

This implements the uh the graph call. I have a required scope, which is the expected scope that needs to be passed into my graph api you'll notice that here I'm injecting the graph service client. This is available to me via the middleware through this line. I'll go back here.

B

Let me just go here, so this add micrograph injects or makes available my graph client via dependency ejection. So I can inject my graph client instance here I don't have to pass any authentication, headers or whatever and then the magic of verifying that the user has the right scopes happens here. This is part of the microsoft attendant web.

B

If you've ever had to validate tokens, if you ever had to make sure that the incoming call has the right claims back in the old days, you had to write about 20 25 lines of code that has all been hidden away for you and it does it with a one-liner.

B

So it's super exciting super easy for me to validate my tokens and if, if I had the required scope, which I passed up here, access as user, then as long as I have the right scope, then I can execute the call- and you can see here we're actually getting the get my events and select a specific subset of the data I want to ground back and then we're creating a calendar reply. This calendar reply is what the protofile defines here.

B

So that's a strongly typed object that has been created at the back of the profile and then I return that back and we can actually run this and then I will show you what the client does on on the other end. So, let's, uh let's open the terminal, let's call dotnet run.

B

This is how you can execute.

B

Calls you can also use the debugger here if you want to uh to do that, and while this is happening, I'm going to switch to my client now the consumer of the grpc service.

B

So uh cd there's the client and I'll open this in different instances of the code, so right here, you'll see that the middleware has kicked off and it's running and it's listening at port 5001 for the service. Now, let's go back to our client and see how the client has been implemented.

B

So this is a console, app, very basic. It could be a website. It could be a different service, anything that can actually call into that. I made it a console because it's a quick and dirty, I know not the best way to showcase stuff, but it is what it is now. Something important here is that we're actually setting the same protofile so somewhere. Here I am passing the protofile.

B

Now you know what I think: it's in the in the cs: projects file yep so down here. I am pointing my protobuf into the same proto now I could have copied that file across, but it makes changes harder because I have to copy the file all the time. This is the the piece of code that instructs the grpc service in dot net to actually go and create the strongly typed objects and to work with and also have the grpc tools again, the grpc client factory and the protobuf.

B

These are the standard, uh grpc components and then down here, I've added uh microsoft, ident decline. So because this is a console app, we cannot use microsoft at the input web. So we need to rely on amsoil to do the authentication for us and for that I'm using microsoft.ndecline, which is the client library for authenticating guest azure ad inside my codes. It's a one file. So let's hide this. For now we have the everything is happening in maine, because I'm lazy- and this is not the best design.

B

But what we do here is we use device code authentication so um we'll use this flow to authenticate the console app we'll grab the token and then we are going to call create a channel to our grpc service and then we're creating um this graph. Client. Sorry for the bad naming here, but this graph client is the grpc graph client, not the actual graph client they get from the graph sdk and that confused me as well, because I named things badly.

B

So the graph client is the grpc service and then I'm I'm actually adding the authorization header here, because I need to make an author authenticated call. The token is the one I acquired from emsal and then I'm making a calendar request and we're waiting for the grpc service to come back and give us the response, and then in here I'm just writing things down. So, let's, uh let's go and run this and see it in.

B

B

So this should kick off our uh our call. As you can see down here, it already said you need to authenticate first before you can use the the app so I'm going to click on this one follow the link.

B

So there you go, let's close this one down there, you go I'll, add the code. I think I used oh no. What happened the request, I guess, did not match the user context.

B

Is it because I had an authenticated user already? Let me see, I might need to clear my class sorry, but I tested the demo the other day, so it was working. Fine.

B

Next, come on, don't embarrass me in front of my audience! Thank you.

B

Okay, so we signed in and then when we come back there you go. Let me just make this bigger. The grpc call has executed. It found two calendar events with a start date of that and start uh end date of this. I think it's only one right now, monday morning, meeting there you go so you could have enumerated all the calls ahead, and uh this is it if I go back to my other instance of vs code, you'll see that the call has executed here. So we got the http request post to the endpoint.

B

It grabbed the token and validated token it it made everything correctly and then it turned it back with executing the right endpoint in grpc and coming back. So uh this is it a few lines of code to implement authentication into end. I think, overall, I didn't write more than uh I think the grpc component was more complex than anything else.

B

The authentication code and the call to to graph were all done with maybe five lines of code, so uh it's super easy with microsoft attended web to get started, but it doesn't mean that this is the only right way. As long as you use our libraries or any open id connect library and grab the access token, it's easy to call services.

B

One of the questions I get is: why should I use grpc over say a web api or say an api build with functions? There are some added benefits with grpc. First of all, it's super modern and super fast. It provides to strongly typing services and clients. So it's easy to generate those uh out of the protobuf files, and I think that the fact that it operates at a much lower level than uh standard um apis means that you get much faster performance. So that's that's one way to create services. Modern services these days.

B

So if you haven't used the grpc before, then I would urge you to have a look at that that it's fully supported in this netcore microsoft, android web, makes your life so much easier and hopefully uh working out of this you'll be able to grab that information start implementing your own fun stuff. Are there any questions.

A

Feel free to put your messages.

B

Into the chat window or.

A

If you want to come off mute, you can also do so. One question I did have for you is: I saw that you did the include in your project file in the client. Does that mean that you update the server side that you then need to rebuild the client to be in lock stuck with that yeah.

B

You need to do a dotnet build as part of the process now when you do.net run on the local machine always builds first before it runs. But if you change the, if you change the protofile to include other things here, then obviously you'll need to add the necessary code. So if I, if I were to add, say a team api component, like I don't know get status or user status or uh presence, then I would need to get a presence request and a present response.

B

And then I will need to extend the services and the clients to include the necessary code.

A

So for like a production deployment, though, you'd be okay to roll up the server side, changes before the client side or what, if you had like conflicting changes in there.

B

Sorry I didn't answer the question.

A

So I'm just curious like most times, if you're adding things to the server side, you're, okay, because the client doesn't even know about those things, but right what? If you were like, let's say taking away some properties or you know making a breaking change on the server side.

A

How would you make sure you roll that up to the client so that they have like in lock, step the same, updated version with the server side.

B

Right, so uh you need to make sure that uh both the client and the service look at the same profile right, because this is what defines the contract. So as long as your client points the same profile, that's why that's? Why? In this instance, I'm setting the same location for the file, so I only have one file, which is the single source of truth for everything that file can leave anywhere. It doesn't have to live inside your solution.

B

Obviously it makes it easier if it's inside the solution, but if you have a, if you have like five different clients that speak to the same product service, then, uh ideally you need to find a way to share that file across all the clients and the services yeah I see daryl is on the call thanks for uh timing in sir, I I think there's a blog post as well that accompanies these and we made the source code available on github.

B

So if you want me to share those links, I'll be more than happy if people want to see how they can build their own stuff with grpc and graph, then everything I have here is available online for other people to look at so hopefully I'll be useful.

A

Yeah, if there's no other questions, um thank you so much for your time today. This is a great demonstration presentation really appreciate you coming on today. Thanks for having me all right with that uh elise you're up next, would you like to present from your machine.

C

Yes, let me present hi, I'm elise yang, and I am the pm for microsoft, graph toolkit.

C

So today I wanted to show you the design specs, that we have for three new components that our team is looking to add to the toolkit and get your feedback on our implementation and and pick any questions or thoughts that you have on our design.

C

So if you're not familiar with the toolkit, yet the toolkit provides a library of components and helpers that allow you to integrate with microsoft graph super easily and quickly. And if you want to quickly learn more, then I would suggest going to our playground.mgt.gov.

C

So for these three new components, they're all using the onedrive and sharepoint apis to allow you to integrate files, experiences into your apps super quickly, and these components are kind of like our first step towards creating files components. So right now we're focused mainly on enabling the basic rendering of files as well as file selection.

C

So this is the first component that we have. This is our basic file component and it allows you to retrieve and render a file from the sign in users sharepoint or onedrive.

C

So this implementation is very similar to how our person component in the toolkit works today, you're able to specify the file that you want to get from graph by a couple of ways.

C

You can either provide the full query to the file like in this first example here or you can provide a combination of identifiers, for example like you could provide the drive id and the item id or the site id and the item id and the component will like compose the request and send it to graph and then, as a developer, you have control over how the file is rendered and what it looks like in your application.

C

So you can use the view attribute or property to determine like if you want to show just the name of the file or if you want to show additional properties and show either one line or up to two lines of text.

C

You also have the flexibility to set the properties that are shown in the rendering, so you can set line one property and line two property with the details. That's returned by the drive item resource and the next component that we have is the file list component so similar to how our person and then our people components work together. This does the same where the file list component is using our file components to show a list of files.

C

So similarly, you can also specify either the full query to a drive or a site or folder that you want to show the list of files from or you could also specify an insight type. So if you wanted to show the files that are most relevant to the signed in user, you can specify either trending used or shared as the insight type and the component will retrieve the list of files from using the insights api on graph and only show the files that are relevant to that user.

C

And yet you have the flexibility to control how many files are shown. So if you wanted to show only like the top five trending files for that user, you could easily do that and then the default for this component, if no identifiers or any queries provided, will be to show the user's route to drive.

C

And then the last component is file picker. So this kind of provides a very basic file. Picking experience for the signed in user it'll have a button with a drop down that shows a file list with the option of the user clicking see all which will kind of open up more full-fledged file. Picker experience, that's similar to the react, picker control or the pnp file, picker control.

C

So, similarly to the file list, you can specify either the drive or the site or folder that you want to show a list of files to pick from or you could specify an insight type. So if you wanted to show the user's most recently used files so that they could select it and do something else with it, you would provide like the recently used insight type and you can also enable or disable multi-select and as developer, you can access the files that the user has selected with the selected files object.

A

At least we have one question from the chat window on here.

C

Yeah, I can take that now.

A

Sure so from uh I think this is the file list. Control uh offer is asking about what about filtering for files? Is that supported with um this control?.

C

So filtering, I think you you would be able to do it if you use the full query and you provide like the odata filter, query and filter that way.

A

Okay, excellent.

C

Yeah, so those are the three components that we are thinking of adding right now we have them the full specs open as issues in our repository, so we can provide feedback there and also see kind of like the full list of what attributes and properties we're proposing to add, as well as other functionality and our repository is at aka mgt.

C

And if anyone has feedback questions thoughts, I would love to hear those now.

A

One question I did have was, I believe, on the mgt file component. You were talking about uh you had site id and list item in there is that using the sharepoint uh ids or is that using the onedrive files ids.

C

Are you talking about here in these examples.

A

C

A

You can prove that you're supported.

C

Yeah so, depending on what like, if you provide the developed device drive id, then we would build the ur the request towards onedrive and then, if it's, if the site id is provided, then we would send it to sharepoint.

A

Gotcha, okay, I missed the distinction between those two and do you happen to have these things in the uh mgt, dev uh playground or because they're still uh in preview they're? Not there yet.

C

So these are just like our proposed designs and we wanted to get some feedback from the community and developers before we actually go and implement this. So right now, it's not in the playground, but if you go to the issues, this is how we are kind of looking to collect.

C

C

So here in this issue, we have the full spec with all the supportive functionality, some examples of how it would be used all the attributes and properties that are available, the apis and permissions that will be used and yeah. If you don't have any questions or feedback now, but think of them later, then you could leave a comment on this issue and we will get back to you. There.

A

You get the first format for the 703 and then you can link to the uh 74705.

C

Yeah they're all linked, so you should be able to find them pretty easily.

A

All right, if no additional questions or feedback, um thank you, elise. So much for your time. This is great to see with the graph toolkit and adding in more support for new components. I know we've seen a lot of requests for people to expand this once they've gotten a chance to play with ngt.

C

A

Excellent all right at this point, um we've got about 10 minutes or so for open forum. So if you have any questions related to microsoft, graph graph toolkit any other services uh related to microsoft, graph feel free to raise your hand, put your questions into the chat window and we'll see if we can address any of those uh today on our call.

A

Andreas has looks like a question here: um returns just the file or also the display url like in the teams files.

D

Yeah, what's for at least because, let's say uh it happened to us, we built the same uis like at least and when you, when you have the file, you have to decide what you do with the user. You want to send him to a proper formatted ui and let's say when you want to send him to teams, you want to send him into a chat window with the file and not into the sharepoint url. That was a question.

C

So you want to send the url to the file and not just the file.

D

Let's say when you have a file picker, the question is: what is the next action? Do you want to download the file or do you want to work with the file yeah so to work with the file, because somebody selected it? You would like to have a the best looking ui that office 365 offers, and that could be some sharepoint that could be sometimes teams files.

C

Yeah, so right now for the kind of like our v1 of this component, um when the user selects a file it'll be added to the file, the selected files object and then ask developer what to do from that file from there so like. If you wanted to build additional functionality to do something with that file.

C

That would be up to you as a developer.

A

And I think to add a little context to um under this question, it's kind of around the nature of deep linking to files through just working with customers and partners.

A

We've seen scenarios where you can get back like the web url for a sure file, but if you want a deep link to it inside of teams or the way that teams represents that url, I don't believe we expose that as a property or something else on graph today, there's been a couple of requests for that like I want to get the display view or what's what's the url to get to it inside of another client. Is that correct andreas.

D

Yes, that's that's correct because let's say when, when you work with the graph api, people want to to do similar things and they're doing the normal client.

C

Yeah, so right now we are looking at like we'll, only be able to use what's exposed by drive item in graph. So if that's not yet exposed by the onedrive and sharepoint apis, then we wouldn't be able to add that functionality. Yet.

A

And I believe we have this as an open um feature request to the sharepoint onedrive folks, I'm not sure about on the team side. Maybe if you have anything to comment on that same thing, on the team side, we have it as a feature request. um There's some andres and.

D

I have been talking about this for some time right now and um we have um a meeting schedule actually we're working on the scheduling meeting next week with some of the pms that are actually working on this great.

A

uh Question from vincent around microsoft, q, a versus stack overflow, um so for those who are not aware stack, overflow is not a much of a property. Basically, it's a third party that we host a lot of our questions on so across all of the m365 kind of ecosystem, um open and available for people ask questions. There is a separate site that we're developing almost to replace the technet forums, msdn forums of days past and it's called microsoft. Q, a the azure team and a few others have already onboarded to microsoft.

A

Q, a but not all other teams are currently there yet uh one of the improvements that we're going to get by going too much of q a is because we own the platform, but we will actually have private conversations.

A

So a lot of times when a question gets raised, it's a hey, can you go and look at you know my tenant, or can you go and look at this specific? You know piece of my code or some kind of sample and it's on stack overflow.

A

We can't actually share those kinds of um confidential secrets or or things because it's not our platform um when we do get to microsoft, q, a though that will be a way for us to actually say hey here's the question we can actually dive into a private chat with whoever the requester is or commenter be able to kind of you know, share those pii kind of things and not be violating any kind of data. uh You know privacy kind of things.

A

So to date we do not yet have the microsoft graph category on microsoft, q a um but look for some announcements for that in the coming months, we'll have more to share once we get into the new year and more stuff has been onboarded question from brandon. How far along is support for managing b2c users and their strong auth methods in microsoft, graph api that will actually be part of our um identity. uh Azure id team we'll take that one as a uh a follow-up to bring up with our identity and security.

A

Folks, because, even though we are all microsoft graph, there are kind of subdivisions in terms of who manages which requests and so forth. So uh sahil's asking app credential flow requires a call to a server-based app to graph. Can you explain a little bit further on that one sahil?

A

Just in general, you would not necessarily require to have a server-based application for that you could make a application credential flow, so basically not a delegated user flow, but a application permission one. Those are support for doing from eight clients. So if you happen to have you know, console application or your workstation, you could run the flow from a non-server machine and in that sense you would have access to you know securely encrypting, a secret or having a certificate for your authentication mechanism for it.

A

So it would not be a hard requirement to go to a server based application, for that, I think, is what you're getting to. But if you can provide any more details into the chat window or come off you please do so all right. If you want to feel free to follow up with us afterwards that we can get some more information on that tyler's asking about. We can get intermediate 404s on known active users when my application queries on behalf of a user when reading mail from a mailbox. The first call will succeed.

A

Second, we'll go to four or four third will succeed. Anyone's experience this behavior that sounds so it'd be helpful. If we had like a request id and a timestamp to actually see what the queries were. Usually, when you get a 404, that's going to be like a couldn't find the resource, so I would check to see: do you have the correct format or the correct user that you're querying into um just to make sure that those kind of things are actually finding the resources that it should be?

A

But if you want to follow up afterwards see if we can actually track down what the specific nature of those four or fours are the probably something we take offline and I see alan and nuke are both pointing over to the uh docs. Yes, so if you happen to deep search into it, there is preview support on the q a platform, but we're not fully. You know publicly announced on that, so didn't want to share too many details just yet, but if you happen to search for it, you will find something out there.

A

Any other feedback comments, or even things that you'd like to see in future community calls feel free to put into the chat window and see if we can get presenters or any other kind of topics like that included on our agendas, if nothing further, we'll finish up with our last couple of slides around things out today, if you're interested in joining the microsoft graph tap, this is a program that our customer partner experience team does run.

A

As part of this, you gain benefits like we're having a monthly tap call where we do uh cover nda kind of material. So, if you're looking for kind of the previews of what is coming with microsoft graph and all that kind of related services, uh very much appreciated for folks join into this, you can find the link down at the bottom aka.msgraphtap form we review submissions on usually a weekly basis or so and we'll get back to you, based on reviews of those things.

A

Other developer community calls to be aware of. We do have a number of them related to microsoft, 365., uh there's a bunch of links on the top of the page. Here you want to get to the kind of one-stop shop for them. Aka.Ms m365 dev calls and you can find links to many different ones, whether it's depth of cards, graph, identity teams, powerapps and so forth. A lot of great content gets covered in a monthly basis, also calling out our very own jeremy fake, who presents with our other friend paul shafeline mvp.

A

They talk about a lot of different topics related to m365. Recently, we've had things on publisher verification, microsoft, to do power, platform and so forth, so feel free to join into the podcast and listen in on new and exciting developments in english. Five, we will be hosting the recording for this on our youtube channel. Aka.Ms m265 dev youtube feel free to find that on there, and just a note for our next uh community call will be taking place on december 1st 8 o'clock a.m.

A

Pacific time more details to follow with that, as we near that date and with that we'll wrap up the recording, I do see a couple of additional questions in the chat and we'll answer those after our session cook was here today. So once again, thank you. Everyone for joining into our november 2020 myself craft community, call thanks so much for your participation. Your questions uh very helpful for us to have all that. So with that, thank you and have a good day. We'll see you guys soon.