►
From YouTube: Bot Composer in Microsoft Teams
Description
In this 11-minute developer-focused demo, Bob German shepherds viewers through the creation of a simple bot that’s installed in Microsoft Teams and calling Microsoft Graph within 15 minutes! Step-by-step - Name your bot, add a trigger, use ngrok to make bot work in Teams, register bot, create an app (in App Studio), install bot locally, connect it to Microsoft Graph, create trigger to respond with person’s title from profile, ask question in Teams! This PnP Community demo is taken from the Microsoft Teams community call – March 2021, recorded on March 16, 2021.
Demo Presenter: Bob German (Microsoft) | @Bob1German
Supporting documents:
• Repo - Microsoft Bot Framework Composer | https://aka.ms/BotComposer
• Documentation - Bot Framework Emulator | https://aka.ms/BotFwkEmulator
• App - Download & setup ngrok | https://aka.ms/ngrok
• Documentation - Instructions to register your bot and an application that can call the Microsoft Graph | https://aka.ms/BotBuilderAAD
Stay connected:
• Twitter https://twitter.com/microsoft365dev
• YouTube https://aka.ms/M365DevYouTube
• Blogs https://aka.ms/M365DevBlog
A
So
without
further
ado,
let's
just
jump
right
in
because
of
the
amount
of
time
we
have
I'm
going
to
assume
that
you've
already.
If
you
wanted
to
follow
along
with
like
the
recording
of
this-
and
I
will
make
a
more
in-depth
recording
at
some
point,
you
need
to
install
a
bot
composer,
the
bot
framework,
emulator
ngrok,
which,
if
you've
worked
with
bots.
A
So
let's
just
do
it.
Here's
the
bot
composer,
if
you've
never
seen
this
before
it
is
available
as
both
a
desktop
application
and
as
a
web
service.
So
you
could
install
it
on
your
own
web
server.
If
you
want
I'm
going
to
make
a
brand
new
bot
from
scratch
and
I'll
go
ahead
and
give
it
a
name-
and
it's
just
a
very
simple
little
bot
and
okay-
and
this
is
what
the
composer
looks
like.
So,
if
you're
familiar
with
bots
at
all,
underneath
of
the
first
simple
bot,
that's
the
bot.
A
There
is
a
dialogue
called
simple
bot
and
a
greeting
inside
that
dialog.
The
first
thing
I'm
going
to
do
is
to
simplify
it,
I'm
just
going
to
go
over
to
the
regex
recognizer.
This
is
what
recognizes
what
the
user
means
when
they
type
something
the
default
is
luis,
which
is
a
great
choice,
but
for
the
purposes
of
a
very
quick
demo,
and
also
not
requiring
you
to
stand
up
louis
necessarily
just
going
to
use
regex
here
and
notice
the
greeting-
and
this
will
look
familiar
to
people
who
have
used
other
low
code
tools.
A
It's
just
going
to
loop
through
this
is
a
this
is
actually
triggered
by
a
thing
called
a
conversation
update.
So
whenever
anyone
enters
or
leaves
the
conversation,
it's
going
to
loop
through
all
the
members
of
the
conversation
and
send
them
all
a
greeting
message.
So,
let's
add
another
trigger
here
and
this
trigger
is
going
to
be.
I
recognized
an
intent,
and
just
the
word,
how
are
the
word?
How
will
trigger
it?
It's
just
a
super
simple.
I
just
want
to
get
something
going
kind
of
hello,
world
type
example.
A
A
So
to
do
this,
I've
already
done
the
registration.
As
I
mentioned,
you
can
see
that
same
ngrok
url
is
there
at
the
top
of
the
screen,
also
there's
the
app
id
and
the
connection
name
that
we
need
that
we're
going
to
need
for
the
for
the
bot
composer
and
then,
if
I
go
into
this
application,
which
is
the
application
that
represents
the
bot,
I
also
had
to
create
a
client
secret
and
those
only
show
up
once
so
it
kind
of
like
right
after
you
create
it.
A
You
have
to
copy
it
somewhere,
safe,
and
so
that's
the
other
thing
that
you'll
need
for
bot
composer.
Okay,
so
our
bot
is
registered.
Let's
go
back
to
the
bot,
I'm
going
to
go
into
the
tools
and
paste
in
that
app
id
that
I
saved
before
and
then
I'll
put
in
that
app
password.
So
you
do
want
to
store
this
somewhere
safe.
As
you
can
see,
I'm
trying
to
do
that
here.
A
Do
you
know,
demonstrate
the
best
practices
and
then
I'm
just
going
to
restart
the
bot.
So
that's
going
to
allow
the
bot
to
talk
over
that
particular
channel.
I
also
enabled
the
team's
bot
channel
as
well
all
right.
So,
let's
go
in,
and
the
first
thing
I'm
going
to
do
is
just
paste
in
the
app
id,
which
is
a
quick
and
dirty
way
to
test,
and,
as
you
can
see,
it
works
okay,
great.
A
Nothing
too
special
about
it.
I
do
have
to
fill
in
all
these
fields.
Teams
won't
and
it's
it's
good
teams.
Keep
me
honest
here
can't
like
half
fill
in
this
form.
All
these
different
things
have
to
be
filled
in
or
it
won't
take
the
app,
and
so
you
probably
already
know
that,
but
I'm
just
trying
to
explain
as
we
go
and
we
need
the
developer
information
and
we
need
the
app
urls
and
I'm
just
going
to
use
my
company's
urls
for
that
and
I'll
skip
the
branding.
A
Let's
just
go
right
over
to
bots
in
the
interest
of
time
and
set
up
our
bot.
So
this
is
an
existing
bot.
I
just
registered
it.
I
showed
you
the
registration
right,
I'm
just
going
to
paste
in
that
app
id
the
bot
id
this
one's
for
personal,
only
and
all
right
now,
let's
go
ahead
and
distribute
that
just
going
to
install
it
locally,
and
that
should
do
it
so
that
you
can
see
that
I'm
still
talking
my
conversation
from
the
earlier
test
is
still
there
and
it
is
still
working
awesome
all
right
so
now.
A
So
I'm
just
going
to
go
back
into
my
bot,
I'm
going
to
add
another
trigger,
and
this
one
I
have
a
how
intent,
let's
make
a
who
intent?
Who
am
I,
and
so
all
I'm
going
to
do
here-
is
report
back
a
little
bit
of
information
from
the
user's
profile
to
do
that,
I'm
going
to
call
an
external
resource
and
I'm
going
to
start
with
the
login,
so
the
user
does
have
to
log
in
occasionally
this
is
not
the
new
teams
sso!
A
This,
who
am
I
dialog,
is
running
so
once
the
user's
logged
in
I'm
just
going
to
do
a
get
request
of
everybody's
favorite,
url
graph.microsoft.com
1.0
me
and
I'm
going
to
pass
that
auth
token
in
and
notice
that
I'm
going
oauth.token
and
there's
a
little
syntax
there
that
you'll
end
up
learning
in
the
bot
composer,
which
is
to
expand
that
property.
I
have
to
use
a
dollar
sign
and
squiggly
brackets,
but
not
too
much
that's
fancy
here.
A
I'm
going
to
stick
the
result
in
dialog,
dot
graph,
result
property
and
ask
for
json
coming
back
and
then
the
last
thing
that
I
need
to
do
is
to
actually
output
the
the
result
of
that
graph.
Call
notice
that
I'm
just
going
dollar
dialog.graphresult.content,
because
the
graph
puts
the
actual
profile
information
in
something
called
content
and
then
I'll
show
the
job
title
and
the
user's
display
name
all
right.
So
that
should
about
do
it.
Let's
restart
the
bot,
and
this
should
start
right
up
and
now
I'm
going
to
go
directly
back
to
teams.
A
Actually,
let
me
yeah
go
right
into
teams,
and
I'm
just
going
to
say
who,
who
am
I
and
there
we
go?
We
got
a
login
prompt.
As
I
say,
you
only
get
these
occasionally
now
I
forgot
to
do
something,
so
it's
not
working.
So
let
me
go
fix
that
all
I
need
to
do
here
is
add
to
the
team's
manifest
and
aren't
you
glad
that
teams
is
keeping
us
safe
right,
like
it's
keeping
me
from
going
to
arbitrary
urls
that
might
be
from
somewhere
nefarious
unless
I
put
them
here
under
valid
domains.