►
Description
In this 26-minute developer focused demo, Luca Bandinelli introduces viewers to the 36-member Team focused on the evolution of SPFx. Then he quickly reviews what’s available in SPFx v1.16 and deep dives into what may be shipped in v1.17, i.e., Adaptive Cards v1.5 schema support for Viva ACE Cards, bump to Teams manifest v1.13 and more, more. Hear about aspirations beyond v.1.17 like Bot driven ACEs, notifications in Viva Connections, move Cache APIs to GA and still more!
This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on January 24, 2023.
Demo Presenter
• Luca Bandinelli (Microsoft) | @BandinelliLuca
Learn more
• 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 - http://aka.ms/m365/community
👋 Join to our weekly Microsoft 365 & Power Platform Community calls to learn more. These are PUBLIC calls for you to get access on the latest details from Microsoft and to see awesome demos from community on these technologies - Download recurrent invites from https://aka.ms/community/calls
A
B
Sharepoint
development
framework
we
built
this
little
thing
called
the
SharePoint
framework
that
has
been
very
much
successful
thanks
to
every
one
of
you
guys.
Thank
you.
Thank
you
very
much,
and
basically,
with
SharePoint
framework
just
to
provide
a
little
recap
is:
is
the
platform
and
the
developer
framework
that
you
can
use
in
order
to
build
solution
for
Microsoft,
365,
canvases
and
hosting
this
solution
in
Microsoft
365
SharePoint
online.
B
So
in
terms
of
Viva
connection.
With
extensibility,
if
you
haven't
seen
what
Viva
connection
is,
this
is
what
it
looks
like
today.
The
majority
of
people
are
experiencing
the
left
version
of
Weaver
connections,
which
is
the
one
that
is
available
everywhere.
There
is
a
mobile
experience
that
is
a
native
experience
built
on
top
of
Microsoft
teams,
and
there
is
a
solution
that
will
show
up
in
teams,
as
well
as
SharePoint
pages
in
your
home
site,
where
you
can
basically
have
cards
feeds
and
everything
that
is
important
for
you
to
access
during
your
daily
work.
B
We
are
also
releasing
a
new
version
of
river
connections,
which
is
the
one
that
you
see
on
the
left.
This
is
right
now
rolling
for
first
release,
targeted
release,
customers
and
the
more
we
are
progressing,
the
more
that
the
experience
would
change
from
the
one
on
the
right
to
the
one
to
the
left.
The
one
to
the
left
is
a
little
bit
more
railed.
B
It
requires
less
configuration
steps
in
order
to
have
that
available,
but
it
basically
use
the
same
technology
and
capabilities
that
the
other
one,
which
means
that
if
you
already
invested
on
your
cards,
if
you
build
your
cars
using
SharePoint
framework
and
adaptive
card
extensions,
you
will
be
able
basically
to
use
everything,
and
there
is
nothing
that
you
have
to
change
or
you
have
to
update
in
the
cards
and
in
your
projects
themselves.
A
couple
of
other
things
important
to
mention
here.
B
B
That
should
provide
more
consistency
and,
most
importantly,
it
will
provide
a
better
and
a
faster
way
for
us
to
align,
fixes
and
capabilities
and
new
functionalities
across
multiple
platforms,
mobile
and
desktop
and
web
vesa,
as
you
noticed
before,
I'm,
not
able
to
see
any
comments,
I'm
not
able
to
see
any
hands
raising
something
like
that.
Please
please,
please!
If
there
is.
B
Yeah,
thank
you
so
much.
Okay.
So
here's
the
theme,
there's
a
big
team
actually,
and
but
all
these
people
are
in
charge
of
many
things.
We
have
SharePoint
framework.
We
have
Vivo
connection
sensibility
platform.
This
is
the
team
on
the
left
that
is
lead
by
John.
Those
are
all
the
engineers
that
are
writing
the
code
that
are
making
things
real.
The
one
on
the
middle
is
add.
B
All
the
PMS
here
are
also
in
charge
of
Viva
connections
and
other
platform
capabilities,
just
like
Microsoft
graph
support
in
SharePoint
other
kind
of
areas
like
notifications,
the
the
fields
in
Viva
connections,
some
country
mechanisms
based
on
OneDrive,
sync,
etc,
etc.
Those
are
the
PMS
over
there
and
then
the
theme
on
the
right
is
the
teams
in
China
that
they
have
been
in
engaging
with
us
for
providing
enhancement
and
future
capabilities
on
the
app
catalog.
B
They
are
the
one
that
built
the
new
app
catalog
experience
as
well
as
store
integration,
and
then
we
have
path
which
is
our
principal
software
architect.
That
is
ensuring
that
everyone
is
not
screwing
up
things
and
when
we
screw
up,
he
tells
us
nicely
that
we
screwed
up
things.
That's
the
theme,
it's
a
big
team,
but
we
are
in
charge
of
a
lot
of
things
and
that's
why
you
can
see
so
many
names
over
here.
Okay,
so
let's
talk
about
what
we
have
and
what
we
will
have.
B
B
If
our
direction
is
the
right
one
and
to
be
able
to
react
on
things
that
are
not
working
quite
right,
the
next
three
slides
are
the
one
that
I
want
to
spend
a
little
bit
of
more
time
and
the
next
three
slides
are
basically
focusing
on
a
couple
of
things.
So
the
next
slide,
which
is
this
one,
is
going
to
is
focusing
on
116..
This
is
what
we
think
to
have
in
116.
B
A
couple
of
things
to
mentioned.
So
one
is
that
for
sure
we
want
to
bump
our
dependencies
to
the
latest
and
greatest
team
JS
SDK.
We
want
to
put
at
least
it's
1.7.
That's
why
there
is
a
plus
over
there.
If
there
is
something
better,
we
will
go
with
there.
We
want
to
go
to
webpack
Five
support.
This
is
aspirational,
but
we
really
want
to
do
that.
We
are
going
to
move
to
the
schema
version
1.5
of
adaptive
cards.
B
This
will
give
you
the
ability
to
do
things
like
table
support
in
quick
view
for
the
adaptive
card.
Extensions
in
River
connections-
and
the
other
thing
that
we
want
to
do
here
is
that
we
want
to
bump
the
team's
manifest
to
1.13
when
you
sync
the
teams,
so
that
they
manifest
the
team's
manifest
version.
Sorry
to
113,
when
you
create
a
solution
using
SharePoint
framework,
deploy
that
in
the
Mac
in
the
SharePoint,
app
catalog
and
click
to
sync
themes
that
will
give
the
capability
of
that
solution
to
also
surface
in
Outlook
and
office.com.
B
That's
a
capability
that
we
ship
it
as
a
better
version
in
116,
but
we
didn't
do
the
proper
wiring
to
our
thing
to
them
feature
that
is
happening
in
117..
That
and
the
other
thing
that
is
important.
We
want
to
GA
the
web
part
top
action
that
was
shipped
as
beta
in
160..
Another
important
thing
that
I
want
to
mention
here
is
that
we
are
going
to
ship
a
feature
to
support
pop-up
pop-up
for
token
acquisition
in
browser,
so
spending
a
couple
of
seconds
on
that
one.
B
You
know
that
when
you
basically
create
this
SharePoint
solutions
that
SharePoint
solution
surface
in
a
browser,
we
leverage
the
functionality
of
the
msal
V1
in
order
to
acquire
a
token
from
ad
and
give
the
token
to
your
code
so
that
your
code
can
call
your
favorite
API
Microsoft
graph
or
whatever.
It
is
right.
B
Now
there
is
a
logic
in
the
code
that
where
we
get
an
error
from
the
library
that
the
browser
is
not
allowing
cookies
or
is
basically
having
some
problem
in
receiving
the
token
because
it's
not
able
to
properly
open
the
iframe
or
the
iframe
that
opens
is
not
able
to
authenticate
properly.
You
have
Safari,
you
have
ITP
that's
standard
scenario.
Our
libraries
automatically
go
and
does
a
full
page
redirected
so
that
the
token
gets
acquired
in
the
full
in
the
in
the
Mainframe.
Msal
doesn't
open
an
iframe
and
your
code
works.
B
That's
interesting,
fine
and
then
the
and
the
cool,
because
it's
all
automatic,
if
you
have
one
or
few
API
access.
But
if
you
are
going
to
access
different
kind
of
apis
and
you
need
different
Scopes
you're,
basically
having
a
lot
of
refreshes
in
your
screen,
because
every
time
you
get
for
a
new
token-
and
you
don't
have
the
cookie
for
log
into
Microsoft
online.com,
we
automatically
refresh
the
page,
and
then
you
see
a
lot
of
flickering.
B
There
is
a
feature
that
will
shift
hope,
pulling
117,
where
the
admin
using
a
Powershell
will
be
able
to
set
a
property
in
the
tenancy
that
basically
will
tell
our
library
to
rely
on
pop-up
instead.
So
the
scenario
is
that,
if
you
are
a
lot
of
browsers
that
have
a
lot
of
unmanaged
clients
that
have
Safari
and
ITP
enabled
you
can
enable
this
capability
so
that,
instead
of
flickering
the
the
moment,
we
try
to
access
KD
to
get
a
token,
and
we
get
an
error.
B
We
instead
of
automatically
refreshing,
we
will
open
a
pop-up
and
then
you
in
that
pop-up
you
will
be
able
to
re-authenticate
or
you
will
be
able
to
be
a
very
solid
pop-up.
If
you
have
single
synonym
and
at
that
point,
that
will
be
the
only
time
you
see
the
pop-up
for
the
session
and
you
will
be
able
to
acquire
all
the
tokens
from
there.
So
that's
capability
that
is
off
by
default
and
the
admin
will
be
able
to
enable
starting
from
117
using
a
SharePoint
online
Powershell.
B
B
We
are
going
working
very,
very
hard
to
be
able
to
ship
that
as
soon
as
possible,
it
really
doesn't
have
any
dependencies
on
SharePoint
framework,
meaning
that
we
will
release
no
update
in
the
SharePoint
framework,
SDK
or
libraries
in
order
to
be
able
to
create
a
bot
driven
Aces,
it's
all
server
side,
so
it
really
is
not
mounted
to
any
kind
of
a
SharePoint
framework
releases.
But
this
is
happening
and
we
hope
to
ship
that
quite
soon
we.
B
You
yes
yeah!
Thank
you!
So
it's
interesting
because
also
with
all
of
these
new
hyphen
Vibes
on
Bots
and
AI
you're,
just
like
oh,
you
are
going
to
build
a
feature
that
you
are
going
to
ask
a
robot
to
build
the
card
and
the
card
will
magically
build
by
itself.
No,
it's
not
that
so.
Botriven
Asus
is
basically
using
the
same
approach
that
teams
use
for
bots
in
order
to
build
adaptive
card
tabs.
B
So
the
idea
is
that
you
can
reuse
your
existing
bot
that
you
built
for
max
of
teams
or
build
a
new
bot
using
whatever
language
you
want.
C-Sharp
Java,
you
name
it,
and
basically
we
will
use
the
bot
infrastructure
to
store
your
code
and
the
adaptive
card,
the
code
that
will
basically
talk
to
the
bot
and
say
Hey
I
want
you
to
give
me
data
so
that
I
can
render
a
card
View
or
hey.
This
is
an
action
that
happened.
Give
me
the
data
to
render
the
quick
view.
B
So
the
idea
is
to
basically
to
use
the
bot
infrastructure
that
Microsoft
has
in
order
to
execute
your
code
that
will
generate
card
View
and
generate
quick
view.
So
that's
what
it
is
has
nothing
to
do
with
artificial
Intel.
Intelligences
has
nothing
to
do
with
natural
language.
It's
more
a
way
for
leverage
and
infrastructure
in
order
to
be
able
to
oste
your
code,
which
will
be
a
new
bot
to
power
and
generate
cards
views
in
quick
view.
Does
it
make
sense,
yeah
I'll.
Take
that
as
a
yes,
okay,
cool?
Thank
you.
B
So
then.
The
other
thing
that
we
want
to
do
is
for
sure
move.
Cache
API
through
ga.
One
of
the
things
that
we're
working
on
is
building
a
notification
platform
for
Viva
connections,
so
that
you
will
be
able
to
generate
a
notification
that
will
surface
in
the
Microsoft
team
notification
infrastructure
and
upon
clicking
this
notification,
you
will
be
able
to
interact
with
your
card
interact
with
your
quick
view,
interact
with
your
solution
from
the
notification
itself,
Viva
Home
experience.
B
The
reason
why
it's
there
is
because,
as
I
mentioned
before
is
yes
already
shifted
to
some
tenants
that
are
in
targeted
release,
but
it's
not
around
the
100
deployed
worldwide.
So
that's
one
of
the
other
things
that
is
happening
as
we
speak.
We
also
want
to
have
a
better
support
for
home
site
in
Viva
connections
mobile.
So
that's
an
interesting
thing.
B
What
do
we
want
to
do
here
is
that
we
want
to
be
able
to
have
a
similar
experience
that
the
new
Viva
Home
users
have
in
the
desktop
in
the
mobile
itself,
and
what
I
mean
by
that
is
that
we
will
be
able
to
give
you
the
opportunity
to
reach
your
home
site,
your
SharePoint
home
site
and
host
that
SharePoint
home
site
browser
experience
within
vivacondaction
mobile
from
viva
connection
dashboard
itself,
so
aligning
the
experiences
between
the
desktop
and
the
mobile.
We
are
also
working
on
new
connection
car
templates.
B
We
had
a
lot
of
success
with
the
new
templates,
but
we
also
got
a
lot
of
feedbacks
that
they
are
good,
but
not
enough.
So
we
are
iterating
across
these
feedbacks
in
order
to
build
new
templates
and
new
capabilities
and
Viva
connection
and
on
the
Asus
platform
itself,
and
then
one
of
the
other
things
that
we
want
to
do
here.
That's
probably
interesting
for
some
of
you
guys
we
want
to
so
you
know
that
today
we
have
this
thing
called
The.
B
Core
the
card
designer
Ace
and
the
card
designer
Ace
is
a
way
for
you
to
be
able
to
quickly
create
an
ace
by
configuring,
the
card
View
and
being
able
to
feed
the
card
itself
so
with
adaptive
card
Json.
In
order
to
have
a
quick
view,
that's
nice
and
we
have
seen
a
lot
of
users
of
that
card.
Design
Ace,
especially
in
scenarios
when
you
want
to
build
static
cards
that
are
a
little
bit
of
functionalities
or
if
you
want
to
build
demos.
B
But
one
of
the
lock
that
we
have
in
the
in
the
car
designer
is,
is
the
ability
to
call
to
consume
SharePoint
data
or
to
consume
data
that
are
exposed
through
apis,
Microsoft
graph
or
whatever?
So
one
of
the
things
that
basically
we
we
are
building
is
the
is
a
functionality
inside
of
the
card
designer
Ace,
where
the
author
of
the
dashboard
upon
adding
a
new
instance
of
the
car
designer
is
in
the
dashboard
itself.
B
They
they
will
be
able
to
also
execute
API
calls
and
being
able
to
consume
and
introduce
outside
external
data
in
the
car
designer
Ace
itself,
and
because
we
want
to
be
able
to
keep
that
kind
of
flow
of
building
a
card.
Configuring
the
car,
consuming
data
and
exposed
and
make
the
card
available
to
the
users
secure
and
governed
by
the
same
governance,
capabilities
and
functionalities
the
SharePoint
framework
produces.
B
That's
one
of
the
things
that
we
are
also
aiming
to
ship
soon
moving
on,
because
we're
not
there
yet
other
things
that
we
are
considering
and
we
are
building
and
we
are
working
on-
are
multi-instance
and
River
connections.
So
today
will
be
the
connections.
You
can
only
hit
one
home
site,
but
what,
if
you
have
multiple
home
site?
That's
one
of
the
things
that
we
are
building
here.
Connection
for
Tablet
support,
I
think
this
is
all
already
available
somewhere
or
it's
going
to
be
available
soon
somewhere.
B
But
the
idea
is
to
basically
to
have
a
third
form
factor,
not
only
desktop
and
mobile,
but
also
tablet
River
Connections.
In
order
to
be
able
to
have
kind
of
a
different
real
estate
for
the
cars
that
they
need,
that
the
most
personalization
is
another
thing
that
we
are
going
to
be
able
to
provide
soon
for
Viva
connections
and
then
another
thing
that
we
are
building
is
this
kind
of
feature
called
the
development
Geo,
and
this
is
the
Azure
Point
framework
capability.
B
So
the
idea
behind
this
feature
is
that
you,
as
a
company,
have
a
set
of
developers
that
you
want
to
dedicated
in
a
place
on
your
environment
so
that
they
can
build
the
content
by
consuming
tenant
data.
So
it's
not
a
different
tenant,
it's
not
a
developer
tenant.
They
are
developing
in
the
tenancy
itself,
but
you
want
to
isolate
them
so
that
they
are
not
able
to
access
I,
don't
know.
Maybe
they
are
not
able
to
access
production,
API
or
they're
not
able
to
access
other
things.
B
We'll
have
a
set
of
permissions
that
are
only
available
that
are
only
available
for
that
Geo
so
that
the
developers
will
be
able
to
hold
their
Solutions
but
only
use
apis
that
are
available
there.
So
that's
one
of
the
things
that
we're
doing
there
a
rather
functionality
that
we're
building
is
more
capabilities
and
control
for
the
admins
to
understand
the
WHERE
on
governed
script
can
potentially
be
injected
in
their
tenancy.
So
today
we
have
this
feature
called
No
script.
B
That's
all
nice
and
dandy,
it's
all
controlled
by
the
Admin,
but
the
admin
has
no
idea
to
understand
where
no
script
is
disabled
or
enabled
so
we
are
building
some
functionalities
so
that
when
you
go
to
the
tenant
administrator,
you
will
be
able
to
have
a
look
and
see
where
no
script
will
disable
and
basically
being
able
to
act
on
that.
And
then
the
other
thing
that
we
are
working
on
is
the
ability
to
create
the
full
page
apps
that
are
isolated
from
the
rest
of
the
tenancy
but
they're
not
using
an
iframe.
B
So
today,
when
you're,
creating
an
isolated
web
pattern
resonated
app,
we
run
that
in
an
iframe
and
then
the
iframe
points
to
a
different
domain,
and
this
is
a
way
for
us
to
be
able
to
constraint
permissions
on
that
weapon.
Only
permission
constriction
is
great,
but
iframes
sucks.
So
one
of
the
things
that
we
want
to
do
is
being
able
to
create
an
app
page.
This
is
a
full
page
app
and
then
that
pull
a
page
up
the
entire
app
will
run
from
a
different
unisolated
domain.
B
Sharepoint
pages
in
Microsoft
graph
API
is
already
there
and
we
are
going
to
extend
and
ship
that
soon
or
make
that
more
available
soon,
and
another
thing
that
we
are
building
is
the
ability
to
have
vanity
domains
in
graphs.
So
today,
if
you
go
to
slash
me,
slash
sites
and
you
are
in
a
vanity
domain
tenant
and
if
you
don't
know
what
advantage
domain
tenant
is
good
job.
B
You
are
not
dealing
with
a
lot
of
complexity
that
can
be
a
pain
in
the
back
sometimes,
but
if
you
have
to
you
know
that
that
information
is
done
available
today
in
Microsoft
graph.
So
what
we
are
doing
is
that
we
are
putting
that
capability
in
Microsoft
graph,
so
that,
in
the
same
way
that
the
multi-g
information
is
there
in
the
same
API,
you
will
also
be
able
to
see
all
the
vanity
domains
that
your
tenant
has.
A
So
I
guess
you
have
one
more
slide
unless
I'm
completely
mistaken.
Yes,
because
we
have
few
minutes
so
we
do.
We
do
realize
and
I
do
apologize
on
this
for
those
who
can
hear
us,
but
they
cannot
see
the
chat
and
we
have
unfortunately
maxed
out
the
chat
with
our
current
meeting
with
1000
attendees
in
a
chat.
But
we
would
love
to
have
questions
in
the
chat
and
and
feedback
for
the
team
for
those
who
can
actually
write
them.
A
A
You're
welcome,
but
we
would
love
to
have
a
discussion
on
jobs
related
on
who,
what
you
need,
what
works,
what
it
doesn't
work
and
we
will
move
into
the
next
topic
and
the
demo
of
the
day
with
AC
right
after
this
slide,
but
please
continue
discussion,
something
what
you
would
love
to
have
or
something
is
missing
or
if
something
works,
positive
feedback
is
absolutely
welcome
as
well.
So
please
let
the
team
know
because
that's
super
valuable
for
the
next
steps
planning
or
if
something
on
this
previous
slide
was
confusing.
A
B
A
We
do
not
say
hell
in
this
show,
because
this
is
a
family
show
and
so
we'll
beep
that
away,
but
it's
okay,
so
sorry
look
thank
you,
Luca
and
and
John
and
Alex
helping
on
the
on
the
questions
on
the
chat
and
then
please
continue
discussion
and
chat.
We
need
to
be
conscious
about
the
time
because
we
do
have
another
topic
which
this
time
relates
on
spfx.
Just
about
a
recap.
For
next
week
we
will
have
a
the
feature
crew
who
created
Viva
Home
joining
us
on
next
week
and
next
week.
A
We
also
talk
about
Azure
communication
services,
but
that's
for
next
week
this
week
we
have
we're
quite
Viva,
Centric
and
SPF
eccentric
by
a
coincidence,
basically,
but
please
continue
to
continue
discussion
again
on
a
channel
related
on
those
questions
and
those
features
which
really
work
for
you.
So
if
there's
something
you
would
like
to
see
in
spfx,
please
let
us
know.
That's
super
important
for
the
team.