Integrate 2018

June 4-6, London


Perfect for Logic Apps novices, Microsoft experts Kevin Lam and Derek Li present some basic demos on getting started with Logic Apps. They then go into a more advanced demo showing the Azure Vision API to interpret a scanned invoice.

Introduction to Logic Apps

Integrate 2018, June 4-6, etc.venues, London


Video Transcript

I’ve got great pleasure introducing our next two speakers, I don’t really think they need too much of an introduction. I’ve got Kevin Lam and Derek Li, both from the Microsoft team. Kevin has been with Microsoft since 1997 and he’s a Principal Program Manager. Derek has been with Microsoft since 2014 as a Program Manager. They’re going to be speaking about an introduction to Logic Apps. Guys, over to you.

Derek: Okay, thank you.

Kevin: All right, touché John. Now it’s your turn [inaudible 00:00:36] my time. So that’s an old joke that we have. So it’s great to be here again in London to talk about Logic Apps. You know, this is a session about the introduction to Logic Apps but it’s really about how to make you guy the integration heroes. So I went to look up integration hero in the dictionary and it wasn’t there. But, I did take the hero definition from the dictionary and tweaked it a little bit and see if this sounds familiar to any of you. In IT, a person of superhuman qualities and often semi-divine origin, in particular, one of those whose exploits and dealings with the ancient on-prem systems were in the subject of myths and legends. Does that represent any of you guys out there? Yeah, some of you guys, right? So you saw some of those gymnastics with the no-host integration server in DB2, and SAP systems and trying to understand that, bring that together and understand messaging, that was the, you know, the integration heroes back in the day. In the States, it just means a mixed meat of submarine sandwiches, but we won’t talk about that. That’s okay.

So, what is Logic Apps? How many people have used Logic Apps? Oh, a bunch of you. Awesome. So I don’t really need to introduce it to at least half of you, if not more. But for those that have not used it, I wanna make sure everybody is level set and understands, you know, what Logic Apps is. So, Logic Apps is Azure’s workflow as a service. It is the integration tissue across the services that you use in the Cloud and on-premises. Those cloud servers are SAS providers, including Office Dynamics, you can talk to Box and Twitter, and whatever service is up there in the Cloud to on-premises systems. And you saw examples of SAP and DB2, and sequel server on-prem and Oracle Database and, you know, a dozen other types of connectors on-prem. So with Logic Apps being that connective tissue providing you a workflow in the Cloud so that you can then automate those processes that then bring the power of Azure as part of your integration platform. Right, Logic Apps is the heart of the iPaas offering. And, you know, recently, we were announced as one of the leaders in the iPaas quadrant.

And it’s because we have these capabilities of being able to easily integrate these services and take the power of Azure to bring it at hand. And with that, you also get the power of Azure’s artificial intelligence. So you can bring machine learning, cognitive services into your business processes. Right, being able to take the data that’s already going through your integration pipes and then being able to enhance that data with intelligence, you know, really makes you the integration hero. You know, we saw with the example of, that companies want to get to market faster, right? It’s not about writing more code, it’s about how do I get my product out to market faster than my competitors, or new things that are coming up that may disrupt our businesses? And Logic Apps with its innovative and smart designer, allows you to go through those loopholes of trying to figure out how to connect these disparate systems. So we’ve created, you know, canonical models of trying to integrate these different systems from, you know, something as distinct as, connecting to your SAP system. How do you get those things to talk to each other, right?

So with our innovative designer, you’re able to quickly and intuitively be able to build these and having to put together. So each connector will provide a set of tokens, and those tokens can be matched to different parameters since everything we talk to is some type of API. And because we’re, you know, at the heart of iPaas, you know, you can build your enterprise applications right on top of Logic Apps. Right, you saw that again, with, it’s the heart of their business that’s running all that in the background, and being able to connect those in a reliable fashion. So, Logic Apps has out of the box, over 200 connectors. There were a couple of new connectors that we talked about that were coming out today. But those connectors connect to social media, Twitter, Facebook, Instagram, to your CRM systems like Salesforce, or to mail systems, Office and Google, right? So we have hundreds of these connectors that are able to connect to those services, our first-class, first-party services, Office Dynamics, SharePoint, Visual Studio.

So all that is available to you as connectors and being able to really easily integrate those services, right? With that, we also have on-prem connectors. On-prem connectors use our on-premises data gateway to be able to give you that same look and feel for all the connectivity that you have that’s up in the Cloud. The connectors create the abstraction across the different APIs and services and protocols that you can speak to, but really, what is the resource is what’s called an API connection. That API connection creates the abstraction of the configuration and off for each of those. And then, those API connections which are as your resources, can get deployed alongside or separately from your Logic Apps, can then be reused across your set of Logic Apps, right? So then you can keep your configuration and your authentication distinct from the business process that you’re actually building.

Finally, if we don’t have the connector that you want or you have your own custom service, you’re able to build your own custom connector. So then you can have the same experience with both using the API connection experience so that your secrets are distinct from your programming model, as well as being able to connect with services like REST and SOAP, right? So if you have your own custom web service that’s either on-prem or in the Cloud, you get to build your own custom connector to do that. Or one of the connectors we built, you don’t like it, everybody has their opinion, you can go build your own, right? We use the same technology to go build these connectors, and then we’ve made it available to you with the custom connector experience. So Logic Apps really provides us great platform versatility, right? So what are types of things that are people doing with it?

So we have connectors for a different messaging system. So for service bus, you get to do cues and topics for asynchronous messaging, and pub/sub. We have Event Grid, being able to do event-based processing across Azure and custom topics. We have Event Hubs and IoT so that, you know, as information is coming off of devices, right, you saw the demo with the with the Raspberry Pi as that information is coming in off of the cloud, you get to consume all that through our messaging platform. Data wrangling, because we have these connectors to various systems to different database types of resources like Sequel DB, Oracle DB, MySQL, Teradata, we have all these different types of connectors to various databases and data sources. Even the cloud-based ones like Cosmos DB, or Table Store, if you wanna think of it as, you know, for your data stores to entity-based systems. If you wanna think of Dynamics CRM or your Salesforce system, and how do you take all that data that’s in these disparate systems and bring them together to make something that’s even more powerful or really get into a single view of the world?

So being able to synchronize that data, you know, cross these distinct entities is really easy on Logic Apps. B2B and EDI, so trading partner management. So we saw some of that today when you’re doing at a factor X12 processing over an AS2 protocol, being able to have the rich set of connectors that makes that super easy to take [inaudible 00:08:30] parsing, as you’re going into an SAP system, for example, and you wanna trade with your partner. All that’s built into the platform today. More classic hybrid enterprise application integration. So, you know, as you’re thinking about different message formats, I have an XML message that has to be transformed into an i-Doc, or to another XML system, a system that needs a different format of that schema. So we have the ability to do rich mapping between these different systems and be able to do that communication either through direct messaging or through queues. Process automation. So everybody has stuff they do all the time, right?

They have daily workloads, weekly workloads or, you know, as things get built up into, you know, into the backend system that you need to clean things up. And so Logic Apps is a really great way to schedule workloads that are happening in the background to go, you know, clean up your database. You know, we use it internally to create weekly reports about what was checked in to GitHub that’s about to be released to market. So then, we get reports that are built out that scans our GitHub to go ahead and build those reports and send out emails. If you want to clean up the, you know…Somebody created a blog about, “Hey, how do I clean up all of my Azure deployment?” There’s a limit of 800 Azure deployments that you could have. And so as you’re doing CI/CD, those things can build up and somebody has to go in and write some script to go clean that up, which could have taken, I think, six days if they had to clean up 800 different deployments and instead, Logic Apps just took about an hour to process in the background because it’s so highly parallelized and then can run every day for you.

And then finally, smart SAS. So how do you add intelligence to your integrations? You know, with the cognitive services like text analytics, video image processing, we saw in the demo earlier today, face recognition, and being able to bring that power to your integrations into your business. Adding intelligence is the, you know, one of the game changers we have for being able to do Bots and doing LUIS, right? So, language understanding as you do your business processes and bring that power to your integration. And finally, all that’s built on a serverless platform. So you don’t have to worry about the scalability of your service, we handle all the events and then scale out those Logic Apps for you. You don’t have to worry about DevOps, and management, and doing OS patching, right? There are no machines, there are no servers. And then finally, Micro Bill you only pay for what you use, right?

So if you’re, you know…your systems either quiesced, you don’t need to do anything or, you know, it’s not one of your peak loads, you don’t have to worry about, “How do I size my system?” And during those holidays, you don’t have to plan for the holiday. It’s like, “Oh, I have to deploy more servers because it’s going to be black Friday in the next couple of weeks. And I have to think about that.” No, we handle all that for you, and you only pay for what it consume. So you’re not paying that maximum cost of the peak load that you expect to have, right? Only what you consume. How do we do that? So the first thing that you need to do is you need to trigger. That trigger is what listens for events in your Logic App and creates a new instance of your Logic App. Where the first type is the recurrence or advanced scheduling trigger. You can…and this is, you know, as we talked about the automated processes, you get to have a timer that’s actually working in the background to go ahead and create a new instance of a Logic App.

Right, that timer can run every five minutes, every hour, every three days or you can do an advanced schedule. So the first and last Monday of every month at 8:00 p.m. and 12:00 p.m., right? So we can do that for you. People don’t realize that Logic Apps has that rich scheduling capability to do all this automated processing for you in the background. The next one is polling. So a lot of APIs today don’t, right, have a callback mechanism to let you know that there’s new data. So you have an older API or just one that’s not built in that way. So we provide the polling capabilities. We can ask that service, “Is there a new data that needs to be processed?” So we have that polling built in. You don’t have to worry about asking that system when there’s new data. If your system supports the webhook protocol, then we have a trigger that will subscribe to that system and give it our endpoint, which will then provide a callback for that system to call us back when there is new data.

So if it does support webhooks then we can provide that. We’ll sit there and wait, and then once it calls us back, then we’ll trigger a new instance based on that callback. And finally, the request trigger. The request trigger essentially creates an API for your Logic Apps so then you can call it from anywhere. You can call it from Postman, or a website, or pass it in as an endpoint to your application or as a backend to your API Management. So then you can call it through API management and instantiate a new instance for Logic App with each call. Action, so we wouldn’t be a workflow engine if we didn’t have a set of control actions, right? So first is a scope which allows you to encapsulate of a collection of actions. That scope we’ll talk about later tomorrow, different ways that you can utilize that for more advanced patterns and scenarios.

Conditions. So if/else, you wanna be able to have conditional paths in your Logic App. Case statement, so you can go through a number of different values on a particular property to determine what you wanna do. For/each allows you to take an array or collection, and then iterate across each of those items in that collection. And for/each provides you a highly scalable paralyzed set of a way to work through that collection of data. And then finally, do/until. We give you that that ability to go ahead and do work until some condition is true. So if you want to, you know, talk to a backend system, and find out until you get a particular value back, keep talking to that system, or some other pattern for being able to do work until you find that condition to be true. And then finally, at the heart, right, there’s a set of actions that you actually wanna call, right?

The first one is being able to call APIs. These connectors that, you know, provide that abstraction to these services up in the Cloud. If you wanna talk to your Salesforce system or your BizTalk server, or your Q, we have connectors that are able to do that and abstract that for you. It can invoke code, so we don’t host your code but we have lots of different ways to actually have your code hosted. Our first way is being able to call an Azure function or other serverless offering that allows you to have, you know, small snippets of code that can be quickly called. We can run a container. So we have an ACI connector so that you can go ahead and run code in a container. If it needs to do a lot of processing, if you need to do ML processing in the background or video processing, you call a container, and then let it do its work. Logic Apps will wait until that work is done and continue if it’s 10 minutes, an hour or a day later, it will wait and continue. Of course, we have the ability to host code, it’s in web apps. So then you can have your API app or web app that’s sitting there. And we can call it somewhere between your, you know, an API call and hosting your code.

But you can call that directly natively from Logic Apps. There’s control behavior, so you can terminate a Logic App, you can have custom retry policies on each of the actions. Every action that we have has a default retry policy so that we do the work for you so that in case there’s a blip in the system, you don’t have to worry about how to handle that, we take care of that right out of the box. Message channeling, they talked earlier about the ability to construct new messages, or transform an XML using an XML map from one form to the other. Do message validation, right, format validation, schema validation. And then finally, expressions and operators. So we have a bunch of built-in functions that are built in to the DSL that allow you do things like, you know, get a GUID or do string manipulation or, you know, find something is null or do some work. So we have about 50 or so different functions. So before you have to go write code, go look at those built in expressions that we have to go ahead and handle that for you in line so you don’t have to go out and write your own code. Okay, so let’s get to the demo.

Derek: So, one thing that we’re really proud of here, within the Logic App team, is how easy it is for you to get started with Logic App. And within a few minutes, with few clicks of a button, you can have your first integration solution ready. And then, you can see the benefit of using Logic App. If you think about it, when integrating with different systems and services, you spend most of your time understanding how to talk to their APIs. Because every API’s are ever so slightly different, how you authenticate, how you provide the payloads, how you specify versions, Logic App, take care of that. Logic App do the hard work of figuring out how to move data from one place to the other so you can focus on what data you want to move and you want to…and where you want to move it to. So let’s get started and see how within five minutes, we can go from, “Hello world,” to integration hero using Logic Apps. So I’m simply going to switch back into the Azure portal. I have an empty Logic App already created.

So in this one, we’re going to implement a logic app that follows request and response pattern. The Logic App is going to expose itself as a REST API. And when called upon, is just going to return, “Hello world,” to the caller. This is one of the very common scenario that people use Logic App for and we’re doing exactly that. So in the visual designer, I’m starting with the trigger, this is just a request trigger. And then, I’m going to follow with a response action. In the response action, I’m simply going to return, “Hello world,” in the body. I’m going to save the Logic App, and the moment I save it, a URL is generated. So this is the new REST endpoint that my Logic App expose itself with. What I can do is I can switch to Postman and make a request to it. So here’s the URI, I’m going to click Send and, boom, “Hello world,” is returned. It’s really as simple as that. With a few clicks of a button, I have a REST API that will return me some content. So that was cool, but let’s keep adding to it.

What I’m going to tell the request trigger now is what a sample input may look like. Here, I’m going to say…it’s going to be a JSON payload with a property cap zip code. I’m not going to give an example, so it’s going to look like something like that. So you see, I don’t even have to know the JSON schema but by just simply telling Logic App a sample of my JSON payload, the schema is generated. Now, with the schema what I can do is, I can instead of return a static content, I can return and consume that input. So I can say, “The zip code you provided was zip code.” So you see here, in the pop-up, we will show you what we dynamic content, or tokens is a set of tokens that you can use to reference output from a previous action or trigger, in this case. So I’m going to select zip code, and I’m going to save my Logic App. Here, I’m going to switch back to Postman and I’m going to change this a little bit. Let’s use a different zip code.

So I’m going to click Send, and we should see the zip code I provided is returned to me. So again, with a few clicks of a button, my Logic App is now consuming the input in the trigger and returning that to the caller. But let’s do something else. I’m going to go between the request and response action, and I’m going to insert a new action here. So, for this example, let’s use that response, again. We’re going to use MS and weather. So, Ms and weather is an out of box connector that we provide you, for you to be able to query the current weather, weather forecast given a particular location. So it’s really as simple as searching for the keyword that I want to add. Here, I have MS and weather, I’m going to select get forecast for today. Zip code, I can use that as the input, and then I can return that to the caller. So let’s say something like the weather for location, location, it’s day summary with a high of…we’re going to choose the temperature high and a low of temperature, low. Let’s keep adding to it. Let’s say the chance of rain is…I think there’s another token that I can use to reference the likelihood of it raining. All right, so let me save the Logic App and switch back to Postman.

So, this zip code belongs to Phoenix, Arizona, that’s where I went to college. I think it’s not going to rain. So it will be high, wow, of 107 Fahrenheit and a low of 78. That’s very hot. And the chance of rain is zero. Let’s change the zip code. Let’s use Redmond, Washington. So the headquarter of Microsoft looks like it’s going to rain. No surprise here. So this is the first demo, really. And I hope your takeaway is within five minutes with a few clicks of a button, I didn’t write a single line of code. But I’m able to consume MS and weather API without having to read a single document describing how to work with that particular API. I’m able to use the logic at visual designer to consume a particular API called Get Forecast for Today. I can transform the data to however the format that I want, and return that to the caller. Right, if you think about in the context of [inaudible 00:23:16] we can have that data in the email that we send to our customers saying, “Whenever you come and pick up your order, remember to bring an umbrella because it’s likely going to rain.” So, hopefully, that shows you how easy it is to go from, “Hello world,” into integration hero in five minutes. Thank you.

Kevin: All right. Thank you, Derek. Excellent. Love it when demos work. So what else can it do? So I’m going to quickly go through this because we have to catch up in our time. But Logic Apps are manageable. So in the earlier demo, you saw how we have a trigger and run history. So you could see every time that the trigger fires, we get a historical event for that and the runs. And so when you click on that run, then you get to see a monitoring view of what that Logic App actually looked like in all the inputs and outputs for every step that occurred. Super powerful to being able to get insights into your Logic App and see what’s happening behind the scenes. You have version history and rollbacks. Every time you save a Logic App, we actually save that version of that Logic App. One, we need it because you may have old Logic Apps still running in the background. So it has to still run on that old version. But new instances will run on that new version. But you get to roll back to a previous version that you had saved.

Diagnostics and alerts. So we can take the power of Azure and provide alerts in case something’s been going wrong. For example, if my Logic Apps has been failing for the last five minutes, send me an email, send me an alert, right? You can have in the new Azure monitoring, you get to have these set of group events that you can even call another Logic App, which then can interrogate your guys who are on call. And then send the message via SMS, or email, or Teams, or Slack or whatever way that those guys communicate with, and all abstracted for you, and being able to do that operations management itself. And finally, Operations Management Suite. So we have solution packs built into Operations Management Suite. So that, you know, in our monitoring view, you get to look at a single Logic App. And then, in Operations Management Suite, you actually get to look across your collection of Logic Apps. So the application that you have likely has more than one Logic App so then you can see the correlation between those and other services in Azure with OMS.

Okay, so the same experience that you saw Derek just build in the portal, we have that in Visual Studio. So for those developer-centric folks who are doing production systems get to stay in Visual Studio. So we are integrated as part of the resource group project. And what it does is actually, it’s working off of the ARM template. So the resource group project recognizes that your ARM template has a logic happening, right, because our definition is serialized into that ARM template. And then we’ll go ahead and render the designer right in Visual Studio. And then you have that same developer experience right in Visual Studio. You get to deploy and save it to source control. And since it’s in source control via STS, then you can do, CI/CD with your logic apps. We’re also exposing the Cloud explorer and Visual Studio. So then you can go find your published Logic Apps up in the Cloud so then you can manage your Logic Apps where you can delete, or enable/disable those Logic Apps and see runs that have happened right within Visual Studio.

So I still don’t have to go to the portal to see what those runs look like. That same monitoring experience is available there as well. A common pattern is that somebody would go right there to Logic App, open the portal and realize, “Okay, I really want to, kind of, bring my DevOps experience to this,” go find in cloud Explorer and then you can download that Logic App and then have it exported as an ARM template, and then imported as your project in Visual Studio. The integration count. So we saw earlier today how we integrated with SAP in doing trading partner management using the integration account. So we have the ability to support EDIFACT and X12 over the AS2 protocol, manage partners and agreements with Logic Apps. And it’s the same, you know, we have tools, I think we’ll talk about later in the conference, to be able to export your trading partners from BizTalk and import them directly into Logic Apps very easily.

With that, we also have the ability to do XML and flat file handling, to restore your schemas and your maps in the integration accounts. Then you can have a rich set of those to choose from, as you build your Logic App, as well as, bring the power of liquid transformation as well so that you can actually do transformations across different types, including JSON, XML, and just strings. And finally, we add the ability to do business tracking into the integration account. So you can add your own tracking data as part of the tracking data that’s going to OMS and enhance that data as well. Logic Apps is secure. So we’re built in Azure as an ARM resource. So then we have a role-based access security, so then, you can have the distinction between operators versus developers. We do auditing. So every change that happens in your Logic App is audited so you know who’s made a change to your Logic App. So you can do that for production.

We have static IP. So if you need to have network rules, so you can go ahead and trust the set of IPs that we give you to set up those network rules. IP constraints allow you to lock down your, you know, we saw that request trigger. And yes, it’s secure with a key, but you can even lock down more with IP constraints. So you can take that IP constraint, for example, and only say API Management can call this Logic App, and then it’s locked down. So then you can do your rich auth [SP] and API management and then call into your Logic App or whatever system that is. You can regenerate those access keys. So, you know, if you have policies that require you to regenerate them at a particular pace, or they get compromised, you can go regenerate them. And everything we have is encrypted at REST.

Derek: So, we have seen how Logic App takes you from, “Hello world,” to being an integration hero. So then now, let’s see how Logic App can give you superpower capabilities. And we’re going to go through a scenario where we take an order in an image format, a JPEG image in this particular case, do some image recognition and have a customer approval experience. Again, I’m going to just switch back into the portal. This time, I will start with a Blob Storage resource. Matt, earlier in the talk, showed you integration between Logic App and Service Bus via Event Grid. The other integration that we have recently enabled you to do is between storage account and Logic App. In this particular case, we even have a few different templates to help you get started. What I’m going to choose is just when a new image is upload the template, it basically recognize whenever a new image is uploaded to Blob Storage, run it through OCR, and then upload it to SharePoint. We’re going to use it as our starting canvas.

I already have all the connections here. We’ll take a few seconds for us to establish that. So one thing I’m going to do, again, just like we mentioned, we’re constantly making improvement to Logic Apps. So the most recent improvement is we allowed you to specify the particular events apps that you care about when subscribed to a particular event, great event. So here, I’m saying, when a Blob Storage is created, and with that, I can even get rid of the condition that I currently have in the template, and the template is going to be updated soon to reflect that change. So I’m just going to move really quick all the actions, all of the condition. I’m going to get rid of the conditioning because I don’t need it anymore now with the improvement in the trigger, and I’m actually going to remove the SharePoint action as well because we won’t be uploading the file into SharePoint. So what we have here is really simple. We’re triggering off a new image being uploaded to Blob Storage, we retrieve the URI so we can reference the image, we send it to OCR connector to do text recognition. I’m going to save this really quick and let’s just make sure that it works.

So now, a Logic App has been deployed. I’m going to switch into my Blob Storage, I’m just going to upload a file using the web interface. I’m going to go into this particular container that I’ve already created, let’s upload something. All right, let’s keep going. So, I think I have an order already created. Let me try to locate that. I think it’s this one. It’s just a book that I bought off Amazon. You see as a JPEG image I’m just going to upload that. And by the time I switch back to the Logic App that I created, hopefully, a run is already triggered, I think we called New Logic App something like New Logic App. All right, so we have a run already, let’s see what happens. So this is the run or monitoring view in which you can review all the runs that had been triggered. So you can see the text is being recognized from the JPEG image that I have uploaded, that’s really cool. Now let’s start adding stuff to that template and make it fit our scenario. The next thing I’m going to do is call into Azure function.

Now the text me recognize is cool but I can’t really be consuming that. I want to extract the older total amounts from that blob of text, and Azure function is great for that. If you think about it, this is actually a great example of showing how Logic App and the function can work together. Use Logic App for workflow and orchestration and use Azure function for complex data manipulation. I already have a function created, and I’m simply passing in the detected text. The function will run some complex [inaudible 00:33:07] logic and return me the order total. Now, what I can do is, then I can add a condition. I can say, “If the total amount is greater than $10, I’m going to do something.” So if true branch, I’m going to use the approval action. Ultimate approval action is another very popular action that people use and make it really easy for implements. Sending an email, waiting for the user to take an action within that email, and then proceed from there, and see what the user selected and execute different business logic.

So I’m going to just send it to me and for the subject, let’s just say, “Order needs approval.” All right, I’m going to save that. And for time’s sake, I’m just going to resend me the trigger, and when I resend me the trigger is going to use the same image over and over again, so we don’t have to go to Blob Storage and do that. So I’m going to sign into my email, and, hopefully, we should have an email ready for us to view. There you go. So this is the email I got. It’s really simple. The option that I specified in Logic App Designer, approve and reject, are actually surfaced as a first-class experience for me to choose. I can simply click approve, and if I go back to the run, you will see that my response is captured here. So what I can do from there on is to add another condition block and say, “If the order is approved, I may want to transfer that into another blob storage or service bus Q. If the order is rejected because it contains some high-risk factor, I can then escalate that and have a second-tier of review.” So that concludes the demo. And, hopefully, you will see how Logic App empowers you to do more complex scenarios, again, with just a few clicks of a button, without you having to write a single line of code.

Kevin: Excellent. Thank you, Derek. So, it really shows you the power that Logic Apps has, from being to do OCR image processing. How many of you have bought an OCR image processing system and spent millions of dollars on that? Anyway, some of you will be out there. To doing it with, you know, fractions of a penny. I’m sorry. So, no, we can do intelligence, we can do long-running workflow processes, all in Logic Apps, and with a few clicks. In only a few minutes, he’s been able to show you that very simple scenario. And you can continue building on that, you know, to meet the business process that you need. So here’s the juicy stuff, what’s coming? This is what everybody’s waiting for, right? Okay. A couple of things, China Cloud. For those of you who are multinational companies who need to work both in here in Europe, or in one country, as well as, in China, right, there are different government rules about running your workloads in China. We’re currently deploying our Logic Apps to China Cloud so then you can run your Logic Apps in China Cloud.

Smart designer. So our designer is already pretty smart and nifty, right?

Man: Pretty smart.

Kevin: But we wanna make it smarter. So we’re actually going to add artificial intelligence into the designer, we’re actually working on that, right now, so that we can do better predictive management of the connector operation that you wanna call next. We’ll add favorites to it. And so what we’ve made fast, we’re going to even make faster for your development process. Dedicated and connected, right? This is our code word for the integration service environment that you saw at the keynote. So we’ll have a whole session or at least half of the session talking about the integration service environment. But that’s the ability to talk to VNets and having a dedicated stamp for your Logic Apps workload. Testability, so the ability to mock inputs and outputs, being able to have custom triggers that, you know, you can actually put in the input yourself, that’s being worked on right now. Being able to call an action just so you can see what an expression looks like are all coming, as well.

On-prem. So we’re pushing ourselves towards the edge. And we’re going to show that initially with Azure Stack, which is Azure’s offering for being able to run your cloud on-prem. Managed service identity, very cool stuff. So, you know, today, you know, as you go in through these connectors, you have to provide a particular identity. Usually, it’s your user identity. You can do other service identities. But now with managed service identities, you can give your Logic App an identity. And then you can, you know, especially as you’re doing backend processing, you don’t wanna use personal identities, you wanna use the identity of the system that you’re talking to. So with MSI, Logic Apps can now have its own identity. And then you can give permission to that Logic App to access one of your systems. Request triggers. So request trigger takes a SAS key, and we are working on the ability for it to take a bearer token so then you can do all auth on that requesting point as well.

Output property obfuscation. That’s important because sometimes you wanna have, you know, data that comes into the monitoring view, everything gets exposed as, you know, for great purposes so you can have insights as to what’s going on. But sometimes there is sensitive data that goes to that through your Logic App and you want to not have your operators look at that, or anybody look at that. In cases of healthcare or finance, you wanna be able to kind of black-line those things out. So we’re going to add the ability to have property obfuscations so that you can mark those properties as not being exposed in that way. They stay encrypted on the store and then don’t get shown in those monitoring views.

Then once we have that, then we can have Key Vault support. All right, Key Vault manages your secrets. And so one of the blocking capabilities for supporting Key Vault so that you can then pass secrets around was this obfuscation of these properties, so then that will follow soon after. So then you can use Key Vault to pass it to, for example, our most popular connector, our or HTTP connector, right? So you’re doing more HTTP calls, and you wanna hide those secrets in your designer as well. Is that enough now?

Together: No.

Kevin: No? Okay, it is enough. So everybody always wants more. You guys are so greedy. So that’s the intro to Logic Apps. Hopefully, everybody feels like they can be empowered to build intelligent, powerful integrations so that you guys can be the superheroes at your companies. Okay, thank you.

Download Presentations

Fill the form below to get all the presentations delivered as a single zip file in your mailbox.

please wait …..

Interested about future events?

please wait ...