►
Description
Microsoft 365 platform community call delivered on March 22nd. Demos - Latest on Microsoft Graph connectors SDK, Microsoft Teams Meeting app sample with link unfurling, and Building Microsoft Graph Toolkit apps with Microsoft Teams. Visit the Microsoft 365 Sample Solution Gallery - 1020+ samples. Register for the Microsoft 365 Developer Program and get a free E5 developer tenant. Six Microsoft 365 Platform related stories, 2 Teams samples, and 3 Teams Step-by-step guides released. The host of this call was Vesa Juvonen (Microsoft) |@vesajuvonen. 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
Welcome
everybody
to
the
microsoft
365
platform
community
called
it
is
22nd
of
march
2022..
My
name
is
sergeant
and
I'm
a
program
manager,
oh
product
manager.
They
changed
our
titles,
no
longer
program
manager,
product
manager
in
microsoft,
365
platform,
side
of
the
house
and
today,
we'll
have
a
great
great,
great
set
of
demos
and
content
coming
up
followed
up
on
our
typical
intro
and
going
to
the
latest
news.
Now,
most
likely
we'll
have
just
a
verbal
warning,
most
likely
we'll
have
a
bit
of
a
lower
attendance
today
because
of
the
time
zone.
A
Differences
for
those
who
are
not
aware-
and
the
global
world
is
a
bit
of
a
challenge
always
because
during
the
autumn
and
and
springtime
u.s,
actually
moves
to
summertime
in
a
different
schedule
than,
for
example,
europe.
So,
therefore,
the
europe
and
u.s
time
zones
are
a
bit
different
and
that
might
actually
cause
some
differences
depending
on
where
the
meeting
has
been
created
and
that's
the
crazy
piece
of
all
of
this,
so
that
that's
why
things
are
shuffled
in
an
interesting
way.
Now,
anyway,
it's
not
a
promotion.
A
A
Let's
get
moving
and
we'll
go
through
the
typical
set
of
slides
first
and
the
latest
news,
and
then
we'll
have
three
demos
today
from
rajib
anui
and
then
sebastian
as
the
last
one
on
this
thing,
so
really
good
coverage
on
the
microsoft
graph,
microsoft
themes,
development
and
microsoft,
craft
toolkit
with
teams.
So
it
is
a
craft
and
team
specific
call
today,
let's
actually
move
on
to
typical
slides,
just
to
recap
on
the
assets
which
we
have,
and
I
know
that
we're
always
having
this
slide.
But
that
is
intentional.
A
We
want
to
make
sure
that
you
are
aware
from
where
you
can
find
the
latest
information
and
after
every
single
call,
I
get
requests
on.
How
do
I
get
access
on
the
recording?
The
easiest
way
to
get
access
on
the
recording
is
to
go
to
our
microsoft.
365
community
youtube
videos
channel
from
where
you
can
open
recordings
in
less
than
typically
less
than
24
hours.
After
the
call
has
happened.
A
You
cannot
access
the
call
recording
directly
from
the
chat,
even
though
you
see
the
link
there
because
of
the
permission
setups
between
the
tenants.
So
that's
the
reason
for
that.
We
do
have
two
different
youtube
channels.
The
other
one
is
for
official
developer,
microsoft,
365
videos
coming
from
cloud
advocates
and
engineering
and
our
marketing
and
the
community.
One
is
the
one
where
we
have
community
touring
videos
from
you
and
people
presenting
in
this
course
and
also
they're
all
of
the
community
called
recordings
as
well.
A
I
should
actually
update
the
image,
because
that
welcome
base
looks
a
bit
different,
not
too
much
different,
but
still,
and
one
of
the
things
which
we
always
promote
here-
is
that
please
remember
the
register
to
our
microsoft
365
developer
program
as
you
do
that
you
will
get
a
free,
e5
developer,
tenant
with
25
accounts
in
that
tenant.
As
long
as
you
use
that
developer
tenant
for
development
purposes
and
there's
some
instrumentation
in
place,
it
will
automatically
renew
in
90
days,
which
is
really
really
cool.
A
A
We
have
this
unified
microsoft,
365
sample
gallery,
which
technically
we
haven't
officially
launched
or
released
yet
from
a
block
announcement
perspective,
but
we're
going
to
do
that
quite
soon,
as
as
we
get
certain
small
adjustments
to
be
done
already
today,
there's
more
than
1200
samples
listed
in
this
one,
centralized
location
from
microsoft
and
from
community
and
just
to
recap
what
this
is.
This
is
basically
intended
to
be
the
easiest
way
to
find
a
starting
point
for
you
as
to
start
implementing
something
somebody
was,
I
guess
it
was
earlier
today
in
the
youtube
channel.
A
Somebody
was
asking
that
hey
do
we
have
a
people,
people,
people,
search
functionalities
in
microsoft,
365
or
kind
of
an
organizational
chart,
and
the
easiest
way
to
find
out
is
to
go
to
this
location.
Do
a
search,
people
organization
chart
or
whatever
you're
looking
for
and
voila.
It
will
actually
give
you
a
starting
point,
typically
as
a
sample
where
somebody
else
has
contributed
either
microsoft
or
community
member.
A
B
Does
thank
you
vessel,
yeah
friends.
All
those
samples
are
contributed
by
amazing
contributors
like
you,
but
we
understand
there
may
be
some
hurdles
in
the
way
for
allowing
you
to
submit
them
or
even
use
them
see
how
to
make
changes
and
resubmit
them
back.
That
is
a
fully
qualified
contribution
in
and
of
itself.
The
way
you
can
do
that,
if
you're
not
sure
join
one
of
the
sharing
is
caring
sessions.
They
are
hands-on,
live
safe
space
opportunities
for
you
to
ask
questions,
learn
how
to
submit
your
first
pull
request
via
github.
B
Perhaps
you've
got
a
power
platform
sample
you'd
like
to
submit,
or
you
just
want
to
work
within
docs
community
content,
community
docs
setting
up
your
workstation
want
to
present
on
a
session.
We
got
your
back.
These
are
free,
safe
space,
meaning
we
do
not
record
them,
so
you
can
absolutely
feel
free
to
ask
any
and
all
questions,
and
we
would
love
to
work
and
collaborate
with
you.
So
again,
we're
going
to
be
scheduling
more
of
these
of
these
over
the
next
couple
months.
B
A
And
congratulations
on
starting
at
microsoft
yesterday.
So
thank
you
to
see
that
happening
knowing
about
that
happening
for
a
while,
but
then
getting
that
moving
as
well.
Now,
some
of
the
other
things
how
to
get
being
up
to
date.
On
microsoft
reasons
to
write
development,
we
have
two
different
podcasts.
One
of
them
is
microsoft:
365,
developer,
podcast,
hosted
by
jeremy,
fake
and
paul
sheffield,
shuffling
jeremy
is
the
craft
cxp
lead,
so
customer
extensibility
team
lead
from
mike's
outside
and
paul
shuffle
and
works
in
365.
A
Quick
recap
on
those.
As
well
and
there
wasn't
a
significant
amount
of
new
news
across
the
let's
say,
the
different
products,
but
there
was
actually
five
news
from
the
microsoft
team
side
of
the
house
and
quickly
just
pinpointing
this.
The
first
one
is
really
about
explaining
how
we
at
microsoft
are
hosting
and
operating
microsoft
teams,
and
so
basically
making
sure
that
there's
a
reliability
with
with
disaster
recovery
and
what
are
our
quality
assurance
processes
kind
of
an
interesting
article
related
on
that
one?
A
The
second
goes
through
in
really
cool
device:
innovation
in
the
microsoft
teams
areas
now
that
we
are
gradually
hopefully
moving
back
to
this
hybrid
way
of
working,
so
some
of
us
will
be
working
from
office
and
someone
will
be
keep
on
working
from
home
and
how
are
those
devices
taking
that
kind
of
a
setup
into
account?
The
third
one
is
about
teams
connect
shared
channels,
so
basically
you
are
able
to
start
sharing
individual
channels,
not
the
whole
team,
with
external
people
in
your
tenants.
So
that's
going
to
be
providing
some
additional
level
of
flexibility.
A
The
fourth
one
on
the
left,
lower
corner
is
actually
really
really
cool.
Announcing
operation
connect
mobile
and
delivering
actually
the
capability
that
you
can
have
one
single
number
and,
as
somebody
calls
to
that
number,
it
will
ring
in
your
mobile
in
your
phone
physical
phone
in
your
desktop
or
in
your
pc.
A
Looking
forward
of
having
that
for
sure
and
then
the
last
one
is
kind
of
a
cool
story
related
on
a
sony
xp8,
where
we
will
have
a
walkie-talkie
physical
pattern
actually
inside
of
that
and
in
the
device
to
start
microsoft,
teams,
integrated
walkie-talkie
feature
so
really
cool
stuff
as
well.
If
you
are
into
the
devices
now
on
the
microsoft
teams
document
side
of
the
house,
I
think
storpy.
You
will
cover
this
one.
C
Yeah,
thank
you,
vessa,
hello,
everyone.
So
I'd
walk
you
through
the
platform
and
documentation
updates,
we'll
start
from
the
platform
update
on
the
left
hand,
side.
We
have
two
samples
to
cover
the
first
one
is
link
unfurling
meeting
sample.
This
sample
illustrates
a
common
scenario
where
a
user
shares
a
link
to
a
resource
with
a
group
of
users
and
they
collaborate
to
review
it
in
a
meeting.
Anuj
gupta
is
going
to
cover
the
sample
in
depth
in
today's
demo.
C
The
second
sample
is
user,
specific
view.
This
sample
illustrates
a
few
different
ways.
Developers
can
consume
user
specific
views
in
adaptive
cards.
Specifically,
it
uses
the
user
action
action.execute
with
refresh
property,
which
enables
developers
to
build
different
views
for
users
in
a
common
chat
thread.
C
Developers
can
consume
this
action
to
build
different
experiences
in
teams
like
user
specific
content
in
shared
context,
like
group
chat
and
meeting
channels,
auto
update
information
in
a
card
for
a
user
in
personal
context,
all
users
when
they
view
it
in
a
shared
context,
think
of
updating
an
order
status
when
a
user
views
the
message
or
an
incident
status
when
a
user
views
it
sequential
workflows.
Where
each
workflow
is
an
adaptive
card
with
the
user,
specific
view
and
options
to
invoke
next
or
preview
card
now,
let's
move
to
the
documentation.
C
Part
on
the
right
step
by
step
guides
is
an
artifact
that
has
a
task
oriented
approach.
Linear
topic
provides
an
end-to-end
scenario
and
loops
you
back
to
the
documentation,
so
we'll
be
talking
about
three
step-by-step
guides
today.
The
first
one
is
create
callings
and
meeting
bots
calling
and
meeting
both
provides
basic
functionalities,
such
as
create
a
call,
join
a
call
transfer
or
redirect
a
call,
join
a
scheduled
meeting
and
invite
the
participants
by
integrating
cloud
communication
apis
graph
apis.
This
step
by
step
guide,
helps
you
to
create
a
bot
with
calling
and
meeting
functionalities.
C
The
second
one
is
generate
a
meeting
stage
view
this
helps
to
enable
and
configure
your
apps
for
teams
meetings.
It
helps
users
to
share
meeting
stage,
allow
meeting
participants
to
add
status,
details
of
past
present
and
future
tasks,
enhancing
teams,
meeting
experience
and
the
third
one
is
your
upload
files
to
team
bot,
the
bot
in
this
step-by-step
guide.
It
helps
you
to
upload
files
from
abort
to
microsoft
teams.
So
these
were
the
platform
and
documentation
updates.
C
A
Helen,
thank
you
for
really
really
cool
stuff
and
I
really
love
those
task
oriented
step-by-step
guidance
and
stuff,
because
they
really
really
help
people
to
learn
on
how
to
get
stuff
done
in
the
microsoft
team.
So
great
show
up
on
that
now.
Also
a
quick
update
on
the
learn
from
the
community
series.
This
is
a
new
series
which
was
started
a
few
weeks
back
with
ike
bass.
A
A
A
Let's
see
if
we
can
get
a
few
more
people
in
the
room
and
then
we
can
start,
I
will
start
to
recording
one
two,
three
four
yeah
still
a
few
more
seats
and,
let's
do
some
hand
waving
everybody.
Thank
you.
Everybody
for
joining
once
again
today,
really
great
to
have
you
on
the
call.
It's
great
to
see
this
diversity
on
this
attendance
attendance
is
within
this
course.
Thank
you.
Everybody
welcome
back
if
animation
and
thank
you
seth
for
being
an
example
and
backroad
again
so
really
very
good.
A
Awesome,
let's
actually
stop
that.
I
will
move
them
away
and
I
will
stop
the
recording
and
let's
go
to
the
actual
stars
of
today.
So
we'll
start
with
raideep
and
then
we
go
to
anui
and
then
sebastian
laberd
as
the
last
one
of
today
but
write
it.
I
can
see
you
on
a
call,
so
let's
jump
on
yours,
yeah
and
move
from
there.
D
Sure
so
I
think
we
can
start
off
then
yep
all
good,
take
it
away,
yeah
so
hi
everyone,
I'm
rajdeep,
I'm
from
the
microsoft
graph,
connectors
team
and
today
I'm
going
to
talk
about
microsoft,
graph,
connectors
sdk.
So
previously
also,
we
have
talked
about
this
topic,
but
since
then
there
has
been
quite
some
changes
that
we
have
made
after
listening
to
feedback
from
you,
and
we
have
come
up
with
a
new
architecture
and
a
few
little
updates
that
we
have
on
the
sdk
and
we
are
going
to
cover
those.
D
So
just
briefly
I'll
also
talk
about
what
are
graph
connectors,
then
we'll
jump
into
the
features
and
capabilities
a
little
bit
on
the
architecture
and
I'll
be
showing
a
demo
of
how
you
can
actually
set
up
a
connector
using
c
sharp
to
start
off
so
graph
connectors
lets.
You
connect
all
your
data
sources,
which
are
third-party
external
data
sources
and
bring
the
data
into
microsoft,
graph
to
power.
D
Intelligent
microsoft,
365
experiences,
so
you
may
have
data
sources
like
file
storage,
some
project
data,
finance
application,
anything
right
and
we
have
out
of
the
box
connectors
to
connect
all
these
data
sources
into
microsoft.
Graph,
like
for
file
storage,
we
have
a
file
share
connector
for
sales
and
crm.
We
have
a
salesforce
connector,
we
have
internet
connector,
we
have
a
servicenow
connector,
and
these
connectors
come
out
of
the
box
from
microsoft.
But
let's
say
you
have
some
line
of
business
applications.
D
Some
custom
database,
some
project
data
that
you're
storing
somewhere,
and
you
want
to
index
that
content
into
microsoft
graph
as
well.
So
that
is
where
microsoft
graph
connectors
and
the
custom
graph
connectors
come
in.
Essentially
so
the
ones
highlighted
in
blue
are
the
ones
for
which
you
might
want
to
write
custom
graph
connectors
on
your
own
and
you
can
power.
Different
scenarios
like
search
is
one
of
the
primary
scenarios
and
there
are
also
upcoming
scenarios
like
let's
say,
e-discovery
and
viva
topics.
D
All
these
things
will
be
powered
by
the
data
that
will
come
in
through
your
data
sources
into
microsoft,
graph
right
so
moving
on
today,
you
can
create
your
line
of
business
connectors
or
your
custom
connectors
as
such
for
these
data
sources
using
microsoft's
graph
search
apis,
but
using
graph
search
apis,
although
you
can
create
your
custom
connectors,
there
are
a
few
drawbacks,
like
the
cost
of
development
is
high
using
this,
because
these
are
not
specifically
made
for
building
connectors
and
connectors.
Specific
functionalities
are
absent.
D
You
need
to
develop
them
on
your
own,
so
reduce
feature
availability
like
like
I
was
talking
like
e-discovery
viva
topics
and
all
those
things
won't
come
out
of
the
box.
If
you
use
just
microsoft
graph
search
apis,
you
need.
You
also
need
to
build
a
separate
admin
experience
just
to
monitor
all
these
custom
connectors
that
you
have
written
a
separate
dashboard,
you'll
be
needing
where
you'll
also
do
some
kind
of
error
handling
error
management,
which
is
also
difficult
today,
right
using
this
graph
search
apis
and
also
on
another
effect,
might
be
compliance
issues.
D
So
you
might
want
to
reflect
the
same
data
that
you
have
in
your
data
source
into
the
microsoft
graph
index.
Once
you
delete
some
content
from
your
data
source,
you
might
want
that
exact
replication
into
microsoft
graph.
So
this
requires
timely
purging
of
deleted
content
to
ensure
data
freshness
and
all
these
logics
are
pretty
complex
annuity
and
you
need
to
write
and
develop
these
logics
on
your
own
in
case
you're,
using
the
graph
search
apis.
D
But
what
we
are
doing
today
with
the
sdk
is
packaging
a
lot
of
these
capabilities
together
into
what
we
are
calling
the
microsoft
graph
platform,
the
graph
connector
platform
right
so
graph,
connector
platform
is
a
platform
that
has
been
built
over
the
last
few
years
on
which
our
out-of-the-box
connectors
are
working.
So
all
the
connectors
that
I
talked
about,
which
come
out
of
the
box,
the
native
connectors,
like
servicenow,
confluence
jira
file,
share
all
these.
D
All
these
connectors
are
running
on
this
exact
same
graph
connector
platform,
which
we
are
enabling,
through
the
sdk
for
customers,
also
to
leverage
this
to
write
their
own
connectors.
So
this
is
a
really
mature
platform
and
also
going
forward
whatever
updates
we
make
will
be
made
available
to
you
through
this
platform.
So
this
platform
today
has
the
capability
of
getting
the
data
from
the
connector
doing
crawl
management
full,
as
well
as
incremental
crawls,
then
scheduling
the
scrolls
triggering
the
straws,
the
integration
with
the
microsoft
admin
center
right.
D
So
you
have
a
m365
admin
center,
where
you
are
managing
your
out
of
the
box
connectors
today.
But
if
you
write
your
custom
connector
using
draft
search
apis,
you
need
a
separate
admin
center.
You
can't
monitor
and
manage
them
from
the
same
m65
admin
center.
But
if
you
come
through
the
microsoft
graph,
connector
sdk
and
write
your
custom
connector,
you
will
be
able
to
start
monitoring
managing
all
your
custom
connectors
as
well
through
the
in
65
admin
center.
D
So
apart
from
that,
just
to
summarize
the
benefits
you
get
a
fast
and
efficient
development,
and
we
are
so
today
you
can,
with
this
graph
connectors
sdk,
you
can
write
in
any
11
languages
of
your
choice,
so
we
have
a
support
for
up
to
11
languages.
You,
your
data
sources,
can
be
cloud
or
on-prem
data
sources.
So
the
connected
platform
that
we
already
talked
about
is
already
really
robust
and
you
can
leverage
the
microsoft
admin
center
to
manage
your
custom
as
well
as
out
of
the
box
connectors
all
in
one
single
place.
D
So
this
rpc
framework
is
actually
based
on
grpc,
which
is
open
source
and
it
works
in
a
client
server
based
model.
So
our
microsoft
graph,
connector
platform
hosts
the
client
and
your
connected
line
of
business
connector
code
hosts
the
server
and
our
client
makes
calls
to
the
server
to
get
the
data
and
we
talk
over
a
tcp
port,
and
this
is
you:
can
stream
unidirectionally
and
by
bi-directionally
and
what
enables
these
11
languages
to
make
this
framework
language
neutral
and
platform
neutral
is
something
called
protocol
buffers.
D
So
these
are
ways
to
share
contracts
between
two
systems
in
a
grpc
model,
and
this
helps
us
to
easily
create
distributed
applications
and
services
right.
So
this
is
a
brief
on
how
grpc
works,
so
the
server
can
be
implemented
in
any
language
and
it
is,
and
it
is
independent
of
whatever
language
the
client
is
essentially
written
in
right,
so
your
grpc
client
can
be
in
ruby
or
android
java,
and
the
server
can
be
in
c
plus
plus
server.
So,
although
they
are
in
different
languages,
it
is
you
can
talk
to.
D
We
can
talk
to
each
other
using
this
grpc
framework,
so
how
this
applies
to
our
entire
line
of
business.
Connector
sdk
is
essentially
this
microsoft
connector
platform,
on
which
I
already
said
that
our
out-of-the-box
connectors
are
already
running,
like
let's
say,
jira,
on-prem,
connectors
or
file
share
connectors,
so
we
host
the
grpc
client
inside
this
connector
platform
and
it
talks
over
http
to
a
grpc
server
which
is
inside,
which
again
hosts
your
connector
implementation,
the
connector
port,
and
you
can
have
multiple
connectors
that
are
running
that
can
talk
to
the
same
connector
platform.
D
So
let's
say
you
install
one
microsoft
connector
platform
and
you
have
three
different
data
sources
for
which
you
want
to
write.
Let's
say
line
of
business
connectors
or
even
you
want
to
run
your
out
of
the
box
connectors
right,
so
you
can
have
multiple
connectors
running
on
just
talking
to
one
single
connector
platform,
and
these
should
reside
on
the
same
virtual
machine,
the
connector
platform
and
your
line
of
business
connector
port.
D
So
you
need
to
define
the
port
on
over
which
each
of
these
connectors
are
running,
so
that
this
grpc
client
can
talk
to
each
of
the
servers.
And
accordingly,
if
you
update
the
configuration
file,
these
connectors
will
start
working
right
so
just
to
go
quickly
over
how
the
entire
flow
is
of
developing
a
line
of
business
connector.
D
So
you
can
download
the
through
id
if
you're,
using
c
sharp,
then
you
can
download
a
template
that
we
are
already
providing
and
it
has
a
project
structure.
You
open
up,
write
the
code
to
read
data
from
the
data
source
as
an
admin.
You
need
to
install,
let's
say
this
connector
platform
and
this
and
update
the
configuration
files
and
you
need
to
run
the
line
of
business
connected
code
that
you
have
written
and
finally,
you
go
to
the
microsoft
admin
center
and
it's
a
very
familiar
flow
of
publishing
and
out
of
the
box
connector.
D
So
it's
same
for
the
custom
connector
as
well.
All
you
need
to
do
is
you
need
to
update
this
manifest
file
and
your
and
fill
in
the
necessary
details
to
publish
your
line
of
business
connector
so
how
this
works
in
c
sharp
is
that
you
already
have
a
template,
so
you
can
go
to
visual
studio,
extensions
and
download
this
template,
and
once
you
install
the
template
and
search,
you
go
to
create
a
new
project
and
you
try
to
search
for
the
template.
D
Something
like
this
will
come
up
and
once
you
install
the
template
and
you
create
a
project
using
this
template,
it
already
has
a
project
structure
with
some
sample
code
inside
it.
So
once
you
finish
coding
update
the
code,
it
will
generate
a
exe
file
and
this
needs
to
run
on
the
same
vm,
where
you
are
running.
D
Your
graph
connector
platform
and
you
define
the
connector
port
over
which
this
connector
is
running,
so
that
this
graph
connector
platform
can
talk
to
your
particular
connector,
and
once
you
update
some
configuration
files,
you
complete
the
testing
and
you
feel
that
it
is
okay
for
deploying
in
your
production
environment.
You
can
directly
go
to.
Let's
say
you
can
directly
go
to
the
admin
center
and
you
can,
through
the
custom
connector
option.
There
is
a
new
option
that
you'll
start
seeing.
D
So
to
give
you
a
brief
on
how
this
works
directly
in
visual
studio,
so
in
visual
studio,
I
already
have
this
connected
template
installed,
which
has
this
project,
so
this
project
has
a
server
cs5
which,
where
you
essentially
create
the
server-
and
you
mention
the
port
over
which
this
particular
connector
is
running,
and
you
define
a
connector
id.
This
will
already
be
defined,
automatically
be
generated
for
you.
You
can
change
it
as
well.
D
This
is
a
unique
connector
id
for
your
particular
connector,
and
then
we
have
some
dummy
database
that
we
are
trying
to
create
and
reading
and
over
here
in
connection
management
service.
It's
a
very
familiar
flow.
First,
you
define
how
the
authentication
works
so
in
validate
authentication,
you
tell
us
how
we
can
talk
to
and
watch
what
authentication
we
can
use
to
get
access
to
the
data
source.
D
Then
next,
once
this
is
done,
you
can
tell
us
how,
if
there
is
any
custom
configuration
that
we
require
to
access
this
data
source
and
once
that
validation
done,
you
tell
us
what
is
the
data
source
schema?
So
what
is
the
schema
of
the
data
source
that
you
are
that
will
be
expecting
and
finally,
in
the
connected
crawler
implementation?
D
This
is
where
you
essentially
write
the
code
so
that
we,
you
can
essentially
crawl
through
the
data
source,
get
the
data
and
send
it
to
our
connector
platform.
So
we
also
have
a
check
pointing
mechanism
so
that
increase
in
case
there
are
any
crashes.
This
can
automatically
resume
the
crawl.
Once
your
connector
server-
or
let's
say
your
connector
platform-
is
up
and
running
wherever
the
issue
went
wrong,
so
once
the
coding
is
complete,
we
also
have
this
testing
utility.
D
D
So
how
this
works
is
that
I
have
a
configuration
file
where
I've
essentially
said
that
this
is
the
connector
id
which
is
running
on
this
particular
port
and
this
test
utility
essentially
tests,
whether
this
connector
is
actually
running
on
that
port
and
whether
our
graph
connector
platform
can
talk
to
that.
Similarly,
you
can
run
the
other
test
cases
and
once
everything
passes,
you
can
go
into
microsoft.
Admin
center
go
to
add,
and
you
start
seeing
the
new
option
that
I
had
just
shown.
D
It
will
hardly
take
two
minutes
to
essentially
publish
this
connection
and
once
you're
done,
I
already
have
a
custom
connector
that
is
published
and
up
and
running
so
once
you're
done,
it
will
be
in
something
like
a
ready
state
and
you
can
open
this
and
actually
see
what
are
the
crawl
statistics.
When
was
it
last
crawl
number
of
items
that
were
indexed
everything
from
the
admin
center
in
one
single
dashboard?
So
you
don't
need
to
go
anywhere
else
to
actually
check
what
is
going
on
with
your
data
source.
D
Like
you
can
see
over
here,
I
have
an
index
limit
of
seven
hundred
thousand
and
I
have
indexed
5489
items
as
well
as
what
is
the
crawl
schedule?
If
you
want
to
change
the
schedule,
you
can
go
into
edit
and
change
it.
Similarly,
all
the
all
the
benefits
that
are
there
or
all
the
capabilities
that
are
there
for
the
out
of
the
box.
Connectors
comes
to
this.
These
custom
connectors
as
well,
so
that
is
all
from
my
side
in
terms
of
demo
and
in
terms
of
timelines.
D
So
today
we
are
in
private
preview
and
we
expect
to
be
in
public
preview
by
calendar
year
22,
and
that
is
the
same
timeline
around
which
a
lot
of
our
other
experiences
are
also
coming
up.
So
in
case
you
integrate
your
third
party
custom
connected
data
by
then,
then
you
can
also
onboard
into
these
other
experiences
like
viva
topics,
integration,
e-discovery
support
around
calendar
year,
2022
h2
timeline,
so
that
is
all
from
my
side.
D
A
E
So,
let's
get
to
the
agenda
I'll,
give
you
a
brief
overview
of
the
main
scenario
this
sample
implements
and
then
we'll
look
into
the
platform
capabilities.
The
sample
consumes
we'll
do
a
live
demo
of
the
application
and
we'll
also
go
through
the
code
and
cover
important
implementation
details
and
if
time
permits
we'll
do
a
live
stream
session
at
the
end.
Otherwise,
we'll
answer
the
questions
or
something
must
be
in
check
so
scenario
overview.
E
E
If
you
think
about
it,
there
are
a
lot
of
manual
steps
that
have
been
avoided
in
this
book.
For
example,
you
don't
need
to
create
a
meeting
by
yourself
or
you
don't
need
to
add
an
application
or
a
tab,
or
even
click,
to
join
that
meeting.
Everything
is
done
by
the
app
in
single
click,
and
this
solution
is
context
over
here.
That
means,
if
you're
doing
something
like
this
you're
sharing
a
link
to
a
resource
in
an
ongoing
meeting
which
is
pretty
common.
E
It
sets
up
the
ongoing
meeting
for
review,
so
you
would
have
the
app
added
to
your
existing
ongoing
meeting
and
also
have
the
tab
that
points
to
the
exact
resource
that
you're
looking
at
now.
There
are
many
platform
capabilities
that
the
sample
consumes
to
build
the
experience
we'll
go
over
a
few
important
ones,
so,
at
high
level
the
app
has
a
bot
which
helps
in
link
unfolding
attaching
an
adaptive
card
to
a
message
and
authenticating
the
user.
E
Let's
understand
what
these
capabilities
mean,
link
unfolding
so
apps
can
provide
customers
experience
when
a
user
shares
a
link
that
is
associated
with
them.
When
you
say
associated
apps
can
define
a
list
of
domains
that
are
associated
with
the
application.
For
instance,
you
see
we
have
a
domain
property
here
and
we've
added
one
domain
over
here.
E
It's
important
to
note
that
you
should
only
add
domains
that
you're
in
control
of
so
something
like
a
start
or
xyz.com,
where
you
don't
really
own
xyz,
isn't
something
that
will
go
through
so
once
you
do
that
you
have
a
capability
to
send
back
a
collapsed
and
expanded
card.
We
look
at
what
these
mean
precisely
when
we
go
over
this
in
live
demo
adaptive
cards.
I'm
sure
a
lot
of
you
are
already
aware
of
this.
E
E
So
in
teams
you
can
develop
experiences
in
meetings.
In
fact,
you
can
integrate
tabs
parts
and
missing
extensions
in
each
stage
of
the
meeting
cycle,
which
is
pre-meeting
in
meeting
or
post
meeting
in
sample,
we
integrate
a
site
panel,
you
can
see
the
site
panel
over
here
to
you
know,
let
users
view
the
dashboard
that
was
shared
them
to
review.
It
also
sets
up
you
know,
meeting,
which
is
a
pre-meeting
stage
where
we
add
the
app.
We
add
the
tab
and
specific
tab
that
points
to
the
resource
that
was
shared
task
module.
E
You
can
create
model,
pop-up
experiences
in
your
team's
app
with
top
modules.
These
are
really
useful
to
display
rich
content
or
you
know
when
you
want
to
complete
a
complex
task
in
this
screenshot.
You
see
that
you
have
a
pop-up
experience
here,
which
we
call
task,
module
and
user.
You
know
the
app
is
trying
to
get
user
input,
which
is,
you
know,
relatively
complex,
to
get
in
a
message
within
a
jack,
so
these
come
in
very
handy
and
they're
built
using
an
iframe
and
desktop
or
web
views
and
mobile.
E
So
you
know
everything
is
in
your
control.
You
can
power
it
with.
You
know
web
app
and
then
you
can
control
how
you
know
your
elements
look
like
and
what
kind
of
input
output
you
want
to
give
to
the
user,
and
also
this
can
be
launched
from
almost
anywhere.
So
you
can
launch
them
from
tabs
or
bought
messages
or
adaptive
cards
in
the
sample.
We'll
see
how
we
launch
it
from
adaptive
cards
and
then
also
missing
extensions,
deep
links,
so
you
can
create
links
to
information
and
features
within
teams.
E
The
sample
here
executes
deep
link
which
lets
the
user
automatically
join.
The
meeting
that's
created
on
the
fly
so
now
that
we've
covered
teams
platform
capabilities
consume
the
sample.
Let's
take
another
look
at
the
scenario
which
we
covered
earlier
and
understand
how
it
works
into
end,
so
the
same
scenario,
where
user
shares
the
link
with
other
users,
and
then
you
know
it
gets
unfold
into
an
adaptive
card
with
list
of
actions.
E
Let's
see
how
this
works
works.
So
here
we
have
a
teams
user,
interacting
with
the
teams,
app
the
teams,
client
of
services
and
then
your
sample
app.
Now
the
sample
app
here
represents
the
bot
and
yeah,
we'll
specifically
be
talking
about
how
bot
interacts
in
this
workflow,
so
user
shares
a
link
to
a
dashboard
in
teams
and
teams
will
determine
if
that
link
is
associated
to
your
app.
If
it
is,
then
it
invokes
an
app.
This
link
query
to
your
app.
E
E
Let's
look
at
the
other
scenario
we're
looking
at,
which
is
review
in
a
meeting
here
again,
a
quick
recap:
user
clicks
on
the
reviewing
meeting
action
and
that
opens
a
task
module.
Where
you
see
you
know
the
app
is
processing
this
request
and
then
user
is
automatically
given
an
option
to
join
a
meeting.
E
So
in
this
workflow
again
we
have
a
teams
user
who
is
going
to
click
on
this
review
and
meeting
action.
We
have
teams,
client
or
services.
We
have
the
task
module
which
is
powered
by
the
web
app,
and
then
we
have
the
sample
app
now
here
sample
app
represents
bot
and
another.
You
know
post
endpoint
that
we've
exposed
to
set
up
a
meeting.
E
E
They'll
bring
up
the
ui,
which
will
prompt
user
to
add
the
app
and,
once
user
adds
the
app
it
will
automatically
continue
with
the
workflow
that
originated
this
installation,
that
is
it'll
launch
the
task
module
for
the
user.
The
dash
module
works
in
this
way.
Your
team's
client
will
open
your
pop-up
window,
but
it'll
also
reach
out
to
your
bot,
saying
that
an
invoke
was
fired
to
open
a
task
module,
and
this
is
where
your
app
is
in
control
of
you
know
showing
what
it
wants
to
load
in
that
class
module.
E
Now
here,
the
sample
lab
returns
back
a
link
which
specifically
points
to
review
a
specific
resource.
In
a
meeting
and
teams
then
opens
that
link
in
the
task
module
again,
because
this
process
involves
you
know,
user,
creating
a
meeting
and
doing
extra.
You
know
steps
like
setting
up
a
meeting
installing
app.
We
do
require
user
consent,
which
is
again
a
one-time
user
consent
to
get
certain
permissions
if
user
consents.
E
The
app
will
then
fire
set
up,
review
or
set
up
meeting
requests
to
the
web,
app
where
it
will
then
create
an
online
meeting
install
an
app
to
the
meeting.
Add
a
tab
with
link
to
dashboard
and
return
back.
The
meeting
details
and
the
reading
details
will
have
a
link
to
join
that
specific
meeting,
which
will
then
be
executed
in
teams,
client
and
user
will
be
able
to
join
the
meeting.
E
I
hope
that
helps
you
understand.
You
know
the
end-to-end
workflow
of
how
it
works.
Well,
it
looks
quite
simple
from
user's
perspective.
There's
a
lot
going
on
behind
the
scenes.
So,
let's
switch
to
a
live
demo.
I'll
share
my
screen,
so
here
I
have
a
user,
let's
call
name
user
administrator
and
then
here
I
have
another
user,
megan
and
they're
in
a
comment
chat.
So
let's,
let's
share
a
resource
with
megan.
E
Let's
send
this
card
and
if
either
clicks
on
view.
Now
this
is
a
stage
view.
It's
not
the
main
scenarios
app
implements,
but
something
you
know
really
useful
where
you
want
to
display
information
in
large
window
with
switch
media
content,
you
can
do
so,
but
then
let's
look
at
it
from
another
user's
perspective.
So
you
get
this
option
to
you
know
view
or
review
it
in
a
meeting
again.
You
can
view
it
just
like
the
user
did.
E
E
Let's
see
okay,
so
this
is
the
meeting
and
then,
if
you
see
we
have
an
app
that
is
already
added
to
this
thing
and
when
you
click
on
that,
you
can
look
at
the
resource,
and
this
is
the
exact
resource
that
was
originally
shared,
and
now
you
can
share
it
with
other
users.
If
any
other
user
in
the
chat
clicks
on
they've
been
meeting
action,
they
will
be
added
to
the
same
meeting
instance.
E
And
they
can
now
collaborate.
You
know
over
the
content
that
the
original
user
is
sharing
with
them.
I
think
it's
taking
some
time
to
load
the
stage
view.
Okay,
we
have
it
here.
So
that's
great,
but
let's
look
at
the
code.
That's
powering
this
experience
here
is
the
project,
and
here
the
web
project
basically
has
the
bot
implementation
and
the
controller
apis
and
the
client
apps.
E
We
send
back
a
sign
in
action
response
which,
when
he
signs
in
then
again
calls
back
this
action
again
and
if
everything
is
good,
you,
then
you
know
check
if
the
user.
Ideally
you
should
check
in
as
of
strikes
to
accessory
resources
and
samples,
because
this
is,
you
know,
heavily
dependent
on
how
you
implement
this,
and
then
it
returns
back
the
cards
and
information
on
previous
image
and
option
to
review
it.
We
talked
about
expanded
and
collapsed
card.
Expanded
card
I'll
quickly.
E
So
the
client
or
you
know
the
task
module
eventually,
when
it
processes,
the
request
validates
that
things
are
right,
sends
a
request
to
your
app
and
says
that
hey
set
up
an
online
waiting
for
this
request
and
what
the
app
does
is.
It
tells
its
data
checks
if
the
resource
really
exists,
if
it
does,
it
prepares
the
conversation
contacts.
This
is
where
we
know.
E
If
it's
a
you
know,
group
conversation
or
team
and
whether
it's
a
team
team
chat
and
then
it
calls
a
set
of
meeting
a
sync
function
here,
which
essentially
creates
a
unique
external
id
for
a
meeting
here.
It's
a
combination
of
conversation,
id
and
or
a
society.
So
anytime,
you
share
the
same
results.
In
another
conversation,
it's
going
to
create
a
unique
or
another
online
meeting,
while
in
the
same
chat
it's
going
to
point
the
same
online
meeting.
E
E
So
that's
from
the
demo.
We
have
a
list
of
resources
that
you
can
point
to
like
link
to
sample
app
and
parts
and
all
the
capabilities
we
talked
about
you
can
refer
to
them.
If
you
want
to
learn
about
these
features
in
detail-
and
that
concludes
our
session
thanks
for
listening
to
the
session.
Thank.
A
F
Awesome,
thank
you
so
much
folks.
We
are
at
the
end
of
our
journey
with
the
mgt
microsoft
graph
toolkit
and
today
we're
going
to
talk
about
teams.
How
can
we
use
teams
to
leverage
the
microsoft
graph
toolkit
component,
so
I'm
going
to
go
quickly
over
the
basics
of
mgt
for
the
ones
that
are
new
to
it?
So
what
is
the
graph
toolkit?
It
is
a
collection
of
reusable
and
framework
agnostic
components
and
auth
providers
that
allows
you
to
access
and
work
with
the
microsoft
graph.
F
So
the
components
are
fully
functional,
they're
ready
made,
they
can
use
them.
It's
kind
of
a
drag
and
drop
in
your
app
and
you're
good
to
go.
You
can
use
components
are
already
connected
to
microsoft,
graph,
which
saves
you
tons
and
tons
of
time
works
with
any
web
browser
in
any
web
framework.
So
you're
using
angular
react
playing
javascript
anything
you
can
always
use
the
microsoft
graph
toolkit.
F
Why
would
you
care
about
the
toolkit?
First?
It's
it
cuts
on
dev
time,
so
you
get
to
your
business
goals
way
faster.
It
is
beautiful,
but
it's
flexible.
So
if
you
love
how
microsoft
365
looks
like-
and
you
want
to
get
some
of
that
in
your
app
you're
you're
good
to
go-
we
already
have
that.
But
if
you
want
to
customize
it,
you
can
also
do
it
on
your
own
terms
and
it
works
everywhere
either
on
the
web
in
electron,
on
a
teams
app
in
a
sharepoint
framework,
page
anywhere.
F
It
just
works,
and
you
know
what
mgt
loves
microsoft
teams.
It
is
a
match
made
in
heaven,
there's
a
lot
of
components
that
are
very
specific
to
teams,
but
also
that
are
really
a
great
way
to
create
apps
that
brings
user
context
in
there.
So
how
do
we
start?
I'm
gonna
do
two
very,
very
quick
demo.
One
we're
gonna
use
yo
teams,
which
is
a
microsoft
teams,
community
driven
yeoman
generator,
which
is
awesome
and
super
simple
to
use.
I'm
gonna
go
through
this.
F
The
only
thing
you're
going
to
have
to
do
you're
going
to
have
to
install
teams
the
teams,
generator,
sorry
and
then
you're
going
to
have
to
say
yo
teams,
I'm
going
to
create
your
app
a
basic
app
and
afterwards
you're
going
to
install
your
mgt
react
components.
In
my
case
I
used
react
and
then
you're
going
to
want
to
install
one
authentication
provider
that
will
allow
you
to
get
access
to
microsoft,
teams,
the
contacts
and
the
authentication
so
you're
going
to
be
fully
authenticated.
F
F
We
have
a
regular,
very
regular
client.ts,
which
is
kind
of
our
entry
point
of
our
app
nothing
special
there
teams,
when
you're
building
apps
a
vast
majority
of
the
times.
When
you
will
build
a
web
surface,
you
will
be
building
a
tab
and
these
tabs
in
your
teams.
They
all
have
their
own
small
apps
if
you'd
say
so.
You're
gonna
find,
for
example,
my
yo
teams
tab
here,
and
this
is
where
all
my
app
would
be
for
this
specific
tab.
So
let
me
go
and
see
what's
in
there,
so
a
couple
of
things.
F
You
will
want
to
use
our
specific
provider,
our
team's
mso2
provider,
that
allows
you
to
have
a
great
connection
with
microsoft
teams
and
will
handle
the
authentication
for
you,
and
the
only
thing
you'll
have
to
do
is
to
say
hey.
I
am
running
in
teams
because
here
you
know
we're
using
if
I'm
in
teams-
yes,
well,
I
mean
teens,
I'm
going
to
reuse
the
library
here
and
I'm
going
to
use
this
configuration
here
which
tells
my
app
that
this
is
the
app
the
aad
app
that
I
want
to
connect
to.
F
This
is
one
artist
codes
that
I
want
to
use,
and
this
is
where
I
want
to
use
my
authentication,
because
authentication
in
non-sso
scenarios
will
be
happening
through
a
pop-up.
If
you
want
to
go
and
set
up
sso,
then
you
will
not
even
have
a
pop-up.
It
will
work
flawlessly
without
building
this,
but
I
didn't
want
to
confuse
folks
to
add
a
little
bit
of
complexity
to
this
solution,
so
I
kept
it
as
simple
as
possible.
F
But
here
I
can
have
my
full
people
card
and
I
can
drag
and
drop
and
see
all
these
kind
of
things,
the
beauty
about
using
teams
as
a
surface
to
build
your
apps
is
now.
You
also
have
the
ability,
with
the
exact
same
bits
of
code,
the
exact
same
100,
the
same
lines
of
code.
You
can
actually
now
build
apps
that
will
land
inside
office.com.
So,
for
example,
I
have
it
here.
F
F
And
finally,
you
also
have
the
exact
same
capability
with
an
outlook.
So
now
you
have
the
ability
to
have
this
and
exactly
the
same
capabilities.
The
beauty
here
it
also
integrates
natively
with
the
theming
engine
of
microsoft
teams.
If
I
go
here-
and
I
put
it
in
dark
now-
all
my
tab
is
now
fully
dark
and
looks
really
really
great.
On
my
ui
second
thing
that
I
want
to
do,
I'm
going
to
go
quick
for
that.
F
If
you
want
to
try
out
teams
building
apps
with
teams
with
the
teams
toolkit,
which
is
a
microsoft
provided
framework
to
build
apps
in
both
net
and
javascript
and
typescript
you,
we
also
have
a
sample
that
is
available.
So
the
only
thing
you
will
have
to
do
is
to
go
to
your
team's
toolkit,
tab,
click
on
view,
samples
and
install
here,
the
contact
exporter
using
the
graph
toolkit.
F
What
it's
going
to
give
you
it's
going
to
give
you
this
great
app
that
we
can
find
here
that
has
a
capability
of
searching
for
folks,
I'm
gonna
search
for
adele
right
here
and
where
I
will
be
able
to
export
this
list
of
folks
straight
to
an
excel
spreadsheet.
What's
the
beauty
here,
this
sample
uses
entirely
sso,
so
you
don't
even
need
to
log
in
the
only
pop-up
you're
going
to
get
is
the
first
time
for
consent,
if
you
don't
have
already
consented
to
these
to
this
app.
F
F
Go
to
our
repo
aka,
not
ms
mgt.
You
can
look
at
our
docs
at
our
issues.
You
can
even
contribute
want
to
see
all
the
samples
that
I
just
showed
today.
They
are
all
available
on
our
sandbox
samples.
You
want
to
play
with
our
playground
or
you
want
to
learn
more
about
mgt
everything.
Is
there
vesa
back
to
you.
A
Anyway,
thank
you,
ready
and
thank
you
annui
and
thank
you.
Sebastian
really
really
cool
demos
today,
awesome
stuff
for
the
community
and
just
a
quick
recap.
We
do
have
quite
a
few
community
calls
which
are
happening
in
a
weekly
basis,
so
we
have
the
platform
card
which
is
weekly.
We
do
have
specific
monthly
community
course
and
bi-weekly
course
so.
Weekly
we
have
at
least
tuesday
and
thursday
calls
happening.
Every
single
week,
if
you're
wondering
on
what
are
the
calls
and
how?
A
A
The
next
call
is
happening
week
from
now
8m
pacific
time,
which
is
then
europe
has
followed
up
on
u.s
from
the
time
zone,
so
at
least
europe
and
us
are
in
the
same
time
zone
so
that
that
should
reduce
some
of
the
confusion
on
the
timings.
But
thank
you
everybody
for
joining
today.
Thank
you
and
please,
please,
please
keep
the
feedback
coming.
We
are
building
all
of
these
capabilities
for
you,
so
your
input
is
super
super
crucial
for
us
to
understand
how
we
can
help
you
even
more,
but
thanks
everybody
for
joining.