►
From YouTube: PnP Webcast - Introduction to PnP Tenant Templates
Description
Introduction to the PnP Tenant Templates. What they are and how you can take advantage of provisioning complex solutions and structures using them to your tenants. PnP Tenant templates support defining tenant level structures like sites, site collections, SPFx solutions, permissions, themes, Site Designs and Site Scripts.
This webcast shows what they are and how you can get started on creating them with PnP PowerShell.
A
Welcome
everybody:
this
is
SharePoint
patterns
and
practices
webcast
and
this
time
we're
gonna
talk
about
the
PMT
tenant
templates,
and
this
is
a
a
hybrid.
This
is
an
evolution
on
the
BMP
provisioning
templates,
which
has
existed
now
for
quite
a
few
years
like
three
to
four
years
already,
and
now
we're
growing
that
engine
and
the
BMP
provisioning
engine
to
support
more
and
more
capabilities
to
align
the
future
of
sharepoint
online
as
well.
A
My
name
is
erina
u1
and
I'm,
a
senior
program
manager
from
SharePoint
engineering
and
with
me
today,
as
the
primary
demo,
man
and
the
creator
of
the
PMPA
tenant
templates
or
the
primary
creator.
Well,
some
one
of
the
creators,
that's
for
the
yes
for
the
father
of
the
team
at
the
engine
or
the
BMP
power
show,
is
the
Irvine
one
Honan.
So
urban
really
did
a
quick
interest
as
well.
Yeah.
B
A
A
As
part
of
the
process,
which
is
actually
kind
of
funny-
and
that's
a
long
story
short,
but
in
this
time
we're
going
to
talk
about
now,
the
evolution
of
the
PNP
provisioning
engine
basically-
and
we
did
have
a
have-
a
had-
a
early
version
or
one
first
version
out
already
in
October
2018
version
of
this
one,
and
but
there
will
be
some
changes
on
that
and
more
stuff
will
be
supported
in
the
future
as
well.
Let
me
actually
go
under
on
the
following
side.
So
what
is
the
BMP
antenna
template?
A
So
classic
BMP
provisioning
engine
has
supported
provisioning
of
elements
in
a
site
level.
So,
basically,
technically
within
your
power,
shell
or
your
code,
you
were
requested
to
create
a
site
or
a
sub
site
or
a
site
collection.
And
then
you
apply
the
template
on
top
of
that
site.
So
there
is
an
existing
site,
so
we
never
actually
saw
for
at
creation
of
hero,
case
or
creation
of
sites
and
site
collections
and
tenant
level
configurations.
We
want
to
be
precise.
A
We
support
some
of
that
stuff
slightly
and
during
this
year,
but
now
we're
kind
of
impressing,
the
tenant
level
provisioning
logic
and
we
support
provisioning
of
all
of
the
elements
basically
which
are
which
has
an
API
available
in
the
tenant
level,
and
like
mentioned
now,
you
can
actually
define
what
site
collections
are
getting
created
or
what
sub
sites
in
the
site
collections
are
getting
created
whenever
a
template
is
being
applied.
This
means,
then,
that
you
have
a
1
p.m.
a
file
which
is
the
BMP
provisioning,
template
or
talent
provisioning.
What
are
we
call
them?
A
Tenant
template
1
file
anyway,
exactly
one
file
which
actually
inside
of
the
BMP
file
it
can
contain.
There's
pkt
file
she
open
framework
solution.
It
can
contain
the
existing
templates,
which
might
have
already
created
the
BMP
provisioning
templates.
You
can
create
instructions
of
creating
site
collections
and
subsides
and
sub
sites
and
all
of
that
stuff
and
then
activating
the
solution
and
putting
the
web
parts
on
a
welcome
page
of
sites,
and
all
of
that
so
with
the
one
file
which
I
can
send
as
an
example
today,
Earvin
can
create
the
file.
Send
it
to
me.
A
A
B
You
have
to
first
create
the
size
collection
and
then
you
apply
the
templates,
but
the
main,
the
main
provider,
or
not
the
enabler
that
we
can
do.
This
right
now
is
actually
modern
sites.
Sure
all
site
collections
classic
site
collections
they
can
take
up
to
like
15
minutes,
sometimes
longer
to
be
created
where
these
ones
are
created
in
in
seconds
and
and
that's
the
reason.
The
engine
is
now
able
to
create
a
few
site
collections
actually
in
a
couple
of
seconds
and
then
apply
those
templates
to
it.
A
Sure-Sure
and-
and
this
is
technically,
this
is
also
a
site
result
of
the
project
which
we
did
and
still
our
building
with
sister
ship
and
stargates.
So
we
wanted
to
make
the
SharePoint
starter
kit
installation
as
simple
as
possible,
and
how
do
we
make
it
as
simple
as
possible
will
be
simplify
the
process
and
steps
which
are
needed
to
install
a
template
to
your
tenant,
so
we'll
add
absolutely
their
starter
kit.
It's
an
awesome
example
of
this
as
static
its
reference
on
the
on
the
video
notes
as
well.
A
So
we
kind
of
I
mentioned
this
one
already.
But
what
are
the
things?
What
are
now
supported
by
the
BMP
tenon
templates,
and
this
is
the
status
in
October
2018,
so
that
it
might
be
depending
on
when
you're,
watching
the
video
there
might
be
additional
things
available,
but
at
the
moment
we're
still
concentrating
on
a
SharePoint
site
and
we'll
come
back
on
that
one.
A
slightly
later,
when
you're
able
to
define
and
what
kind
of
site
collection
should
be
created.
A
What
would
be
the
URL
of
those
site
collections
which
are
created
as
whenever
the
template
is
being
applied?
You
can
create
subsides
inside
of
the
site
collection.
You
can
set
an
existing
site
to
be
a
hub
site.
Basically,
it's
a
root
side
of
a
site
collection
which
is
said
to
be
a
hub
site,
so
you're
able
to
automate
that
one
using
the
template
as
well
you're
able
to
provision
tenant
themes.
A
So
this
sound
modern
talent
themes
for
sharepoint
online
you're
able
to
provision
sharepoint
framework
solution
to
the
app
catalog,
so
you're
able
to
basically
inside
of
your
template.
You
can
have
this
baby
katie
for
all
of
its
system,
adding
the
the
the
customization
to
the
app
catalog
and
also
obviously
using
the
site
level
provisioning
you
can
set
to
with
parts
and
extensions
and
everything
else
available
on
the
site
level
as
well.
So
you
can
fully
automate
the
deployment
and
that's
part
of
the
classic,
let's
say
BMP
site
templates,
whatever
whatever
we
call
them.
A
Provisioning
templates
are
placed
in
the
past.
So
now
you
can
technically
have
again
one
BMP
file
which
creates
you
the
whole
solution
automatically
it's
just
by
executing
a
few
lines
of
code
or
BMP
powershell,
and
that
sounds
amazing.
So
let's
actually
have
a
look
on
this
one
in
practice,
so
let's
jump
on
urban
screen
then
and
then
we'll
come
back
on
the
closing
of
the
web
cast
in
a
second.
So.
B
What
you're
looking
at
here
is
actually
the
starter
kit
XML.
So
we
eye
for
this
demo.
I
will
take
the
starter
kit.
Xml
and
I
will
talk
you
briefly
through
what
what
is
in
this
XML
and
and
if
you're
familiar
with
the
PNP
provisioning
engine.
You
might
recognize
things
because
yeah
it's
just
in
next
iteration
of
the
schema,
and
in
this
case
it's
the
July
2018
schema,
where
we
support
what
you're
looking
at
and.
A
B
Okay,
so
why
is
it
Jason?
That
is
a
long
debate,
long
story,
we
picked
XML
at
the
time
and,
for
instance,
we
are
reusing
things
from
classic
and
it's
much
easier
to
copy
the
classic
elements
from
plastic
features.
I
shall
not
mention
the
word
feature
anymore,
but
feature
XML.
You
could
actually
copy
that
easily
into
this
template
and
that's
the
reason
we
went
for
XML
at
the
time
and
not
Jason.
B
What
you're
looking
at
is
a
declarative,
faul
faul,
ready
in
a
declarative
manner,
define
what
you
want
to
do
in
a
site
collection
which
list
you
want
to
create
which
side
collections
you
want
to
create,
which
content
types
you
want
to
create,
which
fields
etc,
etcetera.
That
is
basically
what
what
you're
looking
at.
B
B
Okay,
so
if
you
are
familiar
with
the
beating
people
vision
engine
as
I
said,
you
might
recognize
this
plus
a
couple
of
things
that
actually
are
different
here,
for
instance,
we
allow
you
now
to
set
Web
API
permissions.
So
if
you,
if
your
SPF
X
solutions,
require
a
certain
web
api
permissions,
you
can
code
that
one
in
your
template
and
we
will
approve
them
for
you
or
effectively.
It's
you
approving
it
because
you
apply
the
template.
It's
your
identity,
approving
these
API
permission
requests,
but
to
go
a
bit
down.
B
I
will
scroll
a
bit
down
and
don't
want
to
go
into
much
detail
here.
This
is
actually
the
very
interesting
part
now
that
we
introduced
and
that's
what
we
call
a
sequence
and
and
with
the
sequence
you
can
define
which
side
collections
are
to
be
created,
of
which
type
and
you
can
define
which
template
to
apply
to
those
side
collections.
You
see
here,
for
instance,
that
I,
let
me
see
if
I
can
actually
format
it
a
bit
in
a
bit
more
readable
way.
B
If
actually
Fisher
Studio
allows
me
to
do
that
it
well,
it
allows
me
to
format,
but
it's
not
formatting
it
in
an
sort
of
a
3d
movie,
so
I
will
have
to
scroll
a
bit
to
the
right
to
show
you
the
properties.
Here
you
see
that
we
create
a
site
collection.
We
apply
a
theme.
We
set
a
site
design
on
that
side
collection.
B
We
apply
a
site
design
to
the
side
collection
and
we
specify
the
URL
if
it's
a
hub
site,
yes
or
no,
who
is
the
owner,
etc,
and
then,
when
the
site
collection
is
created,
we
apply
this
template,
but
we
also
apply
another
templates.
You
can
actually
apply
multiple
templates.
Where
are
these
templates
located
the
provisioning
templates
reference?
They
are
executed
in
the
same
XML
file,
but
a
bit
more
down
in
the
in
the
structure.
Here
we
create
a
normal
sized
collection,
which
is
a
team
site.
The
first
one
you
see
is
a
communication
size
here.
B
This
is
a
team
site
and
we
apply
the
collab
template
and
we
applied
the
logo
template
for
the
HR
site.
You
here
this
is
the
human
resources
I'll
be
creating,
and
here
we
creating
the
marketing
site,
which
applies
the
same
template.
So
we
have.
We
share
a
template
between
those
two
sides
collections,
but
each
of
the
sides
has
a
different
logo,
so
we
made
another
small
template
that
actually
sets
the
logo
of
those
sites.
B
B
This
is
something
we
also
recently
introduced,
so
here
you
can
and
wonderful.
We
actually
embed
initiation
in
the
next
Mel
file
here,
but
yeah
so
be
it
so
here
we
have
the
the
themes
that
we
provide
so
and
we
threw
out
the
starter
kit.
We
use
these
things
called
tokens,
which
is
an
concept
in
the
PNP
provisioning
engine.
Where
does
it
get
this
value
from?
If
we
scroll
all
the
way
up?
B
You
see
that
there's
a
and
parameter
here
being
company
and
that
by
default
to
composer
electronics,
you
can
override
that
at
application
time
you
specify
your
own
value,
so
you
could
say
my
company
or
whatever
you
want
to
put
in
there,
so
they
did.
These
tokens
are
then
automatically
replaced
with
the
actual
value.
So
we
create
themes,
we
create
side,
designs
and-
and
they
are
all
happening
on
tenant
level,
effectively,
side,
designs
and
themes
are
tenant,
tenant,
scopes,
artifacts
then
we
provide
whole
bunch
of
terms
into
your
economy,
your
term
set
term
setting
term
group.
A
B
Are
stations
yeah
and
then
here
we
start
with
the
templates
and
I
will
not
dive
into
all
the
nitty-gritty
details
of
the
templates
because
there's
basically
standard
PNP
provisioning
templates,
but
we
have
a
bunch
of
templates
here.
We
have
a
provisioning
template
called
the
for
the
footer
links
templates.
We
have
the
route
templates,
we
have
the
collab
templates
for
the
team
sites,
and
here
we
have
the
logo
templates
and
they
are
actually
the
simplest
and
all
starter
kids.
B
B
File
correct
actually
know,
depending
on
the
side,
if
it's
a
modern
site,
the
file
will
not
be
uploaded
to
the
site
itself,
it
will
use
an
API
that
tell
SharePoint,
hair
or
actually
yeah
so
office.
365,
listen!
This
is
the
group
logo
for
this
specific
team
site
which
hasn't
connected
off
365
group
and
the
scenes
it
ends
up
in
the
side
assets,
but
that's
actually
the
server
handling
that
we're
not
uploading.
It.
B
But
this
is
the
starter
kit
XML
file,
but
as
Lisa
mentioned
already
during
the
slides
there
is
we
package
these
everything
into
this
PNP
file,
so
everything
the
XML,
but
also
all
the
support
files,
the
logos,
the
SP
PGG
file,
everything
is
actually
located
in
this
PNP
file.
You
see
this
one
is
a
bit
bigger
than
the
XML
file.
Obviously,
so
where
does
it
get
those
files
from
well
they're?
Those
files
are
actually
located
in
the
starter,
kits
repository.
B
So
if
I,
if
I
go
to
that
starter
kits
repository,
you
will
see
that
there
is
a
provisioning
forward
in
there
and
let
me
move
this
foul,
which
is
not
relevant
here.
You
see
the
starter
kit
XML
file.
Let
me
see
this
resources
folder
here
and
in
the
starter
kit,
XML
file.
We
refer
to
all
kinds
of
resources
that
are
located
in
that
resources
folder.
So
you
see
here
this
like
resource
files
for
localization,
use
the
two
side
designs.
We
have
an
images
folder.
B
The
starter
kit
contains
a
PowerPoint
presentation
which
is
located
in
the
Documents,
folder,
etc,
etc,
etc.
So
Becket's
everything
now
together
now
in
the
I'll,
show
you
an
commander
to
do
that.
Now
in
the
October
28th
release,
re-released
pimpy
PowerShell,
with
support
for
these
tenant
templates,
the
command
lists
were
cooled
differently,
though
we
decided
to
rename
them
the
old
command
that
still
work,
they're,
just
basically
aliases
for
the
new
ones.
So
currently,
if
you
want
to
package
this
XML
file
into
a
PNP
file,
you
first
have
to
read
in
this
XML
file.
B
B
I
check:
if,
if
something
in
the
file
was
wrong,
it
would
have
never
loaded
it
correctly.
You
would
get
in
a
nice
or
you
can
say
almost
ugly
PowerShell
error
there.
So
you
see
the
sequence
here.
You
can
actually
dive
into
the
sequence.
If
you
want
so
you
see
all
the
templates
in
here,
so
the
whole
whole
structure
of
that
template
is
here
now
in
order
to
save
it
is
actually
saying
safe,
PNP,
tenants,
template
it
wants
a
reference
to
that
file
and
they
say
now.
B
In
this
case
we
recall
it's
a
P
now
demo
dot,
PNP
and
press
ENTER,
it's
processed
the
template.
It
finds
all
those
references
to
all
the
package
files,
the
JSON
files
to
resource
files
or
any
other
file
that
you
referred
to,
and
will
it
will
take
a
bit
it's
not
too
long
actually
and
in
the
end,
when
it's
done,
is
you
that
image
files
come
here
now
it's
done
in
the
ends.
There
is
my
demo
PNP
file,
and
this
is
everything
in
one
file.
B
There's
nothing
else
that
I
need
to
distribute
I
can
give
this
single
file
to
someone
else
and
all
the
files
that
the
template
refers
to
are
located
in
that
file.
Now,
to
give
you
an
idea
what's
happening
actually
in
that
sprout,
is
that
if
I
open
the,
for
instance
within
unzipper,
an
unzip
to
or
WinZip
or
7-zip
in
my
case
but
you're
looking
at
the
pin
peafowl
is
an
office
open,
XML
file
which
is
standard
file.
B
It's
the
same
file
format
effectively
as
a
dog
X
far
forward
or
an
excel
X
file
for
Excel
and
and
everything
that
is
located
is
in
in
this
provisioning
templates,
folder
or
so
here
you
see,
let
me
go
back
first
to
the
files
here.
Are
all
the
files
now
they're,
not
really
recognizable,
that
has
to
do
with
the
fact
that
there
is
actually
there
can
be
a
folder
structure
and
resulted
by
actually
renaming
all
the
file
names
to
easy
to
understand.
B
With
your
name
says
in
the
very
name,
everyone
gets
one
one
percent
unique
file,
name,
especially
if
you
say
I'm
uploading
document,
one,
the
dog
acts
to
full
X
and
I.
Also
uploaded
document
one
to
do
the
dog
X
to
folder
Zach,
then
there's
two
documents
for
the
same
name:
they
would
have
conflicts
here.
So
that's
why
we
rename
everything
to
acquit
and
then
in
the
provisioning
template,
there's
a
files
map
file
and,
if
I
open
that
one
and
it
refuses
to
open
it,
can
I
see
open
inside
that
should
work,
no,
it
doesn't
well.
B
B
You
see
that
here
this
okay,
so
this
grid
XML
file,
maps
to
demo
XML
this
package
maps
to
that
file,
etc,
etc,
etc.
So
this
is
how
the
the
internal,
actually
it
works
in
that
in
that's
PNP
file.
So
if
you,
if
you're
missing
something
it
could
be
a
way
for
opening
it
up
within
the
7-zip
or
zipper
any
zipper
found
zipper
and
have
a
look
inside
and
see
like.
Ok
are
all
my
files.
There
did
I
make
a
mistake
in
my
references
and
that
kind
of
stuff,
so
back
to
the
foul.
B
Now
how
given
the
fact
that
you
have
this
template,
how
do
you
apply
this
template?
It
couldn't
be
easier,
let's
say,
apply,
be
provisioning
hierarchy
is
the
old
one
and
tenants
template
new
one,
and
then
you
say
demo
PNP
and
that's
all
there
is
to
it
and
then
the
engine
will
kick
in
now.
I
must
connect
it
to
a
site.
Now,
I
can
connect
to
the
side
here.
B
It
does
not
matter
to
which
side
collection
you
connect.
Keep
that
in
mind.
If
you
apply
the
old
provisioning
template
to
the
site,
you
apply.
That's
that
template
to
that
specific
site
that
you
connect
it
to,
but
because
there's
the
the
tenon
templates,
the
name
gives
it
away
are
applied
to
your
tenant.
You
just
need
a
connection
to
your
tenant.
B
We
will
figure
out
behind
the
scenes
the
correct
URLs
to
to
connect
to
to
your
tenant
administration-
that's
kind
of
stuff,
but
so
it
doesn't
matter
which
URL
you
connect
to
as
long
as
you
connect
to
his
site.
So
in
this
case,
I
connect
it
to
the
demo
site
and,
if
I
say,
apply,
P
and
P
for
tenants,
template
and
I
say:
let's
take
the
starter,
kit,
P
and
P
and
there's
a
couple
of
other
parameters.
You
can
say
you
can
specify
the
sequence
ID
if
you
want
to
specify
apply
a
specific
sequence.
B
Now,
when
I
said
there
were
these
parameters,
she
could
overwrite
like
by
default.
It
creates
site
collections
in
the
in
the
format
of
contoso.
Aids
are
contoso
marketing
and
controller
support,
or
oh
yeah
yeah.
So
you
will
have
to
overwrite
a
parameter
and
one
of
them
is
the
site.
Url
prefix.
If
you
look
in
the
XML
file,
you
notice
that
there
is
a
parameter
called
site:
URL
prefix.
That
is
the
little
part
that
we
put
in
front
of
that
URL
source
les
sites,
then
its
side,
URL
prefix,
and
then
it's
HR
marketing
or
portal.
B
So
to
overwrite
it
you
specify
site,
URL
prefix
equals
PP
demo,
for
instance.
This
same
way
you
can
also
say
my
company
equals
my
company,
so
this
is
wave
overriding.
The
the
parameters
presenter
and
you
see
the
engine
is
being
initialized
and
it
will
check
if
the
site
collections
are
already
there.
Even
if
the
site
collections
are
there,
it
will
reuse
those
site
collections.
So
there's
a
nice
way.
B
If
you
have
testing
things
what
it
will
also
do,
it
will
check
if
the
solution
has
already
been
installed
and
if
it
has
been
installed,
it
will
not
free
install
it.
It
keep
it
keep
in
mind
that
we
actually
behind-the-scenes
check
the
hash
value
of
the
hash
code
of
the
solution.
So
if
the
solution
that
you
installing
is
newer
than
the
one
already
installed,
we
will
update
the
existing
one.
Otherwise
we
will
just
simply
skip
it
now
it
goes
for
the
web
api
permissions
and
then
you
say
and
toss
the
side.
B
Scripts
does
the
themes
and
soon
it
will
start
to
create
side
collections,
because
pimpy
demo
is
a
prefix.
I've
never
used
and
they
say
creating
communication
side.
You
see
pimpy
demo
port,
it
start
to
create
such
collections,
etc.
This
will
take
a
while
I.
Don't
think
we'll
have
to
wait
for
that,
but
this
is
in
principle
how
the
tenant
templates
work.
It's
basically
the
next
iteration
you
could
almost
call
it
v2
of
the
provisioning
engine
where
we
take
this.
A
B
A
So
there
there
are
there's
a
development
happening
and
all
of
these
teams
they
have
more
administrative,
api's
and
and
kind
of
a
tenant
level.
Control
AP
is
available,
and
whenever
those
api's
are
available,
we
can
actually
start
using.
Those
AP
is
into
BMPs
and
our
templates,
and
we
also
then
accept
for
requests
and
improvements
on
the
on
the
templating
model.
A
At
that
point,
yeah
and
from
a
positioning
perspective,
the
BMP
templates
are
kind
of
a
moving
more
and
more
to
the
tenant
level
provisioning,
because
we
have
now
two
side,
designs
and
side
scripts
in
the
site-specific
provisioning.
So,
if
you're
creating
a
modern
side
in
a
sharepoint
online,
it's
it's
a
worthwhile
to
use
a
site,
design
side
script
for
your
customizations,
because
it's
faster
and
more
aligned
on
the
future
of
sharepoint
online
if
possible.
B
A
So,
basically,
in
the
future,
you
can
use
the
the
BMP
eternal
templates
for
getting
the
side,
scripts
and
site
designs
or
already
today
getting
the
site
design
side
scripts
available
in
the
tenant
for
inch
users,
so
basically
site
designs
and
side.
Script
is
the
end
user
capability.
But
if
you
want
to
automate
getting
those
provision
to
the
tenants,
you
can
easily
use
the
BMP
eternal
templates
to
do
that,
like
we
do
in
the
chef
starter
kit
as
an
example.
Well,.
B
Sorry
actually
should
have
mentioned
that
during
my
demo,
but
there's
one
thing
important
to
understand:
that
is,
you
need
to
be
tenant
administrator
in
order
to
be
able
to
apply
the
template
yeah,
it
makes
sense
if
you
think
about
it,
because
we're
provisioning
things
at
tenant
level,
but
keep
in
mind
that
you
actually
need
to
be
tenant
administrator.
You
need,
for
instance,
if
you
need,
if
you,
for
instance,
provision
terms
to
your
text
to
your
term
store.
You
need
to
be
able
to
write
to
that
term
store,
yes,
keep
the
demand
that
you
need,
which.
A
Requires
that
you
explicitly
need
to
have
an
administrative
permission,
the
term
store,
because
by
default
as
a
tenant
administrator,
you
actually
don't
have
permissions
to
write
to
the
temp
store,
which
is
slightly
misleading.
They
open,
but
it
is
SharePoint
Online.
So
there
are
good
example
of
a
small
thing
which
we
we
as
an
e
in
the
engineering
we
should
fix.
But
but
those
are
the
good
things
to
keep
in
mind,
yeah
cool
anything
else.
What
we
from
a
roadmap
perspective
whatever
want
to
actually
mention
no.
B
A
Ahead,
absolutely
absolutely
and
then
you
are
able
to
then
automate
the
across
a
whole
office
365.
So
you
have
a
one
template
and
you're
able
to
easily
do
pre-production,
diff
provisioning
in
some
level
and
f10
on
provisioning,
pre-production
production,
their
provisioning
or
just
use
the
templating
engine
for
setting
you
the
basic
stuff
and
the
basic
or
demo
sites
with
a
demo
content
as
an
example
which
is
which
is
relatively
easily
doable
with
the
templating
model.
A
And
although
it
may
be
one
question
which
we
didn't
touch
on
the
on
the
demo,
so
the
the
PMP
provisioning
templates,
the
site
level
provisioning
templates.
They
do
support
extracting
the
template
from
a
live
site.
Yes,
do
we
support
similar
kind
of
stuff
on
a
tenon
level,
template
a
logical
question?
We
don't
yes
and
there's
a
clear
logical
reason
why
we
don't
actually
support
them,
because
how
would
you
define
what
are
the
sites
and
site
collections
and
elements
which
you
would
extract
from
the
xxe
antenna?
A
So
so
you're
able
to
basically
extract
you're
able
to
extract
X
individual
templates
from
a
site
level?
Then
it
would
put
them
on
the
tenant.
A
template,
XML
include
them,
copy/paste
include
them
on
the
on
the
XML
structure,
then
you
define
their
site
collections
and
dislike
these
themes
and
whatever
you
need
to
actually
get
done,
but
you
can
extract
those
from
a
live
site
because
it's
would
get
on
money,
it
would
be
unmanageable.
It
really
isn't
suitable
model.
No.
B
By
the
way,
just
to
tell
you
if
you,
if
you
don't
feel
that
could
too
comfortable
with
XML
I
didn't
demo
it,
because
it
goes
a
bit
beyond
the
scope
of
this
this
this
this
video.
But
there
are
commandments
that
actually
help
you
to
build
up
the
whole
tenant
template
by
using
powershell
commandlets.
So
you
can
create
a
sequence
at
a
site,
to
a
sequence,
add
a
template
to
your
tenant,
template,
etc,
etc,
etc,
and
then
it
basically
builds
up
this
object
and
then
you
can
save
that
as
XML
or
as
a
B&B
file.