►
From YouTube: Microsoft Graph community call-January 2021
Description
We kicked off 2021 with a bang. Topics included Microsoft Graph Changelog v2, community demo on a meeting booking app and a call for feedback on Microsoft Graph feature priorities.
Speakers: Brian Jackett, Molly Shove, Kevin Ritchie (Paradise Computing)
Resources
Survey https://aka.ms/GraphDevSurvey
Changelog https://developer.microsoft.com/en-us/graph/changelog/
Demo walkthrough https://kevinritchie.co.uk
A
Welcome
everybody:
this
is
the
microsoft
graph
community
call
for
january
of
2021.
today,
on
our
session,
we're
going
to
be
having
molly
and
kevin
presenting
I'll
be
talking
about
change.
Log
version,
two,
some
new
recent
updates.
We
have
releasing
for
that
also
like
to
get
some
your
feedback
on
that
and
then
kevin
will
be
joining
us
doing
a
community
demo
talking
about
a
meeting
booking
app
that
he's
developed,
microsoft,
graph
and
some
other
related
technologies
so
like
to
showcase
those
for
you,
one
thing
that
we
will
add
to
the
agenda.
A
I
will
just
make
a
quick
note
of.
We
do
have
a
microsoft
graph,
developer
survey
on
this
coming
from
our
team
different
kind
of
pieces
of
feedback
that
would
be
looking
for
in
terms
of
how
you're,
integrating
with
microsoft
graph.
What
are
some
of
the
different
things
you'd
like
to
see
us
make
investments
into
so
we'll
get
to
that
here
in
a
second
and
then
we
have
our
two
topics
for
the
day
as
well.
A
Also
note
that
if
you
are
interested
in
presenting
again,
we
do
have
slots
available
to
us
later
in
this
year,
if
you'd
like
to
present
on
anything
related
to
microsoft,
graph,
whether
it's
a
solution
that
you've
built
some
kind
of
new
thing
that
you're
working
on
other
kind
of
things,
you'd
like
to
showcase,
please
do
reach
out
to
us.
You
can
reach
us
at
brian.jacob,
microsoft.com
or
jeremy.think
microsoft.com.
A
Please
do
include
things
like
the
solution
or
the
topic
that
you'd
like
to
review
what
other
apis
are
being
used
or
any
kind
of
platforms
or
services
that
are
included
in
that
we'll.
Take
a
look
at
that
work
with
you
on
something
we
can
fit
into
our
schedule
later
on
in
the
year.
We
do
appreciate
any
kind
of
contributions
or
things
you'd
like
to
share
with
us.
A
I
do
want
to
call
on
on
here.
We
do
have
a
microsoft
graph,
developer
survey
that
has
been
launched
just
at
the
end
of
december.
Really
this
will
take
about
five
minutes
to
fill
out.
What
we're
looking
for
is
different
things
that
you're,
perhaps
using
myself
graph.
What
are
some
of
the
different
areas
that
you
think
could
use
more
investment,
whether
that's
code,
samples,
documentation,
different
aspects
of
the
graph
itself?
So
please
do
take
the
time
to
fill
this
out,
so
you
can
get
to
this
at
aka
dot.
A
Ms
slash
graph,
dev
survey-
and
please
do
take
the
time
to
fill
this
out.
That'll
be
great
for
us
to
get
this
feedback
and
incorporate
this
into
our
planning
for
the
coming
semester.
Without
further
ado
we'll
hand
things
over
to
molly
to
talk
to
us
about
the
mix
of
graph
change.
Log
version
two
molly
the
floor
is
yours:
can
I
go
ahead
and
take
over
presenting.
B
I
would
give
me
just
a
moment:
let's
talk
about
the
change
log,
the
labor
of
love
of
my
past
many
months.
We
have
included
many
beautiful
new
features
in
the
changelog
2.0.
You
can
filter
by
date,
parent
workload
and
version.
You
can
also
filter
by
change
type,
but
I
forgot
to
put
that
into
the
slide.
You
can
subscribe
to
an
rss
feed
and
we
have
searchability,
there's
also
a
bunch
of
fancy
automation
stuff
under
the
hood,
which
is
very
exciting
for
us
and
probably
less
exciting
for
you.
B
B
We
also
have
future
plans
for
it.
Although
our
future
plans
in
large
part
depend
on
your
feedback,
we
I
think
it's
very
important
to
have
a
dark
mode,
but
that
won't
be
coming
for
a
long
time,
but
soon
we
are
hoping
to
have
better
support
on
notifying
about
deprecation
and
fixing
a
couple.
Just
miscellaneous
tiny,
ux
front
end
things
move
like
sovereign
plugs
port
as
well,
and
we
want
to
do
powershell
support,
but
we
just
haven't
gotten
there.
Yet,
if
you'd
like
to
try,
it
feel
free
to
click
there.
B
Let's
just
say
that
you
want
to
see
everything
having
to
do
with
the
event
entity.
You
can
type
that
in
and
in
theory
oh
here
it
is
event,
event,
event,
event
event,
and
it
doesn't
just
show
you
things
in
calendar.
It
will
show
you
things
in
identity
and
access,
although
that's
a
different
one,
oh,
and
something
in
lifestyle
notification
still
about
the
event
entity,
so
you
can
see
sort
of
cross
api
changes
to
a
specific
entity.
B
If
you're,
like
I
only
care
about
things
in
event
for
beta,
then
battle
tracks
lovely
date
filters
if
you
would
like
them.
So
I
think
you
all
are
getting
the
general
idea,
but
please
come
try
it
out.
Let
me
know
what
you
all
think
and
specifically
I'm
going
to
get
back
to
the
slides.
So
we
can
talk
about
feedback.
B
I
would
love
to
have
feedback
on
this.
What
features
come
next
is
going
to
depend
largely
on
your
feedback
and
support
directly.
So
please
give
it
to
me
otherwise
I'll
just
go
on
vacation.
Please
add
me
in
the
chat.
If
you
would
like
to
do
something
or
email
mollyshove
at
microsoft.com,
please
put
feedback
change,
log
feedback
into
the
subject
line
so
that
way
I
can
find
it
and
I
don't
lose
it
and
also
so.
My
email
rules
can
do
magical
things.
B
So
it's
easier
to
sort
and
keep
track
of
what
everyone
says
and
then
I
would
prefer
if
everyone
is
very
specific
in
their
feedback.
So
don't
tell
me
that
it
looks
bad.
Tell
me
that
the
title
should
be
green
and
in
comic
sans
or
don't
tell
me
that,
because
that's
probably
not
going
to
happen,
I
feel
as
if
I'm
not
sure
what
marketing
is
doing
right
now,
but
I
don't
think
comic
sans
is
in
their
plans
all
right.
That's
all
for
me.
Unless
anybody
has
any
questions,
comments,
thoughts,
feelings
that
they
want
to
share.
A
So
for
everyone,
if
you'd
like
to
put
your
comments
or
questions
into
the
text
box
or
if
you
can
do
the
raised
hand
feature
in
teams,
we
can
then
kind
of
go
through
people
as
they
come
through.
One
thing
I
do
have
for
you
molly.
I
saw
that
it
has
a
preview
at
the
top
of
the
the
new
change
log.
What's
the
timeline
for
us
getting
to
v1,
or
you
know,
full
release
for
this.
B
A
Excellent,
any
questions
from
the
community,
the
things
you'd
like
to
see
any
kind
of
feedback.
Any
questions
like
to
ask.
While
we
have
molly
here
online
question
from
christoph,
where
do
we
get
these
slides
or
urls?
We
do
not
publish
the
slides
themselves,
but
we
do
record
all
the
meetings
and
we'll
put
these
onto
our.
A
B
It
is
not
something
that
I
can
actually
demo,
particularly
like
quickly
or
smoothly,
because
I
am
not
a
person
who's
very
fluent
with
rss
I
am
yeah,
so
it
does
work.
I
will
say
that
if
you
are
testing
it,
it's
in,
at
least
in
the
version
of
edge
that
I
use
it,
tries
to
format
the
rss
a
little
bit,
and
so
you
need
to
make
sure
that
you're
not
just
opening
up
the
window,
but
that
you're
opening
it
like
you're,
inspecting
and
seeing
the
elements
and
getting
sort
of
the
raw
rss.
C
B
B
B
B
A
B
A
B
A
B
Awesome
no
worries.
Thank
you
also.
If
you
do
think
that
it
looks
nice
and
stuff,
please
also
send
those
emails
to
me
like
it
doesn't
all
have
to
be
constructive
criticism
in
part,
because
if
you
are
all
feeling
very
satisfied
with
it,
then
we
can
get
it
into
ga
sooner,
probably
rather
than
later
like.
If,
if
you
you
are
the
people
who
judge
to
say
hey,
this
is
ready
in
a
big
and
deep
way.
A
C
Right
well
well,
thanks
for
having
me
on
ryan,
it
was
it.
It
was
quite
a
shock
to
actually
get
someone
to
get
in
touch
and
say
how
the
fans
are
talking
on
the
community
call.
So
I'll
hold
my
hands
up
straight
away
and
say
this
is
my
very
first
community
call
ever
and
first
ever
demo,
so
people
will
have
to
bear
with
me
if
it
isn't
great.
I
do
apologize.
C
C
So,
let's,
let's
get
rid
of
it.
You
know
we
need
to
have
something
electronic.
You
know,
there's
plenty,
there's
plenty
of
pieces
of
software
out
there
that
do
this
already,
but
you
know
for
me
it
was
you
know
we
wanted
to
try
out
building
something
in
blazer,
because
it
was
you
know
new
for
us.
We
quite
likely
thought
yeah.
Let's
have
a
go
at
that,
but
also
it
was
an
opportunity
to
use
the
graph
as
well.
C
So
it
was
quite
an
easy
decision
for
us
to
make
to
say:
well:
okay,
let's,
let's
just
build
something
of
our
own,
it's
an
internal
application
for
business.
It's
not
a
commercial
application,
so
you
know,
let's
spend
a
bit
of
time,
researching
the
graph
from
blazer
and
things.
Let's
see
what
we
can
pull
together
so
over.
You
know
course
of
a
you
know
a
day
we
we
managed
to
pull
together
a
fairly
decent
application
for
us
to
use.
C
C
C
The
other
bits
we
needed
to
do
for
the
application
was
storing
references
to
our
authentication
authority.
We
need
to
store
things
for
our
tenant,
id
client
id
and
a
client
secret.
You
know
the
bits
that
you
know
we're
gonna
pass
to
the
graph
to
be
able
to
get
a
token,
and
then
you
know
communicate
with
the
graph
and
do
what
we
need
to
do
with
this
certain
apis.
We
need
now
sort
of
the
first
thing
we
needed
to
do,
and
I
appreciate
you
know
from
teaching
people
to
success.
C
I'm
sorry,
you
know
I'll
just
quickly
go
through
this
before
we
jump
into
it.
You
know,
quick
demo
is
that
we
needed
to
create
an
app
registration
in
the
azure
portal
and
it's
relatively
straightforward,
just
generating
an
app
go
search
for
an
app
registration.
You
generate
it.
The
one
thing
we
failed
to
realize
is:
we've
got
you
know
multiple
tenants,
just
making
sure
you
create
this
app
registration
in
the
right
tenant.
C
Otherwise,
you
know
the
results
you're
going
to
get
back
when
you're
searching
for
you
know,
employees
or
anything
might
not
be
the
right
ones.
So
it's
always
worth
noting
that
making
sure
you're
pointing
at
the
right
tenant.
You
know
when
you're
creating
this
app
registration
in
the
app
registration
there
was
that
you
know
we
had
to
create
the
the
secret
that
we
were
going
to
use
for
the
application
and
also
configure
the
graph
api
itself
and
what
permissions
we
wanted
to
use.
C
Now
you
can
have
delegate
permissions
or
application
permissions
for
us,
because
this
was
a
standalone
application.
There
was
no
one
logging
into
it.
We
just
went
for
the
application
permissions
and
using
user
read
all
permission
because
all
we
needed
access
to
was
the
managers
and
their
direct
direct
reports
and
photos.
That's
that's
all
we
needed,
so
it's
really
straightforward
and,
in
terms
of
you
know,
storing
the
sort
of
secrets
in
client,
secret,
tenant
id
and
things
like
that.
We
have
actually
stored
those
in
the
app
settings.
C
Json
file-
and
I
know
many
people
are
crying
horror,
but
we
decided
to
do
that
because
it,
you
know
it's
a
low
collapse
to
us.
It's
within
our
network,
and
you
know
we
wanted
to
get
the
app
up
quick
and
get
it
running,
ideally
and
in
future
sort
of
versions
of
the
application.
We
can
move
that
off
into
the
usual
key
vault
and
keep
all
the
information
there.
C
So
we
can
have
a
nice
little
photo
when
you
know
a
visitor
wants
to.
You
know
select
which
person
they're
there
to
visit.
That's
what
I'll
do
now
now
we're
at
the
demo.
What
I'll
do
is
I'll
quickly
take
people
through
just
a
quick
snippet
of
the
code
that
we
wrote
just
to
connect
into
the
graph
and
again
you
know
very,
very
straightforward.
C
You
know
it's
not
complicated
and
that's
the
thing
I
like
about
this.
You
know
it's
a
good
thing
about
the
graph
is
that
it's
easy
to
get
started
with
lots
of
information
on
docs
microsoft
as
well.
An
equally
a
good
tool
to
use
was
the
graphic
explorer
because
it
you
know
it's
a
good
sort
of
testbed,
for
you
know
firing
in
your
ap
apis
to
test.
You
know,
make
sure
that
they're
returning
the
right
thing
so
that
that
was
handy.
C
So,
as
you
can
see,
as
I
alluded
to
we're
keeping
the
settings
within
the
app
settings,
json
file
for
the
application-
and
this
is
just
a
way
of
us
getting
that
information
out
of
the
app
settings-
we
create
our
uri
for
authority
here
when
you're
enough,
a
confidential
client
application
builder.
You
see
passenger
client
id
authority,
the
secret,
giving
ourselves
a
scope
for
that,
and
this
is
the
bit
where
we
actually
acquire
our
token
by
the
confidential
client
application
builder,
which
we'll
then
use
to
pass
in
with
the
request.
C
Headers
the
authorization
request
settings
with
the
client,
so
you
can
see
here
the
result,
so
we
have
our
access
token
once
we
have.
That
means
we're,
then
authenticated
within
the
graph
and
the
easy
thing
to
do
here
for
us
some
naughty
code
here
in
there
is
don't
cry.
It's
hard
coded
email
addresses
for
some
of
the
managers.
It's
only
five
of
us
in
the
business.
It's
not
big,
so
we
quickly
hardcoded
it
in
there
just
to
get
the
app
up
and
running,
and
ideally
you
know,
obviously
would
store
that
in
a
database
somewhere
or
whatever.
A
And
kevin,
I
know
one
thing
that
you
and
I
discussed
previously
was
potentially
replacing
some
of
the
http
calls
or
some
of
the
you
know,
custom
classes
with
someone
like
the
sdks
for
years
of
use
for
actually
being
able
to
hey.
I've
got
a
strongly
typed
entity.
I've
got
other
things
I
can
do
directly
with
it
right.
C
Yes,
absolutely
and
one
of
one
of
the
things
that
you
know
eventually
we'd
like
to
do-
and
hopefully
this
will
come
in
with
the
graph
api
at
some
point-
is
being
able
to
communicate
with
teams
directly
as
well,
because
one
of
the
one
of
the
things
in
the
application
itself
as
well
is
that
once
someone's
booked
into
the
business,
it
then
uses
power
automate
to
then
send
a
notification
to
that
person
or
the
employee.
That's
been
visited
that
someone
is
now
in
reception
waiting
for
them.
C
C
Address
well
that'll.
Do
the
system,
in
the
background,
is
going
off
and
checking
if
this
person's
actually
been
here
before,
if
they
have
they'll
present
them
the
screen
with
their
details
to
say,
yeah
is
this
you
and
if
it
is,
you
know
we'll
bypass
entering
your
information.
So
you
know
your
company
information,
your
name.
C
You
can
edit
your
vehicle
registration
if
you
need
to
accept
health
and
safety
policy
for
the
site
and
at
the
start
of
the
application.
Basically,
what
it
was
doing
was
running
off
into
the
graph,
and
it
was
pulling
out
all
this
information
and,
as
you
can
see,
it
was
all
the
people
in
the
business.
C
C
A
To
see-
and
I
like
I
like
that
you
mentioned
about
you-
know
calling
into
graph-
you
already
have
access
to
whoever
my
users,
who
is
their
manager,
who's
their
direct
reports.
I've
got
my
profile
pictures
like
we're,
basically
reusing
all
the
data
inside
of
m365
inside
of
an
application.
You
don't
have
to
go
and
yeah
here's,
my
user
store
and
here's
my
you
know
set
of
relationships
for
who
reports
to
who,
like
it's
all
existing
informations,
you
can
kind
of
reuse,
yeah,
absolutely
and.
C
One
of
the
things
we
also
loved
about
it
was
the
fact
that
we,
we
didn't
have
to
you
know,
manage
those
users.
So
if
we
have
new
employees
joined
in
the
business
we're
already
there,
we,
you
know,
they've
been
added
to
active
directory
or
whatever
you
know,
they're
in
and
365,
so
we
can
pull
from
that
straight
away,
they're
just
there
there's
no
management
of
that,
which
is
great
one
of
one
of
the
things
that
we
we
did
look
at,
and
this
is
one
of
the
sort
of
play
projects
that
I've
got
on.
C
The
side
is
then
using
the
azure
cognitive
services
to
be
able
to
use
either
face
recognition
or
the
speech
services
so
that
we
can.
Actually
you
know
people
don't
have
to
touch
keyboards
they
can
it
can
the
computer
itself
can
visualize
the
person
that
you
can
speak
to
it
and
actually
do
the
booking
process
for
you.
So
you
don't
have
to
use
your
hands.
C
What
I
did
do
I
have
written
on
an
article
myself,
much
like
first
steps
as
well.
So
this
is
a
quick,
quick,
blog
post
that
will
take
you
through
how
we
created
gap.
Registration,
how
we
you
know
the
code
snippets
for
having
connected
and
all
the
sort
of
links
to
those
resources
and
microsoft
docs
as
well,
so
straight
to
the
apis
and
everything
like
that.
So
that's
that's
all
there!
C
A
C
A
A
A
Things
like
that
that'd
be
great
to
just
even
hear
from
a
community
perspective
of
hey.
We've
got
our.
You
know,
v1
launch
out
there
and
then
what
do
we
do
to
kind
of
build
upon
that
further
and
leverage
more
services
or
leverage
more
features,
absolutely
yeah
and
I'd
definitely
love
to
get
back
in
touch
once
we've
got
something
like
that.
Absolutely
again,
we
appreciate
your
time
kevin.
A
Thank
you
so
much
for
sharing
this
demo
and
kind
of
walking
us
through
how
you
integrate,
mix
up
graph
and
all
the
other
kind
of
components
that
went
with
that
as
well.
All
right.
Thank
you.
Thank
you.
So
much
I
will
take
back
over
present
my
screen
at
this
time.
We've
probably
got
about
10
15
minutes
or
so.
If
anyone
has
any
questions,
any
other
kind
of
things
they'd
like
to
ask.
A
Does
graph
have
a
verbose
option
to
add
in
the
odata
rest
query?
So
if
I
understand
the
question
correctly,
what's
the
actual
underlying
query
that's
being
made
whether
that's
like
the
internal
api
or
what
else
is
being
sent
through
that,
and
I
will
share
out
my
screen
here-
real
quick,
let's
go
over
to
graph
explorer
and
you
can
get
to
this
through
aka
dot,
ms
slash
e
k,
a
dot,
oops
dot.
A
A
I
can
highlight
it
properly.
This
is
actually
what
we're
going
against.
So
here's
graph.windows.net
v2
and
you
can
see
over
here
the
users,
basically
the
user,
that's
being
passed
into
now.
What's
fun
is,
if
you
are
trying
to
debug
a
scenario,
sometimes
you'll
have
a
invalid
syntax
or
something
else
that
is
not
getting
back
to
the
happy
path
that
you're
thinking.
So
if
I
go
something
like
me,
join
teams
and
also
one
other
awesome
little
highlight
on
here.
We
do
have
intellisense
now
on
graphic
explorer
as
well.
We
just
released
that
I
believe
in
december.
A
So
thank
you
to
betty
and
team
for
getting
that
out
there.
So
I
connected
to
intellisense
to
look
up
different
queries
that
are
happening
on
here.
But
if
I
look
at
something
like
me,
join
teams,
instead
of
going
against
that
graph.windows.net,
which
is
essentially
the
azure
active
directory
endpoint
instead
go
to
here
for
the
join
teams.
I
can
now
pass
on
that.
A
So
what's
the
actual
endpoint
that
this
is
going
against,
but
it
can
help
from
a
kind
of
diagnosing
or
troubleshooting
perspective
to
know
that
hey,
this
query
is
going
against
sharepoint
or
this
one's
going
against
outlook,
this
one's
going
against
azure
active
directory,
so
that,
when
things
happen
differently
or
you're,
getting
back
up,
you
know
would
be
a
different
response
than
as
expected.
You
get
a
little
bit
of
insight
into
oh
it's
because
it's
going
to
this
api
and
it's
a
valid
syntax
here,
but
it
may
not
be
a
valid
syntax
there.
A
A
I'm
just
asking
there's
a
flag
on
the
bookings
page:
how
to
turn
this
flag
on
using
microsoft,
graph,
api
or
some
other
script
change
the
default
flag
to
on
may
have
to
follow
up
on
that
one
offline
unless
fabian,
I
know
you're
kind
of
our
resident
bookings
expert.
If
you
have
anything
to
to
bring
in
on
punkaj's
question
on
here.
A
D
365
bookings
and
we
actually
have
no
problem
with
reporting
off
of
standard
bookings.
It's
just
the
group
bookings
appear
to
not
be
exposed
via
microsoft,
booking
api.
I
actually
have
a
point
to
open
up
with
microsoft,
premiere
to
just
find
out,
if
you
know
there's
if
they're
on
there.
If
it's
a
feature.
C
D
A
G
A
A
I
don't
see
beth
or
nicola
in
the
call
either
I
know
with
mgt.
They
did
just
release
the
version
two
and
there
was
some
mentioning
about
adding
theming
support.
I
don't
know
if
that
actually
made
it
into
the
v2
release
or
not
or
if
that's
something
that's
gonna
be
coming
at
a
later
date,
but
I'll
have
either
elise
or
sebastian
or
someone
else
see
if
we
can
get
any
kind
of
update
on
that
question
here
from
jose
a
developer
spa
using
graph
on
sharepoint,
so
libraries
and
production
fields
are
not
indexed.
G
G
It
doesn't
return
the
ques.
The
graph
query
in
explorer
doesn't
return
any
any
errors.
Just
doesn't
return
any
data,
but
when
I
go
to
the
sharepoint
library
I
see
I
see
the
data
there,
so
I
just
wanted
to
give
the
administrator
a
guideline
or
document,
so
he
can
do
it
properly.
It
was
working
in
qa
but
we're
having
this
program
in
production
right
now,.
A
A
There
is
some
variance
in
that,
depending
on,
if
you're,
a
user
versus
administrator,
not
something
I've
had
to
deal
with
in
quite
a
while.
So
I
won't
be
the
expert
on
that.
But
generally,
once
you
have
more
than
5000
items
in
a
list,
you
may
or
may
not
be
able
to
actually
add
an
index
to
a
new
column.
Sometimes
you
have
to
go
below
that
limit,
add
the
index
and
then
go
be
able
to
then
go
back
above
the
limit.
G
A
A
E
A
A
Let
me
go
back
to
graph
reference
use,
query
parameters,
and
so
in
here
you'll
see
what
are
the
supported
kind
of
filters.
So
when
you
do
a
filter
parameter
here
is
what
is
supported
at
a
high
level.
So
you'll
see
like
starts
with
or
ends
with,
and
here
contains,
is
not
supported
on
any
of
the
craft
resources.
I
think
this
is
more.
E
A
E
A
Being
able
to
use
fluent
again
we'll
also
follow
some
of
our
entity.
Folks,
when
will
the
next
powershell
graph
sdk
updates,
be
pushed
no,
not
a
problem
if
you
actually
follow
along
under
the
github
repo
for
this,
I
know
that
it's
not
following
the
strict
cadence
of
what
we
have
for
some
of
the
other
ones,
because
it
says
it
literally
just
released
a
v1.
A
A
So
the
powershell
sdk
is
version
one.
It
is
production
supported.
If
you
want
to
be
able
to
use
it,
it
did
just
release
the
v1,
though
in
was
that
around
ignite
time
of
last
year.
So
if
you
have
future
requests
or
things
that
you're
looking
for
in
here,
definitely
feel
free
to
add
them
as
issues
onto
the
github
repo
here,
something
that
they
are,
you
know
prioritizing
in
terms
of
things
that
are
coming
up.
A
E
A
You'd,
like
if
you'd
like
to
please
type
up
that
that
feedback
and
send
it
over
to
me
brian.jack.microsoft.com.
I
was
talking
with
some
of
the
folks
who
actually
managed
this
sdk
about.
How
can
we
best
publish
some
samples
for
this?
I
know
that
we
do
have
like
the
powershell
gallery
and
there's
some
other
different.
You
know
repos
online
for
samples.
We
don't
have
like
an
official
place
for
them
for
powershell
with
something
that
is
top
of
mind
for
that
team,
so
the
more
feedback
that
they
get
the
more.
A
So
when
you
look
at,
for
example,
you're
just
going
to
like
users
get
user
you'll
see
in
the
docs
down
here
we
have
samples
for
http
javascript
objective-c
java
at
a
later
date.
We
will
add
one
for
powershell
no
timeline
on
that.
It
is
work
in
progress
and
it's
a
little
bit
different
in
how
we
generate
those
samples
compared
to
some
like
the
the
manage
code
languages.
So
just
note
that
that
is
something
on
our
roadmap.
I
just
don't
know
where,
where
exactly
that's
gonna
land.
A
A
I
don't
see
any
additional
questions
on
here
and
we
are
getting
close
to
our
end
of
time
really
do
appreciate
everyone
joining
us
today,
flip
back
over
to
our
slides.
I
do
want
to
call
out.
We
do
offer
the
microsoft
graph
tap,
which
is
our
technology
adoption
program.
This
is
an
opportunity,
basically
folks
who
are
under
nda.
If
you
don't
have
one,
we
can
get
you
under
nda
a
way
for
you
to
get
kind
of
early
access
to.
A
A
E
A
A
Podcast
they've
got
a
number
of
different
topics
that
have
been
coming
up
recently
in
terms
of
new
apis
or
things
that
are
kind
of
new
to
microsoft,
graph,
a
great
way
to
kind
of
stay
up
to
date,
with
what
are
some
of
the
changes
and
new
additions
to
microsoft
graph,
and
also
note
that
this
session
has
been
recorded.
We
will
make
this
available
to
on
the
microsoft
365
developer
youtube
channel.
You
can
find
the
link
on
the
page
on
here.
A
Do
we
do
look
forward
to
our
next
session,
which
is
going
to
be
on
february,
2nd
at
8
a.m?
Pacific
time
you
can
find
the
link
for
joining
in
to
get
the
invite
for
this
as
well,
so
want
to
thank
everyone
for
joining
us
on
our
january.
2021
call
and
we
do
look
forward
to
joining
us
in
february.
So
thank
you
all
have
a
great
day
and
we'll
talk
to
you
soon.
Thank.