►
Description
Microsoft 365 platform community call delivered on November 16th. Two demos delivered this week: Getting started on building Microsoft Teams tabs with Adaptive Cards and Microsoft Learn Module - Extend Microsoft Viva Connections with Web Parts. Start Viva Connections development today with free training Learning Path: Extend Microsoft Viva Connections. Join the Microsoft 365 Developer Program and get a free E5 developer tenant instantly. Sign up and attend a Sharing is Caring event in November-December. 3 new Platform related news items this week. The host of this call was Brian T. Jackett (Microsoft) |@BrianTJackett. Q&A takes place in chat throughout and live at end of 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
x5
platform
community
call
for
november
16th.
I
am
brian
t
jacket
your
host
today.
We've
got
some
great
topics
we'll
be
covering
in
terms
of
our
agenda.
Today,
we'll
cover
a
little
bit
of
the
latest
updates
and
news
on
the
microsoft
365
platform.
We
will
once
again
do
our
picture
time,
so
we
appreciate
everyone
joining
in,
live
to
be
able
to
join
into
our
picture
time,
great
great
great,
to
see
that
working
again
and
we've
got
some
great
demos
will
be
coming
up
today.
A
First
from
loki
talking
about
using
adaptive
cards
inside
of
microsoft
teams,
tabs
and
then
also
wall,
deck
investor
will
join
us
to
be
talking
about
extending
adaptive,
charge,
extensions
inside
of
viva
connections
and
then,
if
there's
time
at
the
end,
we'll
open
things
up
for
q
a.
But
this
will
be
our
agenda
for
today
now,
in
terms
of
being
able
to
get
access
to
resource,
there
are
a
lot
of
different
locations.
You
can
go
into
the
first
things
in
terms
of
videos.
A
We
have
two
different
areas
for
both
the
developers
as
well
as
our
community.
You
can
go
to
aka.ms
mtx5dev
youtube
for
our
developer:
videos,
lots
of
great
content
related
to
microsoft,
365
development,
no
matter
where
you're,
at
what
you're
building
great
content
for
you
to
see,
tutorials
and
getting
started
with
other
information
like
that,
we
also
have
our
community
videos
at
aka
dot.
Ms
m265pmp
videos,
all
of
our
community
calls
and
other
types
of
referential
material.
You
can
find
the
recordings
out
there
in
our
community
videos.
Also.
We
are
an
open
source
platform.
A
We
love
to
get
your
feedback,
your
participation,
your
poll
requests
other
areas
to
join
in
from
the
microsoft
65
developer
platform.
You
can
find
a
number
of
links
on
here
for
github
preferences,
also
samples.
If
you
want
to
be
able
to
get
started
and
see.
What
actually
can
I
do
with
these
different
platforms?
What
can
I
be
able
to
extend
and
kind
of
make
my
little
mark
into
areas?
A
We've
got
a
lot
of
different
samples
available
to
you,
whether
you're,
building
with
teams
with
sharepoint
framework
with
other
areas
of
power
platform
and
so
forth,
so
feel
free.
Take
a
look
at
those
samples,
but
as
always,
if
you
want
to
get
the
one-stop
shop
for
all
of
the
different
areas
in
terms
of
the
community
call
schedules,
the
sample,
links
and
so
forth
feel
free
to
take
a
look
at
aka
dot.
Ms
slash
m65
pmp,
your
one
url
for
all
the
different
resources
that
you
may
need.
A
A
Please
do
sign
up
and
join
in
also,
if
you're
looking
for
ways
to
learn
more
about
the
microsoft
65
platform,
we've
got
a
number
of
different
courses
and
training,
materials
and
modules
and
so
forth
at
aka.ms,
slash,
m365,
slash,
dev,
learn
great
ways
to
be
able
to
plug
in
and
find
out
what
is
new.
What's
the
latest
and
greatest,
these
are
constantly
evolving
and
updating
different
trade
materials.
Now
we
even
have
information
in
here
about
via
connections
so
great
way
to
plug
in
there
and
be
able
to
get
up
and
started.
A
As
I
mentioned
previously,
our
samples
gallery
has
now
over
600
samples
out
there
from
both
microsoft
folks
as
well
as
communities.
So
we
really
appreciate
everyone
who
pitches
in
to
go
and
be
able
to
build
out
more
for
this.
You
can
find
this
at
aka
dot,
ms
slash
m265
samples
and
a
little
easter
egg.
I
even
snuck
in
a
little
adaptive
card
sample
into
our
screenshot
on
here,
so
who
doesn't
love,
internet
cats
and
memes
and
so
forth.
A
B
Thanks,
brian
and
friends,
as
you
know,
sharing
is
caring,
is
here
to
provide
you
some
assistance
in
getting
more
involved
in
the
community.
Now
this
may
mean
that
you
want
to
utilize
the
resources
that
are
available
to
you,
some
of
all
the
amazing
samples
that
we
have
the
adaptive
card
extension
samples
and
spfx
samples.
It
may
be
that
you
want
to
contribute
back,
but
there
are
always
some
hurdles,
such
as.
How
do
I
process
and
submit
a
github
pull
request?
B
How
do
I
get
on
some
of
the
community
calls
to
provide
demos
of
my
work
that
I've
done.
These
are
hands-on,
inclusive,
safe
space
opportunities
that
we're
going
to
walk
you
through
how
to
accomplish
and
take
advantage
of
all
of
these
resources.
They
are
scheduled
monthly.
We've
got
a
little
lighter
schedule
coming
up
for
the
rest
of
the
year,
just
to
take
into
account
vacations
and
holidays,
but
we
have
some
ever
popular
sessions,
one
of
our
newest
power
platform,
samples.
B
We
have
those
both
months
coming
up
this
month
and
next
month,
showing
you
some
amazing
tips
and
tricks
how
you
can
submit
your
power
platform
samples
to
the
gallery.
As
always,
we've
got
our
ever
popular
amas
that
are
coming
up.
One
scheduled
today,
it's
a
little
later
in
the
day.
11
a.m,
pacific
time,
but
there
will
be
the
join
teams
link
available
to
you
directly
at
the
sharing
is
caring
site
so
go
hit
that
smash,
join
teams,
button
and
we'd
love
to
see
you.
B
A
A
We
also
have
rpmp
weekly,
which
is
a
great
way
to
get
into
the
announcements,
various
different
interviews
and
updates
related
to
the
platform
so
great
way
to
see
both
microsoft
folks,
as
well
as
community
members,
be
able
to
provide
into
this.
You
can
find
the
links
on
the
page,
aka.ms
pmpweekly,
for
the
videos,
as
well
as
a
podcast
at
pnpweekly.podbean.com.
A
Now,
in
terms
of
the
news
available
for
our
developer
platform,
got
a
couple
different
items
that
are
on
here.
The
first
one
is
that
we
do
have
a
breaking
change
coming
to
the
online
meetings
api.
This
is
only
for
the
beta,
but
we
do
want
to
make
sure
that
all
of
our
developers
are
kept
up
to
date
on
the
latest.
For
this.
In
the
case
here,
we've
introduced
a
attendance
records
essentially
a
new
resource.
A
It
will
actually
change
it
a
little
bit
in
terms
of
the
property
for
this,
rather
than
being
a
complex
type.
It
is
now
actually
a
navigation
property,
so
there's
more
information
that
you
get
to
go
and
find
out
on
there
if
you'd
like
to
take
a
look
and
see
on
our
blog.
For
this,
we're
also
announcing
a
new
preview
of
the
team's
javascript
sdk,
now
supporting
additional
targets
for
this.
A
If
you're
looking
for
office.com
for
outlook
and
some
other
areas
great
way
to
extend
to
other
campuses
beyond
just
simply
the
team's
platform,
so
please
feel
free
to
take
a
look
at
this
in
terms
of
what's
the
newest
with
this
preview
and
see
what
you
can
do
to
build
that
out
and
then,
lastly,
we
do
have
another
blog
post
again
from
vesa
some
great
information
related
to.
How
can
we
actually
go
and
work
with
adaptive
card
extensions?
A
So
please
take
a
look
at
these
blog
posts,
stay
tuned
to
all
the
various
different
resources
that
we
publish
wanna,
make
sure
that
you
are
as
informed
as
engaged
as
possible
when
working
with
the
platform
and
this
time
we'll
turn
things
over
to
do
our
online
picture
time.
So
feel
free
to
turn
on
your
video
cameras.
C
Absolutely
one
second,
so
let
me
share
my
screen,
so
we
can
start
the
camtasia
I
can
see
we
have
hitting
the
50
limit
pretty
soon
you
can
still.
I
think
we
still
might
have
one
or
two
seats
under
on
the
house.
We
are,
I
think,
they're
fully
booked.
So
let's
do
some
handballing
everybody
thanks
everybody
for
joining
once
again
on
the
weekly
con
community
called
awesome.
This
is
the
people
in
the
house.
Thank
you.
Thank
you.
Thank
you.
C
A
Everyone
we
will
jump
back
to
our
presentation
there
we
go
yep
yep.
I
love
that
feature
be
able
to
jump
right
back
into
the
slide.
That
we
were
at
saves
me
a
whole
bunch
of
scrolling
and
clicking
all
right
with
that.
It
is
time
to
move
into
our
demo
portion
again.
Today
we
have
loki
talking
about
building
adaptive
cards
into
teams
tabs
as
well
as
wall
deck
and
vessel
will
be
rounding
out
things
with
the
we're
going
to
do
the
connections
with
that.
D
C
D
D
Before
we
jump
into
the
feature,
I
want
to
just
quickly
go
over
some
of
the
problems
we're
trying
to
solve,
so
some
developers
say:
building
a
tab
or
a
teams.
Tab
can
be
quite
tricky.
Oftentimes.
The
tab
doesn't
look
and
feel
native
to
the
rest
of
teams.
Also,
some
web
apps
aren't
responsive.
Therefore
they
don't
work
easily.
On
mobile.
D
We
also
frequently
hear
about
slow
load
times.
Sometimes
this
is
because
of
the
fact
that
it's
embedded
in
an
iframe,
but
that
could
also
open
up
a
host
of
other
constraints
depending
on
how
the
web
app
is
built.
Finally,
there
are
usually
a
host
of
other
hidden
maintenance
costs.
This
is
because
some
developers
actually
have
a
fork
of
their
primary
web
app
running
in
teams,
but
other
issues
tend
to
crop
up
too,
such
as
making
accessibility
work
or
just
trying
to
figure
out
azure
active
directory
single
sign-on.
D
Another
benefit
of
using
adaptive
cards
is
that
teams
and
the
adaptive
card
team
are
investing
heavily
in
their
future,
so
take,
for
example,
some
of
these
new
or
coming
soon
ui
features.
This
past
year
we've
launched
support
for
form,
validation
and
the
ability
to
use
a
people
picker
coming
soon,
we'll
also
be
releasing
an
overflow
menu
which
will
make
it
easier
for
you
to
create
drop-down
actions
and
adaptive
cards.
There
have
been
many
improvements
made
over
the
last
year
too.
D
D
Adaptive
cards
to
your
users
and
also
provides
a
much
nicer
way
to
interact
with
your
app
rather
than
via
the
bot
chat
on
the
right
you'll,
see
what
it
looks
like
on
mobile
and
overall
you'll
notice
that
it
just
looks
a
lot
more
native.
This
is
because
adaptive
cards
are
styled
to
look
right
at
home
in
teams
so
before
we
jump
into
the
demo.
I
just
want
to
spend
a
few
minutes
talking
about
some
of
the
architectural
decisions
we
made
along
the
way
and
the
developer
experience.
D
So
this
is
how
most
teams
apps
start.
The
developer
builds
a
bot
because
that's
the
easiest
way
to
get
started
and
with
that
bot,
they're
able
to
power
a
number
of
teams,
capabilities
such
as
chat,
bots,
messaging
extensions
or
even
show
dialogues
called
task
modules.
This
is
all
powered
by
a
bot
back
end
and
a
and
an
adaptive
card
front
end
a
few
months
later,
along
comes
their
manager
and
they
they
ask
them
to
build
a
tab,
because
they've
heard
the
tabs
get
better
engagement
and
they
like
how
they
look
okay.
D
So,
let's
look
at
what
that
looks
like
now.
The
app's
architecture
is
fractured.
The
developer
had
to
spin
up
a
separate
web
server
to
host
their
tab
app
and
they
had
to
build
the
front
end
using
you
know
the
usual
set
of
web
tools.
Perhaps
they
wrote
some
glue
codes
so
that
their
back-ends
can
talk
to
one
another
at
the
end
of
the
day.
Not
only
could
you
not
reuse
your
previous
investments,
but
you're
now
on
the
hook
for
maintaining
two
different
stacks?
D
So
wouldn't
it
be
easier?
If
you
could
do
something
like
this,
I
think
that
looks
much
better.
So
what
if
you
could
power
everything
in
teams
with
a
single
bot
back
end
and
an
adaptive
card
front
end?
So
this
is
the
unified
developer
experience
that
adaptive
card
based
tabs
aims
to
solve.
Now
you
can
reuse
your
previous
investments
and
enable
everything
from
a
chat
bot
to
a
teams
tab.
Let's
talk
quickly
about
just
some
of
the
developer
paradigms
that
you
can
expect
so
adaptive
card
based
tabs
should
be
a
welcome
new
capability
for
bot
developers.
D
When
we
were
thinking
about
how
we
wanted
to
structure
the
developer
experience,
we
looked
at
task
task
modules
for
inspiration,
and
we
did
this
for
two
reasons.
First,
task
modules:
they're
going
to
be
used
quite
heavily
from
your
tab,
so
this
will
just
make
the
development
experience
more
familiar
and
then,
secondly,
task
modules
rely
on
something
called
invoke.
Events,
an
example
invoke
event
is
task
fetch,
so
you
can
extrapolate
task
fetch
to
other
events
like
tab
fetch.
D
D
So
here
are
some
common
task:
module,
invoke
events,
task
fetch
and
task
submit.
If
you
were
to
build
adaptive
card
based
tabs,
you
will
be
using
events
called
tab,
fetch
and
tab
submit
instead,
so
let's
take
a
look
at
the
flow
diagram
in
the
first
section,
the
user
clicks
on
the
app
and
and
teams
sends
a
tab,
fetch
event
to
the
bot.
The
event
basically
says:
hey
bots,
I'm
the
home
tab
and
the
user
is
john
smith.
Can
you
please
return?
D
D
Let's
see
before
I
jump
in
to
the
actual
code,
just
some
housekeeping.
How
did
I
get
here
so,
to
start
with,
I
set
up
a
bot
in
azure,
and
I
just
want
to
spend
a
few
seconds
talking
about
the
configuration
panel
over
here,
you'll
notice,
I'm
running
this
on
ngrok,
just
for
local
development
and
I'll
get
back
to
this
microsoft,
app
id.
I
want
to
jump
into
the
oauth
section,
real,
quick,
how
to
set
up
olaf
here.
You
see
the
same
microsoft
app
id
here.
D
D
Okay,
so
into
the
code
itself,
the
first
change
you're
going
to
notice
is
we
now
allow
you
to
have
a
property
called
content
bot
id
under
your
static
tabs
property.
We
used
to
have
a
well
we
used
to.
We
still
have
a
property
called
content
url
that
renders
a
url
to
the
tab.
But
now
we
allow
you
to
put
a
content
bot
id.
That's
that
microsoft.
D
You
know
app
id
or
client
id
that
I
was
just
showing
you
in
azure
earlier
and
basically,
what
this
says
is
when
I
go
to
this
home
tab
instead
of
rendering
a
url
send
a
message
to
this
this
little
bot
over
here.
So
I'm
going
to
jump
into
that
real
quick.
I
have
the
the
app
running.
This
is
just
what
the
sample
looks
like
out
of
the
box
when
you
get
it
up
and
running,
not
pretty,
but
it's
really
here
for
illustration
and
for
instruction
purposes.
D
So
next
thing
I
want
to
do
is
I'm
going
to
go
back
into
my
project.
Let
me
just
stop
my
little
server
here.
I'm
going
to
go
over
to
the
file
called
adaptive
cards.
You'll
notice,
it's
under
the
server
models.
Folder
in
here
is
a
bunch
of
bunch
of
methods
you
can
find,
but
I'm
really
going
to
be
looking
at
the
create
fetch
response.
This
basically
returns.
The
response
to
the
bot
over
here.
You'll
see
two
cards.
D
D
So
if
you
recall
that's
this
one
up
here,
we
want
to
return
this
little
adaptive
card
over
here.
So
what
I
did
before
this
call
is,
I
went
into
the
adaptive
cards
designer
and
I
went-
and
I
created
this
little
card
over
here
down
over
here-
is
the
json
for
that
card.
I'm
just
gonna
copy
this
and
go
back
into
bs
code,
and
I'm
just
going
to
throw
this
in
here.
D
And
voila
there
you
go.
This
is
my
little
adaptive
card
that
I'm
returning
so
in
this
in
this
case,
what
what
what
I
went
and
did
was,
I
went-
and
I
said
I
wanted
to
add
a
a
new
adaptive
card
on
the
top
of
this
vertically
stacked
list,
so
just
want
to
dig
into
it
a
little
bit
more
into
this
demo.
There's
already
some
descriptive
text
over
here
to
let
you
know
how
you
can
do
some
things
inside
of
the
demo.
I
want
to
just
go
through
task
modules.
D
Task
modules
are
a
great
way
to
complete,
as
the
name
says,
little
tasks
so,
for
example,
this
little
demo
doesn't
do
anything,
but
one
of
the
things
that
it
allows
me
to
do
is
after
I'm
I've
completed
a
task
I
can
redraw
what's
behind
here
now
in
this
demo,
it's
pretty
contrived.
It's
just
going
to
return
one
adaptive
card,
one
little
card,
just
with
a
little
bit
of
some
information
about
what
happened
behind
the
scenes.
But
if
I
wanted
to
you
know
in
this
example,
I
have
favorites.
D
D
So
moving
on
from
that,
I
want
to
jump
back
in
here.
I
want
to
just
talk
about
some
of
the
nuances
with
respect
to
how
you
handle
task
module
dialogues
from
your
tab.
So
the
good
news
is:
is
that
there's
no
change
to
invoking
a
task
module,
but
something
to
keep
in
mind
is
that
when
the
task
module
completes
or
task
submit,
you
will
be
returning
a
set
of
adaptive
cards
to
re-render
to
the
screen.
So
in
order
to
do
this,
you
will
be
nesting.
Your
tab
object
inside
a
task
object.
D
This
is
kind
of
done
for
some
tactical
reasons,
because
the
original
request
was
a
task
fetch.
The
bot
framework
expects
a
response.
Parent
object
to
be
of
type
task,
just
something
to
keep
in
mind.
Alternatively,
you
could
just
return
200,
okay,
close
the
dialog
and
not
redraw
anything
to
the
tab.
Finally,
there
are
some
drawbacks
or
shortcomings.
If
you
will
that
I
want
to
point
out,
you
may
have
noticed
that
I
only
showed
personal
app
tabs,
that's
because
we
don't
yet
support
the
adaptive
card
base
tabs
in
group
settings
such
as
chats
channels
or
meetings.
D
D
Don't
worry
we're
thinking
through
all
of
these
think
of
these
perhaps
less
like
drawbacks
and
more
like
a
roadmap
of
what's
to
come
thanks
everyone
for
sticking
with
me
until
the
end
here
is
a
short
link
to
the
documentation
and
where
you
can
find
the
sample
app.
I
showed
you
during
the
demo,
just
visit
aka
dot,
ms
adaptive
card
tabs.
A
D
Okay,
well
I
mean
you
know
the
usual
ones
like
your.
Your
admin
might
need
you
to
be
able
to.
You
know,
side
load,
applications
for
development
purposes,
but
if
you
spin
up
one
of
the
m365
developer
tenants
and
set
that
up
for
teams
development,
you
should
be
able
to
get
going
out
of
the
box.
There's
no
special
restrictions
that
I'm
aware
of.
A
D
A
C
D
D
D
C
C
Audience
for
sure,
but
now
there
are
ways
of
showing
adaptive
cards
in
in
the
and
using
adapter
cards
in
the
weaver
connections,
which
is
a
bit
of
a
kind
of
a
well
behind
of
the
senses.
Sharepoint
still
so,
there's
a
there's
ways
of
doing
this,
but
it's
not
natively
as
such
in
a
web
part
experience
in
sharepoint
online.
Okay
got
it
thanks.
Visa.
A
D
Yes,
with
some
work,
I
have
seen
some
wizardry
from
the
adaptive
cards
team
themselves.
They
have
been
able
to
create
some
really
awesome
components,
I'm
sure
if
you
want
snooping
on
github
or
you
found
some
of
the
github
projects
from
some
of
the
adaptive
cards
teams,
you
will
most
certainly
find
the
ability
for
there
to
be
tabs.
I've
seen
it.
I
just
know
that
it's
not
something.
That's
like
natively
supported
out
of
the
box.
You
have
to
do
some
adaptive
card
wizardry
to
make
that
work.
D
However,
I
will
say
that
I
have
seen
demos
or
I'd
rather
say
prototypes,
that
some
of
our
other
partners
have
built,
as
they
were
kicking
the
tires
and
they
built
tab
like
interfaces.
So,
for
example,
we
had
one
actually
one
of
our
spfx
partners
build
a
prototype
where
they
had
a
a
list
up
at
the
top
of
there
were
buttons,
but
they
kind
of
behaved
more
like
tabs,
where
you
could
switch
between
different
catalogs.
D
A
D
A
A
C
C
That
the
upstream
is
working
properly
from
my
side,
but
you
can
see
right.
Yes,
so
you'll
talk,
I'll
click,
no
just
perfect
move
your
mouse
to
the
left.
Now
to
the
other
left
exactly
now,
so
me
and
waldek.
We
are
back.
We
have
this
series
of
three
different
modules
as
we
are
going
through
the
viva
connections,
extensibility
model
and
in
the
vivo
connection.
C
We
have
three
different
extensibility
options:
we're
going
to
talk
about
them
in
soon,
but
today
it's
not
about
that
after
card
actually
and
because
that
was
a
week
ago,
that
recording
is
available
and
there
will
be
an
individual
video
on
that
one
relatively
soon
in
the
youtube
channel
as
well.
So
today
we're
going
to
talk
about
the
viva
connection
and
the
web
parts,
and
how
do
you
actually
modify
the
viva
connection
desktop,
but
before
we
go
there?
C
C
Wildlife
did
an
awesome
job
of
creating
this
learning
path
and
it's
one
and
a
half
hours
and
you
understand
basically,
what
are
the
different
options
of
doing
extensibility
in
vivo
connections
and
really
good
exercises
simple
to
do
simple
to
follow,
and
then
you
master
rival,
connection
extensibility
right
after
that
right,
weltec,
exactly
yes,
it's
enough
to
put
it
in
your
cv.
I
know
vivo
connection
now,
but
today
we're
gonna
talk
about
the
vivo
connection
and
how
do
we
extend
the
bigger
connection
with
web
parts
and
what
does
that
mean?
C
C
Just
to
recap,
the
situation
viva
connection
toolkit
is
generally
available.
Real
connection
is
generally
available
as
well,
because
I'm
going
to
show
in
practice
today.
What
does
it
mean?
How
do
you
set
it
up
in
in
briefly
so
you're
up
to
date
on
how
to
move
forward
with
this,
but
basically,
as
I
said,
we're
using
a
sharepoint
framework
1.13
as
to
tooling
and
the
toolkit
to
create
viva
connection
extensibility
in
this
case
again
we're
going
to
create
a
web
part
which
is
for
extending
the
desktop
and
the
experiences.
C
C
Just
to
recap
again
on
the
viva
connection,
extensibility
options
that
there
are
three
different
extensibility
options
which
are
going
through
within
this
learning
path
as
well.
So
you
can
create
web
parts
and
web
parts
are
basically,
they
are
configurable
by
the
editors
who
are
designing
the
viva
connection
desktop
experience,
so
they
can
modify
the
properties
and
how
the
how
the
behavior
is
being
done.
There's
the
application
customizers,
which
are
being
exposed
in
every
single
page
in
the
vivo
connection.
C
So
you
can
use
them
to
embed,
for
example,
headers
and
footers
in
the
page
and
then
there's
the
adaptive
card,
extensions,
which
is
mainly
for
the
mobile
experience.
But
they
do
have
actually
desktop
experience
as
well.
I'm
gonna
see
that
in
a
bit
as
well,
but
it's
it's
basically
the
mobile
vivo
connection,
mobile
experience,
that's
when
we
use
adaptive
cards
and
again
just
to
recap
today
we're
going
to
focus
on
web
parts,
not
adapted
card
extensions.
C
We
focused
on
that
one
last
week
and
next
week
we're
going
to
focus
on
application,
customizers
and
then
we're
going
to
move
to
another
learning
path
in
a
completely
different
topics,
but
we
want
to
actually
go
through
this
awesome
material
for
everybody
to
benefit
as
well.
I
can,
by
the
way,
the
questions
as
they
come
on
the
chat,
so
I
will
try
to
follow
up
on
them.
If
there's
any
and
wallet
is
going
to
jump
on
things
as
needed
as
well,
right,
waldek,
definitely
absolutely.
A
C
As
a
principal
program
manager
you're
not
expected
to
write
any
code
anymore,
so
now
learning
objective
of
today,
I'm
going
to
talk
about
a
bit
on
the
development
tooling
how
to
get
started
on
that.
You
might
be
super
familiar
on
that
already
and
we're
going
to
talk
about
how
do
we
extend
microsoft,
vivo
connection
with
web
parts
and
and
deploy
the
test
custom
web
parts
in
microsoft
connection?
So
how
do
we
actually
deploy
those
to
be
available
just
to
understand
the
basics,
how
this
is
actually
being
done?
C
If
you
are
coming
from
a
if
you
build
stuff
for
modern
sharepoint
online,
you
might
be
familiar
with
these
things
already,
but
again
it's
the
same,
familiar
extensibility
model
which
is
available
for
real
connection
in
certain
level,
and
now
we
need
to
point
out
that
the
guy
in
the
second
row
is
doubtful.
So
he's
clearly
not
convinced,
so
I
don't
think
we
actually
have
the
the
slide
where
he
is
convinced
in
the
end.
C
But
let's
see
now,
as
we
have
then
enabled
viva
connection,
and
then
we
want
to
have
the
end
users
or
the
editors
to
be
able
to,
for
example,
surface
internal
data
from
internal
systems
to
the
employees
directly
into
viva
connection
desktop
or
we
want
to
do.
We
want
to
surface
or
aggregate
information
or
we
want
to,
let's
say,
inform
people
in
using
our
custom
logic.
That's
when
we
are
going
to
build
a
reusable
widget
which
is
going
to
show,
in
this
case
a
company
announcements,
the
content
editors
can
play
well.
C
In
our
case,
we're
going
to
put
it
on
the
vr
desktop
welcome
page
and
we're
going
to
talk
about
what
is
basically
the
experience
there
and
and
how
do
you
modify
the
vivo
connection
experiences
as
well?
Now?
How
do
we
get
started?
We're
not
going
to
do
all
of
this.
I'm
going
to
walk
this
through
as
we're
waiting
for
yeoman
generator
to
walk
through.
So
I'm
going
to
show
you
my
setup
so
you're
up
to
date
on.
What's
happening
here,
but
basically
what
we
need
to
do
is
enable
the
vivo
connection.
C
There
is
a
really
good
documentation
how
to
do
this,
actually
in
the
learning
path
as
well.
So
the
learning
path
actually
goes
through
all
of
the
needed
steps.
The
only
a
big
challenge
there,
just
a
vertical
warning-
is
that
as
you
go
through
and
enable
the
viva
connection
and
a
home
site
in
your
tenants
and
then
surfacing
that
eventually,
microsoft
teams
through
the
viva
connection-
and
there
are
caching
situations
and
there
are
some
timelines.
C
So
there
are
server-side
things
which
we
need
to
get
executed
so
every
now,
and
then
there
might
be
a
30-minute
delay
for
something
to
actually
enable-
and
it's
a
bit
frustrating
so
to
say,
but
it's
a
one-time
configuration
per
tenant.
So
that's
why
it's
it's
not
something!
What
we
for
now
at
least,
have
designed
to
be
immediate
because
again,
making
it
immediate,
as
a
one-time
configuration
in
a
tenant,
wasn't
a
justified
cost
so
and
then
we're
going
to
install
sharepoint
framework.
C
And
the
key
point
here
is
that
you
have
full
flexibility
on
designing
whatever
kind
of
experience
you
want,
so
you
can
add
any
web
parts,
you
can
add
additional
web
parts
and
it's
all
flexible
for
you
to
design
we
as
a
microsoft.
We
don't
lock
down
this
experience.
So
if
you're
a
partner,
you
can
basically
design
different
set
of
offerings
on
top
of
the
viva
connection
with
different
set
of
web
parts
and
experiences,
and
that's
one
way
of
approaching:
how
do
we
do
these
things,
which
is
really
really
cool?
C
Web
parts
can
have
content
editors.
You
can
configure
that
you
can
modify
that
you
can
modify
the
web
part
properties
and
on
the
on
the
right
side.
Web
part
always
have
customizable
properties,
well,
not
necessarily
that,
but
they
can
have
customizable
properties.
In
our
case,
for
example,
today
we're
going
to
lock
down
the
information
you
own,
the
html
and
css
of
the
web
part
this
web
widget.
So
you
can
do
whatever
you
want
inside
of
that
chrome
inside
of
the
html
structure
and
including
using
adaptive
cards,
to
render
you.
C
Using
adaptive
cards,
you
can
actually
do
that
as
well.
That
is
true,
yes
and,
of
course,
it's
a
good
idea
to
build
a
responsive,
ui
in
mind
just
to
avoid
any
surprises
over
there
and
also
the
web
parts,
including
in
the
viva
connection
or
in
a
sharepoint
domain.
They
can
be
connected
between
each
other,
so
you
can
build
this
connected
experiences,
which
is
really
really
cool
as
well.
C
Now,
as
a
rule
of
thumb,
we
recommend
building
web
parts.
If
you
need
an
extended,
vivo
connection,
desktop
experience
and
you
want
to
let
content
editors
decide.
What
do
you
want
to
put
on
a
page?
So
you
basically
have
this
then
configurable
option
to
add
on
a
page
or
remove
from
a
page,
and
all
of
that,
so
that's
kind
of
the
rule
of
a
thumb
for
when
the
web
part
is
the
right
option
and
let's
actually
jump
into
the
writing
of
the
code.
C
A
C
That's
good
point,
so
there
we
go
so
we're
listing.
Basically
what
has
been
installed
in
my
computer.
Currently,
I'm
just
going
to
pinpoint
the
right
solution
which
have
been
installed
whenever
the
nbm
is
so
I
have
a
title
yeah
you
need
single
equals
there
we
go.
Thank
you.
Thank
you.
That's
why
you
are
helping
me
on
making
this
happen.
C
C
You
write
in
typescript,
you
install
stuff
from
npm
or
yarn
and
and
typical
web
development,
no
sharepoint
essence
or
v-buck
on
every
connection
isn't
needed
so
to
say,
and
what
we're
going
to
do
here
is
that
we're
going
to
run
the
microsoft
sharepoint
geometry
generator
and
I'm
going
to
follow
up
on
the
guidance
what
we
have
which
we
provided
in
as
a
documentation
and
I'm
going
to
copy
just
the
information.
It's
it's
not
really
writing
code,
as
I'm
copying
the
information
directly
from
the
exercise,
but
still
we're
going
to
target
sharepoint
online.
C
And
as
it
shows
company
announcements,
so
the
descriptions
are
visible
as
the
end
user
is
selecting
the
web
part
and,
and
it
is
using
no
javascript
framework,
and
that
starts
now
the
solution
creation,
as
we're
doing
that,
let
me
show
you
what
we
have
available
in
our
test
environment.
So,
first
of
all,
we
already
have
our
homepage
or
a
home
site
said
a
setup
in
the
tenant.
C
C
Now
and
then
we
then
we
then
we
enabled
that
solution
to
be
available
based
on
the
company
policy
settings,
and
this
is
basically
making
sure
that
whenever
somebody
accesses
microsoft
teams,
they
have
a
certain
set
of
solutions
available
in
the
team's
left
navigation.
It
is
a
really
nice
way
of
defining
a
consistent
experience
across
the
company.
You
can,
by
the
way,
create
multiple
policies,
so
you
can
have
multiple.
C
C
We
can
see
that
the
contoso
application
is
available
in
here,
and
this
is
the
vivo
connection.
So
we
basically
are
surfacing
our
home
site
in
here
and
if
I
click
for
example
in
here,
we
can
see
the
latest
news
and
all
of
that
information
global
navigation
available
directly
within
the
microsoft
team.
So
we
are
in
the
context
of
the
work.
We
don't
have
to
move
anywhere
else
from
here
and
that's
really
the
objective.
What
we're
going
to
do
with
we
have
a
connection
as
well
and
by
the
way,
it's
just
a
note.
C
If
you're
looking
into
doing
a
cool
demos,
you
can
really
easily
use
the
loopbook.microsoft.com
which
we
didn't
use
in
this
case
and
for
example,
I
used
the
perspective
or
one
of
these
designs
and
then
enable
the
viva
connection
in
them.
So
that
way
you
get
a
really
nice
experience
and
a
cool
looking
site,
and
example,
content
and
all
of
that
available
from
demo
purposes
good.
I
got
a
thumbs
up
from
the
valdec.
That's
always
a
good
sign.
So
let
me
now
go
do
the
actual
code,
so
the
scaffolding
has
ended.
C
So
it's
it's
a
simple
scenario
in
this
case,
so
a
content
editor
can
we
can
create
announcements
which
can
be
also
important
and
we're
gonna
render
those
as
part
of
this
web
part
so
relatively
simple
thing,
but
it
really
shows
the
power
of
using
again
typescript
and
the
flexibility.
What
we
have
using
the
web
stack
tooling
as
well.
C
So
let's
go
back
in
here.
We
have
a
baseline
structure
available.
What
I'm
going
to
do
here
is
that
I'm
going
to
add
an
sp
http
reference,
so
this
is
an
easiest
package
and
library
to
use
to
access
information
in
sharepoint.
It's
going
to
do
all
of
the
access
token
handling
and
that
classic
challenge
said.
Where
do
I
get
the
token
you
just
hit
the
api
with
the
token?
Where
do
I
get
the
token?
C
Well,
luckily,
this
this
fellow
is
taking
care
of
all
of
that
for
you,
so
it's
a
really
seamless
single
sign-on
accessing
to
apis
and
and
then
what
we're
going
to
do
is
that
we're
going
to
update
the
render
method.
So
in
this
case,
there's
the
render
method,
I'm
going
to
get
rid
of
the
example
default,
and
I'm
going
to
update
that
a
bit
I'm
going
to
intend
that
a
bit,
because
otherwise
that's
getting
annoying.
C
I
can't
help
it
if
the
indentation
is
not
correct,
it
hurts
eyes
so
actually
close
down.
So
having
a
look
on
here,
what
we're
doing
quickly
we're
hitting
a
api
ship
and
in
this
case
sharepoint
rest
api.
Of
course,
you
can
absolutely,
and
you
should
be
using
microsoft
graph
apis
as
well
for
getting
some
of
the
information.
It
really
depends
again.
What
kind
of
information
you're
surfacing
graph
is
absolutely
brilliant
in
this
case
we're
just
using
the
simple
rest
apis
from
sharepoint
from
the
announcement
list.
C
We
are
getting
title
description
and
importer,
that's
our
objective
and
then
there
are
the
display
results.
Selection,
that's
what's
happening
here,
so
I'm
gonna
actually,
then
take
the
display
results,
I'm
going
to
paste
in
the
needed
code
in
there
and
the
intenders
and
well
it's
there,
but
basically
what's
happening
here
is
that
we
are
getting
those
individual
announcements
and
we're
rendering
them
in
the
right
format
depending
on
is
the
important
set
or
not
so
there's
going
to
be
a
bit
different
rendering.
C
D
C
C
We
can
see
that
there's
no
painting
cases
I'm
going
to
go
back
in
the
comment
line.
I'm
going
to
do
gallop
serve
just
as
no
browser,
and
this
basically
means
that
I'm
running
the
local
host
to
web
service-
and
I
want
to
test
out
this
web
part
in
my
tenant.
So
we
want
to
check
it
out.
That
is
it
actually
working
is
the
code
working.
C
We
would
be
able
to
do
debugging
as
well
optionally
and
we're
going
to
skip
that
today
from
a
timing
perspective,
but
this
is
really
to
make
sure
that
we
are
serving
the
code
still
from
localhost
and
double
checking
that
everything
is
working
fine.
So
let
me
go
in
here.
Let
me
go
to
the
home
of
the
site
and
we
kind
of
use
the
online
workbench
online
workbench
if
you're
familiar
with
this
there's
nothing
new
in
here,
but
you
basically
go
to
a
underscore
layout
15workbench.aspx
a
bit
of
a
complex
thing.
C
If
you're
not
familiar
with
this
stuff.
How
would
I
know
that
it's
there,
and
maybe
we
should
have
a
easier
way
to
get
there
from
a
developer
perspective,
but
again
future
improvements
in
here
as
time
running
the
local
workbench
sharepoint
online
is
smart
enough
to
understand
hey,
you
actually
have
things
available
from
your
local
workbench
and
we
can
see
the
important
analysis
and
web
part
to
be
available
and
it
shows
important.
D
A
C
C
We
created
a
web
part
and
we
created
a
web
part
which
is
running
from
local,
which
is
actually
pretty
nice
that
it's
actually
telling
me
that
it's
running
from
local
host,
it's
not
running
in
the
tenant,
and
I
can
select
the
company
announcement
and
then
there's
our
company
announcement.
It's
actually
working.
So
this
means
that
it's
we
basically
copy
it
to
code.
I
was
able
to
copy
the
code
which
wildex
provided
for
me
in
a
correct
way.
I
can
actually
do
that.
C
It's
working
and
that
the
information
which
we're
basically
seeing
here,
just
to
recap
that
one
is
coming
from
the
announcement
list
that
was
in
the
code
as
well,
so
we
were
accessing
the
announcement
list,
basically
showing
complete
mandatory
training
and
that's
important
and
holiday
season
company
announcement,
and
then
that
was
the
text.
If
I
go
back
in
here,
we
can
see
that
the
information
is
matching
or
from
that
list,
that's
really
cool.
That
was
super
easy
that
wasn't
too
hard
at
all,
at
least
when
you're,
following
up
on
the
tutorial
right.
So.
C
And
then
you
learn,
that's
always
the
thing
you
learn
by
doing
that.
That's,
though,
always
true,
so
for
sure,
so
I'm
going
to
close
up
and
the
debucker.
So
just
closing
up
that
one
and
then,
as
we
are,
we
already
confirmed
that
our
absolutely
awesome
functionality
is
is
functioning.
We
can
already
pocket
package
this
and
get
it
up
and
running
in
the
diva
connection.
C
So
let's
go
call
a
bundle,
bundle,
that's
the
ship,
so
that's
going
to
prepare
our
javascript
files,
typescript
files,
trans
compile
to
be
javascript
and
prepare
them
to
get
packaged
to
get
deployed
by
the
way.
There's
good
comments
on
the
chats
related
from
carl
surf
to
jason
in
a
config
folder.
There's
there's
multiple
options:
how
to
do
these
things?
We've
got
kind
of
a
taking
the
simple
route
right
right
now,
showing
this
in
a
partly
manual
way
as
well.
There
are
more,
let's
say,
sophisticated
ways
of
doing
things
as
well.
C
Thank
you,
carl
on
pointing
out
that
one
and
then
what
I'm
going
to
do
is
then
I'm
going
to
do
call
package
dash
packets
solution
and
that's
the
ship
as
well,
and
this
is
going
to
basically
create
me
the
solution
file,
and
this
is
where
sharepoint
framework
really
shines.
We're
not
going
to
deploy
and
viva
connection.
Extensibility
really
shines:
we're
not
going
to
require
to
be
deployed
our
assets
to
a
website
or
web
in
a
web
application
in
azure
or
aws
or
somewhere
else.
C
We
actually
host
all
of
the
stuff
automatically
for
you
no
costs,
no,
nothing.
It's
just
magically
hosted
and
it
works
without
any
additional
cost
or
complexity
and
operational
or
maintenance
problems
with
that.
So
what
I'm
gonna
do
now
is
that
I'm
gonna
actually
open
up
my
file
system.
We
created
the
package,
it's
pretty
small
from
font
perspective,
but
let
me
actually
extend
that
one.
C
This
there
is
our
spkh
file,
which
is
actually
a
zip
file,
but
it's
more
fancy
to
say
that
it's
an
svp
hd
file
than
a
zip
file,
and
it
actually
contains
all
of
the
assets,
so
javascript
files
images
all
of
that
stuff.
Inside
of
it
so
now
I
can
send
this
to
either
with
email
or
I
can
sell
it
for
somebody
and
for
godzillion
or
millions
millions,
and
then
I
will
retire
for
the
rest
of
the
rest
of
my
career.
C
Well,
not
necessarily
that's
relatively
simple
weapon,
but
it's
a
contained
solution,
and
now
I
can
install
this
to
be
available
in
my
tenure.
So
let's
actually
do
that.
Let
me
go
to
the
app
catalog
which,
by
the
way,
looks
insanely
ugly,
ship
and
app.
Catalogs
is
one
of
those
things
which
are
being
worked
on
to
have
a
modernized,
look
and
feel
it's
pretty
outdated.
But
it's
an
administrative
experience.
C
So
it's
not
a
massive
deal
as
such
and
I'm
going
to
try
and
drop
that
solution
to
be
available
so
and
there
we
go,
and
it's
going
to
ask
me
that.
Do
you
trust
the
solution,
because
it's
running
in
the
browser
with
the
permissions
of
the
user,
I'm
going
to
install
that
to
be
available
in
a
tenant
and
there
we
go.
It
is
now
deployed
it's
not
tenant
deployed
and
no
errors
were
looking
good.
So
we
can
actually
start
using
this
in
that
particular
site.
C
That's
pretty
cool,
so
we're
now
ready
to
go
as
we
installed
this
in
it
actually
extracted
the
package.
It's
booted
automatically
to
be
hosted
in
a
tenant,
and
now
we
can
actually
start
using
that
again
without
the
local
host
servers
or
without
local
host
being
running.
So
now,
there's
no
more
longer
dependencies
on
the
developer
box.
At
this
point.
A
C
By
the
way.
If
somebody
wants
to
buy
this
for
a
million
dollar,
I
we're
willing
to
sell
it's
wildex.
Well,
that
has
the
rights
on
them.
So
I'm
gonna
add
the
web
part
in
and
if
I
scroll
down
now
it's
not
in
the
local
anymore.
It's
actually
in
a
bit
different
experience.
It's
in
the
advanced
we
didn't
set
icon
for
it.
We
didn't
modify
any
of
the
other
settings,
but
we
can
see
the
company
announcement.
C
If
I
put
it
in
here,
there's
our
company
company
announcements,
awesome
brilliant,
looking
web
for
it
and
I'm
gonna
bump
this
this
in
the
sharepoint
online,
and
here
where
it
actually
gets
interesting
with
the
vivo
connection.
So
now,
if
I
go
here
and
if
I
refresh
the
experience
in
the
microsoft
teams,
where
we
have
the
viva
connection
application
running,
we
can
actually
see
that
it
is,
of
course
reflecting
all
of
the
changes
in
here
as
well.
So
we
can
see
the
web
part
available
here
and
that's
how
we
create
web
parts.
A
C
You
follow
the
manual
yes
to
be
fair.
I
think
I
failed
even
on
following
up
on
some
of
that
stuff.
So
from
a
timely
perspective,
I'm
going
to
make
it
one
more
minute
and
then
prank
and
take
us
home,
but
basically
you
might
be
familiar
with
weaver
connection
and
how
do
we
extend
the
video
connection
desktop
with
with
the
sharepoint
framework,
and
we
are
heading
to
a
direction
where
again,
sharepoint
framework
is
going
to
be
renamed.
We
talk
about
level
connection
and
viva
more
from
a
branding
perspective,
but
tech
underlying
technology
is
still
typescript.
C
Web
stack
development,
all
of
that
stuff
and
the
web
part
is
the
one
way
of
extending
viva
connection
on
top
of
the
adaptive
card
and
application
customizer.
So
we're
going
to
do
the
application
customizers
then
next
week,
and
I
think
that's
pretty
much
it
for
for
us
today.
So
brian
you
can
take
us
home
and
close
the
call.
A
Excellent,
let
me
present
back
our
deck
and
we'll
wrap
things
up
here
today.
Thank
you,
vessa.
Thank
you
valdec
for
some
awesome
information
related
to
viva
connections,
all
right
so
wrapping
up
today's
microsoft,
65
platform
community
call,
if
you
are
interested
in
any
other
community,
calls
that
are
out
there.
We
do
have
a
couple
of
ones
related
to
adaptive
cards,
identity
to
office,
powerapps
and
so
forth.
A
You
can
find
the
links
on
the
page
on
here
or
you
can
go
to
our
one
stop
shop
once
again:
aka
that
must
slash
m65
pnp
and
as
always,
these
calls
are
going
to
be
recorded.
You
can
find
them
on
our
microsoft.
65
community
pmp
youtube
channel,
aka
dot.
Ms
slash
m365
m365pmp,
slash
videos
we'll
have
that
available
in
the
short
frame.
Please
do
follow
along
with
us
on
our
various
twitter
handles.
You
can
find
us
at
microsoft365,
dev
or
at
m365pnb.
A
Our
next
session
will
be
next
week
november,
23rd
at
our
normal
time,
8am
pacific,
utc,
minus
eight.
So
thank
you
so
much
for
joining
in
today.
Great
crowd,
great
interactions,
really
love
all
the
commentary,
questions
and
so
forth.
Look
forward
to
seeing
you
next
week
and
have
a
great
day
thank
you.