►
From YouTube: Introduction to Microsoft Graph connectors SDK
Description
In this 12-minute developer focused demo delivered by Rajdeep Chandra, learn about the connectors SDK that will be available for preview in February. The SDK allows developers to write reliable and scalable custom Graph Connectors that are subsequently installed, configured and managed by Admins. Review connector terminology, development, implementation, and management (via Admin portal). Many capabilities of connector development are now addressed by components in the SDK. Register for the Preview today. This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on January 11, 2022.
Demo Presenter: Rajdeep Chandra (Microsoft)
Supporting materials:
• Registration - Microsoft Graph connectors SDK - Preview Sign Up | aka.ms/gcsdkpreview
Learn more:
• 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
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?
A
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
a
connector
code.
Second,
is
the
connector
platform
which
takes
care
of
the
entire
orchestration
bit
like
this
crawl
scheduling,
delete
detection
incremental
cross
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.
A
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
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.
A
The
crawling
incremental
crawls
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.
A
Now,
media
wiki
confluence:
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.
A
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.
A
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.
A
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
label
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.
A
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
connected
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.
A
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.
A
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.
A
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.
A
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.
A
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.
They
are
very
easy
to
implement
and
within
a
if
the.
A
A
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.
A
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.
A
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.
B
A
Where
does
it
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
terms,
so
I
really
need
to
look
into
it
and
I
can
probably
get
back
on
that.
B
C
B
A
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.
B
B
C
So
yeah
so
so
yeah.
This
is
similar
to
bcs,
but
it's
it's
better
than
bcs.
I
would
say
right,
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
microsoft
search,
but
we
are
already
working
on
building
more
experiences
which
will
be
using
this
this
data.
B
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
rajdeep
or
hashid.
If
you'd
like
to
address
the
questions,
yeah
we'll
answer
yeah,
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.