►
Description
In this video Paolo Pialorsi (PiaSys.com) is demonstrating how to take advantage of the tenant wide deployment of SharePoint Framework solutions. This capability will enable you to deploy your web parts to all sites in your tenant just by adding the SharePoint Framework solution package to app catalog.
Presenter - Paolo Pialorsi (PiaSys.com) @paolopia
See more on the tenant-scoped deployment option from official SharePoint documentation - https://docs.microsoft.com/en-us/sharepoint/dev/spfx/tenant-scoped-deployment
More details on the SharePoint developer community from http://aka.ms/sppnp.
A
Welcome
everybody:
my
name
is
Paula
Pelosi
and
I
work
as
a
senior
consultant
at
pcs,
not
calm
in
this
video.
We
talk
about
creating
tenant.
Why
deployed
solution
with
sharpen
framework?
So
first
of
all,
let's
introduce
the
idea
often
and
why
the
deployed
solutions
well
determine
why
the
pad
solution
is
a
solution
that
you
can
deploy
in
the
app
catalog
of
your
target
tenant
and
which
will
be
automatically
available
in
all
of
the
site
collections
that
you
have
in
SharePoint
Online,
without
the
need
to
install
that
SharePoint
framer
solution
in
every
single
target
site
collection.
A
You
need
to
scaffold
a
SharePoint
framing
solution,
so
you're
at
Microsoft
SharePoint.
As
the
starting
point,
you
will
have
to
provide
the
answers
for
all
of
the
questions
provided
by
the
human
generator
for
scaffolding,
a
SharePoint
solution.
First
of
all,
the
solution
name,
which
can
be
the
name
of
your
folder.
You
have
to
target
a
target
environment
which
will
be
SharePoint
Online
for
written
and
white
solution.
You
have
to
select
which
would
be
the
target
folder
and
can
be
the
current
folder.
A
And
then
you
have
to
answer
the
fundamental
question
about
an
on
by
the
problem,
which
is:
do
you
want
to
allow
the
tenant
admin?
The
choice
of
being
able
to
deploy
the
solution
to
all
sides
immediately
without
running
any
feature
deployment
or
adding
apps
inside,
and
if
you
will
reply
yes,
mind
that
the
default
answer
is
no.
If
you
will
answer
yes,
the
solution
will
be
turned
white
actually,
under
the
cover,
there
will
be
a
flag
in
the
package
solution
that
JSON
file
that
you
can
change
later
on.
A
If
you
change
your
mind
or
if
you
want
to
switch
from
tenant
wide
to
site
collection,
targeted
solution,
so
you
can
always
change
your
mind
later
on,
and
then
there
are
many
other
quests
just
like
the
isolated
domains
which
I
will
not
cover
right
now,
and
you
will
have
to
select
the
kind
of
solution
that
you
want
to
create.
Let's
say
that
we
want
to
create
a
webparts
solution.
Name
will
be
tenant.
A
Why
the
web
part,
for
example,
we
can
provide
a
description
and
we
can
select
the
JavaScript
framework
that
we
want
to
use
and
I
will
simply
use
the
know,
JavaScript
framework
selection
to
speed
up
the
scaffolding
process.
So
once
my
solution
will
be
fully
scaffolded,
I
can
open
the
source
code
using
visual
studio
code,
for
example,
and
we
can
have
a
look
at
the
solution
by
itself.
A
So
the
scaffolding
is
now
ready,
making
starfish's
to
your
code
to
have
a
look
at
the
source
code
generated,
and
if
we
go
to
the
package
solution,
dot
JSON
file,
we
can
see
that
we
have
a
skip
feature.
Deployment
attribute
equal
to
this
is
the
flag
that
you
could
use
to
enable
or
disable
the
tenant
wide
deployment.
A
It
is
called
skip,
feature
deployment
because
actually,
under
the
cover,
when
you
enable
the
tenant
wide
deployment,
what
will
happen
will
be
that
any
custom
feature
define
with
the
feature
framework
of
SharePoint
in
your
sharpen
frame
resolution
will
be
skipped
and
will
be
not
applied
to
any
target
cell
collection,
because
you
will
simply
do
the
tenant
wide
deployment.
On
the
contrary,
if
you
set
the
skip
feature
deployment
equal,
false,
you
will
have
to
manually
upload
the
package
to
their
catalog
and
manually.
A
Add
the
solution
to
every
target
set
collection,
and
in
that
case,
any
custom
feature.
Framework
element
would
be
applied
to
the
target
set
connection.
Now,
if
we
open
the
web
part,
we
can
see.
This
is
the
out-of-the-box
that
generated
one
and
we
can
say
customized
upon
experiences
using
this
tenant
while
deployed
for
part
just
to
make
some
changes,
and
we
can
now
use
the
gulp
bundle.
Does
the
ship
to
create
a
bundling
ready
for
shipping
of
our
solution
as
well
as
a--?
A
We
can
then
create
a
package
using
the
package
solution,
option
of
gum
and
in
a
matter
of
few
seconds
we
will
have
an
SP
pkg
file
that
we
can
upload
in
the
App
Catalog.
So
golf
package
solution
ship
again
and
we
will
get
back
the
package
file
ready
for
upload
in
the
app
catalog.
If
we
open
the
SharePoint
folder,
we
can
see,
we
have
the
SD
pkg
file.
We
can
reveal
the
file
in
Explorer,
and
here
we
are.
A
This
is
the
file
and
if
I
go
back
to
my
app
catalog
and
I
upload
the
package
into
the
app
catalog,
you
will
see
in
the
UI
of
the
SharePoint
app
catalog
as
an
admin.
I
will
be
able
to
first
of
all
see
that
this
is
a
package
which
supports
determine
my
deployment.
In
fact,
I
have
this
option
make
this
solution
available
to
all
sides
in
the
organization
and
if
I
select,
this
checkbox
I
will
effectively
make
my
solution
tenant
quite
available.
A
I
click
on
deploy
and,
as
not
me
now,
I
allowed
my
solution
to
be
turned
white.
If
I
go
to
any
site
collection,
my
tenant
I
can
simply
add
a
new
page.
I
will
select
the
page
template
that
I
want
to
use
and
I
would
be
able
to
add
a
webpart
which
can
be
the
tenant
wide
web
part
that
I
have
in
my
solution
and
that's
it
pretty
simple,
pretty
easy
and
my
web
part
is
available
in
any
set
collection
in
my
tenant.