►
Description
A quick demo showing how tenant wide deployment of extensions works in SharePoint Online. Tenant wide deployment support was added with the SharePoint Framework v1.6 release and it enables you to deploy your customizations across the tenant from a centralized location.
Sample code and package used in the video is available from Github at https://github.com/SharePoint/sp-dev-solutions/tree/master/solutions/global-footer.
More details on the capability are available from the SharePoint dev blog or from official documentation - .
A
In
our
case,
we
can
actually
download
this
pkg
file
directly
and
we
can
then
install
this
file
to
our
tenon,
so
I'm
gonna
download
that
one,
let's
actually
open
up
that
in
a
folder
I'm
gonna
go
to
my
tenant
and
I
need
to
be
a
tenant
administrator.
To
make
this
happen
because
or
any
talent
I
administrator
have
to
have
given
me
the
permissions
to
deploy
this
our
customizations
to
my
tenant,
so
I'm
gonna
track
and
drop
that
SP
pk-2
file.
A
Inside
of
my
tenant
and
that's
gonna,
then
prompt
me
to
grant
the
needed
permissions,
and
in
here
you
can
actually
see
that
this
package
contains
there's
an
additional
message
here,
which
is
saying
that
this
patek
package
contains
an
extension
which
will
be
automatically
enabled
across
sites.
Note.
You
need
to
check
box
or
check
out
this
check
box
to
be
able
to
this
capability
to
enable
this
capability
within
your
tenna,
so
it's
actually
deployed
on,
and
what
happened
here
was
that
we
actually
added
automatically
based
on
the
code
which
is
inside
of
the
SP
pkg
file.
A
We
added
an
entry
to
this
tenant
wide
deployment
list,
which
is
basically
telling
sharepoint
that
whenever
we
are
rendering
and
signed
in
a
sharepoint
online,
a
modern
experience
in
a
sharepoint
online.
We
cannot
include
this
extension
inside
of
that
rendering
of
the
page,
and
we
could
feel
that
that,
based
on
a
web
template
in
this
case,
this
is
going
to
be
actually
enabled
for
all
sharepoint
framework,
modern
experiences
so
classic
side
with
the
modern
experience
or
modern
page
or
a
a
modern
site.
In
this
case,
this
is
a
group
associated
team
sign.
A
If
I'm
gonna
refresh
this
one,
we
can
actually
see
that
we
have
now
a
new
customization
available,
which
is
the
fuller
here
on
the
Honda
bundle,
which
has
a
few
buttons
and
a
slogan
of
the
company.
What's
interesting
about
this
extension
also
is
that
you
can
actually
configure
that,
so
you
can
go
here.
You
can
select
this
item.
You
can
edit
the
item
here
as
well.
A
So,
if,
as
an
example,
if
we
want
to
modify
the
definition
of
the
of
the
company
able
to
be
cantos
or
electronic
electron
named
train
sharing,
is
caring
or
update
any
of
the
links
or
update
the
icons
visible
photo
links,
we
can
actually
do
that
directly
using
the
component
properties.
So
this
modifies
the
instance
or
the
definition.
How
do
we
render
the
component?
A
The
eigenvalues
are
obviously
our
fabric
eigenvalues
and
there
is
the
title
and
then
there's
the
URL,
where
we
actually
want
to
pinpoint
when
you
user
clicks
that
button
you
can
also
filter
and
the
existence
of
this
one,
for
example,
to
a
modern
team
site
without
a
group
or,
for
example,
to
a
communication
site.
In
this
case
again,
we
don't
have
any
filters
here.
So
that
means
that
the
same
modification
which
you
can
see
here,
contoso
electronic
now
updating
is
available
in
croup
associated
sites.
A
There
we
go,
you
can
see
the
modification
available
and
it's
also
available
in
that
communication
site.
So
now,
if
I
refresh
this
communication
site,
you
can
actually
see
that
the
functionality
is
available
there
and
obviously,
if
you
go
to
a
SharePoint
or
anybody
creates
a
new
SharePoint
site
within
the
tenon.
So
let's
actually
do
that
as
well.
So
let's
create
a
communication
sign,
let's
create
a
showcase
site.
Let's
call
this
showcase
and
that
is
available.
Creation
of
a
modern
site
takes
on
a
few
seconds.
A
So
one
two
three
four
five
and
here
we
go
and
we
can
say
that
our
extension
is
automatically
available
and
that's
because
we're
taking
advantage
of
this
tenon
pointed
deployment
of
extensions.
So,
basically
you
can
now
say
the
button
or
the
standard
food
are
available
in
here
with
a
a
slogan
of
the
company
as
well.
Now,
if
this,
if
you
want
to
utilize
this
within
your
deployment,
you
can
easily
do
that
by
downloading
the
SP
pkg
file
and
modifying
the
buttons
and
you
are
and
the
slogan
to
match
your
company
or
a
magical
deployment.
A
If
you
want
to
have
a
look
on
the
source
code,
that's
absolutely
available
in
the
industry
in
the
github
as
well,
so
you
can
actually
have
a
look
on
how
it's
being
implemented.
It
is
using
react
components.
So
a
global
order,
and
here
we
go.
It
is
actually
using
a
react.
Office
UI,
react
components
and
rendering
them
the
input
out
input
using
those.
So
we're
taking
advantage
of
the
combine
common,
poor,
contextual
menu
item
and
few
additional
other
components.
A
Now
relatively
simple
thing,
you
can
modify
the
implementation
if
needed,
you
can
modify
the
configurations
if
needed,
but
if
nothing
else,
you
can
also
test
this
by
downloading
the
SP
p
kt
file,
install
that
to
your
channel
and
see
how
the
tenant
extension
actually
work
in
your
case,
so
extremely
convenient
way
for
getting
customizations
deployed
across
all
of
the
sites
within
your
tena.
Thank
you.