Azure Logic Apps

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
14 hours 28 minutes
Difficulty
Intermediate
CEU/CPE
15
Video Transcription
00:00
>> Hello cyberians.
00:00
Welcome to lesson 7.6
00:00
>> of Module 7 of this course titled,
00:00
>> AZ-301, Microsoft Azure Architect Design.
00:00
Here are the learning objectives for this video.
00:00
We'll start out by introducing
00:00
the Azure Logic App Service.
00:00
Then we'll proceed to cover how this service walks.
00:00
Introducing you to the concept of
00:00
connectors, triggers, and actions.
00:00
We'll then look at some of the options that we
00:00
have when we talk about Azure Logic App connectors.
00:00
Then we'll talk about Azure Logic App
00:00
from a pricing perspective.
00:00
Let's get into this. Let's talk about Azure Logic Apps.
00:00
Azure Logic App is a Cloud service
00:00
that helps us to shadow,
00:00
automate, and orchestrate tasks, business processes,
00:00
and workflows when we need to integrate applications,
00:00
data, systems,
00:00
and services across enterprises and applications.
00:00
Now, let's put that in plain English.
00:00
What exactly does that mean?
00:00
This is what it means. Not all applications
00:00
or solutions require writing code.
00:00
Some applications or some solutions
00:00
>> are simply workflows.
00:00
>> For example, do I need to write code if I want to send
00:00
email notifications with Office 365 when
00:00
an event happens in
00:00
another system application on a service?
00:00
The answer to that question is no.
00:00
That does not require me to
00:00
write full-blown codes to achieve that.
00:00
A lot of solutions are just
00:00
moving information from one service to another service.
00:00
It's just integration solutions.
00:00
That's where Azure Logic Apps comes in handy.
00:00
Because Logic Apps comes with a number of
00:00
pre-built connectors so our developers can
00:00
focus on their blocks of code and just
00:00
use the connectors to integrate
00:00
existing systems with one another.
00:00
Let's look at that a little bit.
00:00
Azure Logic Apps has different
00:00
>> pillars that supports it.
00:00
>> Number 1 pillar, it's all about API.
00:00
It has these connectors which are previewed
00:00
API wrappers around different integrations
00:00
with different systems and services.
00:00
It's all server less.
00:00
You don't have any visibility into
00:00
the underlying infrastructure that's
00:00
run in Azure Logic Apps,
00:00
we simply define and
00:00
design our workflows and that's about it.
00:00
It's no code.
00:00
There are ways for us to walk
00:00
and design logic apps with code.
00:00
But in many cases or for many use cases will be
00:00
doing that redesign logic apps
00:00
>> using the visual designer.
00:00
>> It's event-driven.
00:00
It fits right well into
00:00
event-driven architecture where there can be
00:00
triggers and they can be
00:00
actions taken off of different triggers.
00:00
We have a visual designer as I mentioned,
00:00
where we can visually design
00:00
integration between disparate services.
00:00
It's an integration platform.
00:00
It's all about integration of applications and services
00:00
and getting different applications
00:00
to talk and integrate with one another.
00:00
It's all about workflow.
00:00
Let's look in more details at
00:00
>> how Azure Logic App works.
00:00
>> When we create an Azure Logic App resource,
00:00
the key points that we need to know is
00:00
it's built around these things called connectors.
00:00
Now, a connector it's a proxy,
00:00
it's a wrapper around API.
00:00
In other words these are
00:00
pre-built actions and tributes tree guess that will
00:00
pre-build capabilities that have been wrapped around
00:00
APIs that we can simply
00:00
select different options that we want.
00:00
Azure Logic App just ties them together,
00:00
it will make more sense as I carry on.
00:00
Again, the foundation of
00:00
Azure Logic Apps at this fin is called connectors.
00:00
Now, each connector has triggers and actions.
00:00
Some connectors only have actions.
00:00
They do not have triggers.
00:00
Some connections only have triggers and no actions
00:00
while some connectors have both actions and triggers.
00:00
Let's look at that a little bit more.
00:00
Let's take an example of Office 365 Outlook.
00:00
That's a connector that exists in Azure Logic App.
00:00
Now this connector as setting triggers, for example,
00:00
it has triggers that when an email is received,
00:00
when a new email arrives in a shared mailbox,
00:00
when a new email mentioning me arrives,
00:00
when an email is flagged,
00:00
when an upcoming event is starting soon.
00:00
That's not an exhaustive list,
00:00
that's just a sample of some of the triggers
00:00
that disconnect or has beauty into that.
00:00
What that means is they can use any of these event or
00:00
action to lead into another part of my workflow.
00:00
The same Office 365 Outlook connector
00:00
>> has set in action.
00:00
>> For example, it has action to say send an email,
00:00
send an email from a shared mailbox,
00:00
send an approval email,
00:00
updates event and many other actions beyond this.
00:00
Let's take another connector, the Twitter connector.
00:00
The Twitter connector, for example,
00:00
has certain triggers like
00:00
one of the trigger they have is when
00:00
a new tweet is posted and at
00:00
the same time it has certain actions.
00:00
Some of the actions that
00:00
disconnector has is posted tweets,
00:00
retweets, get followings,
00:00
get followers.
00:00
This attribute.
00:00
Let's take the HTTP connector.
00:00
HTTP, for example,
00:00
has a trigger of when the HTTP request is
00:00
received and as an action of invocation HTTP request.
00:00
Finally, let's take an example of Salesforce connector.
00:00
Salesforce is a popular CRM application
00:00
which is Cloud-based.
00:00
It has built in triggers like when a record is created,
00:00
when a record is modified and built
00:00
in actions like create a job,
00:00
creator record, deleted a job, delete record.
00:00
David, where are you getting that?
00:00
Where does all this tie in with Azure Logic Apps?
00:00
Where Azure Logic App means is that I can do
00:00
integration across all these disparate services
00:00
however I want to with
00:00
a combination of actions and triggers.
00:00
For example, I could say,
00:00
whenever a new tweet is posted,
00:00
I want you to invoke an HTTP request.
00:00
Now I'm tying the connector a trigger of Twitter.
00:00
A Twitter trigger that's pre-built.
00:00
I'm tying that into an HTTP action to say,
00:00
when a new tweet is posted,
00:00
I want you to invoke an HTTP request.
00:00
How about another one?
00:00
When a new tweet is posted, send an email.
00:00
I'll need to write code for that.
00:00
I could just tie in those
00:00
workflow together and get that to work.
00:00
Another one. What about when an email is received?
00:00
Create a job in Salesforce.
00:00
Whenever somebody sends an email into an email address,
00:00
I want you to automatically create a job in
00:00
Salesforce that somebody can auction.
00:00
Finally, another one say,
00:00
when an HTTP request is received,
00:00
send an approval email.
00:00
This is what Azure Logic App is great at.
00:00
By the way this is just a simplified explanation
00:00
that I'm giving to you.
00:00
Because the truth is with Azure Logic Apps,
00:00
we can be much more detail.
00:00
We can go tie in action into
00:00
>> another action and then take
00:00
>> parameters from the previous action and then use
00:00
that as input for another action that we are defining.
00:00
We can go into complex orchestrations
00:00
and complex workflows.
00:00
But you get the underlying idea behind this service.
00:00
How many connectors does it have?
00:00
It's a gallery of collectors.
00:00
It has lots of connectors built in
00:00
and the list that you're seeing on the screen again,
00:00
this is not an exhaustive list
00:00
because more connectors have
00:00
been added all the time for a lot of Clouds,
00:00
SaaS-based applications, for a lot of Azure services,
00:00
for a lot of other types of services.
00:00
You can even build
00:00
custom connectors for your own custom applications.
00:00
That's also a possibility.
00:00
Let's talk about pricing briefly.
00:00
When it comes to Azure Logic Apps what
00:00
we pay for is we pay the trigger,
00:00
we pay for the action,
00:00
we pay for connection or the connector executions.
00:00
There are different types of connectors also and
00:00
they have different cost associated with them.
00:00
For example, apart from standard connectors,
00:00
Azure Logic Apps provide enterprise connectors for
00:00
access and enterprise systems like SAP and IBM MQ.
00:00
Those are charged a bit differently.
00:00
By the end of the day what we pay for if we're
00:00
using the consumption-based model,
00:00
we pay for the trigger before
00:00
the action and we pay for the connector executions.
00:00
This brings me to the end of this lesson.
00:00
Thanks very much for watching and
00:00
I'll see you in the next lesson.
Up Next