►
Description
Microsoft 365 platform community call delivered on November 8th. Two demos - Avoid throttling in SharePoint Online by using RateLimit headers in API calls and Build your first Workflow bot for Microsoft Teams with Teams Toolkit for Visual Studio Code. Getting started assets for Microsoft 365 developers – free E5 developer tenant and training modules. Download the latest episodes of the Microsoft 365 Developer podcast and Microsoft 365 PnP Weekly. Register for Power Platform Samples Contributor training. 11 platform related articles and 2 in-depth conversations delivered this week! The host of this call was Vesa Juvonen (Microsoft) | @vesajuvonen. Q&A takes place in chat throughout the call.
Learn more
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/m365pnp/blog
• Download invite for this weekly Microsoft 365 Platform community call: https://aka.ms/m365-dev-call
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - https://aka.ms/m365/community
A
B
I
think
it
is
yes,
it
is
it's
already.
November
holiday
season
is
coming
pretty
soon,
which
is
quite
mind-blowing.
Time
flies
when
you're
having
fun.
Now
today
we
have
two
specific
demos,
so,
first
of
all,
we'll
go
through
some
of
the
typical
assets
and
scenarios.
What
we
go
through
within
this
call
and
making
sure
that
you
know
all
of
the
assets
which
are
available
for
you.
We
also
go
through
the
latest
news
and
the
developer.
B
Documentation
updates
on
the
team's
platform
side
and
we'll
do
a
group
photo
on
the
together
mode
after
that,
and
then
we'll
have
the
real
stars
of
today
who
are
Bert,
Johnson
and
Gary
trinder.
So
Bert
is
going
to
talk
about
how
to
avoid
throttling
in
SharePoint
online,
by
using
rate
limit
headers
in
API
calls
so
pretty
low
level
stuff,
but
quite
important,
because
the
throttling
can
happen
for
your
API
calls
and
just
to
recap,
the
troubling
is
there
to
ensure
that
the
whole
system
does
not
go
down.
So
we
would
do
a
lot.
B
We
don't
really.
We
ask
Microsoft.
We
don't
really
like
that.
We
need
to
travel,
but
it
also
means
that
somebody
is
hitting
the
service
too
much,
so
it
would
start
to
have
an
impact
across
the
other
tenants
and
other
services
and
other
customers.
So
that's
why
the
throttling
is
in
place
to
avoid
those
kind
of
things
you
can.
You
can
also
think
about
the
throttling
kind
of
a
way
of
preventing
denial
of
service
attacks,
because
we
need
to
make
sure
as
Microsoft
that
individual
requests
are
not
causing
a
significant
performance
impact
within
the
service.
B
Now,
on
Gary's
case
we're
going
to
talk
about
built
your
first
workflow,
but
for
Microsoft
teams
using
the
team's
toolkit
for
visual
studio
code,
and
that
should
be
really
interesting
as
well.
Now
before
we
go
to
the
actual
demos,
let's
recap
what
we
have
available
for
for
the
assets
for
you
to
get
started.
So
we
do
have
two
different
YouTube
channel,
a
kind
of
a
teaser.
Maybe
on
that
one.
We
just
are
we're
looking
into
potentially
merging
these
two
channels
in
the
future.
B
To
avoid
the
confusion,
why
we
have
two
different
channels:
that's
a
kind
of
a
historical
thing
as
an
evolutionary
thing
and
why
we
ended
up
having
two
of
them,
but
most
likely
we'll
have
one
in
the
future.
After
a
while,
when
we
get
the
stuff
sorted
out,
we
have
a
lot
of
Open
Source
assets
available
in
the
GitHub.
B
We
also
have
sample
galleries,
which
will
make
it
easier
to
find
the
relevant
sample
for
you
and,
if
you're
wondering
that,
there's
too
many
URLs
to
remember
luckily,
there's
only
one
with
the
same
as
M365
Community,
from
where
you'll
find
all
of
the
links
to
the
documentation,
sdks
tools,
open
source
assets,
YouTube
blog
platform
and
many
many
many
many
many
many
other
assets
as
well.
Now
as
part
of
our
community
efforts,
we
do
quite
a
lot
of
community
calls.
So
the
Tuesday,
this
Tuesday
8
AM
Pacific
time,
is
kind
of
the
primary
Microsoft
presented.
B
Call
in
this
call
and
the
presenters
are
always
Microsoft
Microsoft
employees,
so
we
have
PMS
developers,
Cloud
Advocates,
basically
showing
and
explaining
the
scenarios
directly
who
built
it.
So
the
people
who
are
actually
working
day
to
day
and
designing
new
features
are
then
explaining
for
you
how
to
get
started
on
using
things.
B
We
also
have
a
monthly
Community
course
on
adaptive,
cars,
Microsoft
identity
platform
officers
and
Power
Platform,
and
then
we
have
our
Thursday
series,
which
is
happening
every
Thursday,
7
A.M,
Pacific
time
it's
either
the
Microsoft
365
and
Power
Platform
Community
called
all
the
Viva
connection
and
SharePoint
framework
call.
So
quite
a
lot
of
calls.
You
don't
have
to
join,
obviously,
and
all
of
them
pick
the
calls
which
are
interesting
for
you
and
all
of
them
are
getting
recorded
and
published
in
our
YouTube
channel.
B
So
that
makes
it
easy
for
you
to
afterwards
to
go
and
check
out
if
there
was
interesting
topics
which
you
might
have
missed
if
you're
looking
into
downloading
invites
for
this
course
go
to
the
M365
akms
M365
course
from
there.
You
can
find
all
of
the
links
for
these
individual
course
now,
as
you
can
start
it
with
my.
B
B
We
also
have
two
a
specific
broadcast
Series.
So
we
have
the
Microsoft
365
developer,
podcast,
hosted
by
Jeremy,
fake
and
Paul
Shuffling
from
adding
365,
and
then
we
have
the
BMP
weekly
weekly
podcast,
which
kind
of
entitled
or
implied
in
the
name
hosted
by
me.
Mr
Eugene
from
Microsoft
and
Wildlife
MasterCards
was
a
senior
Cloud
Advocate
from
the
Microsoft
side
as
well.
B
Both
of
them
are
good
things
to
subscribe
into
to
stay
up
to
date
on
what's
Happening
now
we
also
have
a
lot
of
lot
of
samples
available,
so
this
is
basically
the
one
location
and
where,
as
you're
starting
to
build
something
in
the
Microsoft
365,
including
Power,
Platform
and
you're,
looking
like
oh,
maybe
there's
a
sample
available
somewhere
in
a
GitHub,
but
it
might
be
really
difficult
to
find
it
because
there's
so
many
locations.
Luckily,
we
are
surfacing
all
of
our
samples
from
a
one
centralized
location.
B
So
you
can
go
to
this
one
location,
there's
a
new
UI
new
experience,
which
was
just
deployed
there
on
last
Friday.
So
you
can
more
easily
find
relevant
samples
for
you
and
this
location
has
samples
from
Microsoft
and
from
the
community.
So
we're
trying
to
make
this
as
easy.
As
for
you
as
possible,
it's
a
really
really
cool
more
than
one
of
1400
10
samples
available
right
now,
I
think
it's
14
15
right
now.
What
was
the
last
number
which
I
just
checked
before
the
call?
B
A
A
That's
set
up
to
provide
Hands-On
guidance
and
what
that
means
is
that
we're
going
to
work
on
it
together
if
you've
never
done
a
PR,
we're
going
to
show
you
we're
going
to
walk
you
through
it,
it's
going
to
be
a
safe
space
environment,
which
means
we
don't
record
their
live
sessions.
So
it's
free
to
ask
any
and
all
questions
you
want.
We've
already
got
some
more
skidding,
scheduled
up
Power,
Platform
samples,
contributor
and
we're
going
to
get
that
writing
for
the
web
back
on
track
using
PNP
spfx
samples
within
VM.
A
We'll
show
you
how
to
navigate
some
of
those
weird
node
version
differences
and
how
to
use
that
we're
here
for
you.
So
please
don't
hesitate
to
register.
Keep
an
eye
out
at
ak.ms
forward.
Slash
sharing
is
caring,
absolutely
free
of
charge.
There
is
no
cost
and
again
it's
a
wonderful,
safe
space
to
collaborate
with
other
like-minded
passionate
individuals
in
the
community.
So
don't
hesitate
to
sign
up.
That's
it
back
to.
B
You
excellent
thank
you
David
on
on
that
one
I
just
wanted
to
pinpoint
the
free
of
charge.
That's
really
good,
because
everything
in
the
development
in
Microsoft
trade
65
we're
not
asking
anybody
to
pay
anything.
Of
course,
you'll
even
get
to
1000
free
developer
tenants
as
long
as
you're
subscribed
to
the
program,
which
is
really
really
cool.
Now,
on
the
latest
news
site,
there
was
three
developer
specific
news
on
the
Microsoft
365
developer,
plug
on
last
Friday,
and
we
published
the
blog
post
related
on
breaking
changes
in
the
Microsoft
craft,
insights
API.
B
It
is
a
super
super
super
small
chains
and
on
that
API,
it's
not
technically
even
a
Breaking
Chains,
but
it
is
I'm
not
going
to
go
too
much
detail
on
that.
One.
A
property
to
property
has
previously
been
always
a
specific
one.
With
the
in
the
documentation,
we've
been
saying
that
it
could
be
two
options
and
in
future
it
will
be
two
options.
So
it's
kind
of
a
one
of
those
really
really
small
things,
but
it's
a
good
example.
We
want
to
be
transparent
on
our
apis
and
the
involvement
of
those
apis.
B
So
we
want
to
make
sure
that
if
there's
any
changes
which
might
be
impacted
on
our
partners,
we
will
open
and
talk
about
them.
There
was
also
a
a
really
nice
blog
post
from
tomomi
imura
related
on
customizing,
F5,
debugging
and
teams
toolkit
with
regards
to
their
code,
we're
going
to
see
the
team's
toolkit
later
today
and
with
Gary.
So
it's
a
cool
demo
and
then
they
will
say
announcing
announcement
of
SharePoint
framework
1.16
release
candidate
on
last
week
as
well.
B
Sharepoint
framework
1.16
is
planned
to
go
out
in
mid-november
and
which
SharePoint
framework,
regardless
of
the
name.
You
can
actually
build
experience,
experiences
for
Microsoft
teams,
Microsoft
Viva,
Outlook
office
and
SharePoint,
of
course,
and
that's
in
the
name.
Now,
on
other
news
on
the
blog
post,
we
had
a
SharePoint
roadmap,
Pit
Stop
on
October
2022,
which
is
a
summary
on
what
has
happened
on
a
SharePoint
site,
but
that
actually
includes
a
lot
of
other
products
as
well.
So
this
kind
of
a
summary
related
on
one
try,
Viva
SharePoint
and
many
other
other
relevant
products.
B
So
what
are
the
latest
announcements
on,
though?
Those
there
was
a
update
also
on
the
Viva
block
site
related
on
learn
about
knowledge
sharing
through
Viva
topics
at
the
km
km
world.
So
right
now,
there's
a
km
World,
which
is
acknowledge
management,
World,
Conference
ongoing.
So
there's
a
specific
Microsoft
stance
over
there
and
then
there's
there
was
blog
posts
related
on
how
to
build
okrs
your
objectives
and
key
results
into
your
business.
So
how
would
you
get
started
on
doing
that
and
that
relates
on
Viva
goals,
which
is
a
good
way
of
measuring
those
okrs?
B
On
the
team
side,
there
was
a
a
kind
of
a
cool,
well
really
cool
announcement
that
Microsoft
team
Progressive
web
apps
is
now
available
on.
Linux
really
shows
that
we
as
a
Microsoft,
want
to
give
you
the
option
to
use
whatever
technology
and
whatever
platform
you
want
to
use.
We
will
provide
our
services
there.
There
was
also
a
blog
post
related
on
Microsoft
teams,
performance
improvements
and
how
we're
in
a
continuously
investing
and
right
making
the
teams
more
efficient
and
more
performant.
B
And
then,
if
you
are
using
the
team's
phone
and
there
was
a
six
common
questions
which
were
being
answered
in
one
of
the
blog
posts
but
really
really
cool
stuff
again
within
the
last
week
now
related
on
the
cool
stuff,
we
always
want
to
also
cover
what
is
new
in
the
Microsoft
teams,
platform,
documentation
updates
and
what
sheet
is
in
the
call
to
talk
about
them?
Watch
it
take
it
away.
C
Hello,
everyone's
platform
beats,
let's
start
with
the
first
one,
so
Global
routing
is
Now
supported
for
what
it
is,
which
can
be
used
to
send
productive
messages.
A
productive
message
is
any
message
which
is
sent
by
a
bot
that
isn't
in
a
response
to
a
request
from
a
user.
So
this
message
can
be
a
welcome
message:
notifications
with
updates
or
a
scheduled
message.
C
You
can
create
a
conversation
if
it
already,
if
it
doesn't
exist
already
or
you
don't
know
the
conversation
ID
and
to
create
the
conversation,
you
need
user,
ID,
tenant,
ID
and
service
UI,
and
if
service
URL
isn't
available
from
an
incoming
activity,
triggering
the
proactive
scenario,
you
can
now
use
these
Global
endpoint
URLs.
So
this
is
all
documented.
We
have
listed
all
the
endpoints
URL
as
well.
Second,
we
have
added
a
new,
step-by-step
guide
for
sample
code
to
build
in
meeting
document.
C
Signing
experience
so
meeting
signing
is
a
practice
of
Team
sampler
that
enables
user
to
sign
documents
in
a
real-time
scenarios.
It
provides
enhanced
experience
by
allowing
users
to
redo
and
sign
documents
in
a
single
session
during
a
meeting,
and
this
sample
lets
user
electronically
sign
documents
with
their
current
Talent
ID.
So
these
are
the
platform
page.
If
you
have
any
feedback
or
situation,
please
do
post
on
AK
dot,
Ms
teams,
platform
feedback.
The
link
is
available
in
the
footer.
B
Usa
excellent,
thank
you
for
trading
on
that
one
and
then
before
we
go
to
the
actual
stars
of
the
date
and
the
demos
and
let's
do
a
quick
crew
photo
together.
So
those
who
are
willing-
let's
put
the
video
on
and
I,
will
share
my
screen
and
we
will
put
everybody
into
together
mode.
Where
is
the
together
mode
setting
right
now?
There
we
go.
They
keep
on
changing
the
buttons
and
locations
of
things.
It's
always
so
confusing.
B
So
here
we
go
now
we're
getting
into
the
together
mode
and
I
will
select
a
bit
different
scene
this
time.
So
we
get
some
variants
on
the
pictures.
So
let's
use
that
one
I
like
that
one,
a
lot
we're
not
yet
recording.
Let's
wait
and
let's
wait
a
while
we
get
the
50
seats,
good
good,
stretching
on
the
back
yeah
there
we
go.
Are
we
getting
anybody
else
on
the
call
anybody
else?
B
Anybody
else
and
I
will
put
the
recording
on
in
any
second
and
I
will
okay,
so
you
will
see
when
the
numbers
start
going
down.
Let's
do
some
kind
of
thing:
everybody
we
will
capture
a
gif
animation
out
of
this.
Thank
you,
everybody
once
again
joining
really
awesome
to
see
you
on
the
call,
and
hopefully
we'll
see
you
in
the
Las
Vegas
or
Copenhagen,
and
the
in-person
conferences
at
one
of
the
conference
options
later
this
year.
Thanks
everybody
we'll
grab
a
key
FUNimation.
D
My
name
is
Beth
Johnson
I'm,
a
senior
service
engineer
inside
the
customer
engineering
organization
in
SharePoint
and
OneDrive,
and
in
my
day-to-day
role,
I
do
talk
a
lot
with
the
isvs
with
customers
and
throttling
is
a
common
topic.
It's
like
I
think
one
out
of
two
calls
throttling
somewhere
pops
up
and
we
have
to
talk
about
it
so
before
diving
into
the
technical
demo
around
weight
limit,
headers
I
would
just
want
to
step
back
and
say
and
demystify
SharePoint
throttling
a
bit
helping.
You
understand
how
it
works.
D
If
that's
already
in
the
introduction
really
explained
very
well
like.
Why
do
we
need
throttling?
We
need
trottling
to
ensure
that
not
one
particular
user,
one
particular
application
is
not
jeopardizing
stability
for
all
the
other
tenants
inside
an
environment.
So
because
we
share
resources
with
many
tenants.
We
have
to
have
a
fair
use
policy
and
prompting
is
our
way
to
achieve
that.
D
Okay,
all
right!
So
imagine
you
have
a
funnel
what
you
see
over
here
and
your
request
comes
in
what
will
happen?
The
request
comes
in
then.
Your
request
for
the
most
request
is
Titan
application.
So
if
you
have
an
Azure,
the
application
and
using
that
application,
you
make
a
call
to
a
SharePoint
API
you're
on
this
bucket
in
this
application
bucket,
and
this
applies
for
both
delegated
and
application.
Permissions
like
rest
can
also
just
have
a
user
linked
to
it
all
both
request.
D
D
So
what
that
means
is
that
your
application
can
execute
a
number
of
resource
units
per
minute,
and
if
it
goes
beyond
the
threshold,
it
will
get
throttled
we'll
explain
later
on
what
it
means,
there's
resource
units.
So
but
it's
like
a
first
measure
going
further.
We
have
the
similar
measure,
but
then
for
like
a
day.
So
if
your
app
is
doing
too
much
across
a
full
day,
then
it
can
be
throttled
as
well
quite
seldom,
but
it
can
happen.
D
So
these
are
the
common,
the
more
common
approaches
for
getting
throttled
on
the
left
side
for
the
user.
Here,
if
your
request
is
tied
to
a
user,
either
being
a
delegate
of
missions
or
just
being
like
a
script
expert
part
making
a
call
to
a
rest
endpoint,
then
we
also
measure
how
much
use
requests
happen
in
a
certain
time
window
and
if
that
goes
beyond
threshold
that
can
lead
to
totaling
as
well
again,
quite
rare,
then.
D
Finally,
there
is
some
Farm
level
Spike
protection
in
place
just
to
protect
the
resources,
very
rare
that
you
get
throttled
by
this
one.
Eventually,
your
request
comes
here.
We
need
to,
and
in
most
cases
almost
all
cases
is
green.
Your
request
happens
and
you're
good
to
go
you're
getting
data
back,
and
you
can
issue
the
next
request.
D
D
D
Resource
units
we
talked
about
that
previously
visual
students
is
our
way
to
document
what
your
application
can
do
before
it
gets
throttled
and
the
number
of
resource
units
and
application
gets
is
depending
on
the
tenant
size.
So
the
larger
the
tenant
is
the
more
one.
Particular
application
can
do
so.
The
50k,
then
I
can
get
six
thousand
resource
units
a
smaller
one.
You
get
1
200.
D
D
Furthermore,
those
resource
units,
they
are
translated
to
requests.
So,
like
you,
do
a
request
and
and
a
request
can
be
a
system
request,
a
graph
request,
a
SharePoint
arrest
request,
all
these
requests
of
our
kind
of
eject
and
possibly
throttled,
though
the
graph
requests
are
kind
of
more
favored
in
this
model.
So
if
there's
a
graph
equivalent
over
SharePoint
rest
or
see
some
equivalent,
then
you
should
use
that
it's
more
favorable
than
consecrotting
for
the
graph
site.
D
So
we
have
actually
defined
all
the
calls
and
you
can
kind
of
translate
your
request
into
resource
units.
So
if
we
do
a
Delta
request
with
a
token
it's
just
one
resource
unit,
if
you
do
expand
the
permissions
that
will
count
for
five,
because
that's
really
expensive
call
for
us
overall
I,
think
investor
a
guidance
is
to
just
assume
two
resource
units
per
requests.
So
if
your
app
does
1000
requests,
that
means
2000
research
students
on
average.
That
also
then
applies
to
SharePoint
system
and
rest.
D
So
that's
an
easy
way
to
calculate
that
yeah
moving
on
to
rate
limited.
So
you
know,
if
no
learns,
when
you
get
throttled
and
why
you
get
throttled.
No,
no
trolling
is
not
a
good
thing.
Well,
it's
a
good
thing
to
protect
the
service,
but
you
don't
like
any
application,
because
when
you
get
throttle
to
your
application
kind
of
gets
to
a
stop
and
for
that
we've
recently
introduced
A
New
Concept
called
great
limit
headers,
so
rate
limit.
Headers
are
response
headers,
so
we
do
request.
You
get
a
response
back.
D
D
D
D
One
more
thing
is
that
those
headers,
if
you
start
testing
this
and
you
you
can
you,
maybe
you
don't
see
those
headers
immediately
appearing
and
that's
accurate
and
normal,
because
those
headers
only
appear
when
you
are
above
80
percent
of
your
allocated
quota.
So
if
you
don't
see
the
headers
you're
all
good,
you
can
keep
going
if
data
starts
to
appear
and
then
you
need
to
act
on
them
now.
You
might
wonder
like
okay
with
it.
Why
should
it
do
all
of
this?
D
So
your
application,
your
launch
application,
it
gigs
of
like
five
threadsden
threats,
all
those
threads,
they
start
hitting
SharePoint
and
you
keep
ramping
up
and
everything
goes
well
at
certain
points
you
get
throttled
and
then
you
get
to
like
more
like
a
flat
line.
Your
application
gets
fully
throttled
and
it
has
to
wait
until
all
the
struggles,
kind
of
expire
and
you're
good
to
go
again,
and
then
you
see
this
ramping
up
again:
Flat
Line
ramping
up
flat
line.
So
you
you
really
get
those
kind
of
stops
in
the
application.
D
If
you
would
use
rate
limit
headers
the
green
line,
you
get,
you
start
at
the
same
speed
initially,
but
then,
whereas
the
throttling
would
kind
of
get
you
a
full
stop
weight.
Limitators
will
slow
you
down
a
little
bit,
but
you
don't
fully
stop
and
then
you
pick
up
again
because
you're
in
the
next
minute
again
some
small
stuff
delay,
because
you're
delaying
some
requests,
full
speed,
delay
and
so
on.
D
The
good
thing
is
that
this
gives
you
extra
throughput
and
the
reason
why
is
is
because
you
avoid
getting
throttled
and
that
just
saves
requests.
If
you
get
throttled
and
you
try
again,
then
you
do
two
requests,
not
one.
So
you
you
do
two
requests
against
a
particular
quota
that
you
have
so
the
more
you
get
throttled
the
the
more
you
kind
of
worsen
the
situation.
D
B
D
So
in
the
chat
you
see
a
link
to
the
SharePoint
totaling
page,
which
is
the
basic
documentation
and
also
to
the
sample.
So
you
can
the
code
I'm
showing
here
you
can
just
follow
along
and
already
look
at
the
code
there
and
then
play
around
the
sample
to
test.
This
is
relatively
simple.
What
it
does
is
it
allows
you
to
kick
off
a
number
of
threads
like
five
and
decide
whether
you
want
to
use
weight
limit
headers,
yes
or
no,
so
you
can
really
experiment
and
play
with
it
and
and
learn.
D
The
used
application
you
need
to
have
an
actual
application.
Configured
which
is
done
here
already,
is
in
the
documentation
of
the
configured
things,
but
this
case
we
set
up
an
application
with
a
certificate
because
we're
using
application
permissions
I'm
not
going
into
details
of
that.
So
just
check
out
documentation
to
learn
more
on
how
to
do
that.
D
Then.
The
key
thing
in
the
application
is
this
HTTP
client
and
totally
Handler,
now
to
explain
that
a
bit
better
I'm
going
to
go
back
over
here
and
go
to
this
slide.
So
in.net
HTTP
client
is
the
core
class
that
you
use
to
make
a
HTTP
request
to
call
something
to
call
SharePoint,
for
example,
and
in
HTTP
client
model.
There's
a
concept
called
delegating
headless
which
allow
you
to
kind
of
extend
and
plug
in
a
functionality
inside
HTTP
client.
D
So
in
our
demo
we
built
a
delegated
Handler
called
totalinghand
that
will
handle
the
throttling,
but
also
will
handle
the
rate
limiting
so
using
Rate
limiter.cs
Glass.
So
let's
have
a
peek
at
both
of
these
classes
going
back
to
the
code.
So
here
we
have
our
HTTP
client
and
you
see
that
we
are
kind
of
passing
in
a
throttling
Handler
going
into
a
throttling
Handler.
The
main
thing
is
that
we
have
an
overwrite
of
the
sent
async.
D
So
when
you
make
a
request,
you
do
called
send
a
sync
method
and
on
HP
client
and
in
here
we
have
a
loop
and
in
this
Loop
let
me
go
to
the
bottom.
We
do
the
request,
so
we
call
SharePoint
call
the
rest.
Api
call
the
graph
API,
we
call
an
API,
we
get
the
response
and
if
we're
not
throttled,
then
we're
good,
we
return
the
response.
D
Otherwise
we
clone
request
and
try
again
so
because
this
is
a
loop,
so
this
code
shows
you
how
to
handle
throttling
and
how
do
we
try
now?
The
key
part
of
this
demo
is
the
rate
limiting
and
for
the
rate,
limiting.
The
thing
is
that
when
you
do
request
a
certain
point
in
your
response,
you
you
see
those
weight
limit,
headers
appearing,
so
your
code
needs
to
look
at
the
responses
coming
in
and
store
the
information
that
comes
in
the
response
and
then
for
the
next
request.
D
D
Window
methods,
so
let's
go
over
there
and
this
method
is
fairly
simple.
It
would
check
the
response
headers
how
those
headers
there
so
the
limits
remaining
reset
headers
and
if
they're
there
they
just
start
and
that's
it.
So
we
have
a
threat
Safeway
to
read
those
headers
and
store
them
so
fairly
basic.
D
In
here
before,
we
actually
make
the
request,
so
we
imagine
that
our
last
request
gave
us
some
red
limited
us
and
we
store
them.
The
next
request
you
want
to
make.
We
want
to
look
at
this
rate,
limit
headers
and
decide
whether
we
can
continue
yes
or
no,
and
that's
done
using
the
weight,
async
method,
I
get
in
the
right
limiter
class,
and
this
one
you
see
us
here.
D
Looking
at
the
data
we
collected
and
then
the
site,
whether
we
should
wait
have
a
delay
or
not
in
this
case
in
the
sample,
you
can
tune
the
delay
based
upon
the
spinning
capacity
left.
So
what
this
means
is
that
the
whenever
we
have
10
of
resource
units
left
or
less
than
10,
then
we'll
wait.
If
not,
we
continue,
and
this
figure
it
may
depend
on
your
application.
If
you
do
a
lot
of
parallel
threats,
you
might
want
to
put
this
a
bit
lower.
D
Explain
those
things
so
the
HP
client
can
be
used
to
make
a
maximum
graph
call
SharePoint
rascal
for
season.
It's
a
bit
special
there
to
make
a
season
goal
like
you
can
share
position,
call
using
our
system,
libraries,
all
good,
but
to
get
the
response
and
look
at
the
response.
Headers
you
need
to
plug
in
a
custom
web
request,
executive
Factory,
which
then
can
use
those
this
HTTP
client.
So
this
same
HTTP
client
is
used
for
making
graphicals
rest
calls
and
season
calls
right.
D
Let's
go
back
to
My
Demo
class
and
I
will
explain
this.
We
explained
that
that
and
now
here
we
are.
We
are
starting
a
number
of
parallel
threats
and
each
thread
does
some
work
in
this
case
in
the
loop.
We
are
calling
rest
graph
and
season
and
then
we
just
get
the
response
back.
So
it's
fairly
simple
application.
Doing
three
calls
now.
D
Let
me
just
to
start
use
it
with
rate
limit
the
rate
limit
headers
on
five
threads,
so
we
press,
F5
notification
starts
to
run
yes,
yes,
that's
a
little
Annoying
thingy
there.
Okay,
let
me
make
this
bigger,
so
you
can
see
more
and
what
you
see
now
is
that
the
application
started.
We
have
those
five
threats
that
we
kicked
off.
Each
of
those
threads
is
doing
calls
doing
a
rest
call
graphical
and
a
season
call
and
a
certain
point.
D
You
will
see
this
application
getting
rate
limited
us,
the
startup
here
when
we
are
at
80
mark
and
then,
if
we
you'll
then
see
how
they
are
kind
of
processed
and
our
application
will
wait.
So
we
have
to
wait
like
20
seconds
more,
because
we
have
this
one
minute
window
that
we
use
for
the
resource
unit
checking
and
you're
still
ready.
Like
rate
limited,
is
appearing.
You
see
if
we
see
some
of
the
graph
or
rest,
so
it
doesn't
matter
which
API
use.
D
You
get
the
same
rate
limit
address
and
you
see
the
reset
like.
So
we're
still
good
we're
not
having
to
wait
yet
because
I
configured
this
like
only
weight
once
we
are
at
the
less
than
10
percent,
and
we
just
starts
to
happen
right
now.
So
you
see
this
graphic.
Rest
is
delayed
to
four
seconds
and
another
season
request.
Delays
for
eight
seconds,
so
you
see
how
it
works
so
now
we're
kind
of
slowing
down
a
little
bit
and
once
this
slow
down
this
is
done
once
we're
in
a
new
minute.
D
We
can
kind
of
speed
up
again
and
then
slow
down
again,
and
this
is
how
this
kind
of
works,
with
rate
limitators
now
I'm,
going
to
stop
this
application
and
let's
try
again
using
without
using
weight,
limit
letters
and
see
what
will
be
the
difference
so
same
application.
But
now
we
just
ignore
regular
materials,
pressing
a
five
sure,
let's
zoom
in
a
little
bit.
So
it
starts
to
say
you
get
the
same
speed
in
the
beginning.
D
B
B
D
D
So
when
you
get
throttled,
you
also
tend
to
see
like
a
longer
wait
times.
They
will
try
after
header
it's
a
giving
telling
you
to
wait
longer,
which
really
means
this
application
gets
to
like
a
full
stop
and
once
the
minute
is
kind
of
over
and
all
the
wait
times
are
gone
will
kick
off
again
and
we
start
going,
but
this
is
not
so
not
really
that
efficient
compared
to
using
the
weight
limit
headers.
D
So
that's
why
we
have
those
headers,
no
point
in
keeping
this
running
I'm
gonna
close
it
looking
at
the
time.
Okay,
we
have
a
couple
of
minutes.
Let's
go
back
to
slides
and
let's
go
to
some
q,
a
common
questions
that
we
get
when
talking
to
customers
and
I,
see
this
other
exceptions
possible.
The
answer
is
no
even
first
party
uses
the
same
logic
and
the
same
rules
for
most
parts:
the
user
agent
string.
What
about
that
thing?
D
Because
we
initially
said,
like
you,
have
the
special
user
agent
and
we
can
give
you
exceptions
a
long
time
ago.
It
was
today
no
acceptance
anymore
user
agent,
not
required,
but
if
you
specify
it
it's
fine,
because
it
helps
support
and
kind
of,
investigate
and
understand
which
application,
which
version
of
an
application
is
making
political
requests.
So
if
you
have
it
in
there,
just
leave
it
in
it's
good.
D
An
interesting
one
can
I
use
multiple
Azure
applications.
Yeah
you.
You
just
told
me
that
one
application
gets
so
many
resource
units.
What
if
my
application
just
just
uses
five
Azure
the
applications
and
load
balances
across
those?
Is
that
fine?
The
answer
is:
no,
that's
not
fine,
simply
because
you
will
start
to
exhaust
the
complete
tenant
and
that
will
impact
all
applications
inside
the
tenant.
D
So
if
you
do
this
Behavior,
you
will
see
that
the
things
start
to
fall
down
and
then
your
customer
will
be
happy
because
multiple
applications
will
get
heavily
throttled
or
even
blocked.
At
a
certain
point,
if
this
keeps
on
going
so
definitely
a
no-go,
should
I
use
a
service
user
with
delegated
permissions
versus
application,
permissions
and
again
the
answer.
There
is
no
bad
ID,
because
a
service
user
is
a
user
and
remember
that
we
had
that
left
column.
When
you
had
the
funnel.
D
D
D
We
have
a
concept
called
scan
guidance
which
explains
how
to
do
it,
but
it
comes
down
to
the
fact
that
you
do
initial
kind
of
crawling
of
the
content
that
you
need
and
then
you
use
subscriptions
and
Delta
queries
to
update
your
copy
of
the
content.
So
you
do
scan
everything
just
once,
and
then
you
do
Delta
updates
so
and
this
using
this
pattern,
you
can
really
process
a
lot
of
content
in
your
application,
while
not
getting
too
much
throttling
and
last
one
load
testing.
Is
this
a
good
idea
like
many
of
these?
D
D
A
very
good
question
for
the
the
PNP
side
in
in
the
Commerce
Decay.
This
is
implemented
but
not
turned
on
by
default.
So
there's
a
configuration
option
allowing
you
to
just
turn
it
on.
Then
you
can
say
like
I
want
to
apply
waiting
when
we
are
at
10
capacity
left
or
15.
So
you
can
choose
that
like
in
this
demo,
so
that's
there
in
core
SDK.
The
framework
and
Powershell
is
not
owned
by
default
and
not
there
yet
so.
D
B
Cool
really
really
cool
and
awesome.
Demo
I
shared
this
sample
linked
to
the
the
sample
in
the
chat
already
we'll
put
it
in
the
summary
blog
post
and
all
of
that
so
and
a
great
work
on
the
sample
as
well.
The
documentation
on
that
is
awesome,
it's
for
everybody
to
understand,
what's
available
and
how
things
work.
So
thank
you.
Thank
you.
Thank.
A
E
Share
my
screen:
yes,
let's
talk
about
building
your
first
workflow
bot,
using
teams
toolkit
for
visual
studio
code
a
little
bit
about
me.
My
name
is
Gary
trender
Cloud
developer
Advocate
at
Microsoft,
joint
Microsoft
I
did
lots
of
development
and
consultancy
and
architecture
beforehand
was
an
MVP.
If
you've
not
checked
out
to
see
a
live,
Microsoft
365,
please
check
it
out,
I'm
also
a
maintainer
there.
E
If
you
want
to
follow
me
about
Microsoft
365
dev,
then
you
can
get
me
on
the
socials
you'll
find
me
mainly
on
Twitter,
but
obviously,
if
you're
not
on
Twitter
anymore,
there
are
plenty
of
the
socials
around
you
can
get.
The
the
rest
of
my
details
from
from
my
league
tree
just
wanted
to
cover
a
really
small
agenda
and
first
gonna
go
through
what
the
workflow
bot
is.
Introduce
teams
talk
it
Visual,
Studio
code.
E
If
you
don't
know
what
that
is,
we'll
go
through
how
we
create
our
first
project,
have
a
quick
run
through
of
the
the
project
and
how
you
can
run
that
bot
for
the
first
time,
and
what
I'm
going
to
do
is
to
act
so
I'm
going
to
do
a
bit
of
a
live
coding
session,
we're
going
to
build
an
order
form
to
really
show
off
the
the
new
feature
that
that
we're
going
to
talk
about
today,
which
is
the
the
workflow
bot.
So
our
workflow
bot.
E
E
Essentially,
this
workflow
bot
is
designed
to
make
it
really
easy
for
you
to
capture
responses
from
users
in
Microsoft
teams,
so
you
might
send
them
an
Adaptive
card
with
an
action
on
there
or
maybe
a
mini
form,
and
you
want
them.
You
want
the
users
to
enter
information
and
submit
that
and
how
you
capture
that
back
and
it
has
not
been
trivial.
So
this
workflow
bot,
approaching
FEMA's
toolkit
for
visual
studio
code
is
really
really
simplifies.
E
That
and
I'll
show
a
great
example
of
an
order
form
later
on,
which
will
which
we'll
go
through.
So
I
mentioned
teams
toolkit,
and
so
this
is
what
we're
going
to
use
to
build
our
workflow
bot.
And
if
you
don't
know
what
teams
toolkit
Visual
Studio
code
is
it's
a
visual
studio
code
extension
that
you
can
install
from
the
marketplace
which
gives
you
functionality
to
create
a
debug
and
publish
your
team's
apps
to
your
Microsoft,
365,
tenant,
Sports,
JavaScript
and
typescript
as
well.
E
So
let's
just
go
straight
into
the
demo,
so
I'm
going
to
show
you
quickly
how
to
create
this,
this
initial
project
so
I'm
just
going
to
move
into
Visual
Studio
code.
So
if
you
haven't
installed
teams
toolkit
like
I
mentioned,
you
can
simply
go
to
the
marketplace.
Search
for
teams.
Toolkit
select
that
so
you
see,
4.1.4.1.1
is
the
latest
version
and
as
long
as
you're
running
4.1.0
you'll
have
the
ability
to
create
this.
E
So,
let's
select
this
like
I
mentioned,
we've
got
options
of
two
languages:
JavaScript
or
typescript
I,
quite
like
typescript,
so
I'm
going
to
choose
that
and
we
need
to
basically
give
a
location
of
where
our
project
is
going
to
be
created.
So
I'm
just
going
to
use
the
default
folder
for
now
and
I'll
just
give
it
a
name
and
we'll
call
it
Community
call
and
team
stalk.
E
Potentially
you
wait
to
look
through
there's
tons
of
information
here
which
just
describes
about
the
project,
what
the
individual
files
are
and
and
how
you
can
extend
it
I'm
just
going
to
quickly
cover
what
these
folders
are,
that
it's
generated,
so
we've
got
an
fx
folder.
So
this
is
where
it
teams
toolkit
configuration
lives.
We've
got
the
vs
code
folder,
which
is
all
the
ebook
settings
debug
profiles
for
for
visual
studio
code.
We
have
our
bot
folder,
which
is
where
our
source
code
lives
for
our
our
Bots.
E
You
see
the
source
folder
in
there
and
we
have
a
templates
folder,
which
contains
our
app
manifest
templates
and
also
our
Azure
templates.
Bicep
templates
for
when
we
actually
want
to
deploy
this
into
Azure
and
get
this
ring
somewhere
other
than
our
own
machine,
so
I'm
just
going
to
quickly
jump
into
the
the
bot
folder.
So
we've
got
a
few
folders
in
here
and
I'll
just
quickly
expand
them.
So
if
you've
used
teams
talk
it
before
and
you've
maybe
used
the
command
bot
template
this
kind
of
Builds.
E
On
top
of
the
of
that
template,
so
we
have
command
handlers,
which
is
our
instruction
for
our
bot
to
to
do
something,
and
we
have
some
card
actions
which
is
okay.
When
an
activity
a
button
has
been
clicked
on
that
on
a
card.
That's
been
added
into
our
teams
chat
by
invoking
that
command.
We
can
get
the
response.
E
We've
got
a
couple
of
adaptive
cards
as
well,
just
to
kind
of
render
a
bit
of
a
UI
and
and
when
we
actually
get
a
response
as
well
a
few
model
files
in
there
as
well,
and
we
have
initialize
a
file
which
is
where
our
kind
of
Bot
configuration
lives
so
it
by
default.
We
have
a
Hello
World
command
Handler,
so
we're
going
to
invoke
hello
world
and
we're
going
to
get
a
response.
E
E
So,
if
I
run
hello,
world
I
get
a
a
response
with
an
Adaptive
card
that
has
a
button
on
it
and
when
I
click
do
stuff,
the
Adaptive
card
actually
gets
replaced.
So
what
has
just
happened?
There
is
we've
had
a
response.
That's
come
back
to
our
bot
and
our
bot
has
gone
okay.
Great
I've
had
something
happen
from
from
adaptive
card
that
I've
sent
out
and
now
I
can
replace
that
that
adaptive
card
with
some
things
that
just
confirms
that
that
that
something
has
happened.
E
E
So
what
I'm
going
to
do
is
I'm
going
to
jump
through
and
I'm
going
to
guide
you
through
the
steps
of
how
to
build
out
this
form
and
as
I'm,
going
through
I'm,
going
to
explain
all
the
different
areas
of
how
this
this
bot
actually
works.
So,
if
I
go
back
to
my
project,
so
the
first
thing
that
I
want
to
do
is
I'm
going
to
create
a
new
adaptive
card.
E
So
this
is
going
to
be
a
our
our
response
to
our
Command
I'm,
going
to
paste
in
this
adaptive
card
now,
just
to
show
you
what
this
actually
looks
like
I've
actually
used
a
sample.
So
if
you
go
to
the
Adaptive
cards
website,
there's
loads
of
samples
in
here,
if
you
scroll
all
the
way
down
to
the
bottom,
we've
got
a
restaurant
order,
which
is
a
form
that
has
validation
in
it,
has
some
sample
data
and
a
sample
adaptive
card
definition
as
well.
E
So
what
I've
done
is
I've
taken
that
and
I've
made
some
slight
adjustments.
I've
dropped
the
version
to
1.4
so
that
teams
supports
it
and
have
also
changed
the
action.
So
this
is
a
button
that
allows
us
to
place
our
order
and
I've
changed
this
to
action,
execute
and
I've,
provided
a
verb,
so
what's
happening
here
is
when
I
actually
click
that
button
a
verb
is
going
to
be
sent
back
to
my
bot,
saying
I've
got
an
action
here,
called
order
placed.
E
What
we're
going
to
do
now
is
I'm
going
to
go
to
our
models
and
I
am
going
to
just
paste
in
a
load
of
interfaces,
so
this
describes
our
our
order
form
effectively
for
our
adaptive
card.
This
is
going
to
help
when
we
are
combining
our
template
with
some
data,
so
the
data
to
actually
add
items
into
the
into
the
drop
downs
in
in
that
form.
E
So
when
orders
put
in
it's
actually
going
to
fire
this,
this
function,
one
thing
which
I'm
going
to
quickly
do
is
I'm
just
going
to
add
the
async
keyword
here
to
the
the
command
received
function.
So
we
actually
need
that
first
thing
is
I'm,
going
to
create
a
constant
which
contains
our
our
data
that
we're
going
to
pass
into
our.
E
Adaptive
card
template
so
in
here
you
can
see
the
different
questions
and
the
different
values
that
we
that
we
have
a
available
and
then
the
next
step.
What
we're
going
to
do
is
combine
the
data
and
our
adaptive
card
and
then
return
our
adaptive
card
back
to
our
our
bot
chat,
so
I'm
just
going
to
import
some
of
these
statements
and
I'm
going
to
import
our
adaptive
card
as
well,
which
I
have
to
just
do
this
manually.
E
Yeah,
so
there's
our
model,
so
this
is
our
Command.
That's
going
to
get
invoked,
it's
going
to
send
a
a
an
Adaptive
card
back
as
a
response,
and
the
button
is
then
going
to
fire
this.
This
response
with
an
order
placed
verb.
One
last
thing:
we
need
to
do
for
to
tell
our
a
bot
that
this
Handler
actually
exists.
So
if
we
go
to
the
initialize
file
in
here,
I
can
add
my
new
Handler,
which
was
our
order,
command,
Handler
and
save
that.
E
E
Okay,
so
I'm
going
to
paste
this
in
here
and
it's
simply
just
going
to
respond
back
with
some
confirmation
of
what
we
actually
selected
in
the
drop
downs
and
then
provide
some
extra
buttons.
Actually,
so
we
could
carry
on
if
we
wanted
and
add
more
action
handlers
in
here
and
add
more
verbs
and
so
that
you
know
the
cards
can
basically
roll
into
into
one
another.
Let's
add
our
model
as
well
in
here,
so
we're
going
to
add
in
our
response
data
and
our
the
shape
for
our
action
data
as
well.
E
E
So
we've
got
an
action
here,
that's
going
to
be
the
order,
placed
action,
Handler
and
this
time
we're
going
to
use
a
different
interface,
so
the
Adaptive
card
action
Handler
from
teams
FX,
let's
Implement,
that
interface
I'm
just
going
to
quickly
get
rid
of
this
because
we
don't
need
it,
but
we
have
our
trigger
verb
so
similar
to
our
trigger
pattern.
We
can
actually
put
in
our
our
verb
in
there.
E
So
when
the
verb
is
detected,
it's
going
to
run
our
handle
action,
invoked
method,
so
I'm
going
to
make
that
async
as
well
and
one
of
the
things
that
we're
going
to
do
so,
we
can
see.
We've
got
our
action
data,
that's
provided
for
us.
This
is
the
information
that's
submitted
in
the
form,
rather
than
this
being
an
any.
Let's
actually
return
that
as
order
action
data,
so
that's
strongly
typed
and
then
what
we're
going
to
do
is
create
our
response
data
object.
So
this
is
our
shape
for
the
Adaptive
card.
E
E
E
E
And
we
have
our
form,
which
has
all
values
in
so
I'm,
definitely
going
to
have
stake
after
this.
Maybe
some
noodles
and
definitely
coffee,
I'm
gonna,
hit
place
order
and
there
we
go.
We
have
our
response.
We
have
our
responses
back
to
us.
We
have
a
button
which
we
can
carry
on.
We
can
add
more
actions
and
even
provide
edit
orders,
save
orders
as
well,
and
that
is
time
that
is
the
the
demo
I'll
not
carry
on
Visa
I'll.
Let
you
take
that
back.
Yeah
excellent.
B
Camera
really
awesome.
This
is
a
great
demo
and
create
storyline
and
create
way
of
actually
flipping
those
adaptive
cards
so
really
really
cool.
So
let
me
share
my
screen,
we'll
close
up
the
call
right
away
so
that
there's
no
extra
time
for
those
now.
Thank
you.
Bert
really
awesome
demo
and
thank
you.
B
Gary
really
awesome
stuff
as
well,
we're
one
minute
long
and
said,
but
it's
okay,
so
these
things
do
happen
and
it's
important
that
we
actually
get
a
full
functioning
demo
like
with
it,
which
is
really
cool,
so
the
recording
will
be
available
within
24
hours
at
the
Microsoft
racist,
Community
YouTube
channel.
You
cannot
download
the
recording
directly
from
the
chat,
so
just
a
bit
of
a
warning
on
that
one
and
we
always
get
requests
on
getting
access
on
those
recordings
that
does
not
work
for
external
people
in
the
Microsoft
teams.
B
Chat,
follow
us
on
Twitter
and
Microsoft
365
Dev
on
M365
PMP,
the
easiest
way
to
stay
up
to
date
on
what's
actually
happening
and
with
all
of
the
new
videos
and
announcements.
The
next
Microsoft
365
platform
call
is
on
November
15th
8am
Pacific
time.
So
next
Tuesday,
and
then
we
have
a
lot
of
other
calls.
You
can
check
them
out,
but
thank
you
for
this
one.
Thank
you
Gary.
Thank
you,
Bert,
one
more
time
for
your
great
stuff
and
thank
you
for
really
active
discussion
from
all
of
the
attendees
within
the
chat
as
well.