►
Description
Microsoft 365 platform community call delivered on January 11th. Three demos presented in this session - Introduction to Microsoft Graph connectors SDK, Building a Microsoft Teams bot for scheduling tasks and to get reminders, and Microsoft Graph Toolkit – Using the People Component in your solutions. Join the Microsoft 365 Developer Program and get a free E5 developer tenant with instant availability. It’s a great time to sign up for an event or AMA hosted by Sharing is Caring. The host of this call was Brian T. Jackett (Microsoft) |@BrianTJackett. Q&A takes place in chat throughout and live at end of the call.
Learn more:
• See the full blog post for this call at: https://aka.ms/m365pnp/community/blog
• Download invite for this weekly Microsoft 365 Platform community call: https://aka.ms/m365-dev-call
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/M365PnP/videos
A
Good
morning,
good
afternoon,
good
evening,
everyone
this
is
the
microsoft
365
platform
community
call
for
january
11th
2022.
My
name
is
brian
g
jackett.
I'm
your
host
for
today
got
a
great
lineup
of
topics
that
we'll
be
covering
today.
First,
we'll
cover
the
news
updates,
other
things
relating
to
the
microsoft
365
platform.
As
always,
then
we'll
move
into
our
group
picture
time.
We
love
to
have
see
those
waving
hands
and
smiling
faces,
and
then
we've
got
three
great
demos
that
we're
going
through
today.
A
First,
one
talk
about
microsoft,
graph,
connectors
from
rajdeep
yg,
we'll
talk
a
little
bit
about
building
team
spots
and
scheduling
tests
with
that,
and
then
seb
will
be
coming
in
to
talk
us
to
us
also
about
wings
upgraph
toolkit
now
for
those
of
you
who
are
new,
we
got
some
information
on
here
if
you've
been
here
before
yes
kind
of
repeat
of
information,
but
always
good
to
stay
up
to
date
on
what's
the
latest
for
this
we
have
two
different
developers
or
two
different
video
channels.
We
post
all
of
our
different
videos
too.
A
We
have
the
microsoft
365
developer,
videos,
aka
dot.
Ms
slash
m365
dev
youtube.
We
also
have
our
community
video,
so
all
these
community
calls
that
we're
recording
they
will
go
up
to
there
within
24
hours,
so
feel
free
to
take
a
look
at
past
ones.
Recap
on
things
share
with
your
teammates:
go
to
aka
dot.
Ms
slash
m365
pmp,
slash
videos.
We
also
have
a
number
of
different
open
source
initiatives
that
are
going
on
so
being
able
to
contribute
to
these
things.
A
We
love
community
contributions
being
able
to
take
reviews
and
so
forth
so
great
ways
to
feel
free
that
you
can
jump
in
and
help
you
able
to
contribute
back
to
our
open
source
community,
a
number
of
different
urls
on
there
as
well.
Also,
we
have
a
lot
of
different
samples
that
are
available,
so
it's
great
that
you
get
to
hear
about
things,
get
to
see
them
on
our
different
community
calls
like
this,
but
what
actually
want
to
go
and
see
them
kind
of
play
around
with
them.
A
Now,
where
can
you
go
to
actually
go
and
test
out
these
various
different
things
that
you're,
seeing
or
getting
kind
of
a
sample
tenant
to
work?
With?
We
have
our
microsoft
365
developer
program.
You
can
go
to
aka
dot.
Ms
slash
m365
dev
program,
and
here
you
can
get
a
free,
e5
developer
tenant
with
25
free
licenses
on
there
so
feel
free
to
go
and
prototype
solutions,
people
to
go
work
with
sample
data,
and
we
also
have
the
instant
provisioning
in
there
as
well.
A
Also
with
our
samples
gallery.
As
we
mentioned
before,
we
have
a
lot
of
different
samples
out
there
covering
different
areas
between
adaptive
cards,
spfx
and,
more
so
feel
free
to
go
out
there
and
take
a
look
at
this
we're
now
up
to
and
man.
This
number
just
keeps
climbing
higher
and
higher
every
week.
We
do
this.
We're
now
to
780
samples.
A
I
remember
months
ago,
when
we
were
back
down
like
the
500
600
range,
so
great,
to
see
the
continued
growth
of
this
and
people
contributing
back
again
a
great
way
to
share
to
the
community
and
get
to
see
what's
available
out
there
and
I'll
turn
things
over
to
david.
To
talk
a
little
bit
more
about
our
sharingan's
theory
initiative
with
pmp.
B
Awesome,
thank
you,
brian.
Well,
everyone.
As
you
heard,
there
are
a
ton
of
resources,
a
ton
of
opportunities,
a
ton
of
samples.
This
means
that
there
is
a
ton
of
opportunities
for
you
to
take
advantage
of
using
these
resources
as
well
as
contributing
back
to
them,
but
we
know
that
there
may
be
some
hurdles
along
the
way.
Things
like
I've,
never
done
a
pull
request
within
github
or
I'm
not
quite
sure
how
I
would
do
a
presentation
in
one
of
these
sessions.
I'd
like
to
do
one
on
a
pnp
call,
but
I'm
a
little
nervous.
B
Well,
the
sharing
is
caring
program
is
here
to
provide
you
hands-on
guidance
in
a
safe
space
opportunity.
These
sessions
are
not
recorded,
they're
free
of
charge.
You
work
along
with
other
members
of
the
community,
as
well
as
members
of
the
pnp
team.
To
accomplish
all
of
these
topics
that
you
see
available
to
you.
B
We've
got
more
coming
soon
up
in
february
the
video
connections
aces
session,
which
is
going
to
be
a
two-part
session
and
our
always
and
ever
popular
amas,
one
of
which
is
today
right
after
this
call
on
pnp
search,
you
can
go
directly
to
the
ak
dot.
Ms
forward
sharing
is
carrying
link
we'll
provide
you
the
direct
link
on
how
to
get
there,
and
then
we
will
have
a
great
conversation
with
frank
and
mikhail
on
pnp
search,
so
don't
hesitate
to
sign
up
for
any
one
of
these.
B
A
A
Now
it
was
a
little
bit
more
of
a
slow
news
week.
We
do
have
two
items
to
share
out
to
there.
One
was
actually
an
article
written
by
myself.
We
did
talk
a
little
bit
about
in
the
microsoft
graphic
mailbag
series.
This
did
take
a
little
bit
of
a
six
month,
hiatus
we're
starting
to
come
back
more
with
this
share.
A
Some
learnings
about
things
related
to
graph,
and
one
of
the
most
interesting
things
we
saw
recently
is
that
we
have
some
updated
guidance
if
you're,
using
the
microsoft
graph
sdks
on
how
to
actually
upload
large
files.
Large
file
views
within
over
four
megabytes
so
feel
free
to
take
a
look
at
the
blog
post
on
this
see
more
information
about
that.
A
C
And
let's
do
that
one,
that's
a
good
background.
I
will
start
recording
no,
no
waving
it
no
waving.
Okay,
now
we're
recording,
I
guess,
we're
back
fully
backed
on
the
50
people
attending
I,
let's
do
some
handwaving
everybody.
Thank
you,
everybody
for
joining
up
today
and
awesome
to
see
all
of
the
faces
in
the
community.
So
let's
there's
a
good
example
in
the
background
how
this
is
being
actually
done.
Thank
you.
Everybody
for
joining
awesome,
to
see
you
once
again
in
this
course
and
I
well.
C
A
D
So
today
we
are
going
to
talk
about
microsoft,
graph,
connectors
sdk,
so
we'll
mainly
cover
three
topics,
mainly:
what
is
the
graph
connected
to
the
sdk
water,
its
capabilities?
Why
are
we
building
it?
Who
are
the
users
who
will
be
using
this
sdk
and
how
they'll
interact
with
sdk
and
how
the
experience
would
look
like
for
these
users?
So
primarily,
there
are
three
main
parts
when
you
write
a
graph
connector
today
to
connect
your
data
source
and
write
it
into
graph.
One
is
the
connector
code.
D
Second,
is
the
connector
platform
which
takes
care
of
the
entire
orchestration
bit
like
this
across
scheduling,
delete
detection,
incremental
crawls,
all
these
things?
And
lastly,
there
is
the
admin
ui.
There
is
some
kind
of
ui
which
the
admin
uses
for
monitoring
and
managing
all
these
processes
right.
D
So
today,
if
you
write
a
connector
code,
you
have
to
take
care
of
all
these
things
on
your
own,
but
with
this
graph
connected
to
sdk,
what
we
are
trying
to
do
is
trying
to
ease
the
process
and
take
over
the
entire
connector
platform
and
admin
ui
on
the
microsoft
build
platform.
Essentially,
so
all
you
need
to
worry
about
today
when
you
use
this
graph.
Connectors
sdk
is
just
to
write
the
connector
code,
which
deals
with
just
reading
the
data
reading
the
hackers
and
connecting
to
the
data
source.
D
The
crawling
incremental
cross
full
cross
scheduling
the
scrolls
how
to
write
to
the
graph
the
acting
part,
that
is,
the
security
trimming,
part
everything,
and
also,
additionally,
on
top
of
that,
you
will
be
able
to
use
the
existing
admin
ui
that
that
we
have
the
admin
user
interface
that
we
have
today
that
you
use
for
managing
the
out
of
the
box
connectors
that
we
provide
today.
So
some
of
the
out
of
the
box
that
we
connectors
that
we
provide
today
are
like
service
now
media
wiki
confluence.
D
These
are
some
of
the
connectors
that
we
already
provide,
but
in
case
you
write
a
graph
connector
on
your
own
using
this
sdk.
Your
custom
connector
can
also
be
configured
and
managed
and
monitored
from
this
existing
microsoft,
admin
ui
right
so
moving
on.
Who
are
the
main
users
who
will
be
essentially
interacting
with
this
sdk?
So
there
are
two
main
personas
that
we
are
looking
at
here.
D
One
is
the
connector
developer
in
your
organization,
who
will
be
writing
the
code
for
developing
this
graph
connector,
so
this
sdk
will
enable
them
to
write
a
reliable
and
scalable
graph
connector,
and
then
there
is
a
admin
who
will
essentially
be
responsible
for
deploying
and
configuring
these
connectors
and
managing
these
connections.
Once
this
connector
is
deployed,
so
we'll
go
a
bit
deeper
into
how
this
connector
essentially
works,
how
the
all
the
how
all
the
parts
come
in
together.
D
So
if
you
look
at
point
number
one,
the
point
number
one
is:
microsoft
will
develop
and
release
the
connector
platform
and
the
connector
build
package.
So
connector
platform
is
probably
if
you
are
using
graph
connectors
today,
if
you're
using
on-prem
graph
connectors,
you
have
something
called
a
graph
connector
agent,
so
this
graph
connector
agent
will
be
beefed
up
as
a
connector
platform
that
will
be
able
to
support
your
custom
connectors
as
well.
D
So
this
is
a
tried
and
tested
platform
which
is
capable
of
doing
all
the
crawls
scheduling
the
scrolls
deleting
doing
delete
detection
and
all
these
platform
level
activities
and
the
graph
connector
agent
will.
Essentially,
the
platform
will
take
care
of
all
these
and
the
build
package
will
essentially
enable
you
or
the
connector
developer,
to
write
the
connector
code
easily.
So
the
connector
developer
essentially
would
leverage
this
package
to
build
the
code
for
their
custom,
connectors
and
they'll
once
they
are
done
with
the
testing
and
they
are
ready
with
the
connected
binaries.
D
They
will
pass
on
these
binaries
to
the
admin
and
the
admin
will
install
this
connector
platform
on
their
vm
and
run
the
connector
service
to
essentially
build
their
custom
connector,
and
once
this
connector
is
built
and
deployed,
the
connector
developer
will
pass
on
a
manifest
file
of
a
kind
which
will
confi,
which
will
contain
some
configurations
so
that
you
can
create
a
connection,
and
this
connection
on
top
of
this
connector
can
be
created
from
the
admin
portal
like
today.
You
are
creating
out
of
the
box
connections
for
out
of
the
box
connectors.
D
Similarly,
for
your
custom
connectors
as
well,
you
can
build
these
connections
from
the
admin
ui.
So
if
you
look
at
the
developer
experience,
the
developer
should
be
conversant
with
the
following
terms.
So
these
are
some
of
the
terms
that
you
will
come
across
in
the
developer
documentation,
as
well
as
the
connected
package
that
will
ship.
So
these
are
very
basic
terms
that
will
probably
be
used
by
the
developer
at
some
point
of
time.
So
one
is
the
data
source
by
data
source.
D
We
mean
what
is
the
third
party
data
source
that
we
are
talking
about,
for
which
you
want
to
index
the
data
into
microsoft.
Graph
things
can
be
like
I
previously
shared
examples.
It
can
be
service
now
media
wiki
sales
force.
Similarly,
what
is
the
connector
that
we
are
talking
about?
The
connector
is
essentially
the
main
part
of
the
code
that
you
will
write
to
read
this
data.
D
The
access
control
info
and
pass
on
to
microsoft,
graph
and
connection
is
any
specific
instance
of
this
particular
data
source
that
we
are
talking
about,
for
which
you
have
written
a
connector,
so
one
connector
can
have
multiple
connections,
and
these
multiple
connections
can
point
to
your
multiple
instances
of
the
data
source
that
you
are
trying
to
connect
to
the
graph
and
for
connecting
to
the
graph.
The
graph
connector
essentially
needs
to
crawl
this
data
or
traverse
through
the
data
source,
to
read
the
data
in
it,
and
we
support
two
types
of
crawls.
D
One
is
the
full
crawl
which
will
happen
for
the
first
time
to
read
all
the
data
in
the
data
source
and
we
do
incremental
crawls.
On
top
of
that,
to
ensure
that
this
data
is
fresh
so
to
do
this
incremental
crawl
again,
we
support
something
called
a
checkpoint
checkpoint
is
essentially
we
say
that
this
is
the
last
point
or
the
end
point
of
the
last
scroll
and
in
the
next
call
we'll
take
care
of
the
rest
of
the
data
source
that
was
called
from
that
particular
checkpoint.
D
So
these
are
some
of
the
very
basic
terms
that
will
be
mentioned
in
this
connector
package
and
while
you're
in
the
connected
documentation
as
well,
but
the
primary
contracts
that
need
to
be
implemented
are
the
following.
So,
as
you
can
see,
there
are
three
main
services
over
here
that
needs
to
be
implemented,
and
each
of
this
service
has
this
own
methods,
and
essentially
there
are
four
main
methods
that
we
are
talking
about
here.
That
are
absolutely
important
for
building
this
connector.
D
They
are
very
easy
to
implement
and
within
a
if
the.
If
the
connector
developer
is
really
conversant
with
the
code,
we
expect
developers
to
be
up
and
running
and
ready
with
connector
code
in
in
maybe
a
couple
of
days.
So
that
is
the
level
of
speed
that
we
are
looking
at
for
developing
your
custom
connectors.
D
These
rpc
calls
the
rpc
methods
that
you
are
seeing
over
here
are
very
basic,
like
the
name
itself
is
representative
of
what
this
does
and
you
can
essentially
implement
all
these
services
and
methods
and
get
started
for
building
your
connector
now
coming
to
the
admin
experience.
This
is
the
existing
admin
ui
that
you
can
see
for
building
your
out
of
the
box
connectors.
These
are
some
of
the
examples
of
the
out
of
the
box
connectors
that
we
provide
and
to
build
a
custom
connector.
D
Then
you
just
click
next
fill
the
relevant
data
and
you
are
ready
with
your
custom
connector
in
the
admin
portal
that
you
can
start
monitoring
and
tracking.
So
this
is
the
very
basic
of
one
of
how
to
build
a
connector
and
your
custom
connector
and
publish
it.
So
we
are
also
starting
the
preview
in
a
in
a
month
for
this
graph,
connector
sdk,
and
if
you
want,
we
would
like
you
to
sign
up.
There
are
a
couple
of
questions.
D
It
will
take
very
less
time
for
you
to
fill
it
up,
and
this
would
really
help
us.
You
know
reach
out
to
you
and
get
you
onboarded
and
help
you
build
these
custom
connectors
easily.
So
I'll
pause
over
here
and
if
you
have
some
questions,
please
shoot
them
at
me
and
I
can
discuss
them
in
the
next
few
minutes
that
we
have.
A
D
Store
all
the
data,
so
essentially
your
data
is
when
we
are
saying
that
you
we
store
the
data.
We
do
not
actually
store
the
exact
item.
It
is
mainly
your
item
schema
that
is
stored
in
the
microsoft
graph,
so
I'm
not
sure
of
this
data
verse
term.
So
I
really
need
to
look
into
it
and
I
can
probably
get
back
on
that.
A
E
A
D
Yeah,
so
I
think
this
documentation
should
give
a
a
good
view
of
the
licensing,
so
e5
tenants
actually
have
some
quota
that
is
added
on
top
of
it.
Some
free
quota,
but
also
e3
users,
can
also
sign
up
for
some
quota
to
try
and
test
this.
On
top
of
that,
the
main
pricing
that
we're
following
is
for
a
million
items
it's
a
thousand
dollars
per
month.
A
E
So
I
can
take
that
so
yeah,
so
so
yeah.
This
is
similar
to
bcs,
but
it's
it's
better
than
vcs.
I
would
say
so.
This
is
like
helping
you
build
a
graph
connector
which
essentially
brings
in
the
content
and
kind
of
puts
it
in
the
graph
which
powers
multiple
experiences.
Today,
it's
it's
microsoft
search,
but
we
are
already
working
on
building
more
experiences
which
will
be
using
this
this
data.
A
Excellent
and
I
do
see
some
more
questions
in
the
chat,
but
in
the
interest
of
time
I
know
we'll
want
to
move
on
to
our
next
topic,
so
rajiv
or,
if
you'd
like
to
address
the
questions.
Yeah
sure
that
would
be
helpful
so
again.
Thank
you,
so
much
rajdeep
for
being
able
to
give
us
a
little
overview
of
the
graph
connector
sdk
great,
to
see
this
coming
along
and
looking
for
people
signing
up
for
this
to
start
testing
this
out.
I
really
appreciate
that,
and
next.
A
F
F
First,
we
will
cover
the
basics
on
scenario
and
we'll
do
a
demo
using
the
ready
to
try
app
manifests
which
are
available
on
github
after
the
demo.
I'll
show
you
how
you
can
set
this
up
on
your
local
machine.
We'll
also
do
a
code
walkthrough
covering
the
key
code
snippets
and
followed
by
the
questions.
F
F
F
F
F
F
F
F
Meanwhile,
we'll
go
back
to
slides
and
take
a
look
at
the
next
next
things,
so
in
order
to
run
this
sample
locally,
these
are
the
steps
we
are
going
to
follow,
we're
going
to
clone
the
repo
and
open
the
part
daily
task
reminder
solution.
First,
then,
we'll
go
to
azure
and
create
a
new
part
and
capture
the
ids
required.
F
F
F
So
I'm
just
giving
some
dummy
name
here
putting
in
the
resource
group
and
the
type
of
app
would
be
multi-tenant
once
you
fill
in
then
this
information
click
on
review
and
create
to
save
time.
I
have
already
created
a
bot.
This
is
already
available
once
this
bot
is
created,
you'll
be
you'll,
be
shown
the
bot
profile
page.
This
is
where
you'll
be
able
to
upload
your
custom,
icon
and
you'll
be
able
to
set
the
display
name.
F
F
F
F
F
F
This
will
open
up
solution
on
three
nine,
seven,
eight
four
and
we'll
verify
whether
our
n
grock
is
pointing
to
the
right
place.
So
you
can
just
copy
the
increment
and
just
please
just
to
confirm
that
we
are
running
on
right
code,
so
we
got
a
request
on
anger
for
http
get
and
it's
loading
the
same
page
as
localhost.
F
And
just
to
confirm
just
looking
at
the
ngrok,
we
started
getting
the
api,
slash
messages,
a
request
and
you
could
see.
We
got
a
welcome
message
from
the
our
bot,
which
is
running
locally
and
same
way.
You
could
go
ahead
and
create
a
reminder.
It
will
follow
the
same
flow
which
we
have
already
covered.
F
Instead,
I
will
go
next
and
we'll
have
a
code
walkthrough
covering
the
code
snippets
in
the
sample
so
coming
to
the
code.
Walkthrough
we'll
start
with
the
libraries
using
the
sample,
we're
using
what
sdk
v4
for
the
scheduler.
We
are
using
cart's
nuget
package
and
to
store
the
tasks,
details
and
user
details.
We
are
using
in-memory
storage
in
terms
of
flow.
We
first
start
by
sending
out
a
welcome
message
to
the
user.
When
the
app
is
installed,
then
we
capture
the
required
information
of
the
user
so
that
we
can
send
them
a
proactive
message.
F
We
will
go
in
detail
of
each
of
these,
starting
with
the
sending
welcome
message
in
order
to
send
a
welcome
message.
We
have
handle
on
message
added
a
sync
method:
to
send
out
a
message
to
all
the
members
we
get
list
of
members
as
a
part
of
turn
context,
dot,
activity
payload
and
we
iterate
through
the
list
and
then
sender
will
commence
it.
F
This
is
something
is
very
important.
Whenever
your
app
starts,
you
could
just
send
out
information
of
what
to
expect
from
that
and
then
share
the
commands.
You
can
run
after
the
welcome
message.
The
next
thing
is
handling
a
create
reminder
command,
so
this
is
being
handled
in
on
message
activity
as
sync
and
along
with
sending
the
adaptive
card.
What
we
are
doing
is.
We
are
also
capturing
the
user
details.
F
F
Next
thing,
we'll
check
is:
how
do
we
actually
capture
this
schedule?
Information
so
based
on
the
input
provided
by
the
end
user,
we
create
a
cron
expression
and
we
schedule
a
task,
and
this
task
actually
does
a
http
get
on
api.
Slash
task
input,
so,
whenever
a
particular
trigger
hits,
it
will
just
execute
this
part
and
do
http
get
request.
F
F
We
also
set
up
what
locally
and
we
just
site
loaded
and
see
that
it's
running
fine
key
code
snippets
covered
are:
how
do
you
capture
the
conversation
reference?
How
do
you
schedule
a
job
and
then
how?
Finally,
you
can
send
your
product
messages
as
per
the
resources
concerned,
I
have
provided
the
documentation,
link
and
also
a
step-by-step
guide
I'll
paste
in
the
link
in
the
description.
F
The
step-by-step
guide
available
for
practice
message
will
give
you
specific
tech,
specific
steps
about
setting
up
things
locally.
We
have
provided
all
the
troubleshooting
guides
here.
You
could
go
start
from
the
installation
having
everything
ready,
setting
up
a
bot
and
then
doing
some
code
work
by
updating
the
adaptive
card
to
actually
get
the
final
challenge
and
then,
at
the
end,
you'll
be
able
to
read
more
about
the
proactive
messaging
documentation.
F
A
A
Otherwise,
I
do
see
you
put
a
link
on
here
for
feedback
and
questions,
so
folks,
please
do
feel
free
to
take
a
look
at
the
aka.ms
teams,
platform
feedback
and
utilize
that
for
any
kind
of
fault
that
you
might
have
so
that
would
I
really
appreciate
you
coming
on
today,
do
appreciate
you
coming
on
to
share
more
about
team
spots,
a
really
cool
scenario
and
I'd
like
to
I
like
what
you
shared
seb.
Are
you
available
to
present
always.
G
Folks,
today,
we
will
be
moving
on
with
our
journey
of
discovering
all
the
microsoft
graph
toolkit
components.
In
the
last
couple
of
sessions
we
did
over
the
last
four
or
five
community
calls.
We
went
through
some
of
the
components
and
today
we
will
be
continuing
with
the
people
component,
so
feel
free
to
ask
me
questions
in
the
chat
I
might
take
them
offline
after
I'm
done
quick
reminder.
What
is
the
microsoft
graph
toolkit?
G
The
toolkit
is
a
collection
of
reusable
framework,
agnostic
components
and
authentication
providers
that
allow
you
to
work
with
microsoft
graph.
So
basically,
if
you're
building
on
top
of
react,
angular
view
or
any
other
web
framework
you're
thinking
of
we
work
with
them
and
we're
providing
fully
functional
components
that
are
already
connected
to
graphs.
So
it's
not
you
don't
have
to
provide
any
of
the
data
doing
any
of
the
calls
we
do.
We
take
care
of
that
for
you.
G
G
It's
beautiful,
but
it's
flexible
also,
so
we
respect
the
m365
look
and
feel
being
as
fluent
as
we
can
in
the
way
that
we're
designing
our
components,
but
we're
also
allowing
you
to
bring
in
some
customizations
around
styling
templating
logic,
also
that
you
might
change
on
top
of
what
we're
shipping
and
also
we're
working
everywhere.
So
when
you're
thinking
about
the
web,
it
works
you're
thinking
about
teams,
it
works,
you're,
thinking
about
office
add-ins,
it
works
you're,
thinking
about
any
sharepoint
framework.
It
will
work
so
today,
component,
we're
gonna
cover
is
the
people
component.
G
People
is
a
way
to
display
a
group
of
people
or
contacts
by
using
simply
their
photos
or
initials,
and
by
default
it
will
always
display
the
most
frequent
contacts
for
the
sign
in
user.
So
without
any
further
ado,
let's
go
on
to
some
of
the
codes.
Let
me
actually
here,
I'm
going
to
start
fresh
from
here,
so
we
have
a
simple
html
file
that
was
built.
G
That
html
file
is
the
one
we've
been
using
for
the
last
couple
of
sessions,
so
invite
you
to
go
see
some
of
our
previous
videos
that
we
did
on
this,
and
we
have
already
a
msl
provider,
the
msl
provider.
Here
the
role
of
this
emsa
provider
is
basically
just
to
provide
authentication
to
microsoft,
graph
with
the
id
of
your
azure
active
directory
application,
the
scopes.
So
what
are
the
permissions
that
your
app
will
require
and
a
simple
login
component
to?
G
Each
components
will
have
different
set
of
scopes
or
permissions
that
it
will
require
and
the
best
way
to
figure
out
what
are
the
scopes
that
are
required.
You
can
always
go
to
our
documentation,
documentation
which
is
ak
dot.
Ms
slash
mgt,
slash
docs
and
it's
gonna
go
here,
I'm
able
to
open
the
table
of
contents
and
you
will
be
able
to
go
and
see
all
the
components.
For
example,
today
we're
going
to
talk
about
the
people
component.
G
What
we're
gonna
find
here
is
just
mgt
people
with
the
maximum
of
users
around
me
and
that's
it.
No,
nothing
specific!
Nothing
is
specified
here.
It
just
runs
with
what
we
have.
So
what
I'm
going
to
hit
save,
and
now
we
have
this
simple
people
component
right
here
and
you
see
I
have
five
persons
that
are
very
close
to
me
that
are
trending
to
my
users,
but
I
also
have
plus
five.
So
it
means
that
we
did
not
load
all
of
them.
G
I
could
go
here
and
change
it
to
eight,
for
example,
and
automatically
it's
gonna
load
the
right,
the
right
folks
right
there,
something
that
is
great.
We
have
so
little
space
in
these
avatars
that
what
we
can
have
by
default
is
when
you
hover
on
top
of
somebody,
you're
gonna
get
the
full
person
card
as
built
on
top
of
it.
So
that's
really
really
cool.
G
Now.
You
might
also
want
to
do
the
same
thing
in
a
way
to
describe
people
that
live
in
a
group.
So,
for
example,
here
I'm
going
to
add
an
mgt
person
or
entity
story,
an
entity
people
with
a
specific
group
id
this
group
id
should
be
a
group
id
you
get
somewhere,
maybe
using
a
graph
call
or
even
going
to
your
azure
active
directory
setup
and
find
the
actual
id
of
a
group.
G
G
G
What
can
we
do
also
well
something
that
is
super
useful,
especially
in
these
situations
is,
let
me
go
back
here
and
let
me
open
up
teams
of
microsoft.com
teams
is
where
your
presence
will
be
indicated,
so
it
could
be
really
useful
to
bring
in
the
presence
of
somebody
inside
these
things
to
to
know
if
they
are
available
right
now.
So
now
I'm
logged
in
as
my
own
user
here
and
in
a
couple
of
seconds
it's
going
to
lie
on
green.
G
So
now
that
I
can
go
back
here
and
add
a
new
component,
a
new
component.
Again,
I'm
going
to
paste
in
this
again
the
same
kind
of
html
around
it,
but
I'm
going
to
use
the
same
people
entity,
people
with
the
show
presence
to
true.
So
here
it's
going
to
look
around
me
all
the
users
that
are
trending
for
this
current
user,
which
is
me
and
but
show
the
presence.
If
I
hit
save
now,
you
see
that
seb
is
green.
It
means
that
that
user
is
currently
available.
G
G
Maybe
you
don't
want
to
have
the
the
the
hover
card,
because
the
hover
card
also
brings
a
lot
of
information.
So
how
do
we
want
to
limit
that?
Well,
there's
a
way
to
set
up
the
person
card
to
be
none.
So
when
I'm
going
to
hit
save
here
when
I'm
using
the
mgt
first
people
with
the
person
card
to
none
now
I
don't
have
anything.
But
what
shows
up
is
the
name
so
we're
all
always
making
sure
that
from
an
accessibility
standpoint,
everything
is
well
covered.
Let
me
maybe
zoom
in
a
little
bit
here.
G
I
think
it's
going
to
be
a
little
bit
better
for
y'all,
something
that
is
also
really
interesting
is
sometimes
you
want
to
specify
a
group
of
people.
That
is
not
a
group
that
is
not
a
list
of
user
ids,
but
you
have
a
path
on
graph
to
do
things
like,
for
example,
direct
reports.
So
what
I
did
here
is,
I
used
the
resource
property,
so
you
can
point
to
any
user
resource
endpoints
in
this
case,
slash
me
slash
direct
report,
so
what
it's
going
to
do
here?
G
It's
going
to
highlight
all
of
my
direct
reports
that
are
all
basically
all
reporting
to
sebastian.
So
when
I
hit
save
you're
going
to
see
that
I
have
three
different
direct
report,
there's
raul
there
is
stan
and
there
is
lydia
in
this
case.
All
of
this
without
ever
really
writing
any
line
of
code
right.
So
you
all
have
this
part
of
the
mgd
people
stuff.
G
Now
something
you
might
want
to
do
also
is
do
some
code
that
would
fill
in
the
data
of
this
component.
So,
for
example,
let
me
add
this
component
here
so
here
I
have
an
mgtt
people
with
an
id,
so
I
can
reference
these
people
right
there.
So
let
me
do
the
following:
I'm
going
to
go
here
and
I'm
going
to
do
a
little
bit
of
javascript
in
my
javascript,
I'm
going
to
use
a
method
called
load
manager.
G
G
I
can
always
get
an
authenticated
graph
client
that
was
provided
when
we
did
the
initial
login,
then
I
can
go
in
and
say
hey.
I
want
to
find
my
manager,
and
I
want
to
find
the
actual
direct
reports
of
this
manager
and
on
my
people
manager
id
that
I
use
a
little
bit
earlier
this
one
here,
I'm
going
to
set
the
people
on
this,
so
here
you
see
we
have
a
dot
people
property.
G
That
now
just
appeared
that
allows
me
to
bring
in
the
direct
reports
that
value
so
basically
what's
coming
from
back
from
graph
or
it
could
also
be
coming
not
just
from
graph
right.
It
can
come
from
any
api
that
you
have
on
a
third-party
source
or
a
public
rest
api.
Then
we're
going
to
save
on
this
automatically.
Now
you
see,
I'm
the
only
one
that
actually
reports
to
that
to
my
manager.
G
G
So
how
do
you
learn
about
it
all
of
the
documentations?
We
have
always
highlights
an
area
here
that
provides
custom
templates.
So
basically,
here
you
can
override
any
of
of
them,
including
the
default
one,
the
default.
So
it's
basically
the
list
of
person.
So
what
you
can
do
is
to
build
something
that
looks
like
this,
where
you
say
the
following.
Let
me
go
back
here
and
I'm
going
to
put
it
in
the
code
right
here.
G
You
say
that
in
my
mgtt
people
that
doesn't
have
any
and
you
could
have
any
properties
here,
my
default
template.
I
want
to
have
a
ul,
so
an
unordered
list
and
for
each
person
you
can
have
a
way
of
referencing
and
looping
through
data.
I
want
to
be
able
to
loop
in
an
mgt
person,
I'm
going
to
have
a
title.
G
If
the
display
person,
the
display
of
the
person,
is
megan,
I'm
going
to
say,
look
it's
megan
and
if
not,
I'm
just
going
to
display
the
regular
display
name,
the
job
title
and
the
department,
and
when
I
hit
save
on
this
now,
you
see
how
I
was
able
to
loop
through
all
of
these
components,
coming
directly
back
from
graph
and
build
my
own
display
on
top
of
it.
So
that's
really
one
of
the
biggest
value
of
the
graph
toolkit
where
it
provides
default
components,
but
also
customize
components
like
you'd
like
to
have
them.
G
A
A
If
you'd
like
to
find
out
about
any
of
our
other
developer
community
calls
out
there
in
the
microsoft
physics,
five
landscape,
a
number
of
different
resources
on
here.
As
always,
though,
take
a
look
at
the
aka
dot.
Ms
slash
m365
pnp,
where
you
can
find
all
the
different
resources
and
links
that
you'll
need
today.
A
Huge.
Thank
you
out
to
raj
deep
wajeet
and
seb
coming
on
today
shares
a
lot
of
great
content,
a
lot
of
great
demos
to
feel
to
be
able
to
see.
As
always,
our
recordings
will
be
available
within
24
hours.
On
the
microsoft
physics,
five
community
pmp
youtube
channel.
You
find
that
aka.ms
m365pmp
videos
feel
free
to
follow
along
with
us
on
twitter,
at
microsoft,
365
dev,
m365
pnp,
and
our
next
call
will
be
next
week
on
tuesday
january
18th,
at
our
normal
time.
8
a.m:
pacific.
Thank
you
again.