►
Description
Recording of the SIG from 7th of September. Detailed agenda and covered topics from xxx. You can download invite to bi-weekly special interest group call from http://aka.ms/sppnp-core-sig-call.
A
Welcome
everybody:
this
is
the
special
interest
group
for
PMP
site
score:
PMP
PowerShell,
PMP,
site
provisioning
and
the
SharePoint
dev
in
general.
We
do
have
a
lets
say:
weekly
or
bi-weekly
community
calls
so
bi-weekly
we'll
talk
about
SharePoint
development
in
general,
more
on
the
site,
provisioning,
automation
and
all
of
that
stuff
and
then
bi-weekly.
It's
more
specific
on
the
SharePoint
framework.
Today,
we'll
kind
of
talk
about
actually
SharePoint
framework
in
the
context
of
the
provisioning.
A
So
how
do
we
actually
make
SharePoint
framework
solution
to
get
deployed
across
all
of
the
sites
automatically
already
with
the
existing
capabilities?
What
we
have
within
the
shipment
online
and
then
slightly
touching
also
what's
coming
up
in
the
future
and
because
that's
relates
that's
that's
kind
of
the
classic
scenario
of
hey
I.
Have
tens
of
thousands
of
sites
or
I
have
thousand
sites
or
site
collections
and
I
need
to
make
sure
that
my
customization
is
available
in
all
of
those
sites?
So
how
do
I
make
that
happen?
A
And
actually
you
can
do
that
already
today
and
today,
I'm
gonna
do
a
demo
and
you
should
never
ever
start
by
a
presentation
by
apologizing.
But
let's
see
how
well
my
demo
well
I
know
that
the
demo
works,
but
I
haven't
had
a
massive
amount
of
time,
I'm
polishing
up
stuff,
because
this
demo
is
targeted
mainly
for
ignite
but
I
wanted
to.
We
wanted
to
actually
show
you
guys
also
that
it's
doable
already
today
with
the
pre-release
stuff,
which
is
available
in
the
dev
branch,
partly
and
BMP,
partly
and
other
stuff,
and
all
of
that.
A
So
let's
talk
about
that
one
in
a
second
now.
The
second
thing
what
I
wanted
to
actually
quickly
talk
about.
This
is
something
which
came
up
I'm
actually
in
the
internal
SharePoint
internal
Microsoft
discussions,
and
then
we
realized
that
interesting.
We
have
not
actually
explained
anywhere
properly
in
our
documentation
that
you
can
already
today,
with
within
the
SharePoint
Online
related
on
the
modern
Cribs
in
the
shipment.
You
guys
do
native
out-of-the-box
classification
of
the
sites,
so
I'm
gonna
walk
through
that
demo
today,
as
well.
A
I
think
we'll
spend
maturity
of
the
time
on
on
the
automation
of
the
of
pushing
SharePoint
framework
stuff
on
the
sites
in
that
live.
Demo
and
I'll
have
a
look
on
dying
window
and
we
can
have
an
interactive
demo
based
on
your
your
input,
but
key
point
is
to
demonstrate
how
would
I
able
to
push
shape
and
framework
extensions
and
wet
words
to
the
sides
cross?
All
of
my
Tenon's
and
the
second
part
of
the
demo
and
second
demo
today
will
be
around
controlling
doors
of
oxide
classification
in
the
in
the
native
provisioning
flow.
A
A
Indeed,
this
wall
has
a
good
comment,
so
the
themes
app
has
an
indicator
about
growth.
Classification
it'd
be
nice
to
learn
how
to
control
that
yes
and
I'm
gonna
be
like
I.
Usually
it
usually
ends
with
transparent
and
open
on
this
one
again,
so
apparently
we
shipped
that
capability
actually
already
months
ago,
and
but
nobody
actually
understood
that
it
would
make
sense
to
explain
for
the
community
and
customers
and
partners
how
to
actually
do
that.
A
A
Yes,
but
it's
a
positive
surprise.
Patrick
come
on
now,
moving
on
on
things,
so,
let's
actually
a
few
announcements
at
kind
of
a
classic
reminders
on
the
things.
If
you
will
be
in
ignite
later
this
month,
there
will
be
four
specific
sessions
on
the
sharepoint
development,
one
kind
of
a
generic
session,
one
from
Luca
and
Powell,
or
around
SharePoint
framework
equipments
and
extensions
one
from
me
and
urban
around
the
PMD.
A
We
also
have
a
pre
day,
I'm,
not
sure,
if
there's
any
free
spots
on
that
free
day,
but
in
the
free
day
there's
the
office
debt
free
day
where
we
will
have
MVPs
and
me
and
engineering
people
from
graph
teams
and
shipment
talking
about
the
seochon
develop
talking
about
the
development
aspects,
that's
mainly
I
would
say
200-300
level.
So
it's
high-level
if
you're
not
super
familiar
on
the
SharePoint
framework.
That
might
be
a
good
case
and
could
do
time
to
jump
in
and
learn
about
those
stuff.
A
If
you
are
in
ignite,
if
you're
not
in
ignite
you'll,
get
the
material
using
alternative
options
as
well.
What
else
quickly
tucked
mean
pointing
on
let's
say
and
the
usage
if
this
is
kind
of
a
classic
slide?
This
is
us
promoting
hey
people
are
using
a
SharePoint
and
people
shared
the
ship
on
development
is
case
crowing
and
it.
Actually.
It
is
a
good
thing
because
most
likely
you
in
this
call
and
watching
people
who
are
watching
the
video
you
are
actually
working
with
in
a
SharePoint,
and
you
might
be
wondering
that.
A
A
So
in
the
BMP
we
can
clearly
see
that
the
remote
provisioning
models
and
and
the
automation
and
business
automation
models
are
growing
significantly,
so
the
BMP
components,
so
the
BMP
or
BMP
PowerShell,
was
used
in
more
than
eight
thousand
four
hundred
times
within
last
month,
and
that's
quite
a
lot.
I
think
we
had
three
more
than
two
thousand
three
thousand
tenants
with
site
provisioning,
the
ancient
site,
provisioning
engine
usage,
so
definitely
not
alone.
If
start
using
the
engine
in
general.
A
The
second
Canova
chart
on
the
slide
is
showing
also
the
direction
where
we're
heading
with
in
the
from
a
customization
perspective.
So
more
and
more
people
are
actually
using
javascript
to
customize
a
sharepoint
and
sharepoint
online
and
which
is
understandable
because
sharepoint
framework
is
giving
you
those
options
in
a
more
flexible
way
and
also
from
a
more
current
eight
way.
So
the
PM
PHAs
core
helps
an
adaption
of
the
javascript
customization
and
that
uses
is
growing
quite
significantly
as
well.
A
There's
that
pretty
much
at
three
times
more
people
and
the
unique
visitors
within
a
sharepoint
organization
in
github,
which
is
a
great
thing,
because
we
absolutely
want
to
people
to
find
us
and
want
people
to
find
the
samples
and
people
to
use
the
samples
and
and
obviously
github
is
a
great
channel.
To
also
ask
questions.
A
If
you
have
find
issues
using
the
s/pdif,
docs
issue
list
and
reporting
issues
on
the
SharePoint
framework
and
so
on,
cool,
that's
just
a
a
quick
kind
of
an
on
a
quick
topics
on
the
random
random
announcements
on
the
ownership
on
things.
So
I
didn't
have
anything.
Let's
say
mind-blowing
at
this
point,
because
we're
heading
closer
and
closer
or
ignite
and
and
the
reality
is
that
in
ignite
will
do
more
mind-blowing
announcements.
A
So
obviously
the
big
changes
will
be
done
and
announced
in
ignite,
or
at
least
maturity
of
that,
and
that's
why
we
can't
actually
leak
too
much
information
at
this
point
now
what
I
wanted
to
really
spend
the
maturity
of
today
is
on
the
underside,
provisioning
and
SharePoint
framework
combination,
because
this
is
a
big
thing,
and
this
is
not
just
about
the
sharepoint
framework.
It's
also
around
hey.
When
is
the
modern
experience
is
mature
enough
so
that
we
can
a
provision
and
monocyte
be
modify
the
modern
site
based
on
our
requirements
and
see.
A
Would
our
widgets
do
the
modern
sites
based
on
the
business
requirements
and
I'm
gonna
shown
that
today
and
we're
pretty
closed
on
saying
yep?
It's
time
so,
basically,
you
can
already
today
achieve
all
of
these
things.
So
if
you're
looking
into
or
saying
or
considering
the
fact
that
hey,
if
I
move,
that
the
modern
experience
is
because
or
can
I
do
X
&
Y
Z
in
a
modern
expert.
This
probably
you
really
really
want
to
carefully
have
a
look
on
that,
because
most
likely
you
can
do
that
already.
A
The
techniques
or
approaches
might
be
slightly
different
again,
then
in
classic
customizations
in
SharePoint
Online
using
the
JavaScript
injection
or
whatever,
but
you
can
take
advantage
and
you
will
get
an
mandates
on
the
on
the
out-of-the-box,
modern
advantages
and
and
capabilities
on.
The
modern
experience
is
that
sounded
like
a
marketing
statement,
but
anyway,
and
you
probably
understood
what
I
mean
with
that.
So
let's
talk
about
this
one.
So
how
do
we
one
of
the
key
requirements,
obviously
to
be
able
to
use
the
SharePoint
Online?
A
A
So
this
modern
experiences
have
a
no
script
tags
enabled
and
only
way
you
can
actually
add
these
widgets
to
their
sites
and
Java
scripts
to
the
sides
is
by
using
the
SharePoint
framework,
and
that
means
that
the
tenant
administrator
has
to
approve
that
customization
to
be
present
within
the
site.
Client-Side
web
fonts
are
NT
8,
since
February
extensions
are
now
in
release
candidate
status
and
we'll
head
down
and
closer
we're
getting
closer
and
closer
to
the
GA.
So
that's
gonna
happen
relatively
soon.
A
I
cannot
give
you
the
date,
but
you
can
guess
when
that's
going
to
happen,
but
I'm
not
gonna
confirm
that.
But
that's
that's
gonna
happen
pretty
soon
and
really
the
key
point.
What
I'm
gonna
show
today
in
the
live
demo
as
well,
is
that
how
do
I
then
take
one
of
these
period,
widgets
a
web
part
or
an
extension,
or
both
back.
A
So,
first
of
all,
when
we
create
the
customization
the
shipment
framework
customization,
we
need
to
first
of
all
make
a
decision
whether
we
host
that
JavaScript,
because
the
JavaScript
in
the
shape
and
frame
resolution
is
not
getting
deployed
in
SharePoint.
Well
technically
can
be
deployed
on
SharePoint
as
well,
but
it
has
to
be
hosted
in
CDN.
A
Then
you
actually
the
point,
and
then
you
deploy
your
package
to
the
app
catalog,
and
this
is
something
which
we
technically
can
automate
as
well,
but
to
be
able
to
automate
that
that
identity
has
to
have
a
tenant
administrative
permissions,
and
this
is
really
the
one
step
most
likely,
which
will
not
be
automated
within
this
process,
because
the
tenant
administrator
would
like
to
have
a
sign
off
that.
Okay,
what
are
those
widgets
which
we
will
approve
within
our
tenant
and
those
are
the
things
which
we
add
into
app
catalog.
A
Now,
just
looking
at
the
aisle
window,
yeah
I
know
you
guys
won't
tell
it's
only
only
in
a
small
group
of
people
in
here.
Let
me
take
something,
and
now
the
solution
is
actually
putting
in
the
app
catalog.
When
the
solution
is
put
in
the
catalog.
The
solution
can
have
two
different
statuses.
It
can
be
either
tenant
scope
or
it
might
not
be
a
tenant
scrap
if
it's
a
tenant
scope
solution-
and
it
is
enough
for
the
administrator
to
approve
that
once
in
an
app
catalog
and
the
solution
is
available
across
all
of
the
sites.
A
If
it's
not
a
tenant
scope
solution,
the
shipment
framework
solution
has
to
be
explicitly
installed
on
each
site,
where
you're
planning
to
use
that,
and
that's
one
of
the
key
points
and
one
of
the
key,
let's
say
improvements
which
were
released
back
in,
was
it
July
early
August
as
part
of
the
tenant
scoped
capabilities?
But
now
the
solution
content
actually
defines
what
it
means
that
the
solution
is
available
within
the
within
the
site
level.
A
If
the
SharePoint
framework
solution
contains
a
web
part
and
it's
a
tenant
scribe
solution,
the
web
part
is
immediately
available
within
the
site
level
and
that's
super
cool.
So
you
don't
actually
need
to
install
anything
on
a
site
level.
Your
web
part
is
available
across
the
crustose,
like
all
of
the
site
collections
and
all
of
the
pages.
If
your
solution
contains
an
extension
nope,
so
application
customizer
or
a
field
customizer
or
a
ListView
common
sense,
you
still
need
to
associate
that
extension
to
the
right
object.
A
So
you
need
to
still
go
to
the
site
level
and
say
hey
within
this
site:
collection,
level
or
within
the
site
level
or
within
the
list
level.
Let's
associate
this
application
customizer
in
and
that
step
is
the
thing
which
probably
is
still
slightly
confusing
for
people.
What
do
we
need
to
do
on
how
to
make
that
happen?
But
luckily-
and
we
can
actually
use
PNP
provisioning
for
that,
so
we
can
easily
create
SharePoint
remote
provisioning
template
using
the
latest
schema,
which
was
released
with
well
I.
A
Think
technically,
it
will
be
released
tomorrow
or
Monday
at
the
latest
version,
and
you
can
easily
create
a
template
which
you
can
easily
automate
to
be
applied
across
all
of
your
let's
say:
10,000
site
collections
in
a
loop
in
a
PowerShell
or
between
the
code
where
you
are
then
enabling
these
capabilities
to
be
available
and
that's
nothing
more
than
a
classic,
be
MPI
provisioning
templates,
which
you
can
just
configure
in
a
certain
way
that
you
get
those
client-side
component
ideas
our
ideas
on
a
place.
So
let
me
walk
through
this
one.
A
Let
me
walk
through
this
one
so
and
I
can
answer
question
of
us
as
we
move
along
and
I.
Do
apologize,
like
mentioned
I'm
sure
that
the
demo
works,
but
I
didn't
have
a
time
really
really
really
polished
to
demo.
It's
been
a
crazy
day,
finding
some
bug's
here
and
there
and
all
the
same
stuff
up,
but
let's
actually
have
a
look
on
the
under
scenario.
A
What
we're
gonna
do
here,
so
what
we
wanted
to
do
it
is
to
make
sure
that
all
the
main,
our
site
automate
our
SharePoint
framework
solutions
or
customization,
not
the
solution,
customization
to
be
available
across
all
of
the
sides.
What
we
have
so
what
we
need
to
do
is
certain
things
so,
depending
on
how
familiar
you
are,
which
happened,
fame
resolution
I'm
going
to
quickly
explain
this
in
a
solution
level
as
well.
So
in
the
Chapman
framework
solution,
we
have
a
package
solution,
Chason
which
defines
what
is
that
solution.
A
So
what
does
the
solution
actually
do?
And
in
here
right
now
for
the
tenon
scope
configuration
we
have
to
set
this
skip
feature
deployment
equals
true,
and
this
can
be
set
for
any
SharePoint
framework
solution.
One
serpent
solution
can
contain
multiple
webparts
extensions.
Whatever
it
doesn't
matter,
it's
a
one
solution
and
if
I
set
that
to
be
true,
everything
inside
of
that
solution
is
then
available
to
be
associated
to
the
sides
without
the
solution
getting
deployed
to
the
site
level.
Hopefully
that
make
sense.
A
So
what
I've
done
here
is
that
I
have
actually
quite
a
few
solutions.
So
let
me
go
to
my
app
catalog
I've
installed
now
for
solutions
and
from
these
we're
going
to
use
I
think
tree
automatically
within
the
demo.
So
I
have
my
ugly
field.
Extension
customizer
I
have
a
a
react
to
do
basic
web
part
and
I
have
a
app
extension.
A
A
really
simplistic
extension
will
polish
all
of
this
up
for
the
Ignite,
but
you
can
actually
understand
the
flow
already
today
and
so
I
have
these
SharePoint
framework
solution
installed,
but
none
of
this
is
getting
installed
on
the
site
level
they
are
getting
deployed
on
and
on
this
tenant
scope
by
adding
them
on
the
app
catalog
and
because
of
the
setting
was
set
skip,
feature
deployment.
We
can
actually
push
that
solution
to
be
in
quotes
available
in
site
level,
site
level.
A
So,
if
I
create,
let
me
actually
let
me
not
confuse
you
on
this
one,
and
this
is
the
section
which
I
didn't
actually
do
any
practice
or
I
would
actually
explain
this
to
you
in
an
understandable
Foreman.
So,
if
I
create
now
are
quickly
a
new
side,
a
modern
team
side.
Let's
call
this
test
test,
seek
zero.
Five
and
public
settings
is
finds.
Let's
click
OK,
that's
gonna,
take
a
few
seconds
and
immediately
when
the
button
is
getting
active,
we
know
that
the
site
has
been
created
there
we
go,
we
can
go
to
the
site.
A
So
now
we
have
this
site.
Scientists
now
created
without
anything,
getting
deployed
on
the
site
explicitly
using
the
add,
an
app
functionality.
If
I
now
go
to
the
Welcome
page,
if
I
put
the
space
on
the
edit
mode
and
if
I
scroll
down,
for
example
in
here
I,
can
already
immediately
see
my
custom
to
the
web
part
which
I
can
configure
and
that's
because
of
the
tenon
scope.
A
A
So
in
the
shipment
framework
extensions,
how
do
I
get
those
to
be
available
within
these
sites
which
are
getting
provisioned
potentially
using
API
is
PowerShell
or
whatever,
whatever
processes,
and
let's
actually
have
a
look
on
them
and
also
how
would
I
get
this
web
board
automatically
available
within
the
Welcome
page
of
the
site?
So
how
do
I
make
sure
that
whenever
the
end
user
comes
to
this
slide,
my
custom
web
parts
and
configuration
and
everything
else
is
available
within
this
modern
site
automatically
for
them?
So
they
don't
have
to
manually
manually
even
modify
the
side.
A
So
let's
get
rid
of
that
web
part.
Save
that
change
these
so
we're
back
on
the
original
stage
with
this
web
part
with
with
the
sites.
So
what
I've
done
here,
let
me
go
to
my
code
and
let's
actually
close,
that
one
and
let's
actually
slightly
serve
so
this
is
how
would
I
put
it.
This
is
still
early
because
we
haven't
actually
pushed
out
the
PMBA
September
release
and
that
will
actually
have
a
native
support
on
what
I'm
doing
right
now,
I'm.
A
Actually,
as
my
solution,
Explorer
I'm
running
the
dev
version
of
the
PMP,
a
core
component,
which
will
be
released
as
a
nougat
on
Monday,
probably
Friday
or
Monday,
but
I'm
running
that
locally
within
my
boxer.
I
can
actually
demonstrate
you
what's
happening
here.
This
one
is
a
console
application,
but
you
can
absolutely
do
the
same
using
a
powershell
whenever
we
get
this
one
working
whenever
we
get
the
September
release
out
and
what
I'm
doing
here
is
that
I
could
actually
potentially
extract.
A
Let's
actually
do
that
as
well.
So
let
me
show
you
an
extraction
quickly.
So
if
I'm
gonna
go
to
definition
and
I'm
just
going
to
double
check,
what
is
the
name
of
the
file
but
I'm
outputting
from
existing
side
good?
So
let's
go
to
my
nap
on
this
side.
Let's
go
to
a
site
which
has
been
already
modified,
so
we
can
see
that
this
side
has
been
already
modified.
There's
modifications
on
the
side.
We
can
probably
say
that
there's
modification
in
the
front
page
there's
multiple
sections
and
all
of
this
stuff.
A
It's
actually
slightly
modify
this
more
at
a
a
text
here
which
is
saying,
seek
demo
live
extraction
and
maybe
at
a
it
doesn't
really.
We
can
have
to
do
a
web
part
here
as
well.
It
doesn't
really
matter
for
this
quick
demo.
So
now,
I
have
a
custom
welcome
page
and
you
can
see
that
I
have
custom
associations
on
this
live
site,
so
I'm
gonna
take
that
URL
move
back
on
my
coat
and
like
that.
A
We
are
using,
in
this
case,
we're
using
just
native
code,
but
you
can
do
this
in
a
PowerShell
whenever
we
get
the
September
release
out
which
be
on
Monday
did
I
actually
copy
that
success
successfully
assigned
it
good.
There's
my
site,
there's
my
get
provisioning
template
I'm
gonna
go
here
and
put
a
breakpoint,
so
we
can
actually
quickly
have
a
look
on
what
we're
doing
from
a
code
perspective
and
not
we're
not
going
to
deep
dive
on
a
code.
A
The
key
point
here
is
to
show
you
the
capabilities,
rather
than
deep,
diving
on
on
what
I'm
actually
doing,
but
we're
using
the
classic
BMP
provisioning
engine
and
the
provisioning
template
creation
information
we're
just
adding
we're
interested
on
page
content
fields
and
lists,
so
we're
not
outputting
everything
from
the
site
and
just
the
subset
of
objects
in
the
site
and
then
we're
running
this
get
provisioning.
Template
extension
from
the
web
object.
So
as
long
as
you
have
a
reference
on
the
BMP
season
extend
a
core
object.
A
You
will
have
this
method
available
and
then
you're
able
to
extract
the
template
from
a
live
site,
so
I'm
going
to
put
a
breakpoint
over
there
and
let's
actually
execute
that
one.
At
this
point,
my
console
application
is
running
on
a
different
window,
but
I
can
actually
see
how
it
runs
through
the
individual
objects.
Now
it's
fields
list
instances
and
all
of
the
additional
settings
as
well
yeah
after
the
list
instance
running
through
a
list
instance.
A
This
does
take
a
while
because
lists
are
pretty
complex
in
SharePoint,
but
then
it
goes
to
the
actual
Beaty's
and
then
it
analyzes
the
base
structure,
the
sections,
columns,
custom,
webparts
settings
and
all
of
that
stuff,
and
it
actually
extracts
that
to
be
out
of
the
site
as
well.
So
that
section
didn't
take
that
long.
Now
in
this
demo,
yes
I'm
going
to
save
this
as
an
XML
like
you
know,
probably
typically
like
with
anything
in
the
BMP
provisioning.
You
do
not
have
to
say
realize
anything
and
the
serialization
is
absolutely
optional
thing.
A
A
And
now
my
visual
studio,
so
no,
it
actually
went
in
a
different
screen.
There
we
go
so
the
template
object
is
an
object
and
the
template
object
contains
everything
within
the
site.
What
we
extracted,
for
example,
the
client-side
pages
we
have
on
one
page,
which
is
called
home.aspx
in
that
page.
We
have
a
one
section
in
that
section.
We
have
six
controls
in
that
con.
In
those
controls
we
have
a
different
set
of
information
in
those
controls.
A
For
example,
in
this
particular
case,
it
is
a
text
control
and
we
were
doing
and
that's
the
information
within
the
text
control.
So
basically,
we
extract
everything
out
of
the
site,
also
including
everything
from
a
page
structure,
perspective,
the
column,
sections
controls
and
the
web
parts
inside
of
the
thing.
And
then,
if
you
want
again,
if
you
want
to
reapply
that
or
for
future
saving
this
from
a
one
tenant
and
apply
that
to
another
tenant,
that
would
be
a
one
option
or
whatever
you
can
absolutely
say,
realize
that
in
an
XML
format,
as.
B
A
Somebody
might
be
saying
why
do
you
not
extract
all
of
the
content?
Well,
guess
what
doing
that,
which
require
a
significant
amount
of
resources.
Plus
there
is
a
significant
amount
of
existing
migration
providers,
which
are
doing
an
awesome
job
and
the
PMB
is
mainly
there
for
configuration
and
template
handling
not
for
competing
against
the
content.
But
technically
you
can
absolutely
provision
multiple
pages.
So
what
we
extract
is
just
a
welcome
page.
A
I
could
actually
take
this
home
page
from
here
and
just
copy
that
either
programmatically
in
the
code
OOP
not
like
that
programmatically
in
the
code
or
just
practically
in
my
visual
studio
and
then
I
could
have
easily
update
that
to
be
home
number
two
and
that's
it
pretty
much
and
then
I
can
modify.
What's
the
content
is
out
of
the
page.
So
this
way
you
would
be
able
to
have
multiple
pages
in
the
template
now
quickly.
As
you
can
see,
we
extract
two
sections.
We
extra
columns
content.
A
A
B
A
Is
how
you
this
is
the
easiest
way
to
figure
out
what's
the
structure?
Obviously
there
is
a
schema.
There
is
a
document
that
way
of
doing
just
in
a
in
outside
of
without
extraction
as
well.
Now,
in
my
demo,
we
wanted
to
concentrate
on
okay.
How
do
I
apply
certain
things
with
the
SharePoint
framework
solutions,
SharePoint
framework
as
configurations
to
this
existing
sites,
so
I
have
already
prepared
previously
this
template
by
partly
extracting
partly
manually
modifying
the
XML
and
I,
and
we
can
analyze
what's
actually
included
in
the
template.
A
So
in
this
template
we
will
deploy
a
new
field
called
a
percent,
though
this
is
the
same
percent
filled
with
if
you
have
done
SPF
ex
extension
tutorials.
This
is
exactly
the
same.
What
we're
doing
there,
but
using
a
different
option
or
different
ways
of
achieving
this,
but
the
key
point
noticed
here
is
that
I'm
actually
doing
Association
to
a
client-side
component
ID
and
immediately,
when
I
do
this
and
apply
this
template.
A
This
will
mean
that
the
field
customizer
with
that
manifest
ID
is
I'm
not
automatically
associated
to
the
percent
field,
which
means
that
as
long
as
the
field
customizer
has
been
deployed
using
the
tenant
deployed
option,
the
field
customizer
is
automatically
available
within
the
site,
even
though
you
don't
explicitly
install
the
solution
to
the
side.
Hopefully
that
did
make
sense
the
same.
Actually.
So
what
I'm
doing
here?
A
Let's
have
a
look
on
so
we're
provisioning,
a
one
field
and
adding
that
SPF
X
Association
and
that
field
then
we're
provisioning
and
orders
feel
a
list
where
we
actually
use
that
field.
So
that
will
mean
that
there's
an
existing
than
additional
list
available.
Whenever
we
apply
this
template,
we
also
apply
client-side
pages
I
was
we
apply
a
new
home
aspx
and
that's
using
the
overwrite
true
option,
which
will
essentially
overwrite
the
native
out-of-the-box
welcome
page,
and
in
here
we
also
have
well.
We
have
the
newsreel
webparts
I've
acted
with
the
web
part.
A
We
have
a
custom
text
there.
Additional
customs
I
hope
that's
a
content
for
the
custom
text.
We
have
a
custom
web
part
which
is
essentially
the
same.
This
is
actually
referring
the
control
ID
and
the
manifest
ID
of
our
to
do
work
and
because
again,
the
to
do
web
part
has
been
deployed
using
the
tenon
scope
option.
A
The
only
thing
what
we
need
to
do
is
associate
these
IDs
on
the
right,
location
and
voila,
and
those
will
start
working
over
it
in
the
Sun
and
a
scroll
down
slightly
there's
one
more
customization
here,
which
is
the
application
customizer.
So
this
is
for
doing
custom,
header
and
footer
within
a
site
whenever
this
has
been
applied
and
it's
using
the
custom
action
option
and
it
has
the
client-side
component
ID
as
well,
and
we're
using
the
clients
that
component
properties
there
as
well,
can
actually
get
rid
of
that
one,
because
we
don't
need
that.
A
So
this
one
has
to
must
match
with
the
manifest
ID
of
the
application
customizer
now
quickly
explaining-
and
this
might
be
super
familiar
for
you.
But
as
an
example.
If
I
take
this
application,
customizer
every
single
SharePoint
framework
component
has
a
unique
ID
in
the
manifest
and
that's
essentially
the
idea
where
we're
associating
these
things
and
as
long
as
this
solution
has
been
deployed
to
that
catalog
shipment
will
realize
that
hey
okay
within
this
site,
because
the
application
customizer
is
existing
with
that
ID
I'm
gonna
render
this
JavaScript
on
the
on
the
page
Bert.
A
You
just
don't
admit
it
yourself,
so
cool,
okay,
let's,
let's
have
a
look
at
me,
talking
quite
a
lot.
So
let
me
actually
do
this
in
practice.
So,
let's
get
rid
of
the
all
of
that
kit.
We
want
to
apply
the
template
and
let's
go
to
our
newly
created
site.
We
just
created
new
site,
which
was
the
test
as
sick
five,
not
customized,
and
nothing
has
been
installed.
This
is
the
existing
site.
There
is
an
API
is
to
create
modern
groups.
You
can
easily
do
that.
A
That's
not
a
problem
and
after
creating
the
modern
group,
it's
just
matter
of
modern
site,
it's
just
a
matter
of
applying
a
template,
so
a
doctor
bauxite.
Let's
go
back
into
code
and
again
we
have
this
in
the
powershell
format
as
well
we're
starting
from
next
week,
I'm
gonna
put
a
breakpoint
in
somewhere
in
here.
That's
actually
good
at
Prague
mundo
other
so
well,
we
know
when
it's
actually
starts
processing.
A
So
what
we
do
is
that
we
load
that
template
again.
It's
a
template,
object,
template
object,
you
could
programmatically,
create
the
whole
object
and
and
add
additional
objects
and
everything
else
and
configurations
to
it.
But
the
XML
is
is
pretty
nice
because
you
can
serialize
and
save
that
for
the
future
usage
and
now
we're
applying
the
template
and
clicking
f10
being
all
it
is
actually
showing
our
progress
that
we
do
have
here
presentation
of
the
steps.
A
So
if
you
list
instances
running
true,
it
shouldn't
take
too
long
because
there's
only
one
orders
list
getting
created
and
then
the
client
pages
and
client
page
is
processed
and
then
it
runs
quickly,
custom
actions
and
web
settings,
and
we
are
all
done
so
now.
If
our
magic
is
fully
applied,
we
go
to
the
side,
we
press.
Let
me
actually
do
this
front
processor
there's
our
sites,
I
I,
think.
A
Yes,
I
did
yeah
I
didn't
update
this
as
that
one
okay.
So
let
me
do
this,
so
this
one
is
a
leftover.
No,
that's
the
newest!
No!
This
is
out
of
the
box.
Okay,
thank
you.
This
card
chain
see
is
yes,
let's
get
to
the
previous
there
we
go
I'm
gonna
actually
move
back
on
my
code.
Let's
update
the
URL,
yes
I
did
it
helps
if
you
update
the
URL
accordingly
test
six
five
pressing
f5
to
wrist
one
breakpoint
still
waiting,
but
this
doesn't
take
too
long.
A
There
we
go
now
we
can
say
the
console
actually
running
and
two
out
of
five
christine.stone
senses
Earvin.
We
need
to
do
something
for
the
list.
No
nevermind.
There
are
so
many
things.
What
the
list
insolence
object
hunter
is
checking
and
verifying
when
it's
actually
doing
the
Delta
handling
and
comparison
and
applying
the
settings.
A
If
something
has
been
modified,
that's
why
it
takes
a
while,
if
you
don't
have
any
custom
list
instance
configurations
in
your
template,
you
can
absolutely
let's
keep
that
either
programmatically
or
just
keeping
that
in
a
template
there
we
go
going
back
on
the
site,
there's
the
second
phone
number.
Five
and
yes,
hopefully,
f5.
A
We
have
a
custom
welcome
page
with
our
custom
web
part
with
our
application.
Customizer
everything
is
up
and
running
within
a
matter
of
seconds.
We
can
see
the
new
orders
list
in
here.
Orders
list
has
been
configured.
We
still
have
the
same
application
customizer
in
every
single
page
of
the
site.
If
we
add
a
new
item
to
the
list,
we
should
see
also
our
our
field.
Customers
are
getting
activated
on
this
list,
as
we
can
see
that
so
the
percent
is
getting
rendered
using
alternative
UI.
It's
find
it
here.
It
item
B
and
90.
A
So
key
point
what
I'm
sure,
what
we're
trying
to
here
kind
of
explain
and
I'm
repeating
this
many
many
times
as
you
can
see,
there
is
no
solutions
installed
on
the
site
and
I'm
still
able
to
push
all
of
my
customization
to
the
site
as
long
as
those
customization
has
been
marked
using
the
tenon
scope
deployment
option-
and
this
way
I
also
have
only
one
location
to
maintain
one
location.
To
update
all
of
my
solution,
you
I
would
now
go
and
update
my
solution
and
chava
script.
A
Implementation
of
my
haters
I'll
just
go
to
the
App
Catalog
I'll,
just
upload
a
new
version
voila.
It
will
reflect
all
of
the
chances
within
all
of
the
sites
and
that's
super
cool.
So
all
of
the
things
well
technically
super
super
happy
personally
as
well,
and
because
this
proves
that
we
are
able
to
do
full
automation
of
the
structures
and
welcome
pages
and
custom
web
parts
and
extensions
using
the
remote
API
story
and
the
remote
provisioning
story
and
you're
able
to
start
adapting
the
modern
customer
modern
experiences
in
SharePoint
Online.
A
A
That's
super
cool,
bye,
ignite
and
pretty
much
well
bye,
ignite
or
closer
reading
within
the
close
timeframes.
We're
able
to
do
this
within
the
communication
sites
as
well
so
programmatically
create
the
communication
side
and
also
extract
or
apply
settings
in
the
communication
sites
and
making
sure
that
all
of
these
things
and
the
customizations
are
available
there
well.
A
B
A
A
There's
an
awesome
question
from
the
Russian,
probably
so
I
am
personally
responsible
on
this
from
a
ship
and
engineering
perspective.
So
if
I
put
my
engineering
hat
on,
we
are
looking
into
absolutely
having
a
support
for
installing
specific
add-ins
or
SharePoint
framework
solutions
to
a
site
level
natively
within
a
chevron.
Now,
if
you
want
to
automate
that
using
the
be
using
for
multiple
sites,
then
we'll
absolutely
add
that
support
in
the
PMP
provisioning
engine
or
hover
about
it.
A
That's
the
wrong
way
of
putting
that
whenever
the
native
support
for
installing
add-ins
from
App
Catalog
at
the
internship
one
framework
solution
from
and
catalog
that
any
sites
within
your
tenant
is
available,
that
support
will
be
absolutely
added
in
the
in
the
PMP
provisioning
engine
as
well.
That's
the
right
way
of
putting
that.
A
So
that's
timing
for
that.
One
I
can't
give
you
an
exit
timing,
but
it's
it's
coming
pretty
soon,
most
likely
not
by
ignite,
so
we're
looking
into
having
that
support
relatively
soon
as
well.
But
then,
whenever
we
have
the
native
API
and
support,
then
it
takes
a
while
to
get
it
in
the
PMB
provisioning.
And
after
that,
you
can
automate
add-ins
getting
deployed
as
part
of
the
provisioning
template
as
well,
and
we
do
know
that
that
they
say
math.
There
is
a
massive
demand
for
them.
A
One
thing
maybe
to
mention
on
that
one
we're
looking
into
right
now
having
that
as
a
capability
with
supports,
adding
and
adding
from
the
catalog.
So
still
in
the
future.
We
can
not
technically
there's
there's
multiple,
that
that
is
a
super
challenging
thing
to
do
in
the
future.
We're
not
looking
into
having
an
API
to
install
add-ins
from
the
store
to
your
individual
sites
in
a
site
collection,
because
that
has
a
license
and
implication
and
there's
multiple
there's
so
many
variables
within
the
audience
in
the
store
and
that
gets
super
super
complicated.
A
B
A
And
then
there's
the
the
second
dimension,
which
the
sonic
is
mentioning
that
which
is
the
site
collection,
scope
that
catalog
and
that's
something
which
what
we
are
working
on
as
well.
But
I
can't
give
you
a
timeline
on
when
that
will
be
available,
and
that
really
the
main
point
of
that
one
is
that
you're
able
to
then
provide
SharePoint
framework
solutions
specifically
available
within
a
one
site
collection
rather
than
giving
them
and
forcing
them
to
available
Christina.
So
that's
really
the
main
purpose
of
that
one
good.
A
Now
the
second
Emma.
What
I
wanted
to
do
today
if
there
and
we
can
have
a
look
on
the
other
questions
which
is
coming
into
an
window
what's
around
the
policy
settings
of
of
the
of
the
sides?
I'm
gonna,
do
a
live
demo
on
this
one
in
our
MS
IT,
but
I
need
to
do
some
small
cleaning,
so
I'm
not
actually
showing
you
any
anything
which
I
shouldn't
be
showing
so
and
then
I'm
gonna
show
you
how
to
actually
configure
that
in
practice,
so
I'm
going
to
go
to
our
shape.
A
There
we
go
now.
You
can't
see
anything
which
is
super
super
super
confidential.
Now
this
is
from
the
Microsoft
MSI
T,
and
this
is
how
we
have
configured
the
classification
and
how
it
works
when
it
has
been
properly
configured
like
mention.
This
is
the
second
now
we're
moving
away
from
SPF
X
we're
moving
in
the
decide
classification
demo
to
quickly
walk
through
as
well.
So
when
we
are
creating
a
site,
let's
call
this
test
for
some
sick
zero.
A
It
doesn't
really
matter
that's
available
good.
You
can
see
that
we
have
this.
How
sensitive
is
your
data
option
in
MIT,
and
this
is
something
what
everybody
tenant
administrator
or
technically
the
azure
ad
administrator?
You
need
to
have
our
ad
permissions.
You
can
control
with
some
of
the
options
which
are
visible
in
here
and
you
can
also
control.
Where
does
this
link
actually
move
into?
So
in
our
case,
it's
pointing
to
a
km
a
kms
usage
guidelines
which
is
are
in
one
of
the
internal
URLs
in
the
end,
but
it
has
been
it's
just
essentially.
A
Msid
has
decided
what
are
their
settings,
but
you
can
do
this
within
your
tenants
as
well,
and
this
is
the
apparently
we
haven't
documented
this
anywhere,
which
is
or
properly
at
least
anywhere.
So
nobody,
nobody
seems
to
know
that.
So
in
my
case,
let's
actually
walk
through
I'm
selecting
the
NBI,
which
this
means
minimal
business
in
back
data
and
the
site
is
current,
create
it
and
whenever
the
site
is
actually
created
in
modern
few
seconds.
A
Luckily
it's
it's
no
there's
a
few
seconds,
rather
than
15
minutes,
like
a
costume
at
some
point
that
was
so
painful,
almost
like
farm
solution
deployments
on
the
local
development
boxes
and
you
recycled
the
application
pools
and
anyway
those
were
today's.
So
here's
my
site
and
the
site
classification
works
in
a
way
that
I
actually
since
I
selected,
the
NBI
I,
do
have
two
in
there
available
in
here
so
and
if
I
click
that
one
it
actually
pinpoints
again
on
the
same
URL,
which
was
the
guidance
URL
when
I
actually
created
the
site.
A
So
now
we
know
that
people
are
looking
into
how
to
make
this
happen.
I
I
seriously
I
had
a
one
internal
account
contacting
me
saying
here:
they
need
to
make
this
happen,
and
that
has
been
the
number
one
reason
why
the
customer
has
delayed
on
moving
into
the
modern
experiences
which
is
awkward
because
we
have
this
capability
already.
So
let's
actually
make
this
that
configuration
to
our
Testament
in
here,
which
currently
does
not
have
that
configuration.
A
So,
let's,
if
I
go
to
the
SharePoint,
if
I
go
to
the
create
site,
you
can
see
that
in
here
we
are
in
default
settings.
We
do
not
see
that
selection
of
the
classification
available.
So
the
question
is
how
do
I
enable
the
classification
within
this
site
collection?
So
let
me
start
that
one,
that's
a
different
demo
and
jump
into
a
powershell
in
here.
Now
these
these
settings
and
configuration
is
actually
documented,
and
let
me
show
you
the
URL
and
kind
of
paste,
this
URL
into
our
window
as
well.
A
It
is
actually
documented
in
this
Microsoft
a
shared
document
called
Azure
Active
Directory
command.
Let's
for
configuring
group
settings,
it
is
not,
however,
super
clear
anywhere
within
our
documentation
that
this
is
reflecting
or
is
visible.
These
configurations
are
visible
in
the
SharePoint
Online
device
whenever
you
actually
apply
this
settings-
and
that's
probably
the
the
missing
piece
within
our
messaging
there's
few
things
to
notice
in
here.
So
let
me
so,
for
example,
in
the
article
it's
saying
that
you
should
be
using
Azure
Active
Directory
PowerShell
version
2,
which
is
actually
wrong.
A
You
should
not
use
PowerShell
version
2.
You
should
use
the
preview
version,
so
this
is
the
general
availability
version
which
has
been
linked,
which
is
actually
missing
those
powershell
commandlets,
which
has
to
be
used
so
slightly
awkward
again.
But
if
you
go
to
the
azure
ad
preview
in
the
publisher
gallery,
that's
what
you
should
be
using
to
make
all
of
these
things
happen
and
I
do
apologize
on
behalf
of
Microsoft
once
again
or
lame
lame
documentation
on
this.
A
So
let's
do
that
so
I've
already
installed
our
ad
preview
on
my
machine
I'm,
going
to
connect
to
Usher
ad,
so
I'm
gonna
execute
that
one
on
my
favorite
PowerShell
development,
machine
or
tool
which
says
with
us
to
do
code.
So
let
me
actually
close.
All
of
these,
so
I
can
actually
get
that
actually
published
or
visible,
so
I'm
can
actually
sign
in
here.
A
I
think
I'm
in
this
tenant
stir
them
and
what
we
wanted
to
use
for
demonstration
and
let
me
actually
get
Tennant
sorry
way
too
many
process
like
that.
I
am
I'm,
not
super
super
well
prepared
for
today's
demo.
So
here
we
go.
This
is
the
writer
not
good
so
now
I've
signed
in
to
my
utter
ID.
We
can
see
there
for
a
sign
in
using
that
account
against
that
SP
plat
on
microsoft.com
tenant,
so
I'm,
going
to
slightly
zoom
this
more
so
I
can
actually
see
what
I'm
doing
now
in
here.
I
can
see.
A
The
current
configuration
of
my
unsure
director
is
setting
templates.
So
if
I
execute
f8
I
can
say
that
right
now
within
my
tenant
in
this
particular
tenant
or
sorry,
these
are
the
templates
which
are
available
for
the
configuration
and
we
want
to
use
the
group
unified
template.
So
what
we
do
is
that
we
use
Azure
Active
Directory
template
with
that
specific
idea.
So
that's
matching
actually
that
ID
in
here
so
I'm
gonna
actually
create
a
template.
A
There
we
go
and
I'm
gonna
actually
create
that
setting
template
for
that,
and
then
there
are
actually
I
need
to
up
there
we
go
and
then
there
are
certain
string
configurations
which
I
can
configure.
These
configurations
are
actually
document
it.
Let's
see,
if
I
can
find
that
in
the
document
in
the
in
here
so
in
here
in
the
MS
in
the
ad
documentation,
you
can
see
in
April
crew
of
creation
group,
a
creation
allowed
group,
ID
usage
guidelines,
URL
classification
descriptions,
different
classification
and
so
on.
So
you
can
actually
see
their
individual
settings.
B
A
Are
right
now
configuring
the
uses
guideline
URL
classification
lists,
so
individual
options
for
the
classification
list
and
what
is
the
default
classification?
So
let's
actually
do
that.
So,
let's
add
those
settings
in
our
object
and
then
we
actually
add
at
that
as
a
new
Azure
Active
Directory
setting
so
now,
I
can
quickly
double
check
my
configuration,
so
let's
actually
dump
all
check
that
I'm
not
checking
the
right
one.
This
is
my
current
a
shared
directory
settings
all
of
them
there's
my
group
unified
configuration
if
I
take
that
ID
super
intuitive
by
the
way.
A
A
A
There
is
a
some
level
of
a
caching
here,
I've
seen
this
today
when
I
was
actually
configuring
this
and
but
basically
those
configurations
will
enable
here
and
that
selection.
So,
just
out
of
curiosity,
because
I
was
seeing
this
in
my
on
tenant,
this
is
my
own
age,
three
tenant
which
I
use
for
testing
as
well.
A
But
as
a
summary,
yes,
live
demos
assertion,
so
there
is
a
delay
on
I
and
technically
to
be
fully
transparent.
I
did
saw
the
caching
for
some
reason
earlier
today
in
my
tenant
as
well.
So
there
is
a
small
delay
to
be
fair.
This
configuration
what
you
do
in
the
powershell
against
your
other
ad
is
almost
like
a
one-time
thing
and
you
design
your
classification
list,
you
design.
What
is
my
my
options
for
classification
and
what
is
the
default
classification
and
that's
it?
A
And
now,
in
my
case,
let's
just
double
check
this
one,
so
I'm
gonna
create
a
new
new
test
as
such
a
is
sick.
Six,
let's
create
this
one
or
the
default
value.
Let's
say
it's
bi,
because
it's
selecting
two
hbr
in
the
UI.
So
in
my
my
tenant
case
now,
if
I
select
this
one,
it's
going
to
create
the
site,
it's
going
to
show
that
label
within
the
site
whenever
the
site
somebody
success
in
design.
B
Yes,
absolutely
so
you
saw
the
off
the
Box
native
your
experience
to
create
modern
team
sites.
Yes,
if
you
ever
have
your
own
customization
custom
UI,
yes,
then
there
is
an
option.
There's
a
rest
call
and
this
graph
rest
called.
The
gate.
Does
give
you
the
these
options.
You
cannot
use
the
rascal
to
set
the
convenient
things.
So
if
the
confirmation
you
have
to
use
PowerShell,
but
you
can
simply
grab
options
and
URL
and
then
embedded
somewhere
and
your
user
interface,
if
you
want
to
do
something
similar,
yes
and.
B
A
Absolutely
now
coming
back
on
the
Russell's
question
as
I
know,
if
I
click
the
LPI
in
here,
it's
gonna
open
again
at
the
URL,
whatever
it
was
defined.
Coming
back
on
Russell's
question
around
hey,
that's
the
classification
change
anything
any
behavior
on
the
side,
not
at
least
for
time
being
so.
This
is
mainly
right
now
for
subscribing
a
classification
crossed
aside.
So
it
is
a
classic
requirement
for
the
customers,
at
least
in
New
Europe.
To
have
these
kind
of
settings.
A
Do
legal
restriction,
legal
guidance
and
guidance
as
well,
and
then
the
classification
tribes,
for
example,
custom
solution,
governance
checking
if
it's
a
hbi,
for
example,
you're
not
in
in
that
site,
will
disable
programmatically,
for
example,
sharing.
So
all
of
that
is
not
natively,
at
least
he
yet
within
a
SharePoint
Online
we're
looking
into
extending
let's
say
rules
and
guidelines,
and
all
of
that
behind
of
these
things
in
the
fusion.
A
A
Sharepoint
client
slide
I'm,
looking
into
the
object,
so
there's
my
site
class,
for
example,
in
the
season
the
site
class
in
the
season
has
a
property
called
classification
and
that's
where
the
information
is
stored
as
the
classification
property.
But
this
is
essentially
just
a
string
property
for
time
being,
which
is
essentially
storing,
then
the
value
of
h,
bi,
n
bi
and
then
it
is
being
presented
on
the
UI
or
the
order
header
section,
and
the
link
of
that
one
will
point
anyway
to
the
ones
for
our
location.
B
A
A
So
the
thinking
behind
of
that
that
there
is
a
great
question
from
Russell
around
the
extensions
availability
on
the
classic
versus
modern.
Let's
actually
get
to
this
one
and
talk
about
that
one
slightly.
So
the
thinking
is
made
on
Brandon
in
the
way
that
hey.
If
you
are
using
a
classic
experience,
then
you
can
use
the
classic
user
custom
action
and
chase
link
and
all
of
those
capabilities
we're
not
looking
into
having
extensions
supported
in
the
classic
pages.
A
The
web
parts
are
supported,
clients
are
web,
parts
are
supported
in
classic
pages
as
well,
but
that's
kind
of
an
exception.
The
reason
for
not
supporting
extensions
in
a
classic
experience
is
mainly
because
the
amount
of
work
that
would
require
it
would
actually
require
us
to
do
a
massive
massive
rewrite
of
the
whole
classic
experience.
Well,.
A
So
yes,
so
let's
be
super
super
clear
on
this
one.
The
different
data
is
not
on
the
site
type,
so
you
can
absolutely
have
a
classic
team
site
with
the
modern
experiences
so
and
within
the
modern
experience.
Is
this
extensions?
Wilbur
different
data
is
not
on
the
site
type.
It's
not
like.
If
you
select
the
modern
team
site,
you
will
have
to
use
SPF,
X
or
because
modern
team
science,
you
can
actually
fall
back
on
the
on
the
classic
experience
as
well.
A
As
long
as
there's
to
switch
to
classic
experience
link
views,
this
is
an
issue
yeah.
We
do
understand
that
and
there
should
be
a
option
to
disable
that
link
not
to
be
visible,
I'm,
not
sure.
If
that's
already
there,
it
should
be
there.
Maybe
I'll
ping
link
after
Chinkin
yeah.
Maybe
I'll
have
thing
linking
on
that
one,
because
that's
a
good
fun
good.
A
That's
actually
an
awesome
point
from
from
Chris
good
linker
knows
that
capability,
nor
p.m.
team
just
double-checking
quickly.
The
slides
yeah
that
the
site
classification
things
mentioned
in
here.
That
was
the
demo
and
there's
the
resources
for
those
will
get
this
one
mentioned
in
the
community.
Do
recording
notes,
so
you
can
easily
find
them
from
there
as
well,
but
I
think
that's
pretty
much
it
for
this
one
just
quickly.
Looking
into
the
questions,
if
there's
a
link
in
a
state,
where
did
it
is
this
link
that
the
classic
was
to
target.
B
A
Yes,
good
comment
from
Paul
Russell,
so
what's
next
for
in
SPF,
X
after
extensions
will
see,
will
I
think
it's
time
to
get
things
more
polished
and
more
mature
and
more
reliable
and
more
faster
and
everything
else.
Yes,
so
I
think
the
number
one
thing
what
we
want
to
do
so
considering
where
we
have
been
a
fall
past,
let's
say
one
and
a
half
years
with
SharePoint
is
this
kind
of
a
weird
middle
section.
A
Some
of
the
things
are
more
than
some
of
the
things
are
classic
and
then
the
the
end
users
are
super
confused
on
when
they
land
into
the
modern
or
when
they
land
they
do
classic.
Now,
with
extensions
with
acknowledge
announcements,
everything
else
we're
finally
getting
that
the
status
we're.
Finally,
the
modern
experience
is
is
I
would
say
fulfilling
enough.
It's
it's
consistent.
A
You
are
able
to
do
that
in
a
consistent
way,
and
that
means
then
that
we,
what
we
want
to
do
next,
is
more
and
more
in
Westham
polishing
that
making
that
more
controllable,
making
that
more
mature.
Obviously,
there
will
be
more
capabilities
in
the
future
as
well
more
options
in
the
future
as
well.
For
development
perspective
and
and
more
capabilities
and
from
a
SharePoint
capability
perspective,
we
are
obviously
looking
into
modernizing
more
and
more
and
more,
let's
say
classic
SharePoint
goodies
as
well.
B
A
Can
size
be
classified
if
they
are
created
from
the
SPL
admin
center?
I,
don't
think
they're.
So
there's
no
UI
foot
for
that.
For
now,
you
can
absolutely
then
execute
a
PowerShell
to
classify
them
afterwards
by
using
the
site
classification
for
building,
as
there
will
be
announcements
around
the
mall.
Let's
wait
for
ignite
ignite
will
bring
a
lot
of
things
new
stuff
on
the
table,
yeah.
So
on
a
lot
of
things
which
we
should
have
already
moved
on,
but
ignite
is
coming
pretty
soon
couch
I
think
that's
it
for
this
one.
A
So,
hopefully
the
demos
were
used
for,
hopefully
we
were
able
to
kind
of
convince
you
guys,
also
or
demonstrate
that
you
are
able
to
use
already
and
push
about
your
customizations
on
the
modern
experiences.
Extensions
will
Kochi
a
relatively
soon
like
mentioned
quite
a
few
times.
We
want
to
help
you
on
the
journey
of
moving
into
the
modern
experiences
as
well,
because
we
absolutely
believe
that's
the
right
way
to
do
and
right
way
of
doing
customizations
and
the
right
you
is
in
the
future
for
SharePoint.
A
Now,
if
you
disagree
on
that
statement
and
if
something
is
missing,
please
do
let
us
know,
because
that
input
and
your
input
is
super
valuable
for
us
for
addressing
these
gaps.
So
please
do
not.
Please
do
share,
don't
be
quiet
and
if
you
are
in
ignite,
please
drop
by
and
let's
have
a
chat
in
the
BMP
booth
or
within
our
sessions
and
so
on.