>> Microsoft Flow is fantastic for
triggering and executing workflows in many different applications.
Vivian is showing us how you can connect Azure IoT Central,
which is your IoT App application to
Microsoft Flow to trigger flows
when something happens on your devices.
[MUSIC]
>> Hi everyone, this is the Internet of Things show.
I'm Olivier your host and I'm
with Vivian today. How are you Vivian?
>> I'm doing very well. Thank you.
>> Good. So Vivian is here to show us how you connect
an Azure IoT Central Application to the rest of the world, right?
To the big world, and that she's going to use Mike's afloat.
But before that, how about you
introduce yourself and tell people you are?
>> Hi everyone, I'm Vivienne.
I work on Azure IoT Central.
I'm a Program Manager on the team and I'm working
on the extensibility portion of IoT Central.
>> So, IoT Central is our SaaS offering for IoT, right?
So basically, super easy to deploy,
click click click, and you have a website,
and you can play around with create device templates,
create users, roles, dashboards, and so on.
Well, you guys should try it out if you have not yet.
But as you were saying there is an extensibility,
there is a connectivity to the rest of the world, right?
Connect are like collecting data from devices,
extracting insights is not it.
So, today you came to show us how to use
Microsoft Flow for doing that connection. Right?
>> That's right.
>> How does it look like?
>> So, what we're going to do today is we're going to connect
a IoT Central application through
Microsoft Flow to actually a Microsoft Teams channels.
So that when a device fires
a rule in your IoT Central application,
message gets posted in your teams channel.
So that you can visit
all the instances of when the rule was triggered.
So that you can look at the history of the rules being fired.
>> Okay. That's good.
>> Lets begin. All right.
So, here we are in my IoT Central application,
I'm on the homepage.
Let me go to a specific device.
I'm going to go to the rules page.
So, I'll visit this particular device.
So, you can see this is simulated device,
it already has some data flowing through it.
We're going to build a new rule on this.
>> All right. If people want to
follow along while you're showing that.
Actually, you're using one of
the templates that we have in IoT Central,
which is the Contoso app right?
>> That's right. This is the Contoso app template,
and you can basically create a new application and you can choose,
I want a sample Contoso template.
This is exactly what you're going to get.
>> You're going to get these simulated devices that show data.
>> That's correct.
>> Perfect.
>> That's good. All right.
So, let's go to the Rules section.
In the Rule section, you'll notice
there's already a rule that's been created.
I'm just going to create a new one,
I'll change to edit template.
I'll create a new rule.
Let's make a telemetry rule.
Let say, this is a rule
that monitors when the pressure is too high.
So, I'll call it pressure alert.
All right? I'll create the conditions of the rule.
So, this is what defines when the rule is going to be triggered.
I'm going to say, "When the pressure value is let's say,
higher than I'm going to
say I'll give it let's say 20 PSI or something like that."
All right. Then I'm going to save the rule.
This is the interesting part.
So, we're going to add a new action.
>> Okay.
>> You'll see here a list of actions that we have available today.
I'm going to zoom in on the Microsoft Flow one.
This is what launches us into Microsoft Flow.
So, a little bit of a Microsoft Flow.
So, Flow is a service that basically lets you build
wonderful automate workflows across
many different applications and services.
It's a very simple interface,
its drag and drop, no code necessary.
You can use the hundreds of
connectors that are available in the library
today to build these workflows that suit your needs.
>> Yeah. Allow Flow.
Like my first Flow was actually to get
a notification on my phone when my boss is sending me an email.
>> That's its application.
>> That's the one of the templates that we have up there right?
>> Yeah, it's a perfect application of Flow.
You can do it just really easily within a minute,
you've got this automated workflow setup, right.
So, let's jump into this.
So, if I click "Microsoft Flow",
I'm launched into the flow experience here.
So, right now, I'm in Microsoft Flow
and you see that I been launched
into this experience where I
will basically be able to configure the connection.
I'm using a Azure IoT Central connector
that has already been published.
I'll be able to choose a custom actions.
I can choose other connectors that will create this workflow.
>> So to connect this Flow connector to IoT Central,
the credential you using are one of
the users that are registered on the IoT Central app right?
>> That's correct.
>> Are there limitation in terms of,
you have to be a builder and admin or an operator?
>> So, the limitations of this are,
you have to be an AD user first of all.
>> Okay.
>> That's existing limitation,
we're exploring ways around that but you have to be an AD user,
and also in order to build this rule itself,
you have to be administrator or a builder.
>> Or a builder?
>> Or a builder, yes.
>> Okay. Perfect.
>> Yeah. So, if I hit "Continue".
Okay. So, we have the beginnings of our Flow.
Here will have to choose our application,
and we'll have a drop down.
You can enter the idea of the application,
but I'm going to choose the application
by its name, which was Contoso.
I'll pick the rule that I just created,
which is the high pressure alerts.
>> Okay.
>> Let's add a new step, and when we add a new step.
We're picking from various other connectors
that are already published.
>> There are hundreds of them.
>> Hundreds of connectors that are available exactly.
So, I'm going to specifically choose the Teams one item.
I want to go, I want to post a message to Microsoft Teams.
All right. So, I'm going to post a message
to Teams when this rule fires.
All right. I'll have to pick my team ID.
>> So, like for each connectors,
you login into the connectors, then you ID setting.
So that you have access to your channels.
>> Correct. Each connector has its own connections.
So that you are able to pick,
which accounts you to one use with which connector.
>> Makes sense.
>> It nicely segments your connectors so that you don't
have to manage the credentials except on a one-by-one basis.
>> Do we say to Microsoft Flow is free to use.
>> Microsoft Flow is free for,
I think there are limitations but there's a free tier.
>> Yeah. So, building your IoT app like I did
a chores Monitor was
IoT Central and a button for
my kids to make sure to do the chores.
Basically, "Yeah, I'm not paying for Flow."
>> Yeah, there's a free tier and there's
also a nice tier that comes with
your Office 365 subscription or your
Dynamic Subscription and that gives you a couple more flow runs.
It gives you a little bit more but there is a free tier that
any Microsoft account user.
>> Sorry for the interruption.
>> Galleries. Here we go.
So, here I'm going to pick my team ID and I
believe the team that I want to post on is Contoso.
>> Okay.
>> Then I pick a channel ID,
and here I created a device chat channel.
This is where my device is expected or
all my devices are expected to post messages there,
and this part is super-duper cool.
This is where I compose the actual message that
the workflow will send into the teams channel,
and I can pick from a variety
of dynamic content that comes from the actual rule.
So, here I can pick for example, the device name.
So, device name fired.
Rule name, I'm going to pick
a rule name at and I can pick my timestamp with
a value of n and I can
here a specified dynamic content
that is the actual pressure value.
Now, triggered the alert.
So, if I hit "See more",
you'll see one of the items that showed up was the actual value.
>> The actual value.
>> Exactly, it is the value of pressure.
Let's say, this is the entire message that I want to send.
>> Yeah.
>> So now, I'll hit "Save".
>> Yeah. The Flow is deployed, run for you.
>> Yeah. It's called run a custom action,
when IoT Central rules fire,
you can change the name up here.
>> Okay.
>> If I go back.
Okay. So, it takes a moment for everything underneath to setup.
Then, we'll see messages show up in the Teams Channel.
But in the meantime, you'll see that
a new action is automatically shown up in your IoT Central rule.
So, the registration has happened underneath the hood.
So now, whenever this rule is triggered,
we should see a new message in the device chat channel.
>> That shows up.
>> That should show up. Here we go.
So, we have a new message,
and you see this is exactly what we
composed with the dynamic content.
So, it's telling me this device name fired
this rule at this time with this pressure value.
>> Also, its shows as coming from you,
because you were logged in Flow.
>> That's correct.
>> For the Teams connector as yourself.
>> That's correct.
>> What eventually, you can think about it,
and know way to do that like creating
an account specially for
sending data from the IoT Central application.
>> Exactly. You'll notice in the connections pane,
it shows that the person that the account that was
connected to the Teams connector is actually my personal account,
which is why it shows up as me in the Teams channel.
>> This is great demo, love it.
So, this is limitless actually,
once you are in functions,
once you actually trigger Surya likes to flow in there with
all connectors clicking like click
drag click whatever it's super straightforward to do.
>> Absolutely.
>> It can do whatever you want to do in there.
>> You can see actually the library of connectors,
there are many, many connectors out there.
So, if I scroll past,
if I look at your standard connectors.
There are tons and tons of
connectors available that you can choose from.
>> Awesome. Love it.
Thanks Vivian a lot for this demo.
>> Thank you.
>> I hope you liked it. You can check out
some of the links that are below in the description of
this video to learn more and to try out what Vivian
demoed connecting Microsoft Flow to IoT Central.
Thanks for watching, don't forget to subscribe it.
[MUSIC]