►
Description
Microsoft 365 & Power Platform weekly call delivered on February 28th.
Three demos delivered in this call: Dynamically Create a Microsoft Teams Meeting using Microsoft Graph, Teams Toolkit Learn Path - Build a bot using Teams Toolkit for Visual Studio Code, and Remotely debug your Microsoft Teams apps from any device using Vorlon.js.
Activities: 10 articles, 1 sample, and 5 conversations released in the last 7 days.
See the blog post for this call for announcement, news and event details. The host of this call was Vesa Juvonen (Microsoft) | @vesajuvonen. Q&A takes place in chat throughout the call.
Agenda
00:00 – Intro
11:35 – Latest updates and news on the Microsoft 365 platform – Vesa Juvonen (Microsoft) | @vesajuvonen
12:13 – Microsoft Teams Platform updates – Surbhi Gupta (Microsoft)
13:18 – Together mode picture
14:31 – Demo – Dynamically Create a Microsoft Teams Meeting using Microsoft Graph – Ayça Baş (Microsoft) | @aycabs
28:31 – Demo – Teams Toolkit Learn Path - Build a bot using Teams Toolkit for Visual Studio Code – Garry Trinder (Microsoft) | @garrytrinder
46:29 – Demo – Remotely debug your Microsoft Teams apps from any device using Vorlon.js – David Rousset (Microsoft) | @davrous
59:50 – Closing
Learn more
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/community/blog
• Microsoft 365 Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 Platform Community - http://aka.ms//community/home
• Download invite for this weekly Microsoft 365 Platform community call: https://aka.ms/m365-dev-call
A
B
B
Some
of
those
demos,
are
part
of
a
larger
series
which
are
right
now
ongoing,
and
then
we
have
a
additional
bonus,
cool
demo
coming
as
well,
but
we'll
first
start
with
an
updates
on
the
news
on
Meister
365
platform
and
the
Power
Platform
area,
so
covering
what's
happening
within
this
week
and
we'll
then
cover
the
news.
Well,
that's
just
the
news,
but
also
the
assets,
how
to
get
started
on
things
and
Community
assets.
We'll
also
cover
the
news
from
Microsoft
site
in
different
plugs
and
then
we'll
have
the
update
on
all
of
the
Microsoft
teams.
B
Development
guidance
updates
on
the
documentation.
Then
we'll
have
the
group
photo
in
the
together
mode
taken.
So
for
those
who
are
willing,
you
can
enable
the
camera
and
will
crab
a
key
for
animation
out
of
that
which
will
be
shared
within
the
social
media
after
the
call
and
then
we'll
go
to
the
actual
stars
of
today.
So
we'll
have
Aisha
bash
talking
about
dynamically,
create
Microsoft
teams,
meeting
using
Microsoft
graph,
really
really
cool
stuff
for
sure
Gary
is
going
to
continue
his
series.
I
got
I
guess
by
the
way.
B
His
series
related
on
the
team's
toolkit
covering
the
Microsoft
teams,
toolkit
learning
path
and
this
time
we're
going
to
talk
about
building
a
bot
using
a
team's
toolkit
for
visual
studio
code
and
then,
as
the
last
demo
of
today,
we
have
David
rossin
talking
about
remotely
debug
your
Microsoft
teams,
apps
from
any
device
using
verlin.js,
so
really
really
cool
stuff
on
the
schedule
we'll
get
to
the
demos
and
latest
on
quarter
past.
So
every
single
demo
has
15
minutes
to
go
through
before
we
go
there,
a
few
typical
assets
so
just
recapping.
B
We
have
a
Microsoft
365
platform,
Community
video
channels
available
where
we
publish
all
of
the
demos
from
these
calls
and
all
of
the
other
calls
Community
calls
which
we
are
executing
and
the
core
Community
call
recording.
So
you
cannot
access
the
community
call
a
recording
directly
from
the
chat
go
to
the
YouTube
channel
within
24
hours,
and
you
are
able
to
access
that
from
there.
We
just
recently
created
a
new
LinkedIn
group
for
discussions
and
updates
great
way
of
asking
help
or
sharing
your
findings.
B
B
So
main
idea
here
is
that
you
can
start
from
something
rather
than
from
scratch.
So
you
have
a
reference
point
where
you
have
sample,
which
is
showing
you
how
to
make
ABC
functionality
to
happen
and
then
you're
able
to
copy
that
to
your
own
implementation
and
if
you're
wondering
that
there's
too
many
URLs
to
remember.
Luckily,
there
is
only
one
which
is
akms
forward:
slash
Community,
forward,
slash
home,
which
is
the
home
page
of
all
of
these
URLs
and
assets
and
locations.
B
B
So
it's
not
just
Microsoft
365
platform,
but
also
Power
Platform,
because
we
do
have
Power
Platform
Demos
in
this
course
every
now
and
then
as
well
and
and
in
this
call,
the
presenters
are
always
Microsoft
employees,
so
either
PMS
Cloud,
Advocates
engineers
and
so
on.
Who
are
showcasing
the
Articles
possible
from
a
Microsoft
perspective,
then
our
other
course
are
more
focusing
on
community
demos.
B
Which
is
with
Community
demos
as
well,
so
that's
cycling.
Every
single
Thursday,
7
A.M
Pacific
time
you
can
download
for
current,
invites
from
the
akms
forward.
Slash
Community
for
what's
the
score
and
the
agendas
for
these
goals
are
always
published
on
social
media
and
in
akms
forward.
Slash
Community
forward,
slash
Meetup,
and
this
is
our
meet
application,
where
you
can
sign
up
for
those
updates,
so
you
know
Advance
what
is
going
to
be
covered
within
this
course.
So
you
can
decide.
B
Do
you
want
to
appeal
on
the
live
in
the
call
to
have
a
discussion
in
a
chat,
or
do
you
want
to
check
the
recording
afterwards,
whatever
works
for?
You
is
fine
to
us
now
talking
about
this
course.
We
actually
want
you
to
do
some
of
these
demos,
not
because
we
wouldn't
have
cool
stuff
to
show,
but
it's
actually,
as
you
build
something
you
probably
learn
the
real
world
experiences
on.
Okay.
B
How
did
it
actually
work,
or
how
did
you
use
some
of
the
team's
toolkit
or
SharePoint
framework
or
Power
Platform
capabilities
within
your
actual
implementation,
or
you
may
be
implemented
a
sample?
We
would
love
to
you
to
actually
do
demo
and
that
stuff
within
this
course,
and
we
want
to
actually
give
you
this
opportunity.
So
potentially
you
would
able
to
get
an
MVP
status
or
at
least
get
acknowledged
by
Microsoft
from
your
contributions
within
the
social
media
and
within
the
open
source,
open
source
areas.
B
So
please,
if
you're,
interested
and
sign
up
using
the
akms
for
stress,
Community
forward,
slash,
request
forward,
slash
demo,
so
you
can
fill
in
the
form
we'll
get
you
scheduled
in
the
future
cost.
We
do
have
a
lot
of
assets
to
get
started
on
the
Microsoft
365
areas.
We
have
the
Microsoft
365
developer
program
and
you'll
get
a
free,
E5
developer
tenant.
B
We
are
past
1500
samples
in
our
unified
Microsoft
365
on
core
platform
sample
Gallery,
so
you
can
find
from
there
hundreds
and
hundreds
and
samples
cool
samples
to
get
started.
These
samples
are
all
available
in
a
GitHub.
You
can
use
the
simple
search
query
to
find
them
and
thank
you
David,
probably
on
updating
the
numbers
on
fly
on
the
slide.
That's
a
really
nice
way
of
fixing
things
if
I'm
getting
some
update,
something
but
really
really
great
asset
to
find
the
relevant
sample
provided
by
Microsoft
or
by
by
the
community.
B
A
Awesome
thanks,
vesa
yeah
friends.
Are
you
gonna
help
us
get
to
2
000
samples?
We
hope
so,
but
to
do
that
we
need
to
understand
GitHub.
Well,
sharing
is
caring
is
a
program.
That's
provided
originally
just
to
give
a
lot
of
GitHub
experience,
but,
as
you
can
see,
via
the
topics
and
sessions
it
has
expanded.
A
These
are
safe
space
opportunities
that
are
live
meetings
that
we
get
together
with
you
in
other
MVPs
members
of
the
community
members
of
Microsoft
and
walk
you
through
how
to
accomplish
things
like
perhaps
you're,
not
familiar
with
that
landscape
of
GitHub
and
pull
requests
and
git
clone
and
forking,
and
all
that
kind
of
stuff.
We
will
show
you
and
work
on
it
together
and
it's
a
safe
space.
A
That
means
you
can
ask
any
and
all
questions
don't
need
to
worry
about
it
being
recorded
because
it
is
not,
and
we
will
work
together
and
empowering
you
and
giving
you
that
experience
that
you
need
to
do
more
in
the
community
and
we
thank
you
all
for
joining.
They
are
all
free.
We've
got
more
sessions
scheduled
up
for
March
we're
getting
even
more
sessions
in
March
as
well,
and
as
we
move
into
the
the
rest
of
2023,
you
can
access
these
at
AK
dot.
Ms
slash
sharing
is
caring.
That's
it
back
to
you.
B
Excellent,
thank
you
David
on
that
one
now,
a
few
things
tomorrow,
we'll
start
at
the
hack
together
event,
which
is
focusing
on
microsoftcraft
and
net
development,
and
this
is
a
really
cool
event
organized
with
Microsoft
craft
organization,
together
with.net
organization.
So
you
will
see
it's
got
handsome
and
you
will
see
you
know
Arenas.
You
will
see
Fabian
Williams!
You
will
see
a
lot
of
other
people
presenting
cool
stuff
around
the
Microsoft
graph
and
Dot
net
development.
B
That
starts
tomorrow
on
the
1st
of
March,
and
so
we
highly
recommend
you
to
sign
up
for
that
one
so
every
single
day
something
new,
not
too
much
but
learning
new
things.
What
you
can
do
with
Microsoft
graph
within
the.net
world,
so
really
really
cool
stuff,
quick
recap
also
on
other
events
which
are
coming
this
spring.
So
we
have
the
Microsoft
365
conference
coming
up
on
May,
2nd
to
May,
4th
and
2023
and
and
Jeff
deeper
is
really
the
main
host
here.
B
Here's
the
CVP
president,
actually
nowadays
on
Microsoft,
owning
the
Microsoft
365
collaboration
and
platforms,
including
Microsoft
teams,
SharePoint
OneDrive
and
many
many
other
things
as
well,
so
really
really
great
opportunity
of
hearing
the
latest
from
Microsoft
and
from
the
community.
We
also
have
a
more
european-based
location
which
is
European
collaboration,
Summit
2023
happening
in
Dusseldorf
in
late
May,
so
24th
and
26th
of
May.
B
So
if
you're
based
in
finf
in
Europe
and
you're
not
looking
into
flying
the
us
and
we
got
you
covered,
create
and
big
event
coming
up
as
well
with
30
Microsoft
speakers,
12
Microsoft
RDS,
those
are
regional
directors
and
80
Microsoft
MVPs.
So
a
lot
of
lot
of
opportunities
for
in-person
engagement
and
networking
in
there
as
well.
Now,
on
the
U.S
side,
we
also
have
the
365
educon
organizing
quite
a
few
events
this
year.
So
please
do
take
advantage
of
this
as
well.
B
So
the
echucan
DC
is
happening,
June
12
to
16
2023
and
check
out
the
agendas
there.
The
the
sessions
and
everything
is
already
available
for
you
to
know.
What's
available
there
and
then
the
next
Power
Platform
science
is
actually
happening
in
the
European
Power
Platform
conference,
which
is
happening
at
June
20
into
22nd
in
2023
in
Dublin
I've
been
in
that
menu.
That
venue
is
really
good
and
it
works
really
well
and
Upland
as
a
location.
Travel
location
is
awesome
as
well.
C
Thank
you
website
to
be
serpi,
hello,
everyone.
We
have
two
updates
to
cover.
First,
we've
released
talks
on
changelog
for
developer
portal.
This
new
feature
will
enhance
the
user
experience
by
providing
developers
with
a
more
streamlined
way
to
view
updates
and
changes
made
to
the
team's
developer
portal.
C
Second,
enable
SSO
for
adaptive
card
Universal
actions
in
your
Bot
with
single
sign-on
in
teams
app
users
have
the
advantage
of
using
teams
to
access
adaptive
card
Universal
actions
in
a
bot
after
logging
into
teams
using
Microsoft
or
Microsoft
365
Account
app
users
can
use
your
app
without
the
need
to
sign
in
again.
So
this
is
what
we
had
for
today.
If
you
have
any
feedback
or
suggestion,
please,
post
on
AKA
dot,
Ms
teams,
platform
feedback,
the
link
is
available
in
the
footer.
You
could
also
configure
to
the
RSS
feed
to
get
regular
platform
updates.
B
On
that,
one
really
really
cool
to
see
the
weekly
updates
in
this
site
as
well.
Now
it's
time
then
fought
to
take
a
remote
picture.
So,
if
you're
willing,
you
can
enable
the
camera
and
we'll
grab
a
gif
animation,
50
seats
in
a
house
I'm
hearing
rumors
that
we
will
have
more
seeds
soonish
in
this
to
get
them
out
pictures
as
well.
So
it's
not
limited
anymore
to
50,
but
we'll
see
when
that
will
happen.
A
few
more.
Let's
wait
for
the
Full
House
to
actually
arrived.
B
I
think
we
have
more
than
200
live,
attend
this
again
on
the
call
easily.
It's
just
is
that
already
50
still
a
few
more
still
a
few
more
few,
more
a
few
more
a
few
more
maybe
we're
hitting
the
limit.
Okay
I
will
put
the
recording
on,
and
we
can
say
three
two
one
and,
let's
do
some
hand
waving,
say
everybody
thanks
everybody
once
again,
joining
really
awesome
to
have
you
on
a
call
great
to
see
familiar
faces
and
new
faces
every
single
week
here
as
well.
Excellent,
really
really
really
cool.
B
Thank
you
for
that
excellent.
Now
we
will
grab
a
gif
animation
out
of
that
for
sure
now.
Let's
then
go
to
the
actual
demos
and
the
stars
of
today
so
we'll
start
with
Aisha
who's
going
to
talk
about
creating
the
Microsoft
teams
meetings
using
Microsoft
graph,
and
then
we
move
to
Gary
and
then
David
in
the
end
and
everybody
has
50
minutes.
So
let's
get
moving
Aisha.
D
Awesome
thanks
vesa.
Let
me
share
my
screen.
I
turn
off
my
camera,
but
in
one
point
you'll
probably
see
me
through
ACS
hi
everyone.
Thank
you
for
joining
the
session
for
the
ones
who
don't
know
me.
My
name
is
aichabash
I'm
A,
Cloud,
developer
Advocate
at
Microsoft,
and
today
I
will
be
talking
about
one
part
of
the
series
The
over
the
started,
I
think
at
the
beginning,
or
at
the
beginning
of
February
or
end
of
January.
D
So
my
colleague
Dan
Wallin,
already
delivered
three
sessions
about
this
series
and
in
the
first
one
he
talked
about
how
to
integrate
audio
and
video
calling
from
a
custom
app
into
it
teams.
Reading
in
the
second
one
he
showed
how
to
create
Azure,
Communication
Service
resource
on
Azure
and
last
week
he
went
through
how
to
integrate
ACS
calling
feature
into
react
app.
If
you're
interested
in
diving
into
those
sessions,
you
can
go
to
the
M365
Community
Channel
on
YouTube
and
watch
the
recordings.
D
Today
we
will
talk
about
how
we
can
dynamically
create
a
meeting
in
teams
using
Microsoft
graph,
because
so
far
we
were
just
creating
the
teams
meeting
and
then
using
the
URL
through
ACS
and
also
on
teams.
But
at
this
point
we
would
like
to
leverage
from
Microsoft
graph
to
automate
some
of
these
stuff
and
I
will
just
walk
you
through
quickly.
How
we
can
do
that
and
just
to
let
you
know
next
week.
D
So
in
this
demo
we
see
that
customer
is
requesting
to
join
and
both
of
them
are
in.
The
only
difference
is
that
customer
is
using
the
ACs
custom
app
and
the
agent
is
using
teams
to
join
this
meeting
so
so
far
we're
trying
to
build
this
experience
by
using
Azure
communication,
Services,
Microsoft
teams
and
graph
and
in
the
process,
as
as
you
can
imagine,
we're
consuming
Microsoft
teams
meeting
URL.
So
today
we
will
learn
how
we
can
create
that
meeting
link
dynamically.
D
D
If
you're
looking
forward
to
getting
data
from-
let's
say
popular
apps
on
Microsoft
such
as
Outlook
teams
to
do
planner,
you
can
leverage
from
graph.microsoft.com
and
you
can
change
the
url
such
as,
in
this
case
I'm
logged
in
with
my
demo
account
and
when
I
run.
This
I
can
get
the
personal.
The
person
profile
information
about
me,
but
also
I,
can
change
this
data
by
just
updating
the
URL.
D
I
can
get
calendar
events,
for
example,
while
I'm
doing
that
I
I
get
all
of
the
events
from
my
calendar,
but
also
I
can
create
new
calendar
event
by
just
doing
a
simple
post
request
to
this
URL.
So
the
only
thing
I
have
to
do
is
just
defining.
What's
going
to
be
the
event
details
such
as
name
time
and
so
on,
and
today
we
will
consume
exactly
this
API
to
dynamically,
create
teams,
meeting
URL
in
the
calendar
invite
behind
the
scenes.
D
We
because
we
cannot
get
anyone's
information
without
asking
their
permission.
So
in
this
part
of
the
code,
we
are
just
doing
the
app
only
oauth
so
that
we
are
consuming
Azure,
active
directory
app
to
get
the
registration
and
then
create
graph
client.
When
we
create
the
authorization
provider,
we
will
just
create
the
graph
client
in
the
next
step.
We
are
doing
something
exciting,
which
is
the
graph
call
and
we
defined
start
and
end
time
of
the
meeting,
and
we
are
actually
doing
that
in
this
app.
D
Specifically,
we
are
doing
that
by
using
the
time
at
the
moment
and
then
we're
adding
one
hour
on
top
of
it
as
an
end
time,
and
then
we
create
Microsoft
graph
URL
to
call
in
our
case
it's
calendar,
slash
events
and
we
are
using
user
ID
here
instead
of
slash
me
because
we
want
to
Dynamic
create
this
for
all
the
customer
agents,
not
not
only
one
person,
so
user
ID
might
be
user.
Id
will
be
different
for
each
and
every
agent.
D
So,
after
that
we
defined
the
meeting
event
details
such
as
subject
sort
and
and
time
zone,
and
after
that
we
will
just
send
event.
Data
to
Microsoft
using
the
Microsoft
graph,
client
and
I
will
show
the
real
code
as
well,
but
just
going
through
really
quickly
in
the
react
app
side
when
we
will
get
triggered
which
we
will
get
triggered
whenever
user
effect
hook
runs,
we
we
trigger
that
user
effect
hook
whenever
a
customer
start
on
the
start,
call
button.
D
That
means
that
whenever
someone
click
on
start
call,
then
we
will
call
Azure
functions
which
will
get
all
the
data
from
Microsoft
graph,
so
we
will
trigger
Azure
functions,
which
will
create
teams
URL
to
join
the
meeting
by
using
Microsoft
graph.
And
finally,
we
will
return
the
meeting
link
and
it
will
be
used
by
Azure,
Communication
Service.
Also,
the
same
thing:
our
agent
will
join
by
using
Microsoft
teams.
D
Okay,
let's
get
into
the
demo
I
think
I
have
time
for
that
cool.
So
where
is
my
demo?
Okay,
so
I
have
two
pieces
in
this
demo
and
one
is
my
own
react
app
and
the
other
one
is
azure
functions
just
to
get
started
easily.
I
just
first
want
to
show
you
how
my
app
looks
like
at
the
moment.
This
is
my
react
app
and
you
can
find
the
react.
App
under
acs-2
teams,
meeting
clients
react
and
underneath
you
can
go
to
app
TSX,
and
this
will
be
our
app.
D
The
main
area
for
us
in
this
Dynamic
functionality
is
use
effect.
Whenever
we
trigger
this,
then
we
call
react
app
teams
meeting
function.
This
is
defined
behind
the
scenes
in
that
EnV
file.
Let's
go
and
check,
it
is
defined
as
my
function
HTTP
trigger.
So
whenever
I
click
on
the
join
the
call
button,
then
I
trigger
this
function.
D
Let's
take
a
look
quickly
how
my
function
looks
like
and
if
you're
looking
for
the
server
the
function
as
your
functions
part,
you
can
go
to
server,
Dash,
typescript
and
underneath
you
will
see,
teams
meeting
function
and
index.
Ts
will
be
the
place
you.
You
will
be
seeing
all
the
function
details.
The
only
thing
we
do
in
the
HTTP
trigger
to
be
honest,
is
only
calling
the
graph
function
on
another
folder,
so
we
create
a
new
meeting
by
using
this
function
and
let's
go
quickly
check.
D
What
does
that
function
do
on
the
top
I
already
showed
in
the
slides?
We
have
the
authentication
app
only
and
then
at
the
bottom.
We
are
using
the
graph
client
we
created
on
top
just
to
make
a
graph
call
here.
We
Define
start
time,
which
is
now
and
time.
One
hour
later,
we
create
graph
URL
to
call
user,
slash
user
ID,
calendar
events,
after
that
we
Define
the
details
of
the
event
name
start
and,
and
finally,
we
make
the
graph
call
at
the
end
of
this
function.
D
We
return
the
entire
event,
but
let's
go
back
one
step
and
check
what
we
return
in
Azure
functions
as
buddy
of
the
meeting
we
get
all
the
details
about
the
calendar.
Invite,
including
the
URL
and
one
critical
thing
I
forgot
to
mention-
is
that
when
you're
creating
an
event
you
will
have
to
Define.
This
is
on
the
online
meeting.
True
because,
as
default,
it's
coming
as
false,
and
if
you
want
to
create
this
event,
invite
as
teams
meeting,
then
you
will
have
to
Define
this
as
true
here.
D
We
return
all
the
details
about
the
event,
but
we
only
want
to
get
meeting
that
online
meeting
that
join
URL,
which
is
the
teams
meeting
link,
and
we
pass
this
through.
Our
react.
App
and
here,
as
you
can
see,
link
is
defined
as
response,
and
that
means
that
our
link
is
delivered
until
this
part
just
to
be
consumed
by
ACS
feature
in
our
react
app.
So
this
is
how
our
app
code
looks
like,
and
we
already
have
the
link
to
share
with
you.
You
can
take
a
look
and
try
by
yourself
too.
D
Let
me
show
you
how
the
app
the
actual
app
looks
like
it
runs
on
localhost
3000
and
you
you've
seen
that
our
functions
are
running
it
behind
the
scenes
as
well.
So
the
only
thing
for
us
at
this
moment
is
just
to
run
the
app
and
test
out
if
it
will
create
the
calendar,
invite
with
the
teams
URL,
so
our
agent
and
the
customer
can
meet
in
the
same
link.
D
D
And
see
that
our
guest
is
here,
I
will
admit
it,
and
both
of
us
will
be
here,
live
yay.
So
behind
the
scenes,
the
only
thing
we
did
is
we
created
the
teams
meeting
link
dynamically
by
using
Microsoft
graph
so
that
we
don't
have
to
go
to
the
calendar,
create
the
invite
copy
paste,
the
link
for
ACS,
so
on
so
forth.
D
So
everything
is
automated
and
finally,
I
don't
want
to
miss
the
opportunity
to
share
all
the
resources
because
usually
I
miss
this
part
I'm,
always
out
of
time,
if
you're
interested
in
trying
this
tutorial.
The
second
link
here
is
the
GitHub
repo,
and
it's
there's
also
tutorial
available
step
by
step.
You
can
check
out
our
repo
and
take
a
look
at
the
solution
as
well
as
you
can
follow
the
tutorial
to
complete
the
entire
sample
built
from
scratch.
D
If
you're
also
interested
in
other
Microsoft
cloud
integration
scenarios,
then
Walden
and
I
work
on
different
types
of
scenarios
and
it's
available
under
ak.com
Microsoft
cloud
and
there's
also
samples
repo
available,
which
is
a
third
link,
and
if
you
are
new
to
ACS
and
if
you
like,
the
UI
we
use
in
the
react,
there's
actually
a
library,
you
can
leverage
the
fourth
link,
aka.ms
acs-ui,
Dash
Library.
You
can
find
all
the
goodies
for
the
UI
and
use
them.
D
It's
really
easy
to
call
resume
and
if
you're
new
to
functions,
there
are
different
types
of
functions
in
this
example.
I
use
HTTP
trigger.
But
if
you
want
to
learn
more
what
types
of
functions
available
other
than
what
we
used,
you
can
also
check
Azure
functions.
And,
finally,
if
you're
new
to
Microsoft
graph,
the
graph
Explorer
is
the
best
place
to
discover
graph
and
if
you're,
a
dotnet
developer,
we
are
waiting
all
of
you
to
join
hack
together,
starting
from
tomorrow,
don't
forget
to
register.
D
B
Excellent,
that
guy
shot
really
really
cool
stuff
and
a
great
demo
really
really
awesome
demo
just
showcasing
the
value
here
now.
Let's
then
jump
to
Gary's
screen
and
we're
going
to
talk
about
teams
toolkit
learning
path,
moving
forward
within
that
series,
I
think
we
are
in
module
two
or
three
two
okay,
because
we
did
reschedule
some
of
this
stuff
at
some
I'm
so
confused.
So
you
know
which.
B
F
Great
so
as
as
Vasa
just
mentioned
yeah,
so
this
is
part.
Two
of
a
series
today
is
build
a
bot
using
teams
toolkit
for
visual
studio
code.
My
name
is
Gary
trinder
I'm
A
Cloud
developer
Advocate
at
Microsoft
foreign,
so
like
I
mentioned,
this
is
part
of
the
learning
path.
The
learning
path
is
build
and
deploy
apps
for
Microsoft
teams,
using
teams
toolkit
for
visual
studio
code.
F
It
is
live
in
Microsoft
learn
if
you
want
to
go
check
out
that
now
use
the
the
short
link
at
the
bottom,
which
is
aka.ms,
slash,
learn,
slash
teams
talk
it
so.
Last
week
we
covered
just
getting
started,
so
that
was
going
through
a
team's
toolkit
for
visual
studio
code.
How
you
could
install
it
and
install
sorry
create
a
new
project
from
the
the
samples
Gallery.
F
So
if
you
didn't
watch
that
that
should
be
available,
if
not
now
it
will
be
soon
on
the
Microsoft
365
Community
YouTube
channel
this
week,
we're
going
to
be
covering
building
Bots
and
then
for
next
week
we
will
be
covering
building
tabs.
Then,
how
teams
JavaScript
library
integrates
with
some
of
the
projects
as
well
and
finally
we're
going
to
go
through
how
to
deploy
and
publish
your
app
to
to
your
team's
tenant,
using
visual
teams
toolkit
for
visual
studio
code.
F
So
today,
like
I
mentioned
we're
going
to
cover
building
Bots
what
I
want
to
do
quickly?
Just
a
quick
recap.
If
you
didn't
see
the
session
last
week,
where
we
covered
getting
started
with
teams
talk
it
teams
toolkit
is
a
visual
studio
code
extension
that
enables
you
to
build
and
debug
and
deploy
teams
apps
right
from
Visual
Studio
code.
So
if
you're
a
JavaScript
developer
or
typescript
developer,
and
you
run
it
on
and
the
different
operating
systems
as
well,
Windows
and
Mac
and
then
yeah.
F
This
is
a
tool
that
you
can
use
to
to
build
your
team's
apps.
However,
there
is
a
another
flavor
of
teams
toolkit
as
well
just
to
mention
so
it
is
built
into
Visual,
Studio
2022.
So
if
you're,
a
net
developer
using
c-sharp
and
on
Windows,
then
definitely
check
that
out
as
well,
but
for
for
this
series,
we're
just
covering
teams
toolkit
for
visual
studio
code.
F
Okay,
so,
let's
get
into
building
bots.
So,
first
of
all,
I
guess
what
is
a
bot?
So
a
a
bot
is
a
a
capability
within
a
teams
app
that
provides
you
with
a
conversational
interface
to
basically
be
able
to
create
apps
that
can
simplify
and
automate
repetitive
tasks.
Things
like
ordering
you
could
go
to
a
bot.
You
could
create
an
order,
put
your
details
into
an
interactive
card
that
could
be
returned
back
to
you
and
then
carry
on
with
with
your
day
nice
easy
way
of
interacting
with
a
bot.
F
It
could
be
something
that
uses
natural
language
and
is
something
more
like
chat
GPT.
It
could
get
that
advanced
or
it
simply
could
be
a
mechanism
as
well
to
notify
members
in
your
organization,
employees
of
when
they
need
to
do
something.
So
you
can
actually
send
proactive
messages
into
a
a
bot
chat
as
well,
and
that's
great,
for
you
know
needing
some
action.
It's
not
all
instigated
by
by
an
end
user.
At
the
the
system
can
can
send
messages
out
to
users
as
well.
F
A
Bots
can
be
used
across
Microsoft
teams
so
and
the
screenshot
in
front
of
you-
and
this
is
a
a
personal
app.
So
this
is
a
a
bot
that
you
can
use
and
interact
with.
There
are
other
places
that
you
can
put
them,
so
you
can
put
them
in
a
a
group
chat.
You
can
also
put
them
in
a
team
Channel
and
also
into
a
team's
meeting
as
well.
So
you've
got
lots
of
places
where
you
could
potentially
add
a
bot
into
your
workflow,
improve
communication
and
speed
up
efficiencies,
run
meetings
better
yeah.
F
These
can
be
used
in
in
all
those
different
areas
and
I
mentioned
with
the
notifications
as
well.
So
nice
way
of
being
able
to
call
people's
attention
to
maybe
perform
a
task
is
when
a
message
is
sent
into
teams
to
the
bot.
You
get
a
nice
toast
notification
there
that
you
can
click
on
it
and
go
straight
to
that
message
and
then
you
know
act
upon
what
whatever
is
is,
is
needed.
F
So
we
talked
about
how
this
bot
could
send
a
proactive
message
to
a
support
engineer
about
a
critical
incident,
so
this
could
be
something
that
is
in
a
support
system,
an
external
signal
that
happens,
and
we
want
to
trigger
a
message
to
go
into
teams
to
that
that
support
engineer
to
remind
them-
or
you
know,
actually
again,
it
could
be
a
critical
incident
to
actually
take
some
form
of
of
of
action.
Now,
there's
a
few
things
that
you
need
to
actually
develop
a
a
bot
for
teams.
F
The
first
thing
you're
going
to
need
is
a
web
server,
so
this
is
going
to
be
where
your
your
code
actually
runs.
This
way
you
bought
logic,
it
is
going
to
be
running,
you
need
an
Azure
bot
service,
and
so
this
is
the
service
that
is
you're
going
to
interact
with
from
the
code
side
that
is
actually
going
to
send
messages
into
teams
and
you'll
receive
messages
back
as
well.
F
And
finally,
we
need
a
Microsoft
teams
app
package.
So
this
is
the
app
package
that
we're
going
to
deploy
into
teams.
It's
going
to
tell
teams
that
this
app
contains
a
a
bot
and
all
of
the
necessary
information
that
teams
needs
to
be
able
to
to
serve
that
that
bot
in
the
user,
interface
and
users
be
able
to
actually
install
that
and
and
use.
F
F
We
need
the
tunnel
that
sits
in
between
that
is
going
to
basically
be
the
the
the
the
the
go
between
the
middleware.
If
you
like,
between
our
locally
running
code
and
the
the
bot
service
running
in
azure,
we
need
our
teams
package,
which
goes
into
teams
so
that
can
can
actually
be
used,
and
then
the
bot
service
and
teams
are
going
to
interact
the
messages
they're
going
to
get
from
our
local
web
server
through
the
tunnel
to
Azure
bot
service
and
then
into
teams
into
locations
where
that
that
plot
is
installed.
F
So
how
does
teams
talk?
It
actually
help
us
here.
Well,
it's
provides
a
number
of
steps
for
us
to
to
get
up
and
running
very
quickly,
and
so
when
we
create
a
bot
using
teams
toolkit
and
we
hit
the
F5
button,
it's
going
to
do
a
number
of
things
for
us
and
that
we
don't
have
to
do
and
speeds
up
the
development
time
massively.
So,
firstly,
it
verifies
and
installs
we've
got
all
the
prerequisites
on
our
machine.
It
starts
an
instance
of
the
ngrok
HTTP
tunnel
service.
F
It
creates
our
Azure
ID
app
registration
for
us.
It
creates
the
Azure
bot
Service
registration
for
us,
then
compiles
all
the
bot
code
starts.
The
Local
web
server
generates
that
team's
app
package
deploys
that
app
package
to
teams
starts
debugging
session
and
then
finally,
it
opens
up
a
browser
window
that
allows
us
to
go
to
the
team's
web
client
and
actually
install
the
app
and
then
use
it
straight
away,
and
that's
all
from
just
one
press
of
a
button
which
is
handling
a
lot
of
setup
and
configuration
behind
the
scenes.
F
So
let's
talk
about
how
we
can
trigger
this
proactive
message:
once
teams
talk
it,
it's
got
everything
set
up,
so
we
have
our
web
server
and
we
have
a
client
and
that
client
is
going
to
send
a
HTTP
post.
Our
our
web
server
is
going
to
intercept
that
message.
It's
going
to
send
that
up
to
the
Azure
bot
service,
which
is
then
going
to
send
that
message
into
teams.
What
does
that
look
like?
F
Well,
it
just
looks
like
any
normal
HTTP
post,
a
couple
of
examples
there,
so
you
can
either
use
Powershell
or
curl
to
just
send
a
a
post
request
into
into
your
your
local
web
server
and
Trigger
the
message
so
we're
sending
a
message.
We
can
send
text
or
you
can
send
an
Adaptive
card.
Quick
refresh
you.
If
you
don't
know
what
adaptive
card
is.
So
this
is
a
declarative
way
of
Designing
interactive
cards
using
Json
schema.
F
So
basically
we
can
use
the
Adaptive
cards
approach
to
combine
our
data.
Combine
our
templates
generate
a
card
and
send
that
in
our
message.
So
how
does
that
look
from
the
code
side?
So
this
is
the
code
that
is
given
to
you
in
the
in
the
template
so
to
just
explain
what
this
code
is
doing.
This
is
using
teamsfx
SDK,
which
is
aims
to
make
bot
development
much
easier.
F
F
First
is
going
to
accept
a
notification
template,
so
this
is
just
a
Json
file
with
the
Adaptive
card
template
and
then
for
the
render
we're
going
to
pass
in
a
data
object.
So
this
has
the
title
app
name
and
description
and
notification
URL.
The
Adaptive
card
will
have
placeholders
in
there
that
we
can
inject
the
values
into
along
Financial
way.
To
point
out
as
well
is
that
the
Target
that
we've
got
back
actually
provides
type
to
us
as
well?
So
we
can
actually
understand.
Well.
Is
this
bot
running
in
a
personal
context?
F
So
once
we've
actually
rendered
the
card,
we
then
send
the
card
through
to
teams
using
this
send
adaptive
card
method,
that's
provided
on
the
installation,
Target
and
then
finally,
we
just
provide
a
response
like
you
would
do
with
a
Azure
function
quickly
cover
the
different
Target
types
like
I
mentioned.
So
we've
got
a
couple
of
example,
a
few
examples
here,
so
we
can
Target
a
a
channel.
F
We
can
Loop
through
channels
we
can
Loop
through
the
members
of
those
channels.
We
can
also
do
group
chats
as
well
again
looping
through
the
members
of
those
group
chats
and
actually
sending
messages,
or
we
can
actually
identify
individuals
and
send
messages
to
to
individuals
based
on
their
UPN
or
email
address
are
a
number
of
members
as
well.
F
So
with
that,
let's
jump
into
the
demo,
so
I've
got
teams
talk,
it
Visual
Studio
code
running
here,
I'm
going
to
create
a
new
app
click.
The
create
new
teams,
app
and
I've
got
three
options
for
Bots
now
I'm
going
to
create
a
notification
bot
here
it
gives
us
a
few
options:
I'm
going
to
choose
a
HTTP
trigger
running
on
Azure
functions
and
use
JavaScript,
which
is
the
default
location
and.
G
G
F
So
teams
toolkit
has
created
our
app
if
you've
seen
Azure
functions
before
this
should
be
quite
familiar,
but
here's
the
code
here
the
HTTP
trigger
code
that
I
showed
in
the
slides.
This
is
what's
going
to
be
executed
when
we
run
this,
and
so
let's
run
that
now,
I'm
going
to
open
teams,
talk
it
in
here,
I'm
already
logged
in
to
my
tenant.
So
I'm
now.
F
So
we're
going
to
see
all
the
steps
that
teams
talk,
it
provides
us
with,
like
I,
said
before
it's
going
to
go
through
and
it's
going
to
install
lots
of
dependencies.
It's
going
to
check
for
prerequisites,
so
it's
checking
that
Azure
functions
is
there
and
engrock
is.
Is
there
as
well
and
it's
making
sure
that
we're
all
authenticated
and
everything
is
okay?
So
what
it's
doing
now?
Is
it's
just
quickly
installing
the
npm
packages?
F
F
So
that
has
set
set
up
the
the
bot
and
then
I
can
come
into
Powershell
and
I
can
send
a
post
request.
So
this
could
be
anything.
This
could
be
another
web
service,
it
could
be
a
postman
and
there
it's
triggered
the
message.
So
it's
rendered
the
Adaptive
card
in
there
with
a
a
button,
and
that
is
how
quick
it
is
to
create
a
bot
using
teams
toolkit
for
visual
studio
code,
lots
of
resources
available
to
you
for
be
able
to
extend
this.
F
H
I,
don't
have
any
slides,
so
my
name
is
David,
so
I
will
show
you
on
the
some
the
project
in
Action
a
bit
of
code
I'm,
a
principal
program
manager
working
on
the
team's
toolkit.
So
thank
you
Gary
to
show
what
we
are
working
on
and
the
easiest
way
to
contact
me
is
to
discuss
with
me
on
Twitter
at
Dave
Rose,
which
is
also
my
Microsoft
areas.
H
So
I'm
working
on
the
toolkit
on
my
side
and
I
was
thinking
about
the
next
step
to
help
you
building
application
for
mobile.
So
I
don't
know
if
you
follow
the
recent
news,
but
we
announced
that
we
are
officially
supporting.
You
know
apps
on
Android,
for
instance,
so
you
can
build
a
tab,
app
a
personal
app
for
instance,
and
view
it
on
your
Android
smartphone,
but
also
it
it.
You
know
it's
it
comes
on
iPhones
and
on
and
maybe
in
the
future.
H
H
So
I
was
trying
to
think
you
know
as
a
PM
for
the
next
stage
to
help
you
on
how
to
improve
the
debugging
of
those
apps
on
like
an
iPhone,
for
instance,
from
a
Windows
PC,
and
we
know
that
they're
beginning
an
iPhone
is
probably
the
most
painful
one,
because
normally
you
need
a
Mac
to
do
it,
plus.
The
fact
that
you
cannot
today
debug
attach
the
debugger
on
the
team's
apps
on
iPhone.
H
So
you
have
really
no
ways
to
humor
debugger,
an
app
on
on
an
iPhone,
so
I'm
going
to
present
you
a
project
I've
been
working
on
in
the
past,
its
name
voland.gs,
which
was
an
open
source
project.
I,
was
working
a
couple
years
ago
and
I'm
currently
updating
it
with
a
teams
in
in
India
working
on
the
team's
mobile
platform.
So
they
are
doing
an
amazing
work
to
take
the
source
code
that
was
seven
eight
years
old
and
fix
it,
improve
it
so
I'm
going
to
show
you
like
the
existing
version
of
valence.
H
Yes,
so
what
it
does
is
pretty
simple
in
a
way
if
he
sees
not
GS
application,
that
is
using
socket
IO,
so
web
sockets
and
what
we're
going
to
do
is
we're
going
to
reference
the
script
at
the
beginning
of
our
team's
application,
which
is
a
web
app.
You
know,
and
then
this
specific
package
is
going
to
monitor
every
call
to
the
console.log
it's
going
to
enable
like
a
basic
Dom
inspector
or
remote
inspector,
and
it's
going
to
send
back
all
events
from
the
the
client.
So
it
could
be
an
iPhone.
H
It
could
be
another,
it
could
be
whatever
we've
been
able,
even
to
the
debugger
a
Tesla,
because
you
know
you
got
a
web
browser
on
a
Tesla
and
it's
going
to
send
that
back
to
the
developer
machine,
and
then
you
will
be
able
to
do
some
basic
inspection.
So
let's
see
that
together.
So
the
first
step
is
I
defined
a
specific
Android
configuration
file,
one
for
the
local
us,
where
my
teams
app
is
going
to
be
hosted,
so
it's
being
defined
by
the
team's
toolkit
and
one
for
volun.
H
While
you
like
to,
and
now
it's
really
easy
to
control.
You
know
the
various
endpoints
so
I've
injected
the
public
on
point
of
end
clock,
and
last
but
not
least,
this
is
what
I
was
explaining.
You
I've
got
the
specific
script
at
the
beginning,
which
is
volunteers,
the
client
side
of
volunteers.
That
once
is
going
to
be
load
first
and
then
it
will
monitor
everything
being
done
on
the
client
to
be
able
to
send
all
the
event
back
to
to
your
developer
machine.
H
So
I
already
pressed
F5
and
try
to
be
sure
that
I
will
be
in
time.
Let's
check
the
application.
The
application
is
there.
So
it's
running
for
now
on
my
PC
and
I'm,
going
to
show
how
it
works,
look
fully
locally
in
a
way
and
I've
got
also
the
volume
dashboard
being
there
going
to
snap
it
on
the
right,
so
I'm
going
to
load
the
app
and
you're
going
to
see
that
normally
a
new
client
is
is
being
connected
there.
H
So,
thanks
to
the
script
that
was
at
the
beginning,
websocket
was
used
with
socket
IO
to
send
events
back
to
the
volunteers.
Dashboard.
To
tell
me,
like
a
new
client
join
the
volunteer
server,
and
now
you
can
remote
debug
in
a
way.
What's
going
on
so
like
having
a
Dom
inspector,
so
you're
going
to
tell
me
like
okay
David.
This
is
not
that
impressive,
because
I
can
do
that
with
F12.
H
H
So
I
only
have
one
Android
device
for
not
connected
so
now,
I
can
first
I
can
see
the
remote
console
so
what
we
seeing
that
is
the
console
of
this
device,
meaning
that
you
see
that
I
don't
have
any
USB
cable
I'm
running
over
Wi-Fi
on
my
local
machine,
it's
going
to
connect
when
Rock
and
come
back
to
my
machine.
So
there
is
a
big
loop,
but
then
I
can
now
check
the
console
of
My
Remote
device,
which
could
be
already
super
useful
because
sometimes
it's
not
running
on
your
device.
H
But
you
have
no
clue
what's
going
on
thanks
to
valence.
Yes,
you
have
the
remote
debug
being
available
and
once
again
now
I
can't
have
some
basic.
You
know
debugging
capability,
so
we
are
still
fixed
trying
to
fix
Verlin.
But
let's
imagine
I'm
clicking
there
and
I
would
like
to
have
access
to
the
layout.
H
So
now
I've
got
the
iPhone
still
in
Wireless
in
Wi-Fi
I'm,
going
to
open
the
same
app.
The
teams
is
in
French.
So
let's
pretend
is
also
to
test
the
localization,
and
you
see
this
time,
and
this
is
something
we're
going
to
tell
to
my
team
working
on
a
new
dashboard
sample
that
we're
going
to
ship
for
you
in
the
next
version
of
the
toolkit.
We
have
an
issue
there
so
to
potentially
debug
it.
You
see
now.
H
H
So
let's
do
something
very
simple
like
this:
is
the
beauty
of
JavaScript
in
a
way
that
I
can
execute
the
code
live
so
if
I'm
pressing
enter
so
you
see
on
my
device,
it
managed
to
receive
the
code
execution
and
do
something
so
I
can
really
have
some
basic,
remote,
debugging
capabilities
thanks
to
volunteers,
that
you
see
that
you
just
have
to
reference
it
at
the
beginning
and
be
able
to
do
many
things.
So,
for
instance,
I
can
go
to
the
other
object
Explorer
and
go
to
I.
H
Don't
know
the
Navigator
object,
for
instance,
I
should
be
there
going
on
the
Prototype,
and
we
see
that
I'm
currently
running
an
iPhone
oops
with
the
OS
version.
So
I
can
have
a
lot
of
information
on
my
Remote
device
from
this
dashboard.
So
what
we
are
planning
to
do
is
to
try
to
integrate
that
as
a
vs
code,
extension
and
probably
also
in
the
toolkit.
So
we
are
working
in
our
team
with
a
in
in
India
to
to
do
that.
H
H
So
you
will
be
able
to
live
the
edit,
the
style
on
the
Remote
device
that
should
gain
give
you
a
lot
of
productivity
boost,
rather
than
trying
to
guess
what's
going
wrong
and,
for
instance,
you
see
that
I've
got
an
issue
on
my
graphs
there,
so
I
I
will
be
able
to
use
myself
one
to
fix
our
sample
for
the
toolkit.
So
this
is
something
very
useful
for
us
to
to
application.
I
know
we
have
a
little
bit
of
more
time,
I
like
to
do
a
test.
H
So
let's
I'm
going
to
share
this
URL
with
you
in
the
chat
and
if
you
go
on
it,
it's
it's
the
application
running
on
my
local
machine
on
Android,
but
you
will
see
that
if
you
click
on
it
and
open
that
in
your
browser,
I
should
see
people
connecting
in
my
dashboard
and
I
can
remote
debug,
for
instance,
enemy
an
application
so
I
see
that's
a
Windows
Windows
machine
or
Linux
machine,
so
Linux
machine
should
be
fun.
So
who
is
the
Linux
machine?
H
Who
is
running
on
Linux,
but
you
see
that
I
can
remote,
so
everything
is
being
hosted
on
my
machine.
So
if
you
would
like
to
do
more,
you
know
connection
I
should
probably
have
a
public
server
in
Asia
or
something
else
in
the
cloud
to
be
able
to
remember
debug
it.
But
you
see
we
can
basically
a
remote
debug
anything
thanks
to
Valen,
because
it's
pure
web
technology,
it's
socket
using
node.js
app,
so
I
can
basically
remote
direct
something
or
still
in
outlook.com
in
Outlook
the
page
clients
are
in
teams
itself.
H
So
really
it
was
trying
to
share
you
some
fun
with
you.
If
you're
interested
in
knowing
more
please
contact
me
on
Twitter
or
or
to
the
team
and
and
share
any
feedback
you
may
have.
That
may
be
something
useful
for
you,
and
this
is
it.
This
is
the
end
of
of
My
Demo.
So
I
can
stop
sharing
my
screen
somewhere.
B
Excellent,
thank
you.
David
really,
really
cool
stuff
and
that's
gonna
be
really
helpful
for
sure
and
and
we're
going
to
improve
a
lot
on
the
debugging
side.
It's
it's
always
so
hard
to
do
debugging
on
the
desktop
experiences.
So
this
will
be
really
really
cool,
so
awesome
stuff
and
a
lot
of
positive
feedback
on
the
chat
as
well.
So
please,
please,
please,
contact
David
for
your
feedback
and,
and
let's
give
input,
was
that
fun
or
not?
Let
us
know
now.
Thank
you
Aisha!
Thank
you,
Gary.
B
Thank
you,
David
for
the
create
great
great
demos
today
next
week,
we'll
have
Aisha
talking
about
dynamically,
create
Azure
communication,
Services,
identity
and
token
carriers.
Gonna
continue
teams,
toolkit,
learning
path,
series
and
waldek
is
going
to
do
a
recap
on
the
Microsoft
craft
hackathon.
So
if
you
didn't
made
to
the
hackathon,
then
have
the
time
to
participate,
we'll
cover
that
on
upcoming
weeks
as
well,
so
you
can
actually
kind
of
stay
up
to
date
on
what's
happening
there
and
what
are
the
things?
B
What
happened
on
the
previous
week
always,
but
thank
you
for
joining
today
and
the
recording
will
be
in
24
hours
at
the
Microsoft
365
sample
platform.
Community
Channel
at
akms
forward.
Slash
Community
forward,
slash
videos
do
subscribe
there
and
to
stay
up
to
date
when
it's
stuff
is
available
and
we'll
have
the
next
call
within
a
week
thanks,
everybody
have
a
great
rest
of
the
week.
Stay
healthy
stay
and
stay
safe
and
we'll
be
in
touch
bye.