►
From YouTube: Microsoft Graph Community Call - August 2020
Description
In August's call, we cover people centric-experiences and provide an update on throttling.
Resources
Microsoft Graph website https://graph.microsoft.com
Build 2020 on-demand videos https://aka.ms/AA8m0yh
Graph Explorer https://aka.ms/AA8m0yf
Stay connected
Twitter https://twitter.com/microsoft365dev
YouTube https://aka.ms/M365DevYouTube
Blogs https://aka.ms/M365DevBlog
A
A
So,
as
your
host,
my
name
is
brian
t
jacket.
We
also
have
with
us
jeremy
thank
who
is
our
cpx
team
lead
as
well
as
kevin
belliger,
who
will
be
talking
about
the
people
central
experiences,
our
first
topic
that
we
want
to
cover
is
going
to
be
the
microsoft
graph
throttling
which
I'll
be
covering.
We've
got
a
number
of
different
updates
that
have
been
coming
through
in
the
last
month
or
so,
and
we
want
to
kind
of
cover.
A
What
are
some
of
those
changes
that
have
come
down
the
pipe,
but
also
a
little
bit
about
what
you
expect
in
the
future
as
well
for
things
in
this
space
now
at
a
very
high
level,
you
may
have
seen
this
previously.
We
have
our
documentation
for
much
of
graph
throttling
we've
got
the
link
up
here
on
top
of
the
page
now
at
a
very
high
level.
What's
important
to
know
about
throttling
for
microsoft
graph
is
that
we
have
a
number
of
different
throttling
levels.
A
So
if
you
look
at
the
very
top
we're
going
to
have
some
kind
of
graph
all
up
limits,
so
this
is
just
going
to
be
independent
of
any
of
the
specific
workloads
you
might
be
calling
there
are
some
things
that
apply
to
microsoft,
graph
as
a
whole.
One
step
below
this
you'll
see
that
there
are
different
limits
that
might
apply
that
microsoft
graph
applies
on
behalf
of
workloads.
A
Next
to
layer
down
is
going
to
be
with
the
main
kind
of
area
that
we
want
to
talk
about
today,
which
is
the
service
specific
limits
which
happen
per
workload.
Now,
in
the
past,
we
only
had
documentation
for
one
of
our
workloads,
which
was
exchange,
but
over
time
we
were
seeing
that
you
know
a
lot
of
our
customers
and
partners.
A
They
were
looking
for
more
information
about
what
can
I
expect
in
other
areas,
so
I'd
like
to
dive
a
little
bit
deeper
into
that
today
and,
lastly,
you
might
see
that
there
are
some
downstream
dependencies
as
well,
so
things
that
are
not
graph
specific,
but
they
are
things
that
are
being
used
further
on
beyond
just
graph.
So
some
of
those
times
those
limits
will
come
to
play
for
its
following
now.
What's
important
here
is
that
when
you
are
sending
a
request
to
microsoft
graph,
we
are
evaluating
across
all
these
different
first
service
levels.
A
Now
the
first
one
that
triggers
that
will
actually
initiate
the
throttling.
So
you
may
be
saying:
hey,
I'm
not
hitting
a
service
specific
one,
but
you
are
hitting
the
all
up
limit,
or
some
of
the
kind
of
configuration
like
that.
So
just
note
that
we
do
apply
all
the
different
rules:
different
throttling
thresholds
and
the
first
one
that
gets
hit
ends
up
tricking
into
the
throttling
scenarios.
A
A
We've
actually
had
30
or
more
pull
requests
being
submitted
to
our
documentation
site.
So
there's
been
a
lot
of
updates
in
this
space.
So
if
you've
looked
at
throwing
guidance
in
the
past,
you
know
maybe
six
months
or
so
it's
really
worth
going
back
and
looking
to
see
what
is
the
most
up-to-date
information
out
there.
We
do
actually
have
a
couple
more
pull
requests
that
are
in
progress
right
now.
A
So
all
this
has
been
done
in
the
open
if
it's
something
that
you
are
interested
in
or
want
to
take
a
look
into
feel
free
to
go
to
the
doc
site
and
take
a
look
through
the
pull
requests.
You
can
see
specifically
what
has
been
documented,
what
things
are
currently
still
out
there
and
what's
going
to
be
available
for
that,
so
in
terms
of
updates,
you'll
see
that
there
is
now
additional
guidance
for
areas
like
teams
for
online
meetings
for
a
number
of
the
other
specific
workloads
that
are
out
there.
A
A
And
here
you
can
see
our
documentation
page
for
microsoft.
Graph,
throttling
and
note
here
again
is
our
guidance
on
what
to
do
if
you
encounter
throttling
again
the
429s
for
two
minute
requests.
If
you
go
beyond
that
and
you
start
getting
because
503s
that
might
be
a
scenario
where
essentially
you're
getting
blocked
because
you're
not
adhering
to
what
those
429s
are
that
are
coming
back
again,
ways
to
handle
our
throttling
and
then
you
can
actually
go
in
and
see
here
are
all
the
new.
A
So
all
the
resources
that
support
the
retry
after
headers
again,
if
you
find
something
that
hasn't
been
documented
or
your
encounter
scenario
is
not
currently
in
line
with
what's
out
there.
Please
do
let
us
know
you
can
submit
feedback
on
the
actual
page
here
that
will
help
us
to
identify
what
are
my,
perhaps
those
gaps
or
those
areas
that
we
haven't
yet
covered
down.
A
Here
is
the
important
area
where
we've
made
a
lot
of
improvements
in
the
last
couple
months,
which
is
that
service
specific
limits,
so
you
can
see
again
here's
our
exchange
stuff,
but
as
you
go
down,
you'll
see
that
there's
a
lot
more.
That's
been
added
so
for
to
do's
cloud
communications,
onenote
project
rom
for
our
roaming
services
teams,
and
I
know
about
teams.
They
do
have
some
additional
information
on
here
under
this
microsoft
teams
limits
so
do
go
in
there
and
take
a
look
at
that.
A
You
can
see
a
lot
more
information
is
in
here
now.
One
thing
I
do
want
to
call
out
is:
this
has
been
a
gradual
approach
really,
the
the
first
phase
of
this
documentation
update
was
go
and
get
all
those
service
specific
updates,
documented.
First,
we
realized
that
by
putting
all
this
information
out
there,
the
organization
for
this
it
might
be
hard
to
find
the
specific
thing
that
you're
looking
for.
A
So
if
you
wanted
to
jump
to
some,
let's
say
the
education
service
limits,
you
really
have
to
scroll
down
to
the
page
to
actually
find
that
there's
additional
work,
that's
in
place
right
now
or
in
progress
right
now
to
address
that,
so
we
will
have
more
kind
of
coherency
in
terms
of
the
documentation,
that's
out
there
or
find
ability
for
it.
So
be
aware
that
that
is
coming.
It's
just.
You
know
we're
taking
this
into
phase
approach.
First
is
document
everything
then
work
on
the
organization
and
then
start
kind
of
a
phase.
A
Three
is
look
for
those
new
scenarios
that
don't
fit
into
ones
that
are
currently
defined.
As
you
know,
we
have
a
large
number
of
different
apis
and
workloads
on
top
of
myself
graph,
so
we're
trying
to
get
this
into
a
consistent
format
so
that
no
matter
which
workload
you're,
using
whichever
api
you're
calling
into
you're
going
to
get
a
very
consistent
result
based
on
what
you're,
seeing
back
from
that
and
then
one
other
important
area,
let's
go
to
the
very
bottom
one
here
just
know
that
the
subscriptions
as
well.
A
A
Now
we
would
love
to
hear
what
your
feedback
is
on
any
of
the
documentation
updates
that
you're,
seeing
or
some
of
the
changes
that
might
be
pushed
out.
One
of
the
kind
of
main
areas
we're
looking
for
is:
are
there
any
kind
of
business,
critical
blockers
that
you're
running
into
because
of
throttling?
You
know
we
talked
to
a
number
of
partners
and
customers
on
a
daily,
if
not
weekly
basis
kind
of
hearing
from
their
experiences.
A
What
are
you
experiencing?
What
kind
of
things
are
you
running
into?
Is
there
anything
that
is
preventing
you
from
actually
getting
the
work
done
that
you
need
to
those
are
things
that
we
can
then
take
back
to
the
different
workload
teams
and
be
able
to
to
work
with
them
a
couple
things
that
can
be
helpful
for
that
feedback
that
you
may
share.
You
know
what
is
the
frequency
that
you're
running
into
any
kind
of
throttling
scenarios?
A
What
are
the
specific
apis
or
endpoints
that
you're
calling
when
that
happens,
and
also
how
many
tenants
are
impacted
based
on
those
calls?
You
know
if
you're
a
line,
business
customer
and
it's
just
your
tenant,
that's
great.
If
you're
a
partner
and
you're
hitting
you
know
dozens
and
dozens
of
tenants.
That
also
helps
us
understand.
A
Let
us
know
it'll
be
very
helpful
for
us
to
understand
what
we
need
to
focus
on
in
terms
of
getting
those
things
addressed.
And,
lastly,
one
piece
that
we
did
see
come
up.
You
saw
a
blog
post,
I
think
about
two.
Three
months
ago
we
mentioned
that
there
were
throttling
limits
that
were
on
the
beta
version
for
on
those
apis.
A
A
I
will
say
that
with
the
sdk
in
general,
this
does
handle
a
lot
of
things
like
the
caching
of
your
access
tokens
or
being
able
to
understand
what
those
response
messages
would
be.
So
you
should
have
a
basically
a
well-typed
response
that
you
can
be
able
to
monitor
for
we'll
check
with
our
project
with
jason
johnson
and
see
if
he
has
any
kind
of
weight
samples
on
that.
B
Yeah
we
did
a
presentation
at
ignite
last
year
where
we
talked
about
walk
through
how
the
sdk
works
and
what
throttling
it
does
do.
I'll
put
the
the
links
for
that
presentation
in
the
chat
window.
I'm
just
going
to
go,
dig
it
out
from
the
ignite
site
and
we
specifically
kind
of
stop
the
the
sdk
doing
the
throttling
and
then
flip
the
throttling
on.
A
Okay,
great,
I
see
another
question
here:
onedrive
throttling
limits.
This
is
one
of
the
areas
where
we
are
still
working
on
getting
more
information
about
that.
If
you
look
in
our
docs
on
here,
we
do
have
basically
a
callout
for
that
and
there
is
a
link
over
to
documentation
from
the
sharepoint
side,
sharepoint
and
onedrive
and
you'll
see.
You
know
why
can't
you
get
just
in
a
specific
exact
thrilling
limit
for
sharepoint
onedrive
part
of
it
is
due
to
they
don't
have
a
defined
limit.
A
It's
almost
a
elastic
limit
so
based
on
the
load,
that's
going
into
the
entire
sharepoint
farm
or
one
drive
tenants
out
there
you'll
see
that
it's
not
it's
almost
a
sliding
scale.
So
it's
not
a
hard
defined
limit
out
there.
So
sharepoint
and
onedrive
do
have
additional
guidance
for,
like
their
rest,
apis
and
csom
in
terms
of
throttling
microsoft.
Graph
will
follow
similar,
but
not
exactly
the
same
types
of
limits
out
there.
B
A
A
A
Over
here
again,
this
is
once
there's
where
I
don't
think.
I
don't
see
this
documented
today.
Another
good
thing
that
you
can
submit
a
an
issue
for
to
call
for
additional
documentation
on
that
yeah.
I'm
not
gonna,
find
it
just
at
this
moment
I'll,
take
a
look
after
our
community
call
here
and
see
if
there's
any
additional
information
on
that
other
questions.
Other
comments,
things
that
you're
looking
for
any
kind
of
feedback
based
on
following
the
experience
in
the
previous
previous
calls.
A
Yes,
as
paul
mentioned
out
there
daryl
miller,
who
owns
our
sdks
at
the
moment,
he
did
some
work
on
a
chaos
handler
if
you're
familiar
with
netflix
and
some
other
large
organizations,
they've
got
things
like
chaos,
monkey
or
other
types
of
basically
middleware.
That
will
inject
failures,
so
you
can
actually
test
out
things
like
hey,
I'm
getting
throttled
or
I've
got
a
service
connection
interruption.
A
I
know
daryl
doesn't
work
on
this,
probably
a
year
or
so
ago.
So
I'm
not
sure
if
what
state
that's
currently
in,
but
there
has
been
discussions
around.
How
can
we
actually
simulate
this?
So
if
I
wanted
to
get
a
429
on
demand-
or
if
I
wanted
to
randomly
inject
it
into
my
queries,
that's
something
that
we
as
a
team
are
looking
at
and
we'd
love
some
feedback
in
terms
of.
A
C
Sounds
good
thanks.
Brian
thank
you
for
the
opportunity
to
come
and
present
to
everybody.
My
name
is
kevin.
I'm
a
pm
on
the
people
services
group,
so
we
control
all
of
the
people
services
that
power
microsoft,
365
things
like
contact
api,
the
profile
api
which
we
announced
in
at
night
last
year,
and
we
also
have
the
photo
apis
as
well.
I'm
sure
I'll
get
some
feedback
about
that
today.
C
If
I
talk
about
profile
preview,
so
the
the
profile
entity,
we
announced
that
ignite
last
year,
we've
been
steadily
working
on
that
for
past
six
or
seven
months,
and
we've
been
getting
a
lot
of
great
feedback
from
you,
our
customers
and
as
a
result
of
that
feedback,
we've
added
some
entities.
Some
of
these
will
be
very
familiar.
C
Some
of
them
are
things
that
have
cropped
up
since
ignite
last
year,
but
generally
speaking
in
august,
we'll
be
adding
support
for
about
50
more
entities
within
the
profile
things
like
notes,
so
the
ability
to
have
a
personal
annotation
about
yourself
and
really
express
a
little
bit
about
your
personality
within
your
profile
as
well,
there's
certifications,
awards
and
patents.
These
are
very
common
things
that
people
have
on
say
a
linkedin
profile
that
we've
been
hearing
from,
especially
our
larger
customers
or
customers
within
regulated
industries,
that
they
also
need
support
for.
C
In
order
to
find
that
person
that
has
a
specific
welding,
certification
or
managing
an
oil
rig,
or
something
like
that.
In
addition
to
that,
we've
got
things
like
publications
where
someone
has
been
mentioned
in
the
news
or
they've
written
a
research,
article
or
academic
paper
that
they
want
to
have
associated
with
their
profile
as
well.
C
C
So
what
you
see
here
is
just
a
representation
of
a
mock-up
experience
that
I
built
myself
last
week
during
one
of
the
hackathons
that
microsoft
has
annually
and
what
you
see
on
the
left
is
how
easy
it
was
for
me
to
actually
retrieve
the
interests
that
are
stored
within
my
profile
and
then
represent
them
in
the
ux.
So
you
see
a
effectively
a
one
line.
C
C
The
next
thing
I
want
to
talk
about
is
the
profile
card
customization
work.
So
this
is
another
piece
of
work
that
we
announced
at
ignite
in
2019,
we
launched
it
in
july
and
what
it
allows
is
a
tenant
admin
to
surface
some
of
the
data
that
happens
to
be
an
active
directory
or
azure
active
directory
today
that
isn't
actually
showing
up
on
the
m365
profile
card.
C
So
we've
got
a
walk-through
tutorial,
which
gives
you
step
by
step
for
going
and
configuring
the
the
tenant
side,
configuration
and
the
properties
and
how
you'd
like
to
represent
those
properties
within
profile
card,
and
then
we've
got
a
bunch
of
great
documentation
about
how
you
manage
and
customize
it
even
further
with
things
like
localizations
and
the
like.
So
I'm
going
to
take
a
a
quick
break
here
and
we'll
go
in
and
I'll
give
a
quick
demonstration
of
that
work.
C
C
Now,
if
these
were
to
show
up
in
the
experience
today,
they
would
just
show
up
with
custom
attribute
one
or
two
or
three.
In
this
case
it's
not
very
meaningful
and
it's
kind
of
hard
for
anybody
to
take
any
meaning
from
that.
Unless
you
know
explicitly
what
that
piece
of
information
is
meant
to
represent,
so
what
we
did
was
we
created
the
profile
card
properties
collection
within
the
organization
settings
container.
C
Now
what
this
allows
us
to
do
is
take
a
directory
property
name.
In
this
case,
we've
already
set
custom
attributes
three
to
be
represent
the
birth
date
of
a
user
within
a
within
an
organization.
That
means
if
the
property
was
present
on
a
user.
In
this
case
with
alex.
What
we
see
is
his
birthday
is
february
29th,
rather
than
representing
it
as
custom
attribute
three
february
29th.
We
would
actually
render
in
the
profile
card,
with
a
display
name
of
birthday,
for
this
particular
user.
C
The
post
itself
is
actually
very
simple:
you're
able
to
just
go
directly
to
profile.
Car
properties
enter
the
directory
property
name
in
this
case,
we'll
use
a
custom
attribute
2,
which
is
the
cost
center
for
our
user,
and
then
our
annotation
of
display
name
cost
center,
now
you're
able
for
organizations
that
are
not
only
having
a
single
language
as
their
organizational
language.
You
know
it
might
be
that
in
germany
you
use
german
and
norway.
You
want
to
use
norwegian
and
in
america
you
want
to
use
english.
C
C
C
C
A
C
Which
profile
api-
I
guess
is
my
question
there.
So
m365
has
a
handful
of
profile
apis
today.
If
it's
the
one
that
is
in
beta
in
microsoft
graph,
then
the
idea
is,
the
properties
represented
within
the
profile
will
actually
become
possible
to
also
surface
within
the
profile
card
within
a
short
period
of
time,
whether
that
be
extensions,
that
you
add
yourself
or
whether
that's
just
first
class
fields
that
aren't
today
represented
on
the
property,
I'm
sorry
on
the
profile
card.
C
I
think
that
sounds
like
a
great
feature
request.
It's
the
part
of
the
reason
why
we've
gone
about
this
was
because
some
of
the
challenges
that
the
directory
object
represents
devices
by
design
our
directory
objects
in
in
that
case,
so
I
think
it's
an
interesting
feature
request
to
ask
for
it
probably
won't
end
up
in
the
profile
anytime
soon.
Now,
I'm
sorry.
C
It
would
be
either
a
filter
or
a
select.
I
think
it
would
depend
on
how
we
implemented
it.
To
be
honest,
okay,
it's
a
it's
a
very
common
request.
We
receive
from
organizations
that
want
to
understand
one,
how
complete
people's
profiles
are
and
then
to
take
steps
to
increase
the
the
amount
of
data
that's
contained
within
them.
C
A
C
Yes,
that's
actually
there
today,
so
we
have
the
the
notion
of
allowed
audiences.
So
right
now
the
implementation
works
for
me,
which
is
only
I
can
see
a
piece
of
information
in
my
profile,
organizational
user
objects
within
my
organization
and
then
call
it
everyone
which
is
anybody,
can
see
it
as
we
continue
the
road
to
ga
we're
working
on
scoping
to
things
like
groups,
federated
organizations
and
there's
a
handful
of
others
that
we're
looking
at.
C
So
that
is
one
thing
we
hear
quite
commonly
as
well
is
as
we
as
we
look
at
ways
to
enhance
the
amount
of
information
that
is
shared
within
a
profile.
We
also
need
to
be
very
cognizant
of
the
fact
that
not
everybody
wants
to
share
everything
with
everybody.
A
great
example
is
pronouns,
which
is
something
we've
been
working
on
for
a
while
now,
but
we're
we
need
to
be
very
respectful
of
the
needs
of
people
to
also
feel
like
they
can
comfortably
express
themselves
also
securely.
C
No,
I
think,
please
feel
free
to
give
us
feedback
any
anything.
We've
missed
anything
you'd
like
to
see
present
in
the
profile
or
in
the
profile
card,
customization
capabilities,
other
things
that
we
should
be
building
related
to
people
and
and
the
data
related
to
them.
Please
feel
free
to
either
ping
me
by
email
or
twitter.
A
C
A
A
A
Check
out
online
yeah,
so
if
you
are
using
sharepoint
framework
spfx,
it
is
possible
to
create
client-side
web
parts
and
as
part
of
that
they
have
a
built-in
capability.
There
is
a
client
I
believe
it's
called
ms
graph
client,
which
has
the
capability
of
making
calls
out
to
microsoft
graph.
So,
if
you're
looking
to
run
queries
as
the
user,
there
is
a
basically
a
mechanism
for
making
those
calls
using
that
client
and
you'll
be
able
to
the
permission
is
a
little
bit
different,
whereas
there
is
a
tenant
tenant,
scoped
application.
A
That
makes
the
calls
on
your
behalf.
So
it's
not
a
individual
app
registration
that
you
would
bring
to
the
table.
Instead,
there's
one
that's
out
there
and
you'll
apply
permissions
to
it.
Once
that
is
consented,
you
are
able
to
make
calls
out
to
be
able
to
into
graph
from
a
sharepoint
framework
web
part.
B
Yeah,
partly
sorry
I'll,
just
explain
the
question
here,
I'm
familiar
with
the
ms
client,
ms
ms
graph
client
api
to
build
spf
xbox
parts.
I
was
just
wondering
if
there's
out
of
the
box,
you
know
any
future.
You
know
plans
of
of
developing
such
a
web
part
where
you
can
use
and
configure
just
like.
We
configure
query,
you
know
and
bring
you
know,
bring
objects
and
whatever
you
want
to
display
in
in
that
in
that
web
part
using
microsoft
graph,
some
something
out
of
the
box.
So.
A
B
No,
I
haven't
seen
it
kevin.
Is
that
something
that
you've
been
working
with
a
sharepoint
group
on
it
either
I
mean
this
is
something.
Obviously
it
could
be
done
as
a
pmp
web
part,
but
that
again
isn't
really
answering
the
question
of
it
being
out
of
the
box
and
more
of
a
community-led
effort.
The
microsoft
graph
toolkit
obviously
will
have
components
that
you
can
use
and
put
in
to
spfx
web
parts,
but
kevin.
C
A
A
Let
me
follow
the
link
to
make
sure
I'm.
In
the
same
thing,
oh
you're,
saying
pushing
like
a
mobile
push
notifications
or
even
like
the
windows
notifications
yeah
that
I'm
not
aware
of.
I
know
we
did
recently
republished
some
of
our
change
notification,
samples,
which
is
the
link
that
I
put
in
there.
But
I
don't
believe
that's
what
you
are
mentioning
yeah,
we'll
have
to
take
that
one
offline
and
see
if
there
is
anything
in
that.
B
A
A
Update
group
where's,
the
ad
member-
I
see,
there's
an
add,
a
member,
but
I
don't
see
one
for
joining.
Specifically.
Let's
join
teams
yeah,
I
I
don't
believe
there's
one
today.
I
know
it's
capability
to
do
that
in
the
exchange
online
command,
let's
but
that's
outside
of
graph,
and
it's
also
not
for
a
request
to
join.
That's
only
for
a
add
a
member
remove
a
member
subscriber
member
and
similar
and
paul
comes
in
here.
A
If
a
group
is
private
and
the
member
won't
be
able
to
find
a
join
link,
so
let's
see
in
here
is
there
a
way
to
use
token,
create
another
microsoft,
application,
I.e,
azure
devops,
to
call
microsoft
graph
apis
very
interesting
scenario.
If
you
look
back
into
the
ad
all
days
active
directory
application,
library,
authentication
library,
there
was
the
concept
of
what
we
called
a
multi-resource
refresh
token
mrrt.
A
I
don't
believe
that's
still
the
name
for
what
that
concept
is.
But
the
idea
was
that
you
could
have
a
single
azure
id
application
that
had
permissions
to
various
services
so
graph
and
sharepoint
and
exchange
and
azure
devops.
Or
what
might
what
have
you?
You
could
make
a
single
request
out
to
get
your
first
access
token,
but
the
refresh
token
could
be
reused
or
resubmitted
to
other
services
and
you'd
be
able
to
continue
using
that
without
having
to
do
the
first
initial
access.
Token
hop
basically
to
get
additional
tokens.
A
I
don't
know
the
current
status
that
if
that
is
supported
in
msal
or
if
that
is
something
that's
on
the
roadmap,
I'm
not
sure
if
jeremy
or
vincent
or
anyone
else
on
the
call
might
have
any
update
on
that.
I
know
something
that
was
supported
at
least
with
adal,
but
I
don't
know
the
the
currents
of
that.
A
Excellent
question
we've
been
in
good
talks
with
the
stream
folks,
there
should
be
more
to
share
in
a
couple
of
months
right
now.
There
is
no
stream
support
on
microsoft
graph
something
they're
actively
looking
into
and
when
there's
more
to
share
on
that
we'll
do
so,
but
at
least
today
there
is
nothing
supported
for
microsoft
stream.
A
Curious.
Any
plans
for
wvd
and
graph
integrations
is
that
windows
virtual
desktop?
Yes,
I
will
have
to
check
our
internal
roadmap.
I'm
not
aware
of
any
integration
points
there,
any
specific
things
that
you're
looking
for
from
craft
integration
with
that
bring
the
feedback
on
the
date.
Please
do
let
us
know
nothing.
I'm
aware
of
off
top
of
my
head
for
graph
integrations
with
virtual
desktop.
A
Why
can
some
graph
apis
only
be
used
with
delegated
access?
This
makes
automation
hard
to
implement
another
great
topic.
There
are
certain
apis
out
there,
shelter
name
nameless
that
only
support
delegated
access.
They
don't
have
app.
Only
that
might
be
just
a
case
of
it's
a
funding
issue
or
prioritization
issue,
and
they
don't
have
the
either
the
manpower
or
the
developers
support
for
that.
A
You
can
kind
of
fall
back
to
a
use.
A
service
account
in
terms
of
you
know,
use
that
as
a
delegated
user
out
there.
That
does
have
its
own
issues
in
terms
of
what
all
flows
you're
allowed
to
use
or
how
you
can
automate
that
kind
of
process.
If
there
are
specific
apis
that
you're
looking
for
app.
Only
please
please
do
let
us
know.
A
This
is
one
of
our
kind
of
key
points
that
we're
looking
at
in
the
next
probably
6-12
months,
working
with
various
workloads
and
api
owners
to
address
or
even
just
identify,
which
are
those
scenarios
that
don't
yet
support
application.
Only
we
have
kind
of
our
short
list,
of
which
ones
we're
targeting,
but
more
feedback
from
customers
and
partners
would
definitely
help
kind
of
make
that
case,
for
which
ones
do
we
need
to
address
and
kind
of
which
priority
order
so
feel
free
to
follow
myself
and
jeremy
offline.
A
A
I
don't
know
what
the
final
status
is
going
to
be
for
microsoft.graph.,
but
I
believe
we're
going
to
see
a
different
package
or
different
library
that
will
be
unified
across
all
the
different
kind
of
scenarios
that
will
help
with
that
ability
to
choose
like
how
do
you
actually
access
your
your
tokens?
So
last
I
saw
that
microsoft.
Graphic
auth
is
still
in
preview.
A
I
don't
believe
that'll
be
what
finally
gas
there'll
be
some
more
we're
just
sharing
that
in
the
future,
as
we
kind
of
bring
together
the
azure
side
of
the
house,
with
the
myself
graph
side
of
the
house,
there
you
go
jeremy's
in
azure
diet,
identity,
that's
the
the
package
christian
same
planner
for
us
as
well
great.
Thank
you
for
that.
A
Other
questions,
comments,
feedback,
other
things
that
you'd
like
to
hear
more
about
all
right
with
that
we'll
move
on
to
our
wrap-up
slides,
important
call
out.
We
do
want
to
make
on
here.
We
recently
kind
of
formalized
our
microsoft
graph
tap
program
with
this
there's
a
number
of
different
benefits
that
you
can
gain
as
a
customer
or
partner,
we're
holding
microsoft
graph,
tap
monthly
calls
on
this.
We
are
sharing
nda
information
in
terms
of
what
are
things
coming
down:
the
road
early
access
to
private
previews
or
things
that
are
coming
up.
A
So,
if
you're
looking
to
join
into
this,
please
do
submit
to
our
form
on
here.
If
you
follow
the
link
at
the
bottom
of
the
page
on
here,
aka
dot,
ms
slash
graph
tap
form
all
one
word:
no
spaces
on
there
feel
free
to
submit
into
there
we're
reviewing
our
submissions
on
usually
a
weekly
basis,
or
so
so
hear
back
from
us.
Do
note
that,
just
by
applying
it
does
not
guarantee
acceptance
into
this.
There
are
a
couple
of
requirements
in
place.
A
First,
in
terms
of
having
a
valid
nda
signed
with
microsoft
already
so
feel
free
to
submit
into
that.
If
that's
something
that
you
would
like
to
join
into
and
help
us
gain
early
feedback
into
a
lot
of
different
apis
and
things
that
are
being
built
out
also
do
be
aware
that
we
have
a
number
of
different
community
calls
across
all
the
microsoft
365
developer,
ecosystem
that
detective
cars
graph
for
ourselves,
identity
teams,
office,
add-ins,
powerapps,
sharepoint,
sharepoint,
general,
dev
and
sharepoint
framework.
A
You
can
find
all
these
different
calls
together
on
the
bottom
link
as
well.
Aka.Msm365
dev
calls
please
do
join
in
just
having
this
healthy
ecosystem
of
people
bringing
their
feedback,
bringing
their
opinions,
ideas
all
the
things
they
want
to
share
that
really
helps
for
a
vibrant
community
and
helps
make
the
entire
ecosystem
grow
better.
A
Also,
jeremy
and
our
own
paul
shafeline.
They
do
host
a
podcast,
microsoft,
365,
developer,
podcast.
You
can
be
able
to
find
out
a
lot
of
great
interviews,
insider
tips,
news
information.
I
listen
this
on
a
weekly
basis,
myself.
Some
of
the
recent
episodes
are
on
here
as
well,
discussing
fluent
ui,
microsoft,
lists,
identity,
libraries
and
so
forth.
A
lot
of
great
topics
out
there
that
highly
recommend.
A
I
know
it's
a
little
more
difficult,
sometimes
to
listen
to
podcasts
now
that
we're
in
kind
of
lockdown
mode,
but
a
great
way
to
stay
up
to
date
on
what's
going
on
in
my
soft365
developer
ecosystem,
and
with
that
we
thank
everyone
for
joining
us
today
on
our
august
2020,
microsoft,
graph
community
call.
Our
next
call
will
be
on
september,
2nd
again
at
8
00
a.m.
A
Pacific
time
you
can
find
the
link
for
joining
into
the
call
at
the
bottom
of
our
page
on
here
and
note
that
the
recording
for
this
session
will
be
available
on
the
developer
youtube
channel
following
today,
so
feel
free
to
view
into
that
at
your
at
leisure.
As
well
with
that
I
thank
everyone
for
joining
us
today.