►
Description
Microsoft 365 platform community call delivered on May 17th. Two demos - Integrate Microsoft Graph connector content on Office.com, and Your Microsoft 365 app within the fingertips of employees with Viva Connections. It’s not too late to register for Microsoft Build 2022 - May 24-26. Sharing is Caring announced a new training event - “Writing for the Web“ with 2 delivery dates in June. Five articles, 1 document, 1 sample - bot-release-management + Teams terms glossary reviewed in this session. 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 in the Microsoft 365 platform community blog - https://aka.ms/m365pnp/blog
• Download invite for this weekly Microsoft 365 Platform community call: https://aka.ms/m365-dev-call
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - https://aka.ms/m365pnp
A
A
Your
microsoft
resist
5
app
within
the
fingertips
of
the
employees
with
the
web
connection
and
it's
a
cool
story
as
well
now
bit
of
a
pointer
just
call
out,
for
I
think,
brian
and
david,
because
I
know
that
both
are
are
on
the
edge,
because
paula
is
not
on
the
call.
Yet
he
will
be
joining
half
past.
So
we
don't
need
to
rush
before
that
he's
joining
half
past
because
of
other
commitments
as
well,
and
then
we'll
move
to
wildex
and
polish
demos
on
there.
A
A
We
have
the
microsoft
resistor
developer,
videos
youtube
channel
where
we
have
so-called
encodes
official
guidance,
videos
from
cloud
advocates
and
for
marketing,
and
then
we
have
our
microsoft
365
community
videos
channel
where
we
have
all
of
the
community
called
recordings
and
individual
demos
from
this
community
course
and
few
other
videos
as
well
from
a
few
different
group
of
organizations.
In
microsoft,
we
have
a
lot
of
open
source
assets
across
multiple
different
locations
and
organizations
in
github.
We
also
have
a
lot
of
sample
galleries.
A
A
Luckily,
there's
actually
only
one,
which
is
a
cms
forward,
slash
m365,
forward,
slash
community
and
you
will
land
on
our
microsoft,
365
platform,
community,
page
community,
page
trying
to
speak
english.
It's
hard,
microsoft,
365
platform,
community
page
and
from
where
you
can
get
access
on
all
of
the
different
assets
which
are
available
from
microsoft
and
from
other
people.
In
the
community,
because
a
lot
of
these
assets
which
are
getting
built
are
contributed
by
our
open
source
community
through
multiple
different
channels.
A
Now
we
wanted
to
always
recap:
we
do
have
quite
a
few
community
calls
happening.
So
we
do
have
this
weekly
community
call
happening
tuesdays
at
8
am
pacific
time.
This
call
is,
on
a
summer
break
between
july
and
august,
we're
trying
to
make
sure
that
we
don't
have
calls
well.
We
want
to
make
the
presenters
and
also
you
the
opportunity
to
have
a
break,
and
we
want
to
have
it
a
bit
more
easier
during
summer
time
we
will
have
also
other
community
calls
as
well
like
adaptive
cards,
microsoft,
identity,
platform,
office,
add-ins
and
power
platform.
A
Community
calls,
which
are
happening
once
a
month.
Power
platform.
Community
goal
by
the
way
happens
tomorrow.
So
probably
gonna
get
that
one
in
your
schedule,
and
then
we
have
two
recurrent
bi-weekly
calls
happening
every
single
thursday,
so
we
technically
have
at
least
one
or
two
community
calls
every
single
week,
which
is
pretty
pretty
cool.
A
If
you're
looking
into
downloading
the
invites
of
this
go
to
the
akms
m365
calls
that
is
actually
on
the
same
base
as
our
community
assets
and
from
there
you
can
download
the
recurrent
ics
files,
which
makes
it
easier
to
understand,
what's
happening
and
where
now
a
few
assets,
I'm
trying
to
squeeze
this
in
in
a
bit
smaller
area.
But
we
want
to
promote
this
in
every
single
call,
because,
surprisingly,
not
that
surprisingly,
there's
always
new
people
joining
on
this
course.
So
there's
always
new
people
who
give
us
feedback
related
on.
A
I
wasn't
aware
of
this
stuff,
so,
first
of
all,
as
a
developer,
you
should
be
subscribing
on
the
microsoft
365
developer
program,
because
from
there
you
will
get
a
free,
e5
tenant
which
you
can
use
for
developer
usage
and
that's
a
really
really
great
asset,
and
as
long
as
you
use
that
tenant
for
developer
purposes,
it
will
renew
automatically
in
every
single
90
days.
The
other
really
really
powerful,
asset
and
and
location
is
ams.
Entries
is
to
find
dev,
learn
from
where
you'll
find
82
modules.
A
A
Now
I
talked
about
the
samples
they
are
super
valuable
because
again
the
samples
make
it
easier
to
you
to
understand
where
to
get
started
and
a
lot
of
these
samples.
They
some
of
the
samples,
are
really
cool
and
comprehensive.
Some
of
them
are
a
bit
more
simplified
and
that
is
by
design
because
we
actually
want
to
have
a
scenario
and
a
code
example
for
as
much
of
the
different
things
as
possible.
So
whenever
you
are
looking
into,
how
would
I
do
a
bot
in
a
specific
version
of
microsoft
themes
in
a
bot
framework?
A
How
would
I
be
bought
in
a
nodejs?
How
would
I
implement
a
messaging
extension?
How
would
I
do
an
office
and
outlook
application
using
the
team's
toolkit,
sdk
v2,
you
can
go
to
one
location,
you
can
use
those
texts
and
strings
as
your
query
query
parameters
and
you
will
find
the
relevant
samples
provided
by
microsoft
or
by
the
community.
So
akms
m365
samples
is
the
address
of
this
particular
location.
A
B
Absolutely
thank
you.
Vessa,
as
vesa
mentioned,
we
have
a
wide
array
of
opportunity
for
you
to
contribute
to
those
samples,
but
sometimes
github
is
hard
right.
What
do
those
phrases
mean?
Pull
requests
and
fork
and
raw
and
blame
they
can
be
confusing.
Sharing
is
caring
is
a
program
here
to
provide
you
hands-on,
safe
space
guidance
on
how
you
can
submit
your
samples,
whether
it
be
power
platform,
whether
it
be
updating
documentation,
whether
it
be
writing
new
documentation.
B
We
want
to
provide
you
hands-on,
safe
space
guidance
on
how
to
accomplish
just
that.
These
are
live
sessions
where
you'll
learn
together,
we'll
walk
you
through
it
together
and
you'll
collaborate
with
others
in
the
community,
they're
absolutely
free.
They
are
not
recorded
so
you're
free
to
ask
any
and
all
questions.
We've
got
upcoming
sessions
on
power
platform,
samples,
community
content
and
our
newest
writing
for
the
web.
If
you'd
like
to
learn
a
little
bit
more
emily
mancini
and
hugo
bernier
will
be
leading
that
there's
two
upcoming
dates
so
check
them
out.
A
Excellent,
thank
you
david
on
that
one,
and
these
get
so
good
feedback.
So
don't
don't
miss
out.
They
are
really
really
really
great
sessions
to
get
started
and
also
not
just
getting
started,
but
understanding
specific
things
which
might
not
be
familiar
so
check
out.
The
akms
sharing
scaring
address
now
a
few
news
from
the
microsoft
365
developer,
sign
or
from
the
teams
and
and
the
viva
side
of
the
house.
A
So
first
of
all,
we
have
three
new
blog
posts
in
the
microsoft
365
developer
blog
and
two
blog
posts
related
on
specific
changes
in
the
office
and
insight.
So,
first
of
all
in
the
office
adding
specific
for
excel.
There's
a
new
api
for
power,
query
read-only
data,
so
you
can
easily
query
the
data
within
your
excel
workbook.
Then
there's
a
changes
announced
related
on
office,
add-ins,
execute
function
commands,
and
this
is
when
you're
executing
an
external
function
within
your
office.
Add-In
and
that's.
A
There
are
some
adjustments
coming
related
on
this
one
because
of
security
reason,
and
then
there's
this
great
great
great
summary.
Blog
post,
an
article
from
bob
german
focuses
on
natalie
cat's
video,
which
talks
about
how
would
you
publish
an
app
to
the
microsoft
teams,
app
store
so
as
you
build
an
application
for
microsoft
teams?
How?
What
are
the
steps
of
actually
purposing
that
one
in
the
app
store
so
using
the
partner
center
and
then
getting
that
into
app
source
to
be
available
for
people
to
consume?
A
So
really
really
great
video
as
well,
and
then
on
the
teams
block.
We
only
had
a
one
new
blog,
which
was
more
around
celebrating
the
one
year,
together
with
the
microsoft
teams
and
webinars
and
kind
of
a
nice
summary
blog
post
related
on
the
microsoft
themes,
webinars
features
and
they
also
talk
with
with
the
people
behind
of
actually
building
that
capability
within
the
microsoft
teams,
so
probably
want
to
check
that
one
out
as
well
related
on
microsoft
themes.
A
We
do
have
actually
quite
a
lot
of
changes
coming
up
all
the
time
and
awesome
improvements
in
the
microsoft
teams
platform
documentation
and
we
want
to
call
them
out
within
this
weekly
call
as
well
I'll.
Let
surprise
to
actually
do
a
quick
recap
on
what's
happening
in
the
microsoft
teams:
platform,
documentation,
site.
C
Thank
you,
visa
hello,
everyone,
I'd,
walk
you
through
the
platform
and
documentation
updates.
Let's
start
with
the
platform
updates
on
the
left,
we've
published
a
new
scenario
base
sample,
which
shows
how
respective
stakeholders
can
get
notified
when
new
work
item
is
created
in
azure
devops,
this
sample
listens
to
work
item
created
even
and
creates
a
group
chat
with
stakeholders
using
graph
apis.
It
also
sends
a
proactive
message
in
a
group
chat
with
task
details
of
newly
created
chat
using
bot.
This
can
also
be
extended
to
post
regular
updates.
C
This
sample
is
already
published
in
github
rep
repo
at
aka
dot.
Ms
team
samples
bot
release
manage
folder.
Now,
let's
move
to
the
dock
updates
on
the
right.
We
we
have
introduced
glossary
and
we
believe
that
it
will
help.
You
find
the
definition
about
a
term
quickly
without
the
need
for
searching
outside
of
docs.
If
you'd
want
us
to
add
more
terms
or
have
any
feedback.
Please
do
let
us
know.
C
A
Thank
you,
excellent,
really,
really
cool
to
see
the
improvements
in
the
end
that
cluster
is
actually
really
really
really
great
idea.
It
certainly
helped,
and
especially
as
microsoft,
employees,
we
always
use
abbreviations
and
terminology
which
the
external
audience
might
not
actually
understand.
So
it's
really
cool
to
have
the
closer
in
place
for
sure
now
few
events
or
the
most
important
event
for
in
a
year
for
developers
in
microsoft
and
cloud
is
coming
and
next
week
so
may
24
to
26.
Is
the
microsoft
build.
This
is
happening
once
again
in
remotely
this
year.
A
It
might
be
that
will
be
in
person
in
a
year
from
now,
but
no
promises
on
that
at
this
point
now.
This
is
a
remote
free
event
where
you
can
register
and
there
will
be
a
schedule
available
for
you
to
then
see
all
of
the
on-demand
videos
and
also
the
scheduled
videos
which
will
be
out
there
later
available
as
a
recording.
A
But
you
certainly
want
to
register
to
my
build
at
microsoft.com
to
see
the
schedule
and
all
of
the
core
sessions
which
are
available
now,
especially
related
on
microsoft,
365
sessions
or
like
in
this
build.
We
call
them
as
a
collaborative
app
sessions
and
there
is
now
a
collaborative
session
schedule
available
for
you
to
take
advantage.
A
So
if
you
go
to
the
https
that
says
akms
teams
sessions,
it
will
actually
list
all
of
the
different
collaborative
app
sessions
which
are
available
next
week
between
the
24th
and
25th
of
may
so
really
really
good
asset
on
looking
into
what
kind
of
breakout
sessions
are
there.
What
kind
of
on-demand
sessions
are
not
in
my
videos
and
there's
some
expert
sessions
and
product
roundtables,
and
even
more
so,
if
you
have
questions
related
on
microsoft
teams,
development,
you
want
to
probably
check
out
us
to
expert
sessions
or
microsoft.
A
Graph,
there's
specific
as
to
expert
sessions
on
those
and
product
round
tables
are
more
on
the
engineering
and
microsoft
asking
input
from
your
site.
So
as
an
example
there's
a
product
roundtable
for
viva
connection
extensibility
on
asking
on
hey.
So
what
are
the
things
what
you
would
like
to
have
here
or
in
the
sharepoint
framework
side?
What
are
the
things?
A
What
you
would
like
to
see
in
the
future
for
sharepoint
framework,
which
is
a
super
super
critical
thing
for
engineering
to
know,
but
please
please
go
to
the
https
akms
team
sessions
to
have
a
full
catalog
on
that
and
now
before
we
go
to
the
actual
demos
of
today.
Let's
do
a
quick
crew
photo
to
care
about
picture
and
I
will
start
my
connotation
and
I
will
catch
you
in
the
screen
in
a
second
today.
We're
gonna
use
something
different
than
the
white
one.
Whenever
we
get
there
here,
we
go
nice.
Let's
actually
do
that.
A
A
Here
we
go,
did
I
get
there
already?
I
don't
see
myself.
Maybe
I
did,
but
I
can't
see
myself.
Let
me
put
the
recording
on
and
let's
do
some
handwaving
everybody
for
the
other
people
in
the
community.
We
can
see
more
people
joining
excellent.
Thank
you
for
everybody
joining
let's
do
some
hand
waving.
Now.
I
can
see
myself
on
the
screen.
I
can
see
david
on
that
side.
A
Oh,
we
get
more
people,
let's
do
some
hand
waving.
We
are
still
getting
people
in
the
room.
Excellent,
there's
some
free
seats,
excellent,
we'll
craft
a
keep
animation
out
of
that
as
well.
Thanks
everybody
for
joining
on
that
one.
So
I
will
get
a
gift
animation
on
that
as
we
move
to
the
actual
stars
of
the
day.
So
we'll
start
with
monika
related
on
a
microsoft,
integrating
microsoft,
craft,
connector
content
on
the
office.com
and
then
after
her
we
will
move
with
waldek
and
paulo
on
the
viva
connection
and
microsoft
themes
and
spfx
storyline.
D
Awesome,
thank
you.
So
much
hey
everyone.
My
name
is
monica.
I
am
a
product
manager
on
the
graph,
connectors
team
and
today
I'm
going
to
be
talking
to
you
guys
about
how
you
can
integrate
graph
connector
content
into
various
m365
experiences,
so
office.com
search
and
some
new
experiences
that
will
be
coming
your
way
like
context,
iq,
etc.
D
D
Organizational
data
is
growing
exponentially
and
a
lot
of
this
data
lives
in
silos,
and
so
a
major
problem
that
employees
face
within
organizations
is
that
they
spend
20
to
30
percent
of
their
time
at
work,
searching
for
information,
and
they
can't
find
the
information,
because
this
information
is
spread
across.
You
know
various.
D
D
D
Viva
topics
will
be
coming
discovery
as
well
and
more
we're
working
on
that
all
right,
and
then
I
think
that
brings
us
into
our
demo
yeah.
So
let's
see
this
in
action.
So
it's
it's
about
a
three
to
four
minute
demo.
You
can
just
play
that
yeah
click
play
and
then
take
it
away.
Yeah
I
can
go
to
any
of
the
microsoft
search
endpoints,
which
include
office.com,
sharepoint
and
bing
at
work
and
search
for
marketing.
D
D
This
email
looks
good,
so
I
press
send.
Sometime
later,
I
follow
up
with
meredith
on
teams
to
see
if
they
were
able
to
check
out
the
case
study
I
had
sent
over.
They
said
they
hadn't
seen
it
yet,
but
that
they
can
go
to
their
office.com
home
page
to
find
the
shared
figma
file.
Among
other
recently
worked
on
or
shared
items
as
meredith,
I
can
navigate
to
office.com
under
quick
access.
D
D
D
D
D
D
So
there
are
three
high
level
components
to
building
a
graph
connector.
So
you
know,
firstly,
you
need
to
create
a
connection
and
what
this
entails
it.
You
know
it
means
you're,
you're,
defining
your
connection,
object,
you're,
updating
the
configuration
file
for
the
experiences
and
you're
providing
additional.
You
know,
optional
connection
configuration
information.
D
Secondly,
you
need
to
create
and
register
your
schema
and
what
this
entails
is
you're,
creating
a
new
schema
object
properties
and
their
attributes,
labels
and
aliases.
So
you're,
basically
telling
us,
you
know,
for
a
given
item.
What
are
all
the
different
properties
that
are
important
to
that
item
and
how
do?
How
should
all
those
properties
behave
in
search
and
what
what
does
each
property
semantically
mean?
And
all
that
information
is
used?
Empowering
these
experiences
and
then
yeah?
So
you
have
to
register
the
schema
before
adding
items
to
the
connection
as
well.
D
That's
an
important
point
and
then,
lastly,
you
need
to
index
those
items
with
their
apples,
so
this
is
about
bringing
in
that
data
into
graph.
So
this
means
creating
updating
and
deleting
items
and
creating
updating
deleting
external
groups
and
group
members.
So
this
is
part
of
the
data
sync
process,
so
the
first
piece,
like
I
mentioned,
is
about
creating
a
connection.
So
this
is
a
sample
call,
and
so
you
need
to
provide
some
sort
of
connection
id
a
descriptive
name
about
the
connection
and
then
you
would
like
for
enable
content
experiences.
D
You
essentially
include
what
are
the
different
experiences
you
want
that
connector
to
participate
in
and
then,
depending
on
the
experience
that
you
want
to
light
up.
There's
some
requirements
associated
with
that,
for
example,
for
the
office.com
scenario.
The
activity
settings
piece
is
a
requirement
and
within
activity
settings
there's
this
piece
called
url
to
item
resolvers,
which
basically
provides
us
a
way
to
resolve
urls
that
are
shared
within
teams
in
outlook
to
the
item
id.
D
So
in
order
to
populate
the
you
know,
office.com
experience,
we
need
to
know
what
the
title
is.
We
need
to
know
what
the
url
is.
We
need
to
know
the
icon,
url,
etc.
So
these
semantic
labels
are
very
helpful
in
that
way,
and
then
the
last
component,
like
I
mentioned,
is
to
you
know,
create
the
external
item
and
push
data.
So
here
you
can
include
the
apple,
so
this
is
who
has
access
to
that
item
and
all
like
apples
are
honored
across
all
of
our
endpoints
or
all
of
our
applications.
D
Like
I
mentioned,
the
data
is
secure
and
then
the
property
section
maps
directly
to
the
schema.
So
you
provide
the
actual
title
for
that.
Given
item
the
author
and
then
any
other
information,
you'd
like
depending
on
what
your
schema
was
and
then
the
content
is
actually
the
full
text
index
you
know
of
that
content.
So
if
it
was
a
knowledge
based
article,
for
example,
it
would
just
be
complete,
like
the
html
of
the
entire
article
itself.
D
So
that's
that
last
component
yeah
and
then
also
as
part
of
you
could
add
activities
as
well
as
part
of
the
item,
or
you
can
make
this
separate
call
here
to
append
activities
to
the
item
itself.
Activities
is
another
well-known
property
on
the
item.
So
essentially,
what
activities
are
it's
basically
you're
telling
us
who
are
the
different
users
within
your
organization
that
are
doing
actions
like
creates
modifies
comments,
views
etc
on
that
item?
So
this
information
is
very
useful
in
empowering
context
iq
in
outlook
in
office.com.
D
D
Hopefully
it
was,
is
pretty
straightforward
and
you
know
feel
free
to
ask
any
questions
that
you
have.
There
are
a
bunch
of
resources
that
I've
outlined
here.
If
you,
you
know
want
to
learn
more,
you
want
to
just
go
start
building
graph
connectors
right
now,
so
we
have
some
admin,
documentation,
some
developer
documentation
and
then
the
connectors
gallery,
which
shows
all
the
connectors
that
are
either
available
through
the
microsoft
built
connectors
that
we
have,
but
also
the
connectors
that
our
system,
integrator
partners,
also
offer
so
yeah.
A
Thank
you
excellent,
so
monica
let's
do
it
this
way
and
that,
as
we
have
one
more
demo
coming
up,
we
can
answer
the
test.
Few
questions
in
the
chat,
but
if
you
can
answer
on
those
in
the
chat,
that
would
be
awesome
so,
and
this
is
really
really
cool
stuff.
It's
it's
actually
surprisingly
simple
thing
to
do
so:
really:
really
cool
stuff
thanks
monica.
E
Screen
take
it
away
perfect,
all
right
all
right.
So
as
we
build
apps
on
microsoft
365,
they
can
be
of
many
shapes
isis
right
like
we
have
apps
that
are
destinations,
that
is
a
web
app
or
an
app
on
your
phone
right.
These
are
apps
that
you
explicitly
need
to
open,
but
the
really
true
powers,
when
you
think
of
it,
to
extend
your
app
so
that
your
app
spans
from
all
the
way
being
destination
being
a
a
web,
app
being
a
mobile
app
to
extension.
E
E
So
when
you
build
microsoft,
365
apps
think
of
it
that
your
apps,
the
apps,
that
you
built
for
your
work,
can
span
from
standalone
experiences
to
extensions
that
show
up
inside
microsoft,
365
where
users
already
are
when
you,
let's
think
about
scenario
right.
So
let's
say
we
wanted
to
build
an
application
for
our
company,
we're
going
back
to
office
and-
and
we
still
are
required
to
book
a
seat
because
we
don't
want
to
open
up
already
for
everybody.
E
We
have
limited
space,
so
we
want
people
to
book
a
space
ahead
of
time
before
they
arrive,
so
that
everybody
is
guaranteed
a
place
to
sit
right,
and
in
that
scenario
we
have
few
few
use
cases
right.
So
we
are
an
employee
and
we're
trying
to
find
a
seat.
We
we
and
we
wanted
for
a
given
date
or
a
portion
of
the
date,
and
we
when
we
arrived
in
the
office,
we
want
to
check
in
to
confirm
that
yes,
we're
there
and
we're
going
to
use
that
seat.
E
It's
not
available
for
everybody
right
and
then
also
we
have
another
actor
facilities.
Who
wants
to
be
able
to
manage
the
bookings
that
everybody
places
right
and
and
then
then
also
afterwards
to
be
able
to
report
on
that
right?
So
there
are
a
number
like
when
you
think
about
this
scenario.
You
can
already
imagine
envision
few
ways
how
you
could
go
about
it,
how
different
actors
work
throughout
the
workdays
some
might
be
on
the
go.
Some
might
be
behind
a
desk
right.
E
So
what
are
the
different
ways
in
which
you
could
support
them
in
their
work?
And
here
are
a
few
experiences
that
you
could
imagine
you
would
build
right.
So
if
you
we
would
start
on
top
left,
you
might
have
a
personal
app
in
teams
right
that
allows
people
to
manage
bookings
directly
from
teams
so
not
having
to
go
anywhere
else.
Imagine
that
you
are
an
employee
and
you
want
to
book
a
seat
on
the
go
you're
on
your
phone.
E
E
F
F
You
can
find
the
whole
source
code
of
the
solution
that
valdec
showed
us
a
few
seconds
ago,
and
now
let
me
dig
into
the
solution
from
a
practical
point
of
view.
First
of
all,
I
will
show
you
the
user
experience
when
working
with
the
viva
connection
adaptive
card
extension,
which
will
be
the
main
topic
of
my
demo
today.
Of
course,
we
don't
have
time
enough
to
cover
all
of
the
different
flavors
of
ui
that
we
implemented,
but
we
will
focus
on
viva
connections
now
here
you
can
see.
F
Let
me
try
to
be
lucky
and
let
me
search
for
a
free
desk
and
wonderful.
I
found
the
one
desk
desk01,
which
is
really
nice
and
close
to
the
coffee
machine
five
meter.
Far
from
the
copy
machine
I
can
book
it
and
as
such
tomorrow
I
will
be
able
to
get
into
my
headquarter
and
still
using
the
same
adaptive
card
extension,
I
will
be
able
to
check
in
or
check
out
when
I
will
be
done
using
the
desk.
As
you
can
see,
the
experience
from
an
end
user
point
of
view
is
really
straightforward
and
simple.
F
Now,
let's
dig
into
the
technical
solution,
so,
first
of
all,
we
decided
to
use
microsoft,
lists
and
so
lists
stored
in
sharepoint
online,
at
the
very
end,
to
store
the
locations
to
store
the
desks
and
to
store
the
facilities
and
all
the
other
stuff
that
represents
the
repository
and
the
storage
of
data
for
our
solution.
This
is,
for
the
sake
of
simplicity,
and
to
give
you
a
solution
that
you
can
easily
deploy
in
your
environment
to
play
with
it.
F
Then
we
created
a
set
of
apis
on
top
of
the
lists
in
microsoft
lists
and
through
these
apis
we
make
available
to
all
of
the
different
flavors
of
ui
components
that
we
have
the
functionalities.
So
let
me
reduce
this
one,
so
we
have
the
api
to
manage
bookings.
We
have
the
api
to
manage
desks
and
to
do
all
the
stuff
that
we
need.
For
example,
if
I
want
to
book
a
location,
I
can
just
use
the
bookings
endpoint
and
do
my
stuff
through
this
api.
This
api
has
been
registered
in
azure
active
directory.
F
In
the
tenant,
where
we
are
using
this
solution
and
technically
speaking,
this
is
an
app
registered
in
azure
id,
which
is
exposing
an
api.
So
we
are
making
the
rest
api
available
to
all
of
the
client
solutions
that
we
built
for
the
safe
desk
365
and
in
order
to
consume
this
api,
you
simply
need
to
have
the
booking.write
permission
scope
assigned
to
an
application
which
will
rely
on
our
backend
api.
So
now
that
I
have
showed
you
what
we
have
under
the
cover,
let
me
switch
to
the
actual
source
code
of
the
adaptive
card
extension.
F
It
is
a
quite
rich
one,
so
I
will
not
dig
into
every
single
file,
but
I
will
give
you
an
idea
of
how
we
implemented
it.
First
of
all,
we
have
the
adaptive
card
extension
by
itself,
which
is
a
sharepoint
framework
component
which
inherits
from
base
adaptive
card
extension
in
this
component.
We
have
a
set
of
properties
and
a
state
like
we
do
in
real
components
and
from
a
properties
point
of
view.
F
We
simply
keep
track
of
the
settings
like
the
uri
of
the
application
api
that
we
want
to
consume
and
the
url
that
we
want
to
use
and
stuff
like
that,
while
in
the
state
we
keep
track
of
the
status
of
the
ui
and
specifically,
we
keep
track
of
all
of
the
available
locations.
All
of
the
desks
that
we
have
all
of
the
bookings
of
the
user
and
those
that
are
for
today
and
stuff
like
that.
So
we
keep
this
data
of
our
application
to
better
manage
our
logic.
F
Then,
in
the
uninit
method
of
our
component
of
our
spfx
component,
we
do
a
bunch
of
things.
First
of
all,
we
initialize
the
state
of
the
component
and
then
in
every
adaptive
card
extension
that
we
want
to
create.
We
can
have
two
different
flavors
of
ui
elements.
There
could
be
card
views
and
quick
views.
What
we
saw
here
while
booking
our
desk,
this
one
is
called
a
card
view
and
it
is
an
experience
based
on
a
predefined
set
of
ui
templates.
F
We
have
three
templates,
one
just
based
on
text,
one
based
on
text
and
a
secondary
text
and
the
third
one
based
on
an
image
which
is
the
one
I'm
using
right
here,
so
that
I
can
show
a
nice
image
and
a
ui
with
up
to
two
buttons
in
the
ui.
Then,
when
you
click
on
one
of
these
buttons,
this
one
is
called
quick
view
and
this
one
is
based
on
a
json
template
created
using
the
adapted
card.json
syntax.
F
So
here,
as
long
as
you
rely
on
the
adapter
card
schema,
you
can
build
whatever
kind
of
ui
experience
you
like,
and
that's
why
you
were
able
to
see
different
ui
components
through
the
navigation
flow
of
the
user.
So
if
I
go
back
here
here,
we
are
simply
registering
the
card
views
and
the
quick
views
that
we
are
going
to
use
in
our
solution.
The
welcome
one
is
the
one
we
see
by
default
as
the
welcome
screen
of
the
adapter
card
extension.
Then
we
can
select
the
flow
when
we
want
to
book
a
new
desk.
F
We
can
go
for
the
frio
for
the
specific
desk.
We
can
even
get
a
response
that
there
are
no
available
spots.
If
that
is
the
case,
and
we
can
get
the
confirmation
of
a
check
in
or
of
a
checkout
when
the
user
will
do
checking
checkout.
So
once
we
have
configured
the
state
and
the
registration
of
the
card,
we
can
fetch
the
actual
data
from
the
api.
So
we
rely
on
a
fetch
data
method
that
we
invoke
asynchronously
so
that
we
can
start
rendering
the
ui
of
the
adaptive
card.
F
In
fact,
as
you
can
see
here,
if
I
will
refresh
you
see,
we
are
now
loading
and
once
we
will
be
done,
we
will
have
the
actual
data
available.
That's
what
we
do
in
the
fetch
data
and
in
the
fetch
data
we
simply
work
using
different
functionalities
that
we
have
out
of
the
box
in
sharepoint
framework.
What
do
I
mean?
Well,
whenever
you
want
to
consume
in
sharepoint
framework,
whether
you
are
creating
an
adaptive
card
extension
like
we
are
doing
right
now
or
a
web
part
or
an
extension
or
a
team?
F
Stop
doesn't
really
matter
what
kind
of
ui
component
you
are
building,
but
in
sharepoint
framework
you
can
always
easily
consume
an
external
api
which
can
be
micrograph
or
a
third-party
api,
and
you
can
do
that
safely
and
securely,
using
azure
active
directory
as
the
security
infrastructure
supporting
you
in
the
consumption
of
the
back-end
api.
Here.
What
we
do
is
to
use
the
context
of
sharepoint
framework
to
get
through
the
aad
token
provider.
Factory
object,
as
you
can
imagine,
based
on
the
name.
F
F
We
decided
to
create
a
package
so
an
npm
package
that
we
called
safe,
desk,
365
sdk,
which
is
right
now
in
preview
version,
as
you
can
see,
and
we
are
relying
on
this
sdk
to
consume
the
backend
api,
so
that
whether
we
will
create
the
ace,
the
adapter
card
extension
here
or
the
team
stub
or
any
other
or
the
bot
or
any
other
solution.
We
can
always
rely
on
the
same
sdk
and
reuse
the
same
logic.
F
So
what
we
do
here,
we
rely
on
our
client
and
we
get
the
location
we
get
the
bookings,
we
filter
the
bookings
of
today,
and
then
we
configure
the
state
of
our
component
once
we
have
done
that,
we
need
to
render
the
ui
and
the
ui
can
be
rendered
either
using
the
car
views
or
the
quick
views.
I
will
give
you
a
quick
overview
of
the
idea
when
we
create
a
card
view.
F
This
will
be
a
typescript
class
which
will
simply
define
the
buttons
that
we
want
to
show
in
the
ui,
and
here
we
simply
say:
okay,
let
me
see
if
I
have
any
booking
for
today,
because
if
I
have
any,
I
will
show
the
button
to
create
any
booking,
as
well
as
the
button
to
check
in
or
to
check
out
based
on
where
I
am.
If
I'm
already
checked
in,
I
will
have
the
button
to
check
out.
If
I
still
need
to
check
in,
I
will
see
a
check
in
button.
F
Then,
when
the
user
will
click
on
the
button,
I
will
simply
associate
an
action
which
will
be,
for
example,
let's
focus
on
the
action
to
book
a
new
desk.
If
I
select
book
a
new
desk,
I
will
show
a
quick
view,
which
is
the
one
built
on
adaptive
card,
json
schema,
which
will
be
the
one
I
registered
before
in
the
unit
method.
F
I
will
provide
through
a
get
data
method
that
we
have
in
all
of
the
quick
views
we,
I
will
define
the
data
that
I
will
use
to
automatically
do
data
binding
in
the
ui
of
my
adaptive
card
and
then
I
can
eventually
manage
the
triggering
of
actions
inside
the
ui.
So,
for
example,
when
I
click
on
the
book
button,
this
is
the
quick
view.
F
This
list
of
locations
and
this
list
of
time
slots
are
based
on
the
data
binding
of
an
object
that
I'm
providing
through
the
get
data
method,
and
you
can
see
here,
I'm
providing
the
locations
so
in
the
json
matching
to
this
quick
view.
I
use
the
adaptive
card.
Syntax
here
is
version
1.3,
and
I'm
saying
that
I
have
a
container
in
which
I
will
show
a
text.
Then
I
will
show
a
choice
set
and
the
items
in
the
choice
set
will
be
the
locations
that
I
have
in
my
data
source.
F
In
fact,
I
say
the
data
source
are
the
locations
that
I
have
in
my
data
and
for
every
location
I
will
show
the
name
and
address
and
the
value
will
be
the
name.
Then
I
will
show
the
date
control
of
adaptive
card
syntax
and
then
I
will
show
another
choice
to
select
if
it
will
be
the
morning
or
the
afternoon,
once
I'm
done,
I
will
have
a
button
of
type
submit,
which
will
be
which
will
trigger
the
action
that
I
have
in
the
quick
view
right
here
in
the
on
action.
F
In
order
to
start
the
process
of
booking
my
desk
and
again,
I
will
rely
on
my
npm
package
with
the
client
library
and
I
will
do
execute
all
of
the
logic
to
manage
the
booking
of
my
desk.
So,
as
you
can
see,
you
can
really
create
clean
and
simple
solutions
where
you
rely
on
a
backend
api
to
provide
enterprise
level
functionalities,
and
then
you
can
build
on
top
of
it
any
kind
of
ui
components.
A
Excellent,
thank
you
thank
you,
paulo
really
cool
stuff,
and
that
that
is
a
really
nice
cool.
Looking
solution,
and
let
me
quickly
show
a
few
slides
and
we'll
close
up
after
that.
Thank
you
monica.
Thank
you.
Well,
thank
you.
Paula
really,
really
cool
demos,
just
a
bit
of
a
kind
of
a
heads
up
as
we
recreated
some
of
the
meetings
we
we
know
that
some
people
might
be
ending
up
on
the
old
meetings,
even
though
the
akms
address
was
updated.
A
So
that's
actually
one
of
the
reasons
why
we
didn't
have
that
many
attendees
today
for
sure,
but
we'll
get
the
attendee
numbers
back
for
sure
in
the
future.
Now
the
recording
of
this
call
will
be
available
within
24
hours
within
the
microsoft
365
community,
youtube
channel
at
akms
last
m365,
bmp,
slash
videos
or
m365
sas
videos
actually
works
as
well.
I
need
to
update
that
akms
address
to
be
a
bit
more
simplified
if
you're
looking
into
getting
notified
when
the
recording
is
available,
please
subscribe
to
twitter
or
to
that
youtube
channel.
A
You
cannot
access
the
recording
directly
from
the
team's
channel
that
unfortunately
does
not
work
for
non-microsoft
employees
as
it's
getting
stable
in
the
microsoft
corporate
assets.
The
next
microsoft
365
platform
call
is
on
may
24th
that
is
actually
overlapping
a
bit
with
satyanarella's
keynote
from
the
build.
So
we
will
have
a
one
demo
and
one
topic
which
will
cover
before
and
half
past,
so
30
minutes
on
the
call
we'll
start
watching
the
satya
nadellas
microsoft
build
keynote
together
as
a
watch
party.
A
So
we
can
then
have
a
discussion
and
comment
the
stuff
in
the
chat
and
and
see
your
reactions
on
what
satya
is
covering
within
a
keynote,
but
that's
it
and
that's
the
plan
for
next
week
and
we'll
come
back
on
the
normal
schedule.
Then
the
week
after
that,
and
that's
it
for
today,
thanks
everybody
for
joining.
Thank
you
monica
thank
you.
Well,
they
can
duncan
paula
one
more
time
and
we'll
be
back
within
a
week
latest
within
a
week
depending
on
which
community
calls
you're
joining
bye.