►
From YouTube: Managing your Viva Connections and SPFx solutions using the new Apps site in SharePoint Online
Description
In this 17-minute developer focused demo – Vesa Juvonen shows off the completely Modernized App Catalog with Modernized app request process and Modernized app catalog experiences. One place to upload, manage (app request and approval) and deploy SPFx solutions (custom components) in an organization. Existing catalog UX will be updated (aligned to typical Admin UX), no action on your part and no impact on existing catalog functionality. Demo and Roadmap for the SPFx store and app catalog delivered. This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on March 8, 2022.
Demo Presenter: Vesa Juvonen (Microsoft) | @vesajuvonen
Learn more:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp/videos
A
Now,
if
you
are
a
tenant
administrator,
you
might
have
actually
already
seen
a
message
center
post
related
on
the
changes
which
are
coming
today,
we're
going
to
talk
about
the
key
updates,
which
is
happening
in
here
and
I'm
going
to
do
a
live
demo
as
well
on
showing
and
the
real
new
experience,
which
is
actually
pretty
cool.
You
can
see
the
experience
now
on
the
right
side,
so
it's
fully
completely
modernized.
A
I
will
show
you
the
current
or
the
class
or
the
the
previous
experience,
so
you
remember
and
see
how
much
work
has
been
actually
happening
here.
But
basic
idea
of
this
location
is
to
have
a
one
place
to
upload,
manage
and
deploy
your
sharepoint
framework
solution
for
your
organization
and
that's
basically
for
creating
those
custom
components
which
can
enrich
and
modernize
the
ux
of
the
sharepoint
or
viva
connection
or
actually
microsoft,
teams
as
well.
So
it's
basically
for
managing
the
sharepoint
framework
solutions
with
certain
targeting
for
microsoft
teams,
video
connection
at
sharepoint.
A
Now
the
key
updates
in
in
this
area
can
be
divided
right
now
in
two
different
areas:
two
different
main
points
and
number
one
being
the
modernized
app
request
process.
I'm
going
to
show
that
one
in
practice
today
so
kind
of
understand
what
this
means
and
how
things
work-
and
this
has
been
already
rolled
out
to
the
production.
But
it's
not,
it
hasn't
been
necessary,
necessarily
super
clear
that
it's
actually
out
and
what
it
means
and
and
how
it
can
be
accessed.
A
A
We
haven't
actually
done
significant
amount
of
investments
in
the
app
or
in
the
store
for
many
many
years
until
we
started
kind
of
investing
much
more
on
this
area
within
one
and
a
half
years
ago.
If
I
remember
correctly,
but
you
can
pretty
much
see
if
I
go
one
step
back,
that
the
experience
which
we
can
see
here
is
looks
like
a
sharepoint
2013
ux
experience.
A
So
there
was
a
long
time
when
the
app
catalog
and
the
sharepoint
add-ins,
especially,
were
not
getting
any
investments
well
technically
sharepoint
and
are
not
getting
any
investments
even
still,
but
sharepoint
framework
is
and
because
sharepoint
framework
is
actually
using
the
app
catalog
behind
of
the
scenes
and
for
deployment
management
and
that's
why
we
are
evolving
this
ux
as
well
now
showing
here
this
one.
This
is
basically
a
screenshot
which
you're
going
to
see
live
pretty
soon
as
well.
A
So
this
is
the
new
modernized,
app
catalog,
which
is
then
completely
changed,
and
the
features
and
capabilities
are
exactly
the
same.
So
you
can
still
use,
of
course,
the
app
catalog
also
for
sharepoint
add-ins.
We're
going
to
talk
about
that
one
briefly
in
the
in
the
after
the
demos
as
well,
and
you
can
use
it
for
sharepoint
framework
and
then,
as
part
of
the
app
catalog.
A
You
have
all
of
the
different
capabilities
which
you
had
in
the
classic,
but
we
removed
all
of
the
complex
ux
ribbon
settings
and
configurations,
and
all
of
that
so
making
this
more
aligned
with
the
standard.
Administrative
ux
experiences
so
that
it's
super
clear
what
you
can
do
here
and
what's
happening
behind
the
scenes
now,
as
I
can
see
absolutely
question
from
stefan,
which
I
should
have
been
probably
a
bit
more
clear,
is
that
this
is
not
gonna
technically
replace
your
existing
app
catalog,
it
will
get
modernized.
A
So
all
of
this
is
just
that
you,
basically
you
don't
need
to
do
anything.
The
existing
app
catalog
will
have
just
a
completely
modernized
ux,
so
locations
are
not
changing.
Status
is
not
changing.
Behaviors
are
not
changing.
Functionalities
are
not
changing
all
of
the
apps
which
you
have
already.
There
will
be
there
still
we're
just
overlaying
the
whole
modernized
ux
on
top
of
it
and
and
making
it
look
much
nicer.
A
That's
kind
of
the
idea
here
now
before
I
go
to
the
actual
demo
to
talk
about
the
end
user
acquisition
process
and
then
the
operation
deathmatch
of
operations-
and
you
should
see
this
one
in
practice,
so
it's
not
just
pictures
and
smoke
and
mirrors.
I
just
wanted
to
pinpoint
that
as
well
that
we
have
done
some
changes
on
the
app
catalog
creation.
It's
still
not
yet
fully
automatic,
but
it
will
create
itself
automatically
when
you
try
to
access
the
app
catalog
first
time.
A
So
when
you
go
to
the
administrative
ux
and
you
go
to
the
admin
settings
I'll
show
this
one
in
practice
in
the
demo,
it
will
actually
click.
You
click
the
apps
which
is
a
bit
confusing
or
add-ins,
and
it
will
actually
start
creations,
tab
catalog
and
it
will
automatically
create
that
to
a
url
sites,
less
app
catalog.
So
it
will
be
denovating
on
that
url.
This.
This
will
no
longer
debate.
A
Should
we
create
this
automatically
for
every
single
deadline
or
not,
but
that's
a
separate
discussion
which
we're
not
gonna
have
on
this
call,
but
that's
quick
demo
on
on
also
actually
on
the
speed.
So
it's
relatively
fast
to
get
it
created,
which
wasn't
the
case
in
the
past
and
also
it's
fully
automatic.
So
from
the
more
features
you
click,
the
apps
and
open,
and
that
starts
to
automatic
creation
of
site
collection
if,
by
the
way,
the
app
catalog
site
collection,
url
is
already
taken
for
whatever
reason,
which
would
be
super
weird.
A
It's
gonna
take
another
site,
collection,
url.
So
it's
okay,
all
of
that
is
taken
into
account.
Now
can
we
create
an
app
catalog
per
site?
So
can
you
have
a
site
collection,
app,
catalogs,
absolutely
100,
we're
not
going
to
take
any
of
the
existing
features
away.
You
can
still
have
a
site
collection,
app,
catalogs.
All
of
those
features
are
still
in
the
future
in
here
we're
basically
just
focusing
on
modernizing
the
app
catalog
site,
collection
experience
and
making
it
aligned
with
the
administrative
ux.
So
let's
have
a
look
on
that
one
in
practice.
A
So
let
me
first
go:
let's
see
if
I
can
actually
remember
correctly.
Yes,
that's
the
normal
end
user.
So
in
this
case
I'm
the
end
user.
I'm
going
to
start
the
flow
of
acquisition
or
acquiring
a
solution
from
the
store,
we're
going
to
have
a
look
on
the
request
process
a
bit
and
then
the
administrative.
A
So
let's
say
here:
skybo
is
quite
cool
list
burst,
that's
actually
a
pretty
cool
solution
as
well,
and
it
has
even
viva
connection
capabilities
on
it.
So
as
I'm
an
end
user
and
currently
you
cannot,
as
I'm
an
end
user.
Currently,
you
cannot
acquire
any
sharepoint
framework
solution
from
the
store
because,
because
quite
often
sharepoint
framework
solutions
do
require
administrative
permissions
and
they
need
to
be
approved
by
the
administrator
to
get
installed
on
antenna,
that's
kind
of
a
security
reasons
as
well.
A
So,
as
I'm
an
end
user,
I
can
request
and
that's
a
solution
to
be
added,
and
I
can
add
here
something
like
our
business
people
would
like
to
have.
This
show
fails
based
on
region,
so
that
request
is
then
being
sent
to
the
administrator.
So
me
as
an
end
user.
I
can
of
course
go
to
my
request.
I
can
see
what
are
the
solutions
which
I've
been
requesting
to
get
acquired
and
to
get
available
in
my
tenant,
and
then
the
administrator
actually
takes
the
takes.
The
risk
is
responsible
of
making
decisions.
A
A
Now
I
have
now
two
items
requested
as
an
end
user
and
let
me
put
a
different
hat
on
my
role,
so
I'm
the
administrator
now
so
different
role
and
I'm
in
the
administrator
admin
view.
If
you
go
back
in
the
in
the
admin
center,
we
need
to
go
to
the
app
catalog,
so
viva
connection
and
sharepoint
app
catalog,
which
is
under
the
sharepoint
a
bit
confusing
again,
because
you
could
actually
have
sharepoint
framework
solutions
which
are
targeted
for
teams
in
here.
But
that's
something
that
we're
working
on
the
future
as
well.
A
So
I
can
click
more
features
and
then
I
can
click
apps
from
here.
So
when
I
click
to
open
it
will
either
create
the
site
collection
or
it
will
redirect
me
to
the
site
collection,
which
has
been
already
created,
which
is
the
case
in
this
this
tenant
and
we
can
see
immediately
the
new
site
collection
and
the
new
features
and
where
we
have
all
of
the
new
cool
filtering
mechanism,
view
mechanisms
all
of
that
available,
and
we
can
see
that
it's
actually
fully
modernized.
A
So
it's
aligned
with
the
admin
ux
which
we
have
across
the
admin
operations.
And,
of
course,
when
I
do
operations
or
details
in
the
amp
level,
then
the
experience
is
a
bit
modernized
as
well.
First
of
all
quickly
on
the
app
requests.
Let
me
go
in
there
there's
a
bending
set
of
app
requests,
which
is
list
bursts
and
charts,
and
those
are
the
ones
which
are
pending.
A
For
example,
each
chart
is
pretty
cool
solution,
also
works
in
microsoft,
teams
well
targeted,
actually
even
microsoft
teams,
and
we
can
see
that
the
request
was
based
on
that.
We
can
see
the
details
and
we
can
request
and
approve
that
to
be
acquired,
and
that
will
then
start
a
pro
acquisition
process
of
the
solution
me.
A
The
ux
is
showing
that
and
then
encouraging
the
administrator
code
to
api
access
page
to
actually
approve
them
now
coming
back
on
on
here.
If
I
go
on
manage
apps,
all
the
features
have
been
modernized
but
of
course,
all
the
features
which
we
have
are
still
the
same.
So
I
can
still
track
and
drop,
for
example,
sharepoint
framework
solutions
from
from
development
environment
or
from
file
system
directly
to
the
tenant,
and
I
can
install
those
solutions
and
as
part
of
the
installation,
the
messages
and
all
of
these
are
exactly
the
same
as
they
were.
A
But
again
it
has
been
modernized.
So
it's
more
clear:
the
text
has
been
updated
and
I
have
more
control
as
an
administrator,
what's
actually
happening
as
I'm
approving
this
solution
to
be
deployed.
So
as
an
example,
in
this
case
we're
going
to
create
a
telescope
deployment
for
that
webpart.
So
pretty
simple
and
easy
to
do
and
again
it
had
api
requests,
so
I
can
actually
go
to
the
ap
access
page
in
here
now.
A
The
one
thing
to
notice
also
is
that
the
whole
ux
has
been
modernized,
so
it's
no
longer
looking
like
a
sharepoint
site
collection
and
there's
some
ideas
in
here.
I'm
going
to
talk
about
that
one.
When
I
go
back
in
slides,
but
key
point,
that
is
that
you
can
actually
see
even
access
to
api
api
access,
page
the
administrative
location
to
manage
the
apis
from
here.
You
can
easily
access
the
store.
A
First
of
all,
what
are
the
next
steps
for
sharepoint
framework
solution
and
app
catalog?
So
we
keep
on
investing
in
here,
so
you
can
in
future
you
can
acquire
viva
connections,
sharepoint
solutions
directly
from
microsoft,
app
source,
it's
pretty
crazy,
actually
that
that's
it's
not
supported
currently,
which
is
mind,
bubbling,
vmware
connection.
App
type
will
be
in
appsource,
so
you
can
easily
find
them.
Your
connection.
Category
will
be
in
store
and
in
app
catalog,
so
you
can
kind
of
start
thinking
abstractions
on
top
of
that
app
catalog.
A
So
it's
more
about
the
microsoft
365
hosted
apps,
and
then,
where
are
you
targeting
that's
in
viva
connection
or
sharepoint,
or
in
teams
it
has?
It
will
have
a
different
views,
we're
working
also
on
auto
update
on
sharepoint
framework
solutions
from
store.
So
if
you're
an
isv-
and
you
have
a
newer
version
there
and
the
administrator
allows
that
auto
update
to
happen
and
that's
going
to
be
happening
behind
of
the
scenes.
If
you
wanted
to
choose
to
do
so,
showing
additional
metadata
details
in
spfx
solution.
A
Also
in
app
catalog
is
available,
that's
something
which
is
working
for
solutions
which
require
from
the
store,
but
as
I'm
installing
a
solution
from
local
to
the
amp
catalog.
There's
this
kind
of
a
disparency
or
difference
between
the
icons
and
descriptions
and
all
of
that
end.
User
acquisition
for
spfx
solutions
is
in
planning
in
roadmap,
site
collection.
App
operations
in
modern
ux
are
going
to
be
modernized.
Integration
of
sharepoint
framework,
app
catalog
to
admin.
Ux
is
implants
as
well.
A
Now
this
will
happen
whenever
we
can
actually
have
more
granular
based
access
in
the
tenant
admin
operations.
So
you
can
then
dedicate
individual
sections
of
the
microsoft
research,
madmen
ux,
for
example,
for
your
app
catalog
administrators
and
then
the
final
note
before
we
go
to
the
next
demo.
I
just
want
to
call
out
we
are
investing
in
all
of
this
from
the
perspective
of
sharepoint
framework
and
as
as
the
primary
location,
so
the
sharepoint,
adding
model
hasn't
really
got
that
much
well.
A
No
investments
within
many
many
many
years
and
sharepoint
framework
should
be
the
ux
level
replacement
and
then,
if
you
have
a
separate
application
which
is
connecting
to
the
sharepoint
online
or
anywhere
in
microsoft,
365,
please
use
the
azure
ad
based
permission,
management
and
access
points
on
that.
That's
the
right
way
of
doing
things
in
the
future
and
more
guidance
on
that.
One
is,
of
course,
in
the
works,
but
that's
all
I
have
time
to
go
through
within
this
demo
I'll
answer.
Some
of
the
questions
which
I
did
not
have
time
to
answer
during
their
demo.
B
Yes,
yes,
there's
a
long
list
of
questions
about
provisioning
and
what
happens
to
the
previous
store
and
a
lot
of
other
things
so
yeah.
If
you
want
to
take
a
look
at
those
vesa,
if
we
didn't
have
a
solution
on
that
too,
I'm
sure
we
could
schedule
some
time
for
that
as
well.
Yep
excellent.
Thank
you
so
much
great
to
see
this
and
appreciate
everyone
sharing
their
comments,
questions
and
other
feedback
into
the
chat
window.