►
From YouTube: SPFx JavaScript SIG 23rd of November, 2017
Description
Bi-weekly community call around SharePoint Framework and JavaScript development in SharePoint platform. This is recording from the 23rd of November call. You can download recurrent invite from http://aka.ms/SPPnP-JSSIG.
A
So
here
we
go
like
mentioned
on
the
introduction,
for
those
who
are
writing
arriving
exactly
and
our
so
today
is
the
times
giving
it
in
us.
We
won't
have
that
many
people
obviously
attending,
but
we
didn't
want
to
also
cancel
the
meeting
because
there's
a
lot
of
other
areas
than
us
in
the
world
as
well.
So
we
try
to
keep
this
as
a
weekly
thing,
regardless
of
all
of
these
holidays
across
the
world.
A
Whatever
those
are
happening,
except
probably,
the
upcoming
Christmas
holiday
is
probably,
if
that's
overlapping
with
any
of
the
weeks,
we'll
have
a
break
on
there
and
last
week
the
whole
PMP
team
was
actually
in
duckling
in
the
European
SharePoint
conference.
So
we
were
unable
to
do
a
SharePoint
development
special
interest
group,
because
everybody
was
actually
in
a
plane
flying
away
from
duckling,
so
slightly
awkward
situation.
But
there
was
there
was
nothing
we
could
actually
do
undone
well,
everybody
was
on
a
plane
except
Patrick,
who's
still
on
parental
leave,
but
anyway,
so
welcome
on
this.
One.
A
Welcome
on
this
special
interest
group
call
around
the
SharePoint
framework
and
JavaScript
development.
Let's
see
how
many
people
are
joining
like
mention,
but
what
we
wanted
to
do
today.
I
didn't
actually
schedule
any
community
demos
on
this
one.
We
rather
wanted
to
go
through
some
of
the
demos
which
we
went
through
also
last
week
in
the
European
SharePoint,
the
European
ship
on
conference,
because
we
did
do
some
announcements
and
some
additional
details
and
we
showed
some
capabilities
last
week
in
duckling.
A
So
we
wanted
to
actually
get
all
of
those
things
recorded
today
and
also
to
be
available
in
the
YouTube
channel
starting
tomorrow,
and
if
there's
any
questions
around
any
of
these
topics,
more
than
happy
to
actually
answer
on
those
as
we
move
along
on
today's
call.
So
basically
that
means
that
it
will
be
just
me
talking.
So
my
name
is
sauce.
A
If
there's
anybody
who
has
never
been
in
the
SharePoint
framework
special
interest
group,
just
explaining
what
this
one
is
all
about,
so
we
originally,
we
had
only
monthly
community
calls
in
the
Chevron
patterns
and
practices,
but
quite
fast
to
realize
that
well,
the
monthly
community
calls
are
our
one-hour
course
where
we
summarized
the
previous
month
and
we
started
running
out
of
time.
There
was
no
time
for
Q&A.
There
was
no
time
to
really
have
a
discussion
in
our
window
and
no
time
to
actually
show
anything
additional
capabilities.
A
So
quite
soon
we
started
then
keeping
or
started
doing
this
special
interest
group
course
and
we
started
SharePoint
framework.
Special
interest
group
called
already
one
and
a
half
years
ago,
and
this
is
around
concentrating
on
JavaScript
development,
so
concentrating
on
on
the
BMPs
core
JavaScript
development,
also
other
JavaScript
development
techniques
and
also
on
the
SharePoint
framework,
and
this
is
part
of
the
larger
SharePoint
VMP
initiative.
Now,
if
you're
interested
on
things
over
see
our
documentation,
AKMs
PDF
Doc's,
that's
official
SharePoint
documentation
in
the
dr.
McComb.
A
If
there
are
questions
spbm
a
community
is
the
great
location
for
ask
those
questions
in
Microsoft.
Tech
community
and
obviously
all
the
other
social
media
channels
so
like
mention
today,
we're
not
going
to
actually
once
again
we
kind
of
skip
the
p.m.
PHAs
core
topic
and
I
do
apologize
and
that
Patrick
Rodgers
who's,
leading
on
that
one
is
still
on
a
parental
leave
and
I.
A
We
did
demonstrate
these
capabilities
in
the
European
SharePoint
conference
last
week
in
Dublin,
but
unfortunately
that
keynote
and
the
follow-up
session
was
not
recorded.
So,
there's
no
way
for
anybody
to
know
what
we
actually
showed.
So
that
is
exactly
the
reason
why
I
wanted
to
go
to
all
of
these
things
today
in
the
special
interest
group
call
good,
let's
actually
and
hopefully
we'll
have
time
for
a
Q&A
and
depending
on
how
much
time
I
will
again
ramble
on
this
thing.
A
So
I
tend
to
use
quite
a
lot
of
time
when
I'm
only
talking
by
myself,
but
we'll
see
how
it
goes.
If
you
have
any
questions
when
I
caught
you
of
capability
slides
feedback,
whatever
please
use,
the
I
am
window
you're
able
more
than
happy
to
jump
on
there.
I
I
have
multiple
screens
on
my
setup,
so
I
can
say:
what's
actually
happening
there
as
long
as
there's
not
too
many
questions
coming
up.
A
On
the
same
time
before
we
go
to
the
actual
content,
if
you're
interested
on
the
on
participating
on
the
special
interest
group
activities,
the
easiest
way
to
do
that
is
volunteer
to
do
a,
for
example,
a
demo
on
a
SharePoint
framework
solution
which
potentially
could
be
shared
using
the
github
and
in
here
and
just
the
pin
point
opportunity
as
well.
You
do
not,
if
you're,
for
example,
building
your
own
product
is
for
an
ISV
or
representing
an
ISV,
and
you
would
like
to
show
your
product
which
is
built
using
a
SharePoint
framework.
A
That's
absolutely
fine
as
well.
You
don't
have
to
share
the
SCOTUS
shared
code
using
github
channels.
Obviously
you
can
also
contribute
using
the
open-source
channels
in
a
key
time,
but
if
you
are
an
IV
and
you
want
to
just
show
hey,
this
is
cool
stuff
build
using
SharePoint
framework.
We
are
absolutely
interested
on
that
as
well.
A
So
that's
a
good
be
an
interesting
opportunity
for
some
of
you
if
you're
building
that
kind
of
products,
if
you
are
using
the
HP
pnp
chase
in
a
project,
that's
also
interesting
and
absolutely
to
show
how
people
are
using
that
library,
because
it's
being
used
more
and
more
by
customers
and
partners.
It
is
a
really
nice
library
to
simplify
JavaScript
development
on
top
of
SharePoint.
A
Now
nobody
provide
feedback,
use
our
issueless
channels
and
used
on
windows
and
all
of
our
community
channels
to
give
us
feedback
Ron,
what's
not
working
and
rather
than
rather
than
criticizing,
Microsoft
I'm
not
telling.
What's
what's
wrong,
we
are
trying
to
fix
whatever
is,
might
be
potentially
wrong
or
might
not
be
working
cool,
let's
actually
jump
into
the
SharePoint
framework.
Topic
lighter
right
away.
I
have
few
slides
before
we
go
into
the
specific
tree
scenarios
which
we
want
to
go
through
from
a
new
capability
perspective.
A
The
dust
of
Mike's
dot-com
platform
right
now,
all
of
the
old
SharePoint
BMP
guidance
and
everything
else
has
been
already
consolidated
in
here,
and
the
next
step
is
that
we'll
start
updating
existing
chip
and
adding
model
guidance
and
our
scenario
and
solution
design
guidance
in
here,
and
we
are
planning
to
actually
do
a
quite
nice
setup
related
on
scenario
based
guidance
which
should
help
you
in
the
future.
As
an
example,
if
you're
looking
into
hey
I
need
to
do
custom
trending
in
the
modern
experiences,
what
are
my
limitation?
What
are
my
options?
A
What
are
the
the
scale?
How
would
I
do
that?
So
there
would
be
explicitly
at
one
page,
which
is
explaining
your
options
and
so
on.
So
really,
if
you're
looking
into
long-term
operations,
there's
a
one
page
which
is
explaining
long
long,
lasting
tasks
and
how
they
can
be
implemented
in
SharePoint
Online,
for
example,
in
the
cell.
Comparing
the
scenarios
in
service
like
Tommy
jobs,
and
then
we
are
also
planning
into
implementing
a
completely
new
series
around
how
to
transform,
add-ins
and
form
solutions
to
SharePoint
framework
and
modern
experiences.
A
Because
already
today
you
can
actually
use-
and
you
can
achieve
quite
a
lot
of
typical
scenarios
in
the
modern
experiences
and
seems
to
be
that
people
are
not
quite
familiar
with
this
stuff.
You're
able
to
have
custom,
widgets
you're
able
to
use
custom
printing
you're
able
to
do
a
lot
of
other
stuff
in
the
modern
experiences
as
well.
So
we
are
gonna,
invest
time
on
on
that
guidance
right
after
say
holiday
season,
and
so
that's
when
we
start
actually
concentrating
on
that.
A
I'll,
come
back
on
that
one
in
a
second
on
the
schedules
as
well
and
the
one
our
new
announcements
which
we
did
last
week
in
in
Dublin,
which
I
I
noticed
earlier
today
that
I've
haven't
actually
done
a
proper
announcement
know
it's
available,
but
now
it's
officially
available.
It's
100%
worldwide.
The
point
there
was
a
during
last
weekend:
there
was
a
small
hiccups
relay
the
Elam
API
capabilities.
So
if
you
were
playing
around
with
this
one,
we
did
announced
it
on
last
Thursday.
Then
we
did
small
modifications
during
weekend
and
then
it
came
back
on.
A
Was
it
on
Monday
or
Tuesday,
and
so
you
might
have
seen
those
hiccups,
but
now
it's
actually
up
and
running
100%
deployed
worldwide.
So
the
a
lie
made
me
eyes
are
now
available,
so
you're
able
to
automatically
deploy
up,
create,
install
onion
style,
whatever
whatever
is
needed,
sharepoint
hosted
sorry
shipment
add-ins
to
both
sharepoint
hosted
aliens
and
also
provided,
hosted,
add-ins
and
also
sharepoint
framework
solutions.
So
you're
able
to
explicitly
install
these
things
to
any
site
collection
or
any
site
within
your
within
our
channel.
A
Then
we'll
have
a
look
on
that
one
during
today,
as
well.
Now,
let's
actually
move
into
quickly
on
the
roadmap
content,
will
jump
into
those
three
capabilities
and
walk
through
the
actual
demos
around
on
this
one.
This
is
just
the
roadmap
slide,
which
I've
been
updating
as
we
move
along
within
the
special
interest
groups,
and
this
right
now
we
have
updated
daily
may
be
nice
to
be
on
a
just
shipped
site
and
I'm.
You
can
actually
see,
and
that
will
shift
quite
a
lot
of
stuff
since
end
of
September
already.
A
So
that
would
be
one
point
for
version
released
as
part
of
that
one
I
can't
disclose
the
date
exactly
right
now,
because
it
might
be
that
we'll
still
find
something,
and
we
need
to
take
a
few
more
days
extra
to
do
some
testing
or
chessmen.
So
that's
why
we're
not
actually
gonna
give
you
an
exact
date,
but
it's
coming
really
really
soon,
and
the
second
thing
is
sign
designs
with
the
next
sensibility
points
demonstrated.
Also
in
ignite
and
last
week
in
in
duckling,
it's
gonna
arrive
in
preview
usage
on
December
2017.
Right
now.
A
We
are
mainly
concentrated
on
documentation
side
of
the
story,
so
making
sure
that
we
have
the
sufficient
guidance
for
you
to
get
started
on
the
side
designs
and
with
that
xsn
extensibility
point
moramax
of
craft
supports.
Essentially,
scopes
will
be
available
for
microsoft,
craft
client
and
that's
going
to
arrive
on
preview
in
December
2017
as
well,
and
then
there's
a
small
line
on
the
slide
which
I
can
in
amber
Leslie
and
then
early
next
year.
A
Welcome
will
release
on
preview,
the
hub
sites
and
hub
a
POS
and
also
the
court
before
a
POS,
and
that's
part
of
the
reason
why
the
full
transformation,
guidance
story
and
and
step-by-step
instructions
on
how
to
transform
existing
classic
sites.
The
modern
sites
will
wait
until
the
early
next
year
because
we
want
to
have
to
crop
it
for
Krupa
Phi
API
available.
We
did
demonstrate
this
one
last
week
in
the
monthly
community
core.
A
So
how
do
you
how
you
can
actually
crop
by
an
existing
classic
theme,
site
and
modernize
the
UI,
but
we'll
have
more
details
and
more
guidance
on
all
of
that
process
whenever
we
well
later?
That's,
let's
put
it
this
way.
Good.
If
there's
any
question
feel
free
to
jump
in
the
iron
window
and
any
of
these
topics,
but
what
I'm
planning
to
do
like
mention
is
that
I'm
gonna
walk
through
those
tree
different
capabilities,
so
LM
api's,
the
site,
collections,
scope,
catalog
and
also
the
site
assets
bucket
in
a
solution,
and
so
with
the
live.
A
Demos
and
I'm
gonna
use
actually
slides,
which
we
already
have
recorded
for
our
webcasts.
But
that's
absolutely
fine,
and
so
you
will
see
a
webcast
related
on
these
capabilities
as
well,
where
we
also
talked
about
slightly
in
a
different
format
on
the
capabilities
but
I
think
it's
fine
from
a
it's
always
there's
no
harm
for
repeating
the
message.
So
people,
then
how
things
are
actually
working
so
LM
apos,
you've
probably
seen
this
lined
already
back
in
two
weeks
ago.
If
about
this
special
interest
group.
A
But
the
whole
point
of
daily,
maybe
is
that
you
will
have
a
REST,
API
partial
API
partial
comment:
let's
and
sees
maybe
ice
to
install
add-ins
to
that
catalog
enable
them
in
a
half
catalog
without
going
to
the
UI,
install
add-ins
to
explicit
site
collections,
and
this
is
not
a
tenon
scope
deployment
model.
This
is
actually
getting
that
in
install
to
design
and
also
are
creating
those
areas
and
solutions
in
the
side
and
uninstalling
solutions
that
site.
Technically,
we
have
few
additional,
let's
say,
operations
available.
A
When
would
we
be
able
to
say
plan
for
q2
and
forward
at
some
point?
Let's
say,
let's
say
well,
we'll
come
back
on
that
one
good
question
related
on
roadmap
roadmap
stuff,
but
not
yet
whenever
we
have
something
to
disclose,
will
update
there.
Yes,
scenarios
now.
This
is
de
el
mapa,
as
I've
mentioned
at
the
key
points
now
understand.
This
is
for
both
sharepoint
framework
solutions
and
Adams.
So
the
whole
point
is
that
you
can
you
can
automate
programmatically
and
the
whole
deployments
in
a
scenario.
A
So
if
you
are,
let's
say,
if
you're
a
syndication
partners,
your
hosting
or
managing
multiple
tenants,
you
can
easily
automate
deployment
even
to
add-ins
on
SP
FX
solutions
to
your
customer
tenants,
the
squad
of
syndication
partners
out
there.
This
is
the
full
automation
support
so
including
on
to
trust
operation
as
well.
A
So
all
of
the
scenarios
all
of
the
API
is
supported
using
the
app
only
access
and
also,
if
you
are
using
provider,
hosted
atoms
which
have
associated
app
installed
or
uninstalled
eV
and
all
of
those
are
getting
properly
fired
because
the
adding
is
correctly
installed
to
the
site.
It's
it's,
not
the
classic.
How
would
I
put
it
tenant
scoped
deployment,
adding
if
you
remember
what
that
option
was
in
office
traces
to
file
just
to
cover
all
of
the
operations
we
do
have
documentation
available
in
the
docs
of
my
stuff
that
come.
A
So
the
rest
api
is
has
been
created
by
a
shipment
engineering,
so
well
technically
me
and
my
team,
and
then
we
use
the
community
channels
to
create
a
season
wrapper
for
the
REST
API
and
also
the
PMP
powershell
commandlets
to
automate
this
in
a
scripting
perspective
is
needed.
So
these
are
for
getting
details
around
available,
apps
or
details
or
on
specific
app
or
chevron
framework
solution.
A
A
A
quick
question
is
checking
from
Joel,
assuming
that
this
is
not
possible,
haven't
checked
in
sorry,
will
we
be
able
to
use
a
nail,
maybe
as
for
visitors
to
the
online
CI
pipeline?
That
would
be
awesome.
I,
don't
see
any
reason
why
you
should
could
not
be
doing
that.
Absolutely
you
can
do
that
you're
able
to
get
the
solutions
automatically
deployed
using,
for
example,
apparently
access
and
then
getting
stuff
installed
on
the
site,
absolutely
good,
good
point
and
good
scenario,
for
they
are
maybe
ice
as
well.
Let's
actually
have
a
live
demo
on
this
one.
A
So
let
me
share
my
screen
and
somebody
needs
to
tell
whenever
the
screen-sharing
is
successful
in
the
session.
So
let
me
share
one
of
my
screens
now.
If
you
go
to
the
dost
of
myself
that
come
slash,
appoint
you
land
on
this
page,
then
you
can
decide.
Are
you
a
chef
pond
developer
or
are
you
a
chef
on
server
and
I?
Know
it's
a
bad
joke
and
I
always
do
that
and
we're
all
develop
on
developers
as
in
the
shipment.
A
Ap
is
we
have
an
ALM
ap
is
listed
and
the
document
that
here
this
isn't
really
optimal
right
now
the
documentation
and
we've
been
struggling
on
finding
time
to
get
stuff
polished,
but
it
at
least
it's
telling
the
endpoints
and
URLs
and
all
of
them,
and
it
also
lists
or
EMP
powershell
commandlets,
and
so,
if
you
prefer
to
do
this,
you
scribble
to
do
that
as
well.
There
is
a
season,
maybe
is
available
as
well,
like
I
have
like
shown
in
the
slides,
but
it's
not
yet
listed
in
your
inter
documentation.
A
A
And
let
me
okay
there
we
go
now
we're
in
the
right
status
call.
So
let
me
actually
cover
the
PowerShell
side
of
the
story
and
I'm
kind
of
use
now
the
PowerShell
and
just
for
the
sake
of
it,
because
the
PowerShell
is
super
easy
to
show
how
to
API
stopped
working
and
how
how
things
are
behaving
now
urban
and
we're
supposed
to
connect
to
the
site
or
we're
supposed
to
connect
to
the
app
catalog,
just
a
discussion
point
for
us
on
site,
and
so
whenever
we
are
installing
something
let's
actually
go
to.
A
We
can
use
this
one
at
this
particular
site.
So
it
doesn't
really
matter
that
much
in
this
context,
I'm
going
to
actually
sign
in
to
the
site
collection,
so
I'm
going
to
do,
connect
the
online
and
the
URL
and
let's
actually
connect
with
outside
sir
I,
have
to
mention
that
there
is
a
difference.
If
you
use
the
REST
API
directly,
if
you
use
the
be
provided,
Caesar
may
pies,
where
the
powershell
commandlets
you
connect
to
the
site,
because
they
will
figure
out
where
the
app
catalog
is
created.
A
So
some
of
the
some
of
the
operations
you
execute
through
the
REST
API
directly,
you
you,
you
execute
towards
the
app
catalog
site.
Yes
now
now.
All
of
that
is
in
the
document
that
in
the
documentation
and
we'll
make
sure
that
that's
absolutely
up
to
date.
So
it's
not
too
confusing
now
in
here,
I
do
have
a
simplistic
property
hosted
at
in
and
we
can
actually
use
that
one
to
play
around
with
the
with
the
scenario.
A
But
in
my
case
we
want
to
actually
add
that
additional
solution-
and
this
is
a
property-
hosted
Irene
just
for
the
sake
of
it,
and
we
want
to
add
that
one
to
the
catalog,
it's
been
like
years
since
I
created
a
ship
and
host
a
time
heading,
but
just
to
demonstrate
the
capability.
So
I
can
now
do
add,
BMP,
adding
no
app
and
path
being.
In
this
case,
the
there
we
go
SP
apps,
SP
host.
This
is
now
then,
installing
that
app
did
and
catalog,
and
there
we
go
now.
A
We
can
actually
see
that
it's
available.
So
now,
if
I
do
again
the
get
empl
now
we
can
see
that
what
are
the
identities
are
available
and
one
of
these
aliens,
which
is
now
listed
here
as
a
new
one,
is
the
SP
apps
just
be
hosted
so
now
because
I'm
in
the
I'm
using
the
PMP
PowerShell,
which
means
that
in
the
in
the
context
of
this
slide,
because
that's
how
the
PNP
power
shop
works,
the
native
shipment
online
management,
shell
works
in
the
way
that
your
in
the
conduct
of
tenant.
A
That
proposal
works
always
that
you're
in
the
context
of
sign
I,
can
easily
now
install
this
adding
to
the
side
as
well.
Now,
right
now,
if
I
remember
correctly
and
Evan
can
actually
this
easily,
we
still
need
to
do
a
populist
PNP
app.
Yes,
because
this
is
actually
the
baptists
PNP
app
is
the
operation
which
is
basically
the
same
as
your
truck
and
dropping
the
sba,
adding
or
SPF
x
solution
to
the
app
catalog,
and
you
need
to
trust
it
in
a
10
on
that
catalogue
level.
A
A
There
is
a
small
hiccup
which
we
can
easily
fix
step
manually.
Okay,
so
let
me
actually
close
and
do
this
manually
for
install
this-
it's
actually
already
enabled
it
was
already
enabled.
Oh,
it
was
okay,
yeah
yep,
that's
fine!
So,
but
I'm
gonna
now
do
the
same
thing
in
here
and
basically
the
publish
would
be
doing
exactly
the
following
step
down
here:
yeah.
A
It's
sharepoint
hosted
at
in
that's
different,
exactly
that's
true,
so
if
it
would
be
a
solution
and
shape
on
hosted
solution,
then
you
actually
get
this
icon,
which
is
which
is
telling
you
to
pay.
Do
you?
Are
you
trusting
this
SPF
x
solution?
Sorry,
further
confusing,
it's
been
a
while
on
stem
cells
until
I've
used
a
Chapman
hosted
add-ins,
but
this
is
the
shipment
framework
solution
and
it
would
actually
that's
when
the
populist
operation
has
to
happen,
which
basically
means
same
as
somebody's
clicking.
A
A
Now
if
I
go
to
the
site,
if
I
go
to
the
site
contents,
we
can
see
that
my
Japan
hosted
app
is
getting
installed
and
like
within
the
normal
user
for
an
operation
the
installation
does
take
a
while,
so
it
it
can
take
one
it
can
take
20
seconds.
It's
indebting.
Second,
slightly
depends
when
the
time
is
up
is
actually
being
executed
on
the
site.
Hopefully
this
time
it's
not
super
super
slow.
A
Come
on
darica,
so
there's
my
sharepoint
hosted
allen,
and
if
I
want
to
look
on
the
on
the
details,
all
of
this
is
good
to
go
and
the
permissions
has
been
approved.
Permissions
has
been
handled
and
the
trust
operation,
which
would
be
there
for
all
of
its
being
automatically
done
using
the
context
where
the
rest
operation
of
season
operation
or
the
powershell
operation
happen
so
using
that
person's
permissions.
A
So
now,
if
I
go
to
this
chair
plan,
Hotel
earnings-
and
this
is
just
she'll
demonstrating
she
upon
hosted
at
in
and
it's
it's
saying
that
it's
a
awesome-
cellphone
hosted
a
map.
It's
been
a
while,
since
I've
actually
use
Chevron
hosted
apps,
but
that's
a
different
discussion.
Why
I
shouldn't
paint
necessarily
using
them
good
now?
If
we
need
to
then
uninstall
or
upgrade
stuff,
we
can
absolutely
do
that
as
well,
so
uninstallation
uninstall
the
app
and
we
can
use
the
same
identity
here
on
installation
who
happens
automatically
as
well.
A
Maybe
a
small
pinpoint
or
small
note
to
remember
or
to
know
around
that
the
uninstallation
is
that
done.
Installation
happens
in
a
way
that
we
do
not
use
to
recycle
thing.
So
the
solution
is
getting
an
SPF
x.
Solution
on
the
add
in
solution
is
automatically
getting
fully
cleaned
and
removed
from
the
site.
A
So
there's
no
recycle
in
step
in
here
which,
by
the
way
is
in
which
it
is
an
awesome
thing
from
a
developer
perspective
as
well,
because
quite
often,
if
you're
testing
deployments
do
these
things
to
the
side,
it
is
quite
frustrating
to
go
to
the
recycle
bin
and
delete
and
delete
from
a
second
stage,
recycle
bin-
and
that
takes
time
so
using
the
BMP
powershell
using
the
REST
API.
So
you
can
fully
uninstalled
the
solution
from
a
site
extremely
easily,
which
is
cool,
good
I.
A
Think
that's
around
the
LM,
API
automation
and
the
documentation
is
already
out
there.
It
is
listing
the
rest
state
operations
you
are
able
to
you
have
accessed
on
the
PMP
code.
You
can
see
the
season
operations
you
can
see
in
the
PMP
PowerShell
and
commands
and
how
they've
been
implement
it.
If
you
want
to
implement
similar
stuff
by
yourself,
if
you
don't
want
to
use
those
existing
implementations,
but
let's
flip
quickly
back
on
the
slides
so
and
concentrate
on
the
following
topic:
selecting
the
right
set
of
slides
and
the
following
topic
was
around
site
collection.
A
Now,
the
site
collection
of
catalogue
was
also
kind
of.
It
was
originally
explained
that
it's
coming
in
the
Ignite
and
then
last
week
in
in
duckling,
canary
reinforced
message
and
first
time
ever
demonstrated
that
probably
and
this
one
is
coming
within
matter
of
days
rather
than
weeks.
The
whole
point
of
the
site
collection,
app
catalog-
is
that
typically
by
default
you
in
the
past,
you
always
had
and
telescope
app
catalog
and
which
meant
that
whenever
you
install
a
solution
to
do
ten
on
ten
inscribed
kabak,
those
solutions
are
available
across
the
tenor.
A
So
you
can't
isolate
and
visibility
of
an
ad
in
only
to
a
specific
site,
collection
or
set
of
site
collections.
Now,
using
the
site,
specific,
app,
catalog
and
first
of
all,
the
tenant
admin
can
enable
that
in
a
subset
of
site
collections
or
site
collections,
where
they
want
to
use
them
and
then
an
it
is
a
tenant
level.
Ten,
an
admin
operation,
so
there's
still
the
centralized
governance
and
centralized
control.
A
But
after
that
has
been
done,
you're
able
to
then
install
or
set
add-ins
to
be
visible
only
in
the
subset
of
site
collection,
so
basically,
and
then
add
to
add
into
the
site:
collection
scope,
their
catalog
and
they're.
Adding
is
only
available
within
that
site.
So
typical
scenarios
would
be
something
like
the
global
internet
scenario.
We
have
a
one
site
collection
with
a
global
internet,
and
then
we
have
10,000
collaboration
sites.
You
don't
want
to
have
same
add-ins
and
SharePoint
framework
solutions
to
be
visible
for
to
be
installed
on
collaboration
sites
you
can
use.
A
I'll
come
back
on
the
well
actually
Arturo's
question
is
really
good.
It's
there
a
way
to
deploy
an
app
to
all
sites,
including
new
sites.
By
default,
like
the
deployment
option,
we
had
on
manual
path,
we
well
I,
think
the
deployment
of
shop
manual
path
is
referring
to
the
tenon
scoped
and
deployment
option
for
add-ins
and
that
a
slightly
different
scenario,
because
that
never
actually
installed
the
adding
to
the
site
level.
A
The
tenants,
a
scope,
adding
deployment
actually
meant
that
you
created
a
an
instance
of
the
adding
to
the
app
catalog,
and
then
we
added
a
links
to
the
site
from
a
site.
Contents
page
did
the
app
catalog
instance
and
that's
a
different,
slightly
different
scenario.
Now,
if
you
need
to
have
the
app
or
SharePoint
framework
solution
installed
are
available
across
all
the
sites
automatically.
So
it's
again
slightly
depends
on
the
on
the
detail
scenario.
If
it's
an
app,
you
would
need
to
automate
adding
the
app
to
decide,
for
example,
as
part
of
your
provisioning
logic.
A
So
again,
it's
now
depends
on
how
the
end
users
are
creating
and
requesting
a
new
site
collection.
Do
you
have
a
custom
UI?
Do
you
have
a
custom
home,
or
do
you
call
an
admin
and
request
the
site
collection?
Do
they
create
it?
If
you
call
an
admin,
for
example,
they
probably
use
any
way
PowerShell
and
then
they
would
have
just
include
the
step
of
activating
the
add-in
on
those
Power
Cells.
If
it's
an
out-of-the-box
UI,
you
can
automate
the
whole
installation
of
an
adding
to
the
site
using
the,
for
example.
A
The
extensibility
points
on
the
other
box
provisioning
yours,
so
there's
this
small
dependencies
and
different
options.
Some
time
website
specific
app
catalog
would
be
awesome.
I
do
agree
on
that.
One
good
point
from
Chris:
we'll
need
to
wait
for
hub
sites
to
be
truly
available
and
that's
a
good
scenario
and
I
don't
capability
which
might
be
there
in
the
future
good
point:
is
it
possible
also
remove
hide
out-of-the-box
app
web
parts
from
a
specific
site
answer
is
unfortunately,
no
from
Oliver's
point,
especially
in
the
modern
experience.
This
is
not
possible
technically
in
a
classic
experience.
A
A
So
I
have
a
custom
provisioning.
The
problem
is
that
all
new
sites
created
by
crews,
so
you
are
creating
well
yeah,
okay
in
the
future,
whenever
there
you
say
you
can't
you're
able
to
associate
default
recipe
to
be
applied
whenever
a
sharepoint
and
modern
crew
risking
they
can
create
it.
So
it
doesn't
matter
if
the
group
is
created
using
the
crew.
A
P
is
in
Outlook
or
croupiers
in
SharePoint
or
croupier
as
an
alternative
science,
as
default
recipe
would
be
applied
on
the
crew
and
that
default
recipe
can
then
actually
contain
the
extensibility,
a
story
on
applying
to
needed
solutions
and
add-ins
to
the
site.
Right
now
that
automates
and
extensibility
point
doesn't
exist,
it
will
be
available
as
a
preview
capability
in
mid-december
right
now
we're
working
on
a
documentation
on
that
good.
A
Now,
just
quickly
add
in
points
on
this
one.
Why
is
that
actually
important?
It
provides
flexibility
for
enterprises
on
deployment
options,
it
decentralized
management
for
add
instant
SPF
X
application.
So
you
don't
have
to
call
your
tenant
admin
to
be
able
to
take
something
into
a
use
and-
and
you
have
a
scoped
deployment
option
for
add-ins
and
SPF
X
solution.
One
thing
to
notice
on
this:
one:
I
don't
want
to
scare
people,
but
this
also
means
that
people
need
to
be
aware
on
what
are
they
actually
installing
on
the
site?
A
Collection,
scoped
out
catalog,
because
there
is
always
a
risk
behind
of
all
of
these
customizations.
So
if
we
enabled
app
app
catalog
for
every
single
site
collection
in
a
tenant
automatically,
you
lose
control
and
you
might
have
then
potential
security
risks
within
your
tenant.
So
you
lose
the
control.
What
the
whole
SharePoint
framework
is
providing
for
you.
So
there
are,
let's
say,
scenarios
to
think
through
the
governance
to
think
through
with
this
option
as
well.
A
Let's
have
a
quick
demo
on
this
one,
just
walking
through
and
I'm
good
point
from
David
with
great
power
comes
great
responsibility
exactly,
and
that
is
a
great
way
of
filling
that
now.
Let
me
share
my
desktop
and
hopefully
sharing
the
right
screen
this
time.
Yes-
and
let
me
actually
close
this
one.
A
A
And
because
the
site
creation
doesn't
take
that
long,
hopefully
we
don't
have
any
challenges
there.
We
go
a
few
seconds
and
there's
a
new
site
collection
created.
So
this
is
a
new
site
collection
and
which
is
just
created,
and
if
you
want
to
deploy
a
specific
solution
which
is
only
available
within
this
site
collection,
we
have
to
enable
the
site
collection,
scope
of
catalog-
and
this
is
quite
simple
stuff.
Actually
so
I'm
going
to
use
a
PowerShell
again.
A
A
And
there
we
go
if
I
do
get
SPL
tenant.
We
are
able
to
say
that
I'm
in
the
context
of
the
admin
site
I'm
using
the
sharepoint
online
management
shell
and
in
the
shipment
on
my
management,
show
the
new
version
of
this
one.
I
would
will
go
live
later
tomorrow.
We'll
have
a
new
powershell
commandlets.
The
capability
is
not
yet
enabled
for
you,
but
it
will
be
enabled
in
a
matter
of
days,
but
the
PowerShell
commands
little
for
you
starting
tomorrow.
So
then,
after
that,
you
can
always
check
that.
It's
not
really
working.
A
Is
it
already
working?
Well,
how
it
works
is
that
you
use
ant
SPO,
site
collection,
apke,
dog
and
prettied
self-descriptive
command
flight
name,
and
then
you
put
the
site
where
you
want
to
actually
enable
this
capability.
So
if
I,
if
the
URL-
and
we
want
to
enable
the
site
collections
catalog
in
that
site,
we
can
easily
do
that.
A
If
I
refresh
here
in
the
site
contents,
we
don't
see
it
yet
when,
if
I
refresh
one
second
or
two
seconds
more
able
to
see
that
the
app
catalog
activation
there,
we
go,
we're
able
to
say
the
apps
for
shipment
have
a
catalog
being
visible.
So
what
basically
happened
on
the
background
is
that
we
activated
a
feature.
We
double
check
that
the
operation
requests
for
activation
of
the
specific
feature
is
coming
from
the
tenant
admin,
and
then
we
created
the
apps
for
SharePoint
app
catalog
for
this
particular
site.
A
A
A
A
Oh,
but
it's
solution
and
just
ship
actually
create
the
SharePoint
folder
gets
created
on
the
understructure
and
we
create
the
sp-
file,
which
we
can
then
track
and
shop
and
get
installed
on
the
App
Catalog.
So
now,
if
I
go
to
my
SharePoint
folder
and
solution,
I
can
see
this
baby
a
chief.
Well,
let's
put
that
one
over
there
and
there's
my
app
catalog
and
now
I
can
actually
track
and
drop
and
that
particular
solution
to
be
available
in
the
site
collection.
Now,
in
this
case,
I
didn't
update
the
URL.
A
So
it's
still
passed
the
CDN
because
I'm
just
demonstrating
the
capability
works
properly
and
if
you
are
wondering
there
are
certain
things
which
right
now,
when
we
start
at
the
journey
with
site
collection,
curb
type
that
does
not
work.
So
the
10th
grade
option
doesn't
work
with
this.
One
and
the
asset
packaging
does
not
work
with
a
site
collection,
app,
catalog,
we'll
we'll
get
all
of
these
limitations,
or
things
documented,
probably
when
the
capability
is
fully
available.
A
It
is
in
a
matter
of
days
and
now
I'm
going
to
click
deploy,
and
that
means
that,
within
this
site
collection,
this
solution
is
ready
to
be
installed
and
to
the
site.
So
if
I
now
go
to
the
site,
content
and
click
new
app
getting
install
to
this
site,
we
can
actually
see
that
there's
a
webcast,
app
catalog
client
solution
available.
If
I
now
go
to
another
site
which
is,
for
example,
that's
not,
let's
go
to
another
completely
another
site.
A
Yesterday,
URL,
yes,
that's
a
aura
which
is
available
so
now
in
this
site.
If
we
quickly
have
a
look
on
what's
available
in
add
an
app
functionality
that
particular
app
is
not
available.
So
in
here
we
can
all
say
the
three
applications,
so
these
are
the
ones
which
are
coming
from
tenant,
I've
got
and
in
this
one
we
can
say
for
because
that
is
additional
one
which
is
coming
from
the
cyclist,
cannot
good
one
more
thing
to
go.
True,
we
have
12
minutes
always
this
always
happens
to
me.
A
So
let
me
actually
flip
back
on
the
slides,
a
few
things
on
the
slides
and
then
I'll
do
a
live
demo
on
the
side
assets
packaging
as
well,
while
we're
doing
that
flipping
between
the
screens
quickly
checking
the
pictures.
Some
specialists
have
switched
up
cut
our
clips
to
modern,
which
means
that
the
pop-up
won't
appear,
which
means
your
app
won't
work
here.
I
know
dirt
and
that
story
which
slightly
horrible
we
sooner
or
later
we.
Luckily
the
options
will
be
there
that
you're
able
to
be
in
the
modern
all
the
time.
A
So
right
now
there's
this
capabilities
like
the
app
catalog,
where
you
need
to
be
in
classic
to
be
able
to
make
that
library
work,
which
is
slightly
awkward,
will
the
site
collection
of
catalog
work
within
assets
included
in
packets.
Eventually,
that
is
absolutely
the
intention
right
now.
It
is
not
there,
it
will
be
there
within
say.
Well,
it
won't
be
there
today
it
will
be
there.
A
It
won't
be
there
immediately
when
we
release
the
site,
collection
and
catalog,
but
it
will
be
there
quite
often
is
it
possible
to
install
SPF
solution
with
global
deployment
option
for
web
parts
in
the
site,
collection
of
catalyst,
so
the
users
don't
have
installed
manually
and
so
right
now
is
no,
unfortunately,
but
we're
looking
into
getting
that
one
absolutely
supported
in
the
following
steps
and
there
will
be
whenever
the
the
documentation
capability
will
be
out.
We
will
mention
all
of
the
supported
capabilities
and
the
scenarios
as
well
do
site
collection,
administrator
catalog.
Yes,
they.
A
Basically
it
is
an
app
catalog
in
that
site
collection,
so
you'll
be
natively
the
owner
of
that
one.
It's
not
the
app
catalog
to
the
tenant,
F
catalog.
It
is
the
site,
collection,
scoped
and
catalog,
so
it's
a
completely
different
instance
cute
quick
story
around
acid
packaging
as
well.
We
will
have
a
burst
of
webcast
and
videos
and
all
of
the
stuff
more
detailed
on
these
things
as
well,
but
assets
include
an
employment
packet
is
this
is
actually
massive
dealer.
A
A
So
when
you
are
installing
this
biblical,
a
founder,
the
App
Catalog
or
taking
the
SPP
case,
a
file
into
use
by
default
will
extract
the
JavaScript
files
inside
of
the
package
and
if
the
CDN
office,
traces
to
five
CDNs
enable
will
serve
the
content
from
office,
365
CDN,
if
it's
not
enabled
or
office
365
CDN,
it's
not
used
within
the
tenant,
will
serve
the
content
natively
directly
from
the
App
Catalog
URLs.
So
you'll
lose
some
performance
impact
performance
gains
which
the
student
would
give.
A
If
the
URL
to
my
CDN
correct,
how
do
I
do
the
OCD
and
configuration,
or
whatever
Amazon
or
whatever,
service
and
STD
and
configuration
in
optimal
way,
you
don't
have
to
worry
about
that,
will
take
care
of
the
whole
thing
for
you
and
if
you
go
and
flip
and
disabled
or
enabled
office
365
CDN,
we
actually
make
and
flip
the
URL
so
automatically
for
you.
So
you
don't
need
to
have
to
worry
about
the
URL
setup
at
all
and
that's
absolutely
brilliant.
A
A
Well,
the
default
behavior
is
toughest
races
to
five
CDN,
but
you
are
able
to
control
this
in
the
manifest
files
and
I'll
show
you
that
in
a
second.
Why
is
this
an
awesome
thing
as
there's?
No
additional
asset
hosting
location
needed
will
take
care
of
all
of
that
for
you
organization
in
control
of
solution
assets
and
that's
a
really
important
thing
as
well,
and
that
means
that
you
as
a
tenant
admin
or
the
person
who
has
the
permissions
to
deploy
the
stuff
in
our
catalog
controls
when
the
JavaScript
files
are
getting
updated.
A
So
there's
no
way
for
somebody
go.
Do
that
it's
a
random
CDN
location
and
update
the
the
JavaScript
file.
You
actually
control,
because
the
JavaScript
files
are
stored
inside
of
your
content,
inside
of
your
site
collections
and
that's
actually
great,
let's
say
additional
security
measurement
as
well
and
possible
to
promote
the
same
package
and
to
dev
you,
eighty
and
a
quad
really
big
thing,
because
this
changes
the
whole
ball
game.
I
can
actually
now
do
a
sample.
A
Wit,
port
and
I
can
send
that
so,
let's
say
Chris
Kent
now
using
an
email
and
say:
hey
Chris,
can
you
have
a
look
on
this
one?
Can
you
get
me
a
feedback
or
you
can
do
the
same
package
which
is
coming
out
of
the
visual
studio
online
as
a
package
solution
or
from
your
let's
say
visitors
to
their
code.
You
are
able
to
take
the
exactly
the
same
package
student,
the
very
part
URLs
and
move
it
between
two
death.
You
ate
the
environment
and
production.
A
If
you
have
multiple
tenants
or
whatever
is
set
up
and
that's
a
really
really
really
big
thing,
so
a
real
deal
breaker.
So
let's
have
a
look
on
this
one
in
practice
as
well.
So
let
me
flip
to
screen
sharing
what
I
didn't
have
the
most
like.
Absolutely
we'll
have
a
look
on
this.
So
let
me
actually
share
my
screen
again
and
let
me
start
from
the
resource
to
do
code
sight
and.
A
And
and
here's
my
visual
studio
solution,
so
let's
actually
get
my
console
available
in
business
to
do
for
able
to
do
some
stuff
here
as
well.
So
this
is
just
then
and
really
plain:
I
just
scuffle
the
solution,
there's
nothing
special
here
and
and
if
we
have
a
look
on
the
right
manifests,
which
is
the
one
which
we
need
to
update
by
default.
A
If
we
want
to
host
stuff
in
the
CDN
and
we
were
forced
to
do
in
the
past,
you
need
it
to
always
figure
out
what
is
the
URL
and
in
here
you
do
not
necessarily
need
to
do
that
anymore.
So,
the
by
default,
the
in
the
packet
solution.
We
have
a
new
attribute
which
controls
our
we're
packaging,
our
assets
inside
of
the
SP
pkg
file-
and
that
is
this
asset.
An
attribute
here,
which
is
called
include,
client
assets
and
by
default,
is
true,
so
but
you're
able
to
flip
that
to
false.
A
A
Okay,
good
good
sir
Oh
just
confirming
so
the
include
client
side.
Assets
is
true
by
default
and
now,
if
I
do
cop
bundle,
ship,
we're,
gonna,
hack,
again,
I
guess
the
solution
get
it
ready
to
go,
and
then
that's
just
bundling
the
JavaScript
files
or
trans
compiling
the
type
script
in
JavaScript
for
all
of
the
process,
good
to
go,
and
then
we'll
do
called
package
solution
and
that's
a
ship
and
that
will
prepare
our
solution
file
to
be
deployed
on
the
tenant
and
that
generates
the
file.
A
And,
let's
quickly,
have
a
look
on
the
file
before
we
use
and
test
that
everything
is
working
properly.
So
in
the
in
the
SharePoint
solution-
and
we
have
this
PPK
a
file
and
what's
great
about
the
solution
structure,
is
that
you
can
always
extend
the
debug
folder
in
the
solution,
and
this
is
exactly
what's
inside,
of
the
SP
pkg
file.
If
you
rename
this
PPK
file
as
a
sip
you're
able
to
extract
an
LC
and
that
these
are
the
files
which
are
inside
of
there
as
well.
A
The
whole
point
of
this
one
is
that
we're
able
to
see
what's
inside,
of
the
the
SP
pkj
file
and
one
of
the
things
what
is
now
inside
here
is
also
the
client-side
assets,
so
the
bundle
and
also
the
the
the
language
files
for
the
JavaScript.
So
there's
the
bundle
and
there
is
actually
the
language
translations
and
these
are
available
inside
of
the
packets,
the
other
fake
thing.
What
we
do
is
that
we
changed
how
we
actually
enable
creping.
How
do
we
define
the
URL?
A
So
if
you
do
not
change
anything
and
if
you
do
not
define
the
URL
to
see
the
URL,
your
CDN
URL
will
be
SP
client-side
asset
library,
which
this
attack.
It's
a
label,
it's
label
to
tell
the
SharePoint
that
this
is
the
one.
This
is
the
one
well
for
this
web
part
you
should
be
flipping.
The
URL
automatically
based
on
is
to
see
then
enabled
or
not.
A
So
you
don't
need
to
worry
about
this,
to
see
it
and
enabled
or
not,
and
what's
the
URL
we'll
take
care
of
all
of
that
for
you
and
that's
a
really
really
really
great
thing.
So,
let's
have
a
look
on
this
one
in
practice,
so
I'm
gonna
actually
do
install
that
solution
from
the
solution
folder,
which
we
just
compiled
and
let
me
use
slightly
different
tenant
for
the
testing
so
that
all
the
capabilities
are
available.
A
I
can
drop
the
asset
packaging
in
here
and
there's
the
asset
packaging,
and
one
of
the
things
notice
here
is
that
the
URL
client-side
solution
will
get
content
from
the
following
domains.
Point
online:
why?
Because
it
depends
again
on
the
hysteresis
if
I
say
then
sitting
with
what
is
the
URL
whatever
kind
of
users
here
now
I'm
gonna
use
the
tenant
scoped
option,
so
I
can
actually
quickly
show
how
the
URL
is
getting
rendered
automatically
and
I'm
not
going
to
deploy
this
one
directly
in
their
name.
A
The
tenant
now
to
be
able
to
use
the
to
be
able
to
use
the
solution.
I
will
quickly
go
and
double
check.
What
is
my
solution
with
part
name,
so
I
can
actually
find
it
in
the
Wetwork
picker.
So
my
wit
part
name,
is
the
tenon
scoped
asset
Wetwork
actually
get
that's
my
house
in
case
site.
Let's
create
a
page,
let's
in
the
page,
select
the
tenant
scoped.
What
was
it
tenant?
Something
related
on
telescope
assets
and
there's
my
web
part.
A
So
without
me
doing
any
hosting
anything,
any
setups
everything
is
getting
served
and
where
is
it
actually
getting
served?
So
let's
actually
have
a
look
on
that
one
as
well
in
this
case,
and
the
CDN
has
been
enabled
in
this.
So
let's
have
a
look
on
the
URL
and
if
we
have
a
look
on
the
sources
actually,
let's
let's
fill
that
this
in
here
click
see
so
now.
If
I
request
at
the
URL,
we
can
say
that
the
tenant
scoped
assets
are
getting
loaded
from.
A
Oh,
how
do
I
zoom
in
there
shall
I
say
that's
more
easily
from
here.
I
probably
can
say.
Definitely
you
say
from
here
we're
able
to
say
that
the
this
seek
asset
is
getting
actually
loaded
from
the
public
CD
and
automatically
what's
interesting
around
the
URL
is
also
I
can
actually
show
you
that
URL
is
that
it's
saying
that
it's
the
public,
CD
and
sharepoint
online,
of
course,
as
cantos
ademma
SJS
hairpin
turn
commerce
less
sites
as
app
catalog,
slash
client-side
assets.
A
So,
basically
now,
if
we
would
disable
the
CDN,
we
would
just
flip
this
URL
would
be
flipping
to
its
it
it'd
be
condo
so
demo
as
cheat
of
sharepoint
outcomes,
websites
as
app
catalog
source
transit
asset.
So,
depending
again
on
your
CDN
setting
and
the
URL
will
be
coming
from
the
CDN
or
either
directly
from
the
side,
and
you
don't
have
to
worry
about
changing
that
URL
everything
is
fully
automatic.
Based
on
this
big
84
and
that's
superb,
isn't
it.
A
Should
we
used
officer
stuff
sittin
on
the
dock
leap
approach
for
saving
asset,
so
this
christians
question
is
good
because
that's
exactly
what
we're
doing
here,
so
we
aren't
actually
using
doclet
if
the
syrian
is
disabled,
if
to
say,
then
is
enabled
then
were
using
CDN
and
everything
is
fully
automatic
and
is
CDM
better
than
using
a
document
library
in
office
365,
absolutely
because
CDN
is
getting
the
assets
closer
to
the
user.
So
that's
the
whole
point
of
the
content
delivery
networks.
It
will
have
a
performance
game
now.
A
Some
people
might
be
saying
that
the
public
CDN
isn't
good,
because
the
javascript
files
are
gain
exposed
anonymously
outside
of
the
tenon.
But
it's
only
choice
get
false.
It's
not
the
content
on
all
ABARES
questions,
so
the
client
side
asset
Syrian
origin
is
set
automatically
by
Microsoft.
Ec
DNS
enabled
correct.
You
do
not
have
to
set
this
manually.
All
of
the
URLs
are
getting
automatically
updated
so
for
this
particular
web
part
we're
just
saying
we.
A
The
definition
was
like
this,
or
the
definition
was
such
SP
client-side
library,
and
all
of
that
is
getting
automatically
replaced
based
on
again
the
tenant
level
settings
and,
unfortunately,
having
hard
time
and
zooming
on
that
one.
But
it's
saying
public
stayed
in
automatically.
I
can
see
this
being
useful
once
we
have
an
ability
to
put
our
own
solution
in
door
first
or
am
I
onto
something
there.
A
Wesa
I
can't
confirm
or
deny
anything,
but
David
has
good
idea
a
good
way
of
thinking
on
that
one
as
well,
because
again,
one
of
the
challenges
within
this
door
and
a
marketplace
perspective
may
be
for
customer
might
be
that
hey.
If
it's
a
JavaScript
file
hosted
in
external
stadion,
somebody
might
be
able
to
change
the
CDN
if
it's
a.
If,
if,
however,
the
javascript
file
is
getting
hosted
dynamically
from
the
content
of
the
tenant,
then
customer
owns
the
location
that
it
is
part
of
the
content
of
the
tenant.
A
So,
therefore,
the
risks
of
any
security
challenges
around
the
store,
handling
less
but
and
the
store
story
is
still
not
quite
there.
Yet
we're
working
on
the
store
story
and
that
might
come
in
the
future,
but
good
way
of
thinking
from
David,
but
really
really
really
great
capability,
and
this
will
be
part
of
21.4
release
of
human
templates,
which
is
coming
out
relatively
soon.
I,
like
mentioned,
when
we
started
the
roadmap
discussion,
it
will
come
out
within
a
matter
of
days
rather
than
weeks.
A
So
quite
certain
I
can
guarantee
that
we're
not
going
to
ship
anything
on
the
on
the
eve
of
on
the
eve
of
Thanksgiving
or
the
day
after
Thanksgiving,
because
everybody
will
be
shopping,
something
probably
in
u.s.
tomorrow
rather
than
working.
If
there's
any
potential
issues
but
I
think
that's
it.
We
went
through
our
three
minutes
long
from
a
Content
perspective.
A
I
do
apologize
and
that's
not
a
massive
amount
additional
time
for
Q&A
and
we
went
through
some
of
the
questions
as
we
move
it
along
on
the
demos
and
if
we
messed
up
the
Skype
kind
of
messed
up,
some
of
the
some
of
the
schedules
as
well,
but
the
whole
point
of
this
webcast
and
sr8.
This
special
interest
group
call
was
around
going
through
those
three
capabilities
which
we
demonstrated
last
week
in
the
ended
up
link
as
well
and
get
the
whole
thing.
They
record
it.
A
Quick
question:
can
you
say
something
to
the
scopes
from
the
more
MS
craft
support
on
the
preview
for
Dec
data
endpoints?
So
this
is
good
question
from
Rolf.
So
what
will
happen
on
as
part
of
the
next
step
on
the
craft
scientist
that
will
actually
give
you
all
the
Scopes
what
you
want,
but
it's
going
to
be
a
tenant
administrator
grinding
those
two
scopes.
The
whole
system
works
in
a
way
and
we
actually
were
talked
about
this
one
in
ignite
session
as
well.
A
We
will
give
you
a
SharePoint
application
object,
which
basically
is
the
object
and
application
in
the
ASO
ad,
which
is
behind
of
the
craft
client,
and
then
the
tenant
administrator
is
able
to
add
additional
scopes
for
that
object
or
that
application.
So,
technically,
if
your
tenant
administration
approves,
you
can
add
whatever
scopes
to
the
craft
client
as
you
wish,
but
it
really
comes
down
again
on
the
fact
that
there's
a
tenant
at
administrative
operation
for
adding
those
scopes
in
so
you
as
a
developer.
A
You
can't
do
it
and
this
is
required
so
that
there
is
a
tenant
level
control
and
then
an
admin
level
control
on
getting
additional
access.
So
if
you
have,
if
you're
good
friends
with
your
let's
say,
10
an
administrator
and
they
trust
you
and
they
trust
your
code
and
there's
a
proper
covenants
and
you
can
get
whatever
you
want
photograph.
What's
it
gray,
but
and
that's
that's
really
the
way
it
will
be
implemented.
A
The
preview
will
be
available
in
mid-december
and
then
we'll
move
forward
from
there
and
get
the
feedback
in
so
really
nice
for
the
admins
and
not
to
care
about
them.
Yes,
but
I
really
I'm
super
stoked
about
that
capability
as
well
and
super
excited
because
it
will
end
unplug
all
of
the
craft
scenarios,
but
the
key
point
being
on
the
fact
that
the
talent
administrator
has
to
approve
those
additional
scopes.
So
we
as
a
Microsoft,
we
cannot
actually
allow
additional
scopes.
A
There
will
be
default
scopes
and
that's
days,
that's
it,
but
we'll
make
the
option
of
granting
additional
scopes
for
the
craft.
Cornett
cool
I!
Think
that's
it
for
this
one,
so
hopefully
interesting
stuff,
we'll
keep
on,
and
the
video
recording,
Thank
You
bird
for
saving
the
recording,
we'll
get
the
recording
on
the
YouTube
channel
tomorrow.
If
somebody
needs
to
say
this
again
and
feel
free
to
ping,
us
in
social
media
and
other
channels
to
ask
additional
questions.
What's
on
what
is
coming,
LM
ap
is
already
outside
close.
A
Let's
go
catalog
coming
pretty
soon
slight
package
at
packaging
coming
up
really
soon,
as
well
with
the
yeoman
template
version
1.4
for
us,
people
enjoy
your
Thanksgiving
and
have
have
a
relaxing
weekend
and
for
European
and
Asian
people
who
are
not
who
are
working
tomorrow.
Let's
get
back
to
work
and
be
have
fun
with
a
sharepoint
development,
but
thank
you
everybody
for
joining
sorry
for
slightly
going
late
on
the
on
the
call
who
doesn't
usually
happen,
but
will
I
do
apologize
to
describe
issues.
Thank
you,
everybody
and
we'll
be
absolutely
in
touch
bye-bye.