►
From YouTube: Introduction to Microsoft Graph Developer Proxy
Description
In this 14-minute developer focused demo, Sébastien Levert presents a load test simulation tool in preview for Pro Developers building apps on top of Microsoft Graph. Learn what is the Microsoft Graph Developer Proxy, install and see it in action. The Dev Proxy generates issues/errors so you can see how your app that’s making requests to the Graph API reacts under load, with and without the Graph SDK. Be confident your app will accommodate thousands of users in a tenant. Glimpse at what’s next. Use tool and provide feedback. This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on December 13, 2022.
Demo Presenter
• Sébastien Levert (Microsoft) | @sebastienlevert
Supporting materials
• Repo - Microsoft Graph Developer Proxy | aka.ms/graph/proxy
• Article - Introducing the Microsoft Graph Developer Proxy community preview | aka.ms/graph/proxy/launch
Learn more
• 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 - http://aka.ms/m365/community
A
Foreign
you're
gonna
have
to
wish
me
all
very
much
of
luck,
because
we're
gonna
do
one
of
the
first
live
demo
of
the
Microsoft
graph
developer
proxy
and
when
we
say
proxy,
it
means
playing
with
my
network
capabilities
while
I'm
doing
the
demo
so
we're
all
crossing
fingers
at
things
goes:
go
smooth,
I've
tested
it.
It
should
work,
but
if
you're
losing
me
just
I,
don't
know,
send
a
pigeon
here
or
something
like
that.
My
name
is
Sebastian.
I
am
a
senior
product
manager
on
the
Microsoft
graph
developer.
Experience
team.
A
You
might
have
known
me
from
the
past
around
some
capabilities
around
their
Microsoft
graph
toolkit,
but
today
I
want
to
bring
your
attention
to
the
Microsoft
graph
developer
proxy
that
we
released
a
week
and
a
half
ago
during
the
European
SharePoint
conference
as
I
think
a
really
cool
capability
for
pro
developers
that
are
building
on
top
of
Microsoft
graph.
That
is
any
type
of
devs
from
any
type
of
language
using
using
or
not
using
any
of
the
sdks
we
provide.
So,
let's
start
by
just
going
through
what
is
the
Microsoft
graph,
the
rubber
proxy.
A
But
when
you
push
that
to
production,
sometimes
you're
hit
by
the
realed
world
throttling
might
hit
you
service
issues
might
hit
you,
and
we
want
to
make
sure
that
you
get
an
understanding
of
these
things
are
about
to
happen
and
it's
normal.
We
live
in
a
cloud
world
and
that's
the
way
that
the
cloud
is
working.
A
So
how
can
you
simulate
that
and
that's
what
the
graph
Dev
proxy
really
brings
to
the
table,
because
it
helps
you
and
improves
the
quality
of
your
application,
because
you
hit
these
issues
way
way
way
before
you
used
to
hit
these
issues.
When
you
were
building
apps
that
are
landing
in
production
in
large
tenants,
you
can
have
the
ability
to
generate
throttling,
to
generate
service
errors
and
to
be
able
to
react
to
them.
So
you
don't
necessarily
need
to
generate
a
heavy
load
on
Microsoft
graph
itself.
A
What
you're
going
to
have
to
do
is
to
use
the
proxy
simply
use
the
the
common
line
that
we
provide
and
we
will
be
intercepting
calls
to
graph
where
we're
going
to
generate
429s,
where
we're
going
to
generate
503s,
which
are
I,
would
say
two
of
the
most
common
errors
we
see
on
graph,
but
you
can
also
provide
your
own.
The
own
area
that
you'd
like
to
test
against
you'll,
also
be
able
to
provide
your
own
mocks
So.
A
A
Why
is
that
useful?
Because
now
you
will
be
able
to
test
against
a
very
specific
scenario.
You
will
be
able
to
always
know.
What's
the
results
that
will
be
coming
back
from
the
from
graph
and
I
think
it's
going
to
help
you
building
quality
in
your
app
this
proxy
works
on
Windows
on
Mac
and
on
Linux.
A
It
also
works
with
WSL
and
that's
what
I'm
going
to
show
today
and
it's
currently
in
a
community
preview
state
so
we're
there
for
feedback,
we're
there
to
hear
from
the
community
on
scenarios
that
you
think
you
could
use
to
build
applications
to
really
increase
the
bar
when
you're
building
apps
with
the
Microsoft
graph.
So
we've
waited
long
enough.
Let's
go!
Let's
do
a
little
bit
of
a
demo
here.
A
Let's
show
you
a
little
bit
how
all
of
these
things
can
work
all
together.
So
let's
do
this!
Let's
bring
that
here
and
let's
start
with
this,
so
first
we
launched
a
couple
days
ago:
I
invite
you
to
go
and
read
in
depth
our
launch
blog
post,
all
the
material
that
sits
next
to
it.
I
think
you're
gonna
definitely
learn
a
lot
about
the
graph.
The
approxy
I
have
all
the
Links
at
the
end
of
the
presentation.
A
So
I
would
say:
let's
start
with
this,
like:
let's
I
would
love
you
to
go
on
and
do
this.
The
second
thing
that
I
want
you
to
do
is
to
go
and
look
at
our
repo,
so
we're
gonna
do
AKA
dot
Ms
slash
graph
proxy,
and
this
is
where
it
might
not
work.
It
actually
works
I'm
happy.
This
is
where
playing
with
the
network
is
tricky.
A
You're
gonna
see
all
of
our.
The
rubber
proxy
is
an
open
source
project
available
in
the
Microsoft
graph
organization
on
GitHub,
and
you
have
all
the
how
to's
our
manuals.
Our
Wiki
is
super
super
detailed
on
all
the
different
scenarios,
how
all
the
different
ways
that
you
can
use
to
graph
proxy
to
deliver
more
quality
applications,
so
it's
open
source-
and
this
is
where
we
need
your
feedback-
go
in,
go
into
the
repo
create
issues
we're
going
to
be
more
than
happy
to
respond
and
to
help
with
these
issues.
A
So
Now,
demo
time-
let's
go
here,
I
have
let
me
reload
this
page
here
and
let
me
go
here:
let's
go!
What
is
the
the
dev
proxy
Dev
proxy
is
a
CLI
it's
installed
globally.
On
your
machine
and
I've
done
that
before
joining
the
call
today-
and
here
you
see
that
we
have
multiple
ways
that
we
can
configure
our
proxy
in
this
case,
we're
going
to
launch
the
developer
proxy
on
a
specific
Port
which
is
8080.
In
that
case,
we're
going
to
ask
the
proxy
to
generate
a
failure
rate
of
50
percent.
A
So
every
single
requests
are
coming
in
is
going
to
have
a
50
chance
of
being
treated
as
a
failure
either
or
429
or
503.
You
can
actually
add
your
own
in
this
specific
scenario:
I'm
just
going
to
use
a
429,
but
you
could
do
any
type
of
errors
on
graph
and
we're
not
going
to
provide
any
mocks.
So
it
means
that
we're
going
to
use
graph
as
our
backing
store.
A
So
what
I'm
going
to
run
it?
The
proxy
will
go
in
listen
mode.
It's
going
to
listen
to
all
the
the
graph
calls
that
are
happening
on
my
machine,
and
this
is
where
it
becomes
tricky
when
you're
on
a
team's
call,
because
teams
is
actually
calling
graph.
So,
let's
see
how
much
of
this
is
working
and
how
much
of
this
is
not
working,
we
tested
it
earlier.
It
worked
great,
so
we'll
see
how
that
goes.
A
So,
starting
this
now,
it
just
says
that
I'm
listening
I
have
it's
registered
as
a
system-wide
proxy
on
my
machine
and
now
it's
listening.
So
let's
go
on
and
let's
try
to
see
an
example
of
an
app
that
we
built.
So
we
are
providing
this
sample.
It's
a
very
simple,
JavaScript,
simple:
it
doesn't
just
do
gyroscript.
The
proxies
for
any
language
is
going
through
graph,
but
in
this
specific
scenario
we
did
it
as
a
Javascript
app
where
you
have
the
ability
to
test
it
with
or
without
the
Microsoft
graph.
A
Sdk
we're
going
to
talk
we're
going
to
start
with,
without
with
a
very,
very
raw
way
to
get
data
from
Microsoft
graph
and
where
we're
not
really
handling
any
errors,
any
throttling
any
whatsoever.
So
we're
expecting
this
app
to
potentially
potentially
fail
right.
So,
let's
go
to
the
without
the
SDK.
A
Now,
I'm
going
to
hit
this
and
now
what
you're
going
to
see
here
is
first
you've
seen
that
the
and
we're
we're
lucky
here
because
we're
in
a
50
chance
of
generating
failures,
but
the
first
time
it
hit
we're
seeing
three
things
that
happen.
The
first
thing
is
we
intercepted
that
V
1.0
users
request
that's
great.
It
means
that
the
proxy
works.
A
A
We
highly
suggest
that
you
use
the
SDK
to
handle
errors
to
be
able
to
pass
in
your
own
middlewares
to
be
able
to
have
all
the
types
and
so
on
and
so
forth.
So
we
give
you
a
tip
on
that
query
where
you
can
go
on,
and
how
can
you
move
from
the
JavaScript
from
the
JavaScript
fetch,
for
example,
to
the
Microsoft
graph,
JavaScript
SDK?
A
And
third,
we
fail
the
request.
We
fail
the
request
with
a
429.
here.
It
says:
failed,
V1
users
with
too
many
requests,
and
here,
as
you
can
see,
my
app
is
totally
broken.
My
app
is
not
working.
Maybe
I
would
have
never
caught
that
when
I
develop
on
a
simple
developer
tenant
where
there's
no
load
where
I'm
the
only
one
developing
there,
because
here
I
basically
just
did
a
slash
again
on
slash
users
but
might
fail
sometime,
maybe
Azure
80
is
under
load
and
then
it
would
return
a
429..
A
But
here
you
see
my
app
is
totally
broken
now,
if
I
reload,
it
might
work.
Actually,
here
you
see,
and
now
you
see
all
the
requests
that
came
in
and
that
some
went
through
some
did
not
some
were
throttle.
Some
were
not
throttled,
and
now
you
see
that
my
app
is
kind
of
half
working
I
have
errors
on
some
images,
potentially
are
429
or
maybe
there's
no
image
for
that
user.
So
it's
working,
but
it's
working
potentially
half
the
time.
If
I
do
another
refresh
here,
it
might
take.
Oh
this
time
it
worked
here.
A
You
see
we're
literally
throwing
a
dice
and
and
see
that's
not
what
I
wanted
to
do
it
here,
bang
again,
it's
broken,
so
it
really
depends
on
on
on
on
the
percentage.
It's
a
great
way
to
do
integration,
testing
and
you
can
even
Force
f429
by
going
100.
For
example,
all
your
queries
would
return
429.
So
that
way
you
can
test
it
now
if
we
do
the
exact
same
demo,
but
with
the
SDK
going
here
now.
If
I
go
back
here,
go
down,
there
was
some
throttling
it.
It
goes
on.
A
A
More
will
be
a
lot
more
successful
when
we're
finally
launching
this
app
in
a
real
tenant
that
it
will
have
tens
of
thousands
of
users
using
my
application
same
thing
with
background
processes,
same
thing
with
an
Azure,
an
Azure
function,
calling
in
any
type
of
capabilities
you
want
to
build
could
benefit
from
the
graph
developer
proxy.
So
let
me
go
back
to
slide
just
before
I
hand
it
over
to
you
vesa.
A
A
We're
going
to
also
add
support
for
rake
limiting
headers
that
SharePoint
introduced
on
on
its
endpoint,
so
you're
going
to
be
able
to
to
mock
these
and
to
generate
failures
on
these
to
make
sure
your
app
works
accordingly,
we're
also
going
to
add
more
guidance
on
the
API
usage,
for
example,
when
you're
doing
a
call
to
the
API,
for
example,
on
you
users,
and
you
not.
You-
do
not
provide
a
specific
set
of
properties
that
you're
expecting
from
graph
we're
going
to
tell
you.
A
You
should
not
be
using
a
a
get
without
a
select,
so
you
should
be
using
it
and
it.
It
will
kind
of
be
used
as
a
an
advisor
to
your
to
your
development
techniques,
to
make
sure
that
you
get
the
full
value
out
of
graph
the
best
performance
possible,
the
best
error
management
possible
and
finally
try
it.
Now
you
can
go
on
a
repo,
AKA
dot,
Ms,
slash
graph
proxy,
and
if
you
want
to
read
the
announcement
graph,
slash
proxy
slash,
launch.