>> Hey friends. You love Logic Apps I loved Logic Apps,
but I also love having full control of
my environments and all the security that it brings.
Integration service environments are an offering for
hosting your Logic Apps with stuff like dedicated compute,
private static upon IP addresses and all that good stuff.
Kevin is here to show us how they work today on Azure Friday.
[MUSIC]
>> Hey friends, I'm Scott Hanselman and
it's another episode of Azure Friday.
I'm here with Kevin Land we're going to talk about
integration service environments. How are you sir?
>> I am great, how are you doing?
>> I'm feeling pretty good. I like learning about new things.
I've been doing some Logic Apps and now you've come
with some new stuff that's going to
make my Logic Apps even better.
>> Yes. So, Logic Apps is our serverless offering,
allowing you to build workflows up in the cloud that
do integration not only in the cloud but on-prem.
So, one of the great things about
Logic Apps is that it's serverless,
and so that provides a lot of things like
micro billing and the ability for you not
to have to worry about
the infrastructure and how it gets scaled out in the cloud.
It also give you the ability to talk to entities on-prem,
but you needed to install something called the
on-premises data gateway which
was a reverse proxy using
relay as the backbone for that communication,
and that was very convenient for some folks.
But guys who have expressed routes or have
tight security constraints in their Network
where they want to punch holes into their firewall going back out,
freaks some of the security guys out.
They say hey, how can I get my Logic Apps to talk to
my very important private On-Prem entities,
and I've invested in this express route,
how can they take advantage of those two things?
>> I see. So, you really what you want is to be
all in the same subnet or have a clear route between
each other if not in the same subnet darn near close.
>> In the same VNet.
>> The same VNet pardon me,
and a reverse proxy isn't
the most elegant or secure way to do that.
>> Right, because then you have to install a machine inside of
your datacenter or your on-premises to then connect back,
and people don't want to just like I'm going to the cloud.
Why do I want more machines?
>> Right. So, I want the power of Logic Apps at
my own personal space that can talk to all of my on-premise stuff.
>> Yes and sometimes,
some financial institutions or
hospitals or other more paranoid types of
customers want to make sure that their Logic Apps are
running in their own environments
and have their own private storage.
So, we've come up with an integration services department to
host your Logic Apps running
inside of your VNets all for yourself.
>> I've used App Services,
it's one of my favorite things.
I like App Service Environments and I recommend that to customers
who as you say just because you're
paranoid doesn't mean they're not after you.
You want your own space.
You want to know that there's
no noisy neighbors are any issues like that
even though it's not really a problem with Azure
you want dedicated hardware.
So, there's dedicated space for your Logic Apps.
>> That's right. So you can have the dedicated CPUs
and storage just for you and you have
to worry about nobody else being right next door to you.
>> Very cool. So, you got a little demo for me?
>> Yeah. Well, first I was going to just go through
one or two slides so we can get
a conceptual overview of what it is.
So, we've talked about that VNet connectivity where we
inject these components into your VNet.
So, then you have direct line
of sight to the components that you're
talking to but your SAP system your VM.
Also because you're in that VNet,
you get to talk to other Azure entities
that are participating in that VNet.
>> Okay.
>> So, Azure now offers capabilities for Blob and Cosmos DB,
for example Time Service endpoints.
And so you can lock down your
traditional PaaS services but now into a VNet,
and so now we can communicate with all those through
the VNet connectivity in an Integration Services Environment.
We also talked about the dedicated computing isolated storage,
but with this, now you can have
more control over your endpoints. You can lock that down.
You can have private static outbound IP.
So, then if you wanted to do even
more constraints within your VNet,
we give you more of that control.
The other thing is that on one hand,
it's great that serverless gives
you the ability to have micro billing,
you only pay for what you consume,
so that allows you to deal with the peaks and valleys,
but some customers really liked that predictable pricing.
Just tell me what it's going to cost at the end of the year.
I know exactly what I'm going to get charged for that and I
can go party on that and not have to worry about,
I used a lot of Logic Apps today and it's going to
cost me this much this month but you know something less [inaudible].
>> Right, for some customers that
burstable costing is a great thing but people just want
to rent the parking spot and know that it's always
there and available for whoever they want to park there.
>> So, as we think about our Logic Apps offering,
we have the PaaS service which runs your Logic Apps,
we have these things called connectors which abstract
all the different services you need to talk to
Salesforce or SAP system or an FTP server,
and so what we've done is we've taken
the runtime portions and put that
into the ISE which is the Integration Service Environment,
and that's what gets injected into
your VNets which then has access to your entities on-prem.
>> Interesting.
>> Then what do you get with that integration service environment?
With that initial stamp,
you'll get 75 million action executions per month,
and if you want you can scale that up for
an additional 50 million executions
per scale unit that you can go ahead and auto-scale.
>> It's a huge amount.
>> Its monstrous, and there
we have some customers doing quite a bit
of workload on logic apps in our PaaS offering.
So, it's not that crazy to
think about hundreds of millions
of transactions running through that thing.
>> That's amazing. For the kinds
of things that I'm doing that might be overkill,
but it sounds like it can scale
effectively infinitely to any workload.
>> It feels that way. Yes and and we'll scale up.
So, even if that's not enough we can continue to add
scale units to that workload.
Then you also get an enterprise connectors.
So, if you want to talk to SAP or NQ
series that's included into that environment,
so you don't get any extra cost for that as well as
a standard integration account
which allows you to do B2B processing.
So, if you're doing X12, EDIFACT,
AS2 or XML mapping with
XSLT or liquid maps that gets included as well.
>> Forgive my ignorance but are the customers like
the base talky type people.
The people who are going to be most interested in that.
Because a lot of the things that connectors that you described,
I think of as being those kinds of customers.
>> As you think about the classic integration scenarios,
base talk customers are
the canonical professional integrators
and they would utilize a lot of those features.
But now we're seeing the democratization of integration.
So, now we're seeing ad hoc integrator.
So, normal developer says,
hey I want to connect to some system,
but I don't want to have to read all the docs about the APIs
and understand the auth model and the shape of the message.
So, I can use a Logic App to go create
that and then have that connectivity taken care
of for me and then continue and write the code that I
really care about not all like goop that just talks to us.
>> When you say that I feel
seen because that's exactly what you would want to do.
Right? Like we don't want to necessarily
have an entire dedicated team.
We all want to be all full-stack developers,
and being able to do something like this is super powerful.
>> Yeah. Okay so let's go ahead and try it out.
>> Let's do it.
>> Okay. So, the first thing I'm going to do is I'm going to
create an Integration Services Environment,
and I'm going to show you how easy
it is to actually to create that.
So, I'll go ahead and pick it Integration Service Environment,
and I click "Create" and it's going to ask you some questions.
This is very typical questions as you
go through creating any Azure Resource.
First, it's going to ask you for a subscription,
and then a resource group
and I'm going to put it into this clam ISE demo,
then it's going to ask me for a name,
and then a location.
I'll put in west US2.
Then here you can decide to have additional capacity there's
a base unit and you want to start it
right off with a couple additional units.
You can do that later if you want as well,
and then you have to select the VNet
that you want to inject it into.
So, here I'm going to pick this demo ISE VNet.
So, now this is the VNet that we're going to take
our runtime and inject our Logic App into,
and then you're going to have to specify four subnets.
Those subnets have to have,
each has to have 32 IP addresses and then switch a slash 27,
and I already created some of these subnets.
Then that's it. So, I can go ahead and create, I click that.
It checks to make sure that everything looks okay as I
go create that, and then it looks okay.
>> Does this take long to happen?
>> No. Well, at least this part doesn't take very long.
So, this took about two minutes to go create,
but now this will go ahead and bake and this
will take about an hour and a half to go ahead
and create all the entities
that are needed and inject that into your peanut.
>> Because you really are getting your own
personal space to not to
push the analogy too much when we
use the analogy of App Service Environments,
you can make an App Service in a minute
or to make an App Service Environment,
we are dedicating space hardware effectively to you.
So, you're really getting our own personal station,
it might take a bit.
>> What you'll see is that what's that acting as
it's almost as if one or more datacenters is running just for you.
>> Yeah.
>> So, it's like conjuring up
a whole new platform just to run your Logic Apps.
>> Yeah.
>> So, it's not just some VM that's sitting in the back there.
>> Yeah.
>> So, while that's cooking, I already created one.
So, let's go ahead and look at the one that I've already
created so we don't all want to wait an hour and a half.
>> Cool.
>> So, this is what it looks like when you first open it up.
What you'll see in your start screen is that
will tell you how much workload that you're doing.
There's a couple of components.
If you notice from my architecture slide from before,
they were two pieces of the runtime.
One is the Logic Apps Engine runtime
and the other part was the connector runtime.
So, you can see the utilization of
the CPU and memory across the number of nodes that we created,
so we abstracted the CPUs.
So, then as you start using more workload,
you can go ahead and scale that up if you want.
Then what you'll notice on the left-hand side is that
we will also list all the entities that you can load into that,
Logic Apps, integration accounts,
connections to your connectors.
You can create custom connectors that all run in this environment.
Here you see all the Logic Apps that we
have posted to this integration service environment,
but what I'm going to do is I'm going to create a new Logic Apps.
You can see what that experience is like.
So, once I create that new Logic App,
I simply go to "Integration" and "Logic App."
The only thing you need to understand to be able to say, hey,
how do I get this logic app to run in that ice?
So, I'll give it a name, test-file-copy,
and I will put it into an existing resource group.
What you'll see here's these are
your typical datacenter locations,
but at the very top of the list,
there's a list of integration service environments.
So, instead of putting it into a datacenter,
you put it into your
integration service environment that you created.
>> Which is interesting because when you gave that analogy,
it's almost we're making our own datacenter for you.
>> Right.
>> I say, oh wow. You must be overstating it a little bit,
but then here you are in the list of
locations almost as if you have your own datacenter,
because you really have your own personal space.
>> That's right. It's all yours and it's
cooking your Logic Apps is going to run.
So, very quickly it's going to go ahead and create that Logic App,
and now that logic app will be running in that environment.
So, what you'll see when I create
that Logic App is
that we'll have an attribute up here that's letting you know.
>> This isn't Logic App Lite, this is logic Apps.
>> This is just Logic Apps
>> Once I already know how to use.
>> Exactly how it runs in the serverless offering,
it runs in the same way in this environment.
>> Awesome.
>> So, you'll see this attribute for
integration service environment and it's
pointing out that ice that we had created.
So, when I go ahead and create a Logic App,
one of the things that you'll notice
is that we have a special set of
connectors that run inside of that ice.
So, that will allow you to connect
to your entities that are On-Prem.
So, I already have in that VNet a
couple of VMs that are running in those VMs,
one VM I have an SFTP server,
and then also I have a blob storage that has
a service endpoint that is connected to that VNet as well.
So, now I can start connecting those two things together.
So, before I couldn't access that,
that's by design that blog because it was closing that VNet.
So, I'm going to go ahead and add a step,
and what you'll see is that as I go ahead
and look at my convector zone would be this little tag called ICE.
That's letting you know that that's
an ICE connector and that's running inside of that environment,
and now can see any of those entities that's inside that VNet.
>> It's just very natural there because they're in the same VNet.
I used the word subnet because I
don't know a lot about networking,
but they are networking route
accessible within that address space.
>> Yes. If you have multiple VNets on your on-premises,
then you can create routes across those VNets and
gateways and bridges and those things
that can communicate across those as well.
>> Fantastic. Software defined networking is
absolutely revolutionary and makes these things possible.
>> It used to be really hard,
now it's super easy.
So, one of the things we can go do is now look at our logic apps.
So, I'm going to go ahead and list the blobs in this was before
an inaccessible storage. Right here.
>> Is it private to this VNet storage?
>> Yeah. What you'll see then is that once I do that,
this is going to list all the blobs,
now for every blob,
I want to move that into an SFTP server.
So, there are a lot of banks and other corporations that have
their private SFTP servers that
communicate intra bank communication.
So, yes I have a blob and I want to
make sure that those files get pushed around.
So, I'm going to go ahead and copy those files.
>> It's so amazing that I could talk to a mainframe in ANS 400
I did banking retail online banking 15 years ago,
and the amount of work that was required to do
the kinds of things that you're describing
would take weeks or months of work.
>> Months.
>> Now you can prototype it in
a weekend and lock it down in a week.
>> We have all those old classic connectors as well as you're
talking to an ADB2 systems,
an AS2, and AS4 400.
>> The amount of custom C++ code that I did
to try to solve these problems.
It's fantastic. We're standing on the shoulders of giants.
>> In my old days,
I had to write a deck VLAN abstraction layer
to communicate to Windows NT 3.51 machine.
>> Good times.
>> So, I'm going to "Create File,"
and then Logic Apps
is smart enough that one of the things that
has the intelligence to say,
"Oh, I saw that you had a collection of blob."
So, I'm going to go ahead and put that int for each for you,
so it's doing predictive programming.
One of the things we did do besides things like this is we
added artificial intelligence into the connector picker,
so based on the previous actions that you
have that predicts which actually you probably want to do next.
We let the scope, we save it, and then we can run it.
So, just in a few minutes,
we're able to go, once
we have our ICE created it'll
take a little while to get that created,
but create a Logic App that goes ahead and reads from
a service endpoint on a blob store,
takes that file, and then pushes it out to an SFTP server.
>> All done in a private space.
>> All done in a private space only you are
working on that and nobody else gets to see that.
>> Fantastic. So, if I understand
Logic Apps now and I've doing Logic App work,
I can go and explore this option that's available to me now,
and check it out, and I can mix and match and
use these things however my VNets
your set out power my environment.
>> Correct.
>> Fantastic.
>> Yeah.
>> All right. Well, I am learning all about
integration services environments here on Azure Friday.
[MUSIC]