Uncategorized

>> Great, hi, everyone. Happy last day of build Thank you for joining us. Today we are going to be talking About developing custom connectors for microsoft flow I’m tessa palmer. >> I’m — >> We have a ton of great content and interesting demos Before we get started who has heard of a custom connector Before? great. Good audience How many have built a custom connector before? Okay, legs. We will do a few things We will give you an over view. Which will start at the Beginning, explain the products. Hopefully you’re familiar We will do a quick run through. We will show you how to build a Connector and how easy it is. We will build a connect in a few Minutes and use it. Then we will go into the flow of Architecture. Showing you how it works under The covers. Then get into the advanced Connector concepts. We will have time for questions At the end. If you can hold until the end, Unless it’s absolutely urgent. Okay Starting off we have the business application platform That of course power apps and microsoft flow are part Of. It includes power apps bi What are powers apps again? many are family hrar if you have Used our connecteders Sometimes people use something more than another It’s about building low or no co Business applications. The applications can be used on Mobile devices or on the winners Flow — web. Flow is about connecting Automated work flows. You can do a series of trans Transformations all automated without code with our visual Designer. We have a web in mobile Experience for flows. Even though power bi is not in The tight to day it’s part of the business application platform It’s focused on self service business analytics Even though we’re not showing how to build a connector Specifically for power bi. We have connector platform Across the suite as well. We’re still the right people There was a session on monday that talked more about that as well Keep that in mind if you’re interested. We will spend most of our time On flow and power apps today. So, what is a connector? Many have use aid connector and the folks building them are more familiar It’s a wrapper or a proxy that interacts between the praod ubgts So between flow and power apps and the back end service or data source It allows the communication between the two translating Between flow to the back end and then voice verse a Sidney has a great picture later we will see So, the connection — connectors Can access from cloud and premise We moe there is a wide variety in the cloud and services you Use today there is a lot especially enterprise data Sources on premise. You can connect to them through Products with the on premise tkpwat a — data gateway Because of the way we interact with the connectors each user Will be signed a user access Because of that the under lining permissions are also respected You’re not working around Anything with the connectors. We have over 00 connecters to day They’re a wide range of sources and vert calls and all of these different things You can see from the number of colors on the screen how many Different source that’s we connect to We don’t connect to them all. If you have a service or a — Something you want to see in flow this is where our custom Connectors come in. To to define it a little bit the Public connectors, are those available to all users Those are out of box. You go to Flow .. Microsoft.Come there is a list of connectors or Public connectors if we have to qualify them The custom connect erdz are those that are build by someone In the organization or yourself in your organization

They can be exposed to just you, a kwrup of people or your tenant As well. We have some that are exposed to All users of microsoft. They’re internal services So, before i show you how to build a connector maybe context On why you want to build a connector or have to build a connector We split this into two sections. One is enterprise developers The typical reason they build connectors is either a, in the Large list of sources we support it does haven’t the one critical Source that you need to get your work done So, that’s kind of the first case where people come to it Even if the source is had it may not have the features that you need The second is if you look for connectivity to a custom or Internal service. This is something you have build Or organization uses internally Sid know will show a great demo of that as well The other case is for partners or Isrv — isv. They want to provide Accessibility and end points to their customers We have a full partner program we work with partners owning Their apis. And Released as public connectors So, typical life cycle flow of building a custom connector you Start with developing. I will show how easy it is to Build that connector definition You can import from existing artifacts you may have If you use opener en api or postman collections or something For example you can start from there instead of from scratch You make sure the connector works. We have basic test capabilities In the portal. Of course you have the products To show you the end to end testing. You can share it Again with custom connectors you can share to a group of people Or within your organization. The last step if you’re looking At building a public connector you could all of the same first things You build test share and you certify At that point you send it to microsoft We validate it on the functional size and have the -Bgs experience as well. We then release the connector to All of our users. On that we will hop into Building a connector So, here i am within flow. Hopefully this is familiar to Most folks. If you go knot gear you will see The option for custom connectors. It’s the same option from power Apps and azure logic apps if you’re familiar You may of come to this experience in a few different ways I don’t have any custom connectors. If i create one it will prompt Me to provide artifacts i may have If i have an open api fold hosted or locally i can use that Or a postman collection. I have a postman collection, i Think that’s the fastest way to go 0-60 with the connectors We will build a quick connector against the github api You all have access to that and it’s very well documented So we will create a connector that let’s you submit a bug So, i will go over here. Create an issue It gives you the path of how you post on the api to create a Bug. So coming back over to postman i Set the verb correctly. Start choosing my url You can see i have done this before The nice thing about github it’s already parameterized the path For me. That’s important. When this is a connector in flow You want your user to provide you don’t want it hard coded This is a way to do this, through parameters I will provide my values. The next step is Authentication. Github is very well documented And easy to sign up. Postman actually let’s me hook This up through postman as well. The last bit to create a bug Provide information about the bug. Switching back over to the Documentation there is an example here All i have to do is copy and paste this. We will just simplify a bit for Our case today and hit saved. Just like that you can see the

Response is out and it came back to create a bug So this point my postman collection the operation looks pretty good I will save it give it a nice name. Will you see why in just a second Create a new issue. We will create what is called a Postman collection this. Is a concept within postman We leverage it to make it easier to build a connector out of Box. Github built demo to 18 Create that -frbgs save it and i will export the collection I export it to a folder i remember Now i switch back over to flow. I snow it’s ready for the Postman collection. Spent time building it It’s quick to come back into this experience Really start building my connector now I will give it a title Let’s see build 2018. Find the collection It’s on my desk top >> You can see it’s imported This is one of the things that wasn’t important We set it now. We support authentication If you choose this you will see a variety of providers supported Including github this. Is where depending on the source You connect to your authentication maybe special I will copy over the client id and client Secrets github has told me about the Things to provide here and i will head to the definition this Is where the information i have provided and saved in the Postman collection. Giving it lecture time and a Thrice name it helped me now when i’m building my connector I can see it has prepopulated as well what the request looks like Including the parameters, owner, repository and the body i Provided. I will add a a response You know you can use the data that comes back, especially if It’s well structured and predefined into sub sequent Steps as well. Defining the response is quite important I will copy that straight out from postman and hit import Now you can see it is parted out The response and puts in the individual feelings. I can use in my subsequent work flows I will create a connector. I import this. Define security Clean it up on the definition side. I can hit create a bit earlier And i have a connector within the environment i share I will go back a few steps. I will up load an i con What is a demo without a good icon as well Again this is totally optional. Providing a nice experience and Then it will stand out a bit when we use it within flow and Power apps. Great, we will update that Once it confirms i will also show quickly we have a test tab, As i mentioned. Imagine you’re building a connector You have different operations and want a quick way to make Sure they work. This test tab can be helpful I will go straight into the product and show you where it Shows up there. Flipping over to the new tab i’m In my flow. I choose create from blank I’m going to choose a streuger to show how it could be set up Within a flow. Kwepb it could be any trigger At this point my connector is showing up along side the other Public connectors. If i search for it quickly you Can see it’s not yet showing up That’s typically because it takes time for the connector That you want to create to register fully. >> If i test it did for example In the test pane i may of seen it said, hold on we’re still Prepare t-fplgt i can also choose to create a connection From this experience similar to any connector where you can go Within flow directly or you can go outside through the Connect creation experience I will go back here to the flow and do this one, one more time And again even though i’m creating this in flow will you

See this same connector. The same connections i am Creating will show up in power apps as well My bright pink connector. The action i Built create an issue It will prompt me to sign in. I hit authorize Now it’s giving me the option to go actually create an issue I switch over to github quickly. I have one open issue created in postman I will create another one. I will give it a Description. At this point it’s worth calling Out the parameter names are pretty raw I just imported it this. Is the difference between you Building something to test out and you building something to Share this. Is where it would split Out. I will save it and test If i used another trigger like e mailing i could send a mail to Trig they are. I will see the flow ran successfully What i provided will now show up in github Pretty cool. I created it so fast and proved It was working. I will also show how to work it In power apps really quickly. Again the way it works in power Apps is the same as any other connector. It shows up along side the Existing connectors as in flow. That will also happen in power In the maker portal i open my gear. I have a list of custom connectors It’s the same one. I can edit anything here It will work vice versa in flow. Remember what you build has more Benefits across the full platform You have to build one and the connector can show up everywhere And work everywhere. As this power app is loading i Have one to use the fields. This is to use the same Operation, in flow n a power app Again getting double the value for this one connector that i Built. And imported So really basic. This app and i’m going to close That one. Don’t allow Let’s see if we just tie it to a new data source So zooming in a little bit. I just have a button and two Text input fields. What i do is go and add a data Source. Let me remove this old one And add in a new one. Let’s guess it’s the top one We will find out pretty sure how this works So, when you’re using things like posts and power apps you Need to tie it to an action. A button is an example of this This is the same for all connectors It just happens that the way we’re using it, you know, It’s — this is a custom connector now It could be any connector you’re using as well So i provide the parameters. I can could things again in Power apps like tie parameters to user inputs So instead of this being hard coded i put it as the output, The text field from my first input Same thing with the body it’s text input one Hundrederscore one dot text. >> If you look to build a Connector but are not familiar with power apps The tutorials you can leverage for your connectors as well Now with this auto complete it looks good I can say new bug from power Apps awesome description again and hit submit Fingers crossed. There was something with the Connections before hands. In theory it looks to be submitted I refresh again. We don’t have a bug In theory that’s where the bug would show up when we hit submit Invoking the function. You can see it hit a issue You can see the issue coming up there comes directly back from Github. It didn’t successfully create a One it’s going through my same connector returning error Messages from the service. With that i will switch back over As a recap within a few minutes we were able to create a postman Collection and up load to create a connector Then use the same connector in solve and accomplish quickly

Quick note. You is a hi a sad parameter name And no description. Once you build this for yourself And partner take time for names You want a few gets for each application. If you build a connector, Specifically with more scenarios of flow in mind you can use what We call dynamic values and schema Makes the user experience ritcher, drop downs and that Type of thing. For work flow automation, Triggers are important. You can use web hooks when you Add the parameters these work in power apps. You just don’t have the capability I would say my create one operation but wouldn’t see a Trigger about a new bug. Depend depending on the clients You will see the capabilities. Now to the advance stuff >> Awesome. That was a cool demo Within five minutes we had a connector running It was usable in power apps. How does this work What is happening? >> i will tell but that in detail So, you have on one side power apps flow and the business Application platform. On the other side you have Restful apis. They can be on premises or Cloud. You may notice in the custom Connector ui you have a check box. I want to call out custom Connector supports on data gateway as well The apis have to be restful Even on premise. You have those two things on Either sides and then custom connectors are the bridges in The middle Where do the connectors sit. We said it’s a proxy type Wrapper that sits in a hosting environment. That is owned by microsoft All connectors custom or not sit in a hosting environment You get the same sort of experience if, you know, either You use a public connector or Custom connector the Interactions happens — this is a little interesting to learn About. Let me tell you more about That. For power apps or flow to make a Call or execute a operation you need to have Three basic building blobs You need to know the connector name You need to know the operation you want to run In tessa’s case it was the github connector and create bug Operation. Timely you need a connection id The connection id is a reference to the credentials used to Provide — perform the operation. This is what know and power apps see When you create a kuft on connector what really happens is We take the open api description Of the restful api and traps form it so it describes this Wrapper we have created as well So again flow and power apps never call or direct to your Services. Once the building blocks are Provided it all goes through. This information is Transformed. The lines are actually directly related Kofrpger id tells me what the host Does. Operation tells me the path to use Conk id tells me the credentials to use You may have one anonymously authenticated We a cent phi which user is making what calls to power apps Using the connection as well. Connection has like some Overloaded concepts Yes, this is the tpupdment alz of how kofrpgers Work. Then here the api responds and The custom connector responds back to flow or power

Apps. This is for flexibility in terms Of not requiring all to have — apis The other piece is this allows us to have a more secure Environment. Your credentials never leak off The clients Yes, this is how it works at a high level In the previous demo we connected to a existing Service. If i’m a organizational Developer i may not want an exquisite service I may want dass a in my organization but what if it’s Not exposed to apis. Another example is a want to off load hroplg i can I have have a power app to up load images to a blog I want to expose that to everyone in my organization So you may want to build custom connectors for these scenarios Right. You set up a web service itself That does this logic You can call it a micro service as well You can set it up for assure functions and Assure web sites — azure >> This is important. We are talking about existing Apis and those internal ones. You think what is in my ecosystem You this the other platforms and services we mentioned like Functions or the web api he will show today you can build and Kind of build a service that can still interact with flow and do Some significantly more powerful things then what we do in the Product native way Yes the mess message still is this unlocks the customizations And capabilities you want in the power apps and Work flow. There is a common saying there Is an app for. That not for business applications With that i jump into showing you how to build your own web Api. For this specific first demo i Will show You mike microsoft flow power apps I will use this and create a custom connector for it and use It in the product with. That let’s jump over to the Demo. Going back here and typing in my Password alright So i have this web api set up. It’s super easy to create All i have done is taken the boilerplate. Web api you can create through The templates right. I go on file New project. Create web api That’s it. This is what you get out of the Box. Then i change the value from Value one to value two. After this demo it’s value one And value two. I have changed them What is this api do? nothing really, nothing fancy it Has values that return these strings There is another one that Returns if you get a individual value for the post puts and Deletes they’re you can implemented, right Nothing really fancy see If i go to this page you can see it’s deployed to build Right. So it’s live Working and deployed. Then if i go over here No judgment in what products you use She likes postman. I like Fiddler. Yes, if i go to my composure and Execute a request You can see i’m doing this here. Right When i execute this it comes back with two hundred The values right here. I can use this to create a connector Right. So, we can again go through the process

We’re good on time. I will go Here. Actually i will jump out of Here. I will create a new one from Blank. So build real demo >> This is great. I started from the console and Definition it’s built for me. He will go from scrap and copy It in and see how easy that is as well >> Memorizing hex code that’s great. No 001122 >> Yes. Here is the connect on premise Data gateway that i early talked about. You can create a connector that Works through your on premises apis In the host section i have some things copies here We’re including or providing the host you want to connect too We have no authentication on the connector now We are going to keep using not. Then i will start add a new Action. It’s called get values >> You can see on the left and right there is val digs He’s writing from scratch. There is a warning The ui will guide you there building from scratch as well. >> If i start with a lower case It will tell me you should use an upper case >> That’s not functional requirements It’s more for the user experience sharing these things >> Right. Now i will import the request this Is pretty, this is straight forward I ask to fiddler. Match that It’s a get operation I will copy this and again you can copy from fiddler as well It’s just hard tore get it from here So, i will go back to that. You can, based on the full urf If that’s what you have the ui is smart enough to pars this out And just keep the segment that is important, for importanting The ui. >> As you can see i based it in The path it automatically made it full H — after this i will define the response The response is pretty easy to define No headers i’m particularly interested in Same thing. He copy paste the request You can copy paste the response. I did it that way as well Whatever is easier. >> I don’t think i want in the Ui for the item to be called key item output I will change that to value. This is what tessa eluded to Early at the end of her demo. You can use all of these tkepl Decoration helper ui. They allow you to improve the User experience. Right. You don’t want your users to see The raw htp request parameters they want to see what they mean Contextually in flow and power apps. You can use this for That this is pretty much it. I will hit create Connector. Then wait for it to create >> As sidney eluded to we use open api and swagger as well It’s a smooth path. If you use that for a Documentation that has well described names and descriptions And it’s thorough you will see a auto box connector take Advantage of that as well. And there is a yate tool that Generates open api documents from it You have your code an owe dated Properly you don’t even have to go through the entire Process. You come and say, you get to This spot immediately

Accept authentication. It can be Automated. So now i will create a new connection Even if you don’t have authentication you need to Create a connection Test the operation. This is the response from my Service. That’s step number one how you Create your web api Then hook it up in flow or power apps way custom connector Now the next topic is pretty interesting topic We get a lot of questions about it. Security How do i secure my api How do i secure my custom connector You want to sat right security in place With that i will show what you to do to secure this specific Web api. Then i will talk about more why We do why we approach security that way So securing the web api has two Concepts, right. One you want To use this for sensitive data. You Can use others that are not industry Standard anymore. For this specific functionality this Is the most secure recommend ad proefp that we provide or suction You first secure your web application or api with an eye Dent tee. Then create another ad Application to secure and provide the identity to your Custom connector. You have a department tees that Depend on each other This can be a sub assess of the functionality exposed by the web api You don’t want to join those concepts Say for example you have have a Bug in the system and someone can escalate permissions You don’t want someone with Custom access do that. Keep this all separate Now i will go back to showing you how to pro tebgt your web Api first We will configure all of this. It’s complicated process with a Lot of steps. So keep up with me and please Pay attention. >> One of the reasons we’re Showing this. As sidney mentioned having Access to a custom web api is something you have built that Does exactly what you need for your scenario It’s super powerful and unleashes capabilities With the power comes responsibility That’s the securing aspect comes in We have a lot of folks. Even internally we use this quite a bit We want to give you quick steps of how to secure it Maybe you have seen the other sessions around explaining this As well >> There is no reason for you to just use this authentication: in This infra strict tour and architecture this is what we Recommend it’s more secure: this Does not provide you the ability to have this joint identity for Both services. The custom connector and web api I will quickly bruise down to authentication and authorization I will turn on app service authentication Again this is the assure website that is running my web serve I turn this on. Then you want to you know be Sure to check and say log in with Assure — azure active directory. It’s possible to activate this On your website but not your apis. Right

Insure you do this. Then go and configure All you need to do is select the application in this en saeur yo I could tonightually choose a new one if it let’s me Once this is set up you will, now your api is protected and secured We are talking to connect through the connector Also through any other client or tool that wants to connect to Your api can take advantage of this as well >> I will hit okay and save. I will not be able to make api Calls to my web api. Will Say 401 unauthenticated It’s important to demo failure cases Too. Have to please the demo gods Yes, request has failed. Unknown errors The request has also failed because we have no Authentication really. If i go through fiddler it will Give me the exact report message. I replay the request Execute and there you go. A 401. We saw different error Messages. In in this scenario we directly Hit the api. We’re smart enough here to know We’re connecting to aad. We have no secrets in the Connection and have abandoned that request That’s a 401. Right How do i enable this for my custom connector. That’s the next step What we do now is go to assure again Create a new ad application. As part of the process we have One application, right. One pro protecting the web api I have a lost them. This is the second application i have created It doesn’t have all of the configurations. So we will go con figure it The first thing you need to do is you need to grant — okay When you create an a d application it starts with This. What we will do here is A want my ad application To have tkepl gated access to ad application Number one. This identifies my web service That’s what we’re doing here. We say can you find — build demo Again we’re getting into the weeds of how ad works Once this is configured this opens it up not just for your Kofrpger but anything accessing your service >> Now i have selected the ad application protecting the web Service. I say allow for permissions to Access the website Once i’m done with this the next step is to go update the Connector, right. We are going to the security is Being eugs. You will hit edit and say you Want to hit o-ot2 and say i want to use azure activity directly. Yate What do we do with these? anyone know? >> Ya. So you need to provide a client Id, a secret and resource, right I will explain what these are and how they translate to Actually the architecture that we saw We have assigned this to the web service as part of the Experience in assure — azure We haven’t assigned the identity to a resource, right This ui allows you to do that. This here you say my custom Couldn’ter has the ad app i just created This is the second. Note the number is two I will copy the application id first. That is that

I go back here. That’s the first thing Then i probably need to create a secret You can click on it by creating a key >> I will create a new key. >> When i did the quick github One. Defending on what you Configure — you can use it for more than your custom connect Eras well. If you want microsoft graph or Any of the microsoft apis this is a common step to follow You don’t have to be a expert. Understanding it helps. All you need to do is fill out The red bangs here and we take care of the set of requests underneath this Is a little more with ad on both sides. You own and control It’s complicated this process is similar to the github side I just assumed of prework had already been done >> So the resource url specifies The actual resource for this to connect to. We have stebed it’s a proxy And the resource owner is the web api >> Right. The resource owner is the web Api. You provide it’s identity, Right. This can be defined in two Ways. You provide the url or provide The client id. This case we provide the client Id this. Is not off this application It’s off the build demo one application. >> Yes You troy to access. >> Correct >> So because that ad application is used to protect The web api Those are the three things we need to provide Once you update the custom connector we’re not done You have to do two more things. You have to copy the redirect url This has to be registered with the second ad application This is important. Why? when you create a connection you Are signing in and providing your details Your kredent kwraldz for the second ad application As part of the process when you sign in you need a call back url Where the token will go. This token comes to us Again you’re providing microsoft and the hosting environment Access to the token for your custom connector Not for the first — we never looked at that secret or what Not. That’s abstracted away and safe From the flow of power apps and business applications platform of resources >> You may not that which he copies was generated Automatically. The other thing it had a name in it A region. That’s correlated to the Environment you created. That is common One of the things you notice from flow and power apps The environment is the place where each resource lives Saeuplz for custom connectors. They live in a kpefbg Environment. In a specific region You can manually migrate it. You may need to reconfigure These things especially the redirect url >> As you can see i have registered this already It’s the same as my previous connector i built before the Demo i won’t go and change that The final piece that you should remember to do is enable Course. On your website So cross is cross region resource sharing I won’t go into details what had it means and why it’s there Essentially it’s there to prevent — if you apply a file To facebook but if the storage account goes to someplace else Amazon, right. Then the browser locks that If you’re on the facebook domain why is your image going Someplace well

You can white list certain dough domains to do that Be sure you go to a core saiding for the right origins In my case i say allow everything. >> If you’re really interested In white listing only specific environments we have document Eighths to tell you what course, do domains you need to enable For specific regions of flow and power ap environments Each flow and power ap environment is bound to a region Internally bound to a hosting environment with dough phaeupbdz And what not to register those directly here If you don’t do that you will see a course error and won’t be Able to debug from there on. >> We started with a Unauthenticated api. Make calls and get feedback. Great Then we went another layer and were secure with ad on both sides Then you can go further by restricting domains and that thing Whether you’re looking to get started and poke around you may Start on the first side and leave is unaugust en at this Cased. Once it’s a noted point to share Within the team for example, you want to get further down the steps >> Right. >> So, the last step is to Update the connection. Our conk had no authentication No token. Not signed in anywhere now >> You this pops up. It says pick an account I pick an account. I have already kwrapbded consent To that application. It didn’t ask me for consent If it was the first time it would ask to build demo I would say yes or no. Based on that the process Getting complete. Then the tokens would be stored In the connection. The other thing about add Securing the connector and the end website because we log into Flow with aad and power apps with aad it’s prepopulating and Your account is there. When i do it with github i log In with addition to my flow account You use different services and you have the barriers If you target other than all yens with flow you continue that Reuse and it’s a smooth user experience So testing the operation again you see the response does come back If i ask to fiddler and replay the request i see this No august at this cation has been applied it won’t work >> Can you show the test tab and the request? >> Yes. So, if you’re interested in the Raw request, right. I can break this down for, maybe this Is where the proxy shows itself to you through the test tab and That thing If you just use a connector up don’t notice the issue You may see errors You snow github wouldn’t send that Where did that come from. Once you create a connector and Make calls that is where you start to see, ya that gap >> So, as you can see the first segment of the Url. >> Make that bigger unless your Eyes are better than mine >> This is the hosting environments address This is the connector id right as we discussed earlier Connector id and operations. These are the three things we Need. The b75ecd is the connection Requires choired to make the request /Api/values is the path of the request. One of the things i would like To bring up as well is that — Yes. So this token is actually the Token with the flow. Not your website

So, ad — this is like a common concept. When you issue tokens you have To provide the audience that you’re trying to access this Is ad token grants you permissions to use the Connection that is provided in the url It does not grant you permissions to access the Resource under the covers behind the custom connector That is that never comes down to the client >> That’s where if you didn’t have an authenticated end point You would see this authorization You need it to be able to use the connection that we use That’s why we’re bringing up again the probgs y intimate You as connector developmenters understanding the architecture Will save you a lot of time. If heave forbid if you hit an Issue building your connector. >> Yes To recap very quickly, i think we can go back to the slides >> Yes. >> That is the end of my demo To recap we created a web api. A simple api returning a string When you call it Then we added the authentication to the custom connector and api Remember to enable course. Remember to delegate Permissions. Remember to put in the right resource The client id of the web api is the resource The khroeupbt id in secret identifies the connector That’s the second. That’s how it works Essentially. Also since we looked at the url If you don’t want a bold star allow all, all domains Allow the ones in the url. Canada-oo1 is the stkoe main you Want to allow. That domain makes the calls to Your service under the covers. So with that i will give it back To tessa. Go from there >> Perfect. A lot to absorb I know that was a lot in the last demo The main per pos is this is where the power starts to Unleash. Connecting to existing services Is interesting. We have 200 something connectors We are hitting quite a few of them I’m sure someone in the audience has a favorite connector we Haven’t supported. We have done quite a bit Now when we talk about custom connectors we look at the pro Dev, the enterprise dev scenario where you use the custom Connector feature to bring more amazing capabilities into the products If you go down the paths you have advance cases especially Around building your own api. As we stated this was straight forward The possibilities are endless with what you can do once you Off load the work outside of the product So did the demo. Perfect. Resources Then we will go to a much an over view Most of these are hyper links. You need the powerpoint to remember it If you have to remember two urls or take pictures it’s the first And second one. This first one, i don’t know how Many times a day say that it’s a favorite website it has a few Different things in it one of them, you may of been there and Taken advantage of, this is our connector reference documentation If you use a connector and don’t know exactly how it works, all Of the reference documentation is on this site In addition to the connector references you can also get all Of our help documentation for custom connectors That’s is everything from what what is a custom connector How you build a custom connector. A postman from scratch to open Api we have tutorials for all these We talk about web hooks. Want to add triggers and Dennamdi i can values and seem as There is a tutorial on doing the web api and the authentication It’s not quite the same as we showed today here The video maybe your best bet going forward If you remember the specific fields he mentioned this maybe There as well. The second One for ak — that is for partners and isvs that Want to build a connector and have it certified by microsoft This will link i believe to a blog post with a “how to.” It may of been from last year’s announcement this. Is where we opened it up at

Build last year. It’s been a great year working With partners to get their connectors out to the users of Flow and power apps and logic apps There is a link to directly submit for certification here This will take through a nomination process and all of The artifacts you need to do. That will put new touch kw-t Certification team at microsoft. Out of the 00 connectors those Released recently are partner built. We have a strong ecosystem We suggest if you have a service or a favorite service get them To talk to and make sure we get a connector for you to use in The platform as well. So, a quick over view After this i think we have two more slides Then we will open it up for questions if you’re still Processing that. We start wapb over view of the platform You know many folks are familiar with one product or another The business application platform works across power ib Flow and power apps. So, you know some of these Connection stories are across. It shows how to build a Connector in a few minutes and how to easily use them with products You can spend time customizing and making it better after that Getting started and seeing the instant value can be on the Order of minutes. What partners come to us and say How much work is in a kopgter. You can get a production ready Connector in less than a week. In a day if you’re dedicated to it >> Internally we have a lot of Internal microsoft products we build and use connect erdz for For service and incident management we have connectors That are not public. It improves productivity a lot, right You can use a power ap or flow. >> Yes think of any service you interact You have to flip out and in. You wish, wouldn’t it be nice to Have a button or a automatic trigger. Those are great candidates for Our platform. >> Give an over view of the Connector architecture. We gloss over That it works it works, great. Wince you start to build a connector it’s important to Understand the layers and how they interact. Then you have to see a demo of The advance concepts Specifically around building your own api and securing it How to tie that all together for flow and power apps Hopefully it’s possible. Any api, serg or data — Anything is accessible through flow and power apps and long i Can — logic apps. How to get started, the Different resources we. Have it’s the last day of build We’re one of the last sessions down at the bottom Though are the other sessions for microsoft flow and power Apps. Maybe you’re familiar with power Apps more than flow. You want to learn more, this Slide is available. Search for them on the build Site there. Are a few here for the rest of The day. If you’re interested you can Take a look at the next three as well With that yes we will remind everyone submit your evaluations This is how we take the feedback and make sure we learn to keep Things exciting year after year. >> Yes, i recommend doing they Value evaluations. It tells us what you want to see From us in the sessions. It’s great for us to be customer Obsessed as well. >> Yes With that we have about ten minutes left for questions If you do have a question just come use one of the mics in the Middle of the room. Anyone have One? >> okay I have a number, first question is. There a practical limit or a Hard limit in terms of the size of the swagger file? If i have thousands of different resources all with crud ob Playingses, post, past, delete Have we ran into that. >> So >> In general there are no such Hard limits. The user experience will be Great with too many actions in a trigger somewhere we recommend

You break them apart. You can always have one Connector or ten connectors going to the same apis. Right The office graph has lots of end points, right The segment is by capabilities. There are admin capabilities Separate connector. So on That’s how we recommend you segment them out >> If you can’t the product itself won’t break It’s just sear searching for the Operations is great. >> If are you familiar with Swagger in an open api. Doing dependencies and related definitions If you have many levels of dependencies i have found that We are a little slow on processing. It’s not, that’s not intended In theory it’s more focus focusing on the utilitier experience >> I work for an isv. We want a flow connector We are on premise. So we were looking at doing an Open api file and i am importanting this Is there a a way to program connectors. Click a button and we can create A connector foe you. >> — We are shipping soon Under the coverages if you can figure out the apis they’re All public, not documented. The fact of what happens through The ui can be done with api calls. If you want to do it as soon as Possible i recommend the fiddler route. >> If you can wait a bit we are Shipping partial command lists. If you do have a user in your Customers tenant you can did i ploy it yourself and share with The organization or whatever users want access to the connector >> I had a second question with aad Is it, does it ultimately become the user running the flow, Running the connector that connects to the api or the user That set up the connector whose permissions i have received them In the api. >> It’s neither of them >> Yes, neither. >> The person connecting the – Creating the connector they’re describing the api surface They provide the — or there is a difference with user name, password You create the app identity. Any user can create a connection If i use a connection in flow the flow will operate as me If you create a connection on the same connect we are your User name and password and you use that connection in a flow Then it will use your credentials there. Is one more thing You can share the connect. You can share your connection With me. If i use the connection then It’s your identity being used by me in the flow >> As close to the first one. The user with the flow and calve Yet that users share connections If i share my connection with you and trigger ally it’s using My connection. Who ever creates the connection That’s the identity used. >> Sharing of connection s-pbz Recommended for all. >> Only things that make sense To share. >> We didn’t talk so much about connections What’s the difference between connection as a instance of a connector >> Yes. >> — Required to call the operation >> A connector and credential pair. Right. >> If you think about when You’re in flow first you choose the connector and sign tph-fplgt The output that had is a connection that is used in each operation >> Thank you. >> Yes Phufrpblgts question is related to on Program — on p Ram isv. I wonder if the service was Gateway. The on program gateway is on Paper customer — >> — basis >> From what a saw it’s my connector when i design the Connect eric use the connector to get to the on prime gateway >> Yes. >> Can that be used by a Customer of my isv solution. >> Yes. So the way that works again Everything is bound to a tenant, an environment If you deploy a on premise connector in an environment

What happens is when you create a connection on it it will ask For the data gateway. If the user has access they Create the connection and use it. If they don’t have access they Won’t be able to. >> Yes. >> Until we don’t have a Connector published, publicly what do you recommend as a way To redeploying the test in another tenant >> Today we don’t have an official guidance around it We are. We have something in the works I would say stay tuned. >> Yes Exporting and importing is the closest thing It doesn’t include everything. You need to work a little bit With your customers until we fill the gaps >> As long as we have a script doing it it’s okay >> Yes. The scripts haven’t been Released but in theory they will fill the gaps. >> The bare minimum after you Create a connector there is a button to download the open api file You do that and you can get it to the question >> My question is probably late Is there a way to runt power apps and connector and power Flow on prime? >> not today Anytime line? >> we can not give a time line Unfortunately, power apps and flows are predominantly built To run in the cloud. At the same time though logic Apps the offering equal to flow they’re planning to be in azure At some point. Would i recommend reaching out To that team to get time lines. >> Okay >> I think separately and another powerral the types of Scenarios you’re interested in would be helpful We want to support a lie pwreud scenario As — hybrid scenario as much as possible >> That’s the key word. Hybrid. >> Yes hybrid scenarios will be supported >> I guess this is continuing on another question Today we have the gateway for accessing sql and a couple of things Can we do custom connections through the gateway >> Yes. I think a blog went out maybe Six months ago. We can find the link for it When you go to create your custom connector under the host Or above the host you indicate it should use that gateway and It uses the same gateway. Same technology for the sefbg connector >> As long as your api on premise is restful check that Box and you create the connection it will ask for a gateway That’s it. >> Thanks. >> I think my question is Related to his. I have a set of – services Those use windows authentication. >> Okay >> Does that mean i have to synchronize my on prem activity Directlyery. >> No you won’t You will expose your api again through the custom connectors ui When you check the check box the selection in the security panel Will change to windows ought, basic ought and — >> That’s what i missed. >> We didn’t show an on prem one >> Because you do not recommend sharing credentials. >> Correct >> Does that mean i have to generate credentials? >> So one of the important pieces again is you create the Connector. Connect is created by a end icer You have one connector and connections Connections can be owned by each individual user and they have Full access over it connectors on the other side Two levels of permission. One is the owner permission The other is the utility user. You would be the owner sharing With everyone. They see the connector like Every public connector out there. When we say there are two Hundred public connectors out of the box they don’t have credentials >> As the connector author you say you should use it with windows You say the type of credential they should use When they use it they provide. How do

I marry the kred kredent — credentials — [inaudible] >> Can we take that off-line. >> Yes Thank you. >> Similar to the other questions You did a stkepl owe with assure — azure active directly >> Yes. >> With we’re with on prem does that work as well >> If you’re azure active directlyery it depends on your Admin privileges there isn’t a straight answer Active directlyery is very complex. If you don’t mind coming and Talking to me after — >> it will be have You have to register. The connector is another Interaction eugs. Go ahead >> So, what would be the prefered scenario yo for a Double initial hit. We use — i can hit it, it’s not The cloud offering. The first thing we have to do is You have to — >> exchange. Yes >> It’s not even an exchange. >> It’s a calling the project And that behind the scenes sort of message structure so your Next call is related to the project you hit >> Do you get something back? a toke stphepb >> You get an adjacent object of the structure. >> You want to reuse that >> You say i want to use project x. It says the available issue Types are this and that. >> That was an advance concept We didn’t demo as well it’s specific to flow then power apps You want to look at dynamic values and dynamic seem afplt That allows you within an operation to populate and get Additional information from multiple calls That’s one way. Another way, again if they’re Not related you can change actions together within a flow >> That’s where i was going. Scenario [Inaudible] >> you can do it within one If it has multiple — >> yes >> Sorry. >> A common example is share Point within flow. Say you want to create an item You first select the sharepoint site name and then the list name And then the fields get populationed. That’s generally available to All custom connectors. We can discuss and show you how That is done. It’s possible. >> Then depending on It’s totally possible and you can take a look for sure with That the thing is beep beeping at us We have to go. Thank you, i hope you have a Great rest of build. Thank you. >> Thank you

You Want To Have Your Favorite Car?

We have a big list of modern & classic cars in both used and new categories.