►
Description
More details on the covered content in this webcast from http://dev.office.com/blogs
A
A
B
A
Very
so,
let's
immediately
dive
into
the
details,
so
you
heard
the
term
modern
quite
a
lot
recently.
We
always
talk
about
modern
experiences
and
maybe
that's
not
really
a
future-proof
name,
modern,
because
a
certain
point
it
probably
we
have
to
call
them
the
it
used
to
be
modem
experience,
but
we'll
see
there's
something
to
figure
out
in
the
future.
A
Today
we
call
it
modern
and
what
does
modern
actually
mean
it's:
a
collection
of
new
user
experiences
and
functionality
that
really
sure
sharepoint
online
and
in
the
modern
bucket
we
see
obviously
25
group
sites
or
modern
team
sites.
So
the
new
team
sites
that
you
can
create
from
shopping
online.
We
see
that
the
new
modern,
listen
library,
experience
and
modern
pages,
so
these
three
topics
are
kind
of
the
modern
set
of
functionalities
that
we
talked
about
now.
A
These
modern
experiences
are
turned
on
by
default
in
your
tenant,
so
Microsoft
takes
a
policy
of
releasing
fairly
quick
and
adding
new
functionality
in
a
quick
pace
and
turning
it
on
moyes,
often,
but
typically
you
as
an
admin,
can
always
turn
it
off
again,
because
maybe
it's
too
early
to
absorb
this
new
functionality,
because
it's
not
feature
complete
enough
for
you
as
a
user,
or
you
want
to
prepare
the
whole
lot
of
the
feature
in
your
organization
and
so
depending
on
on
the
organization
size
that
super
important.
Now.
A
B
B
So
it's
not
like
a
one-off
based
on
how
the
side
was
graded
and
that's
really
the
thinking
behind
of
having
these
multiple
scopes
around
this,
but
like
bird
mentioned
as
an
administrator,
you
probably
want
to
be
aware
which
kind
of
sites
and
which
kind
of
list
which
kind
of
bait
is
not
getting
created
and
using
the
terminal
configurations
you
can
control
them.
Typically,
there
is
change
management
requirements.
If
you
have
customizations
that
might
be
a
factor,
and
all
of
that,
so
let's
actually
have
a
look
on.
How
do
we
control
this.
A
Yes,
so
and
the
first
one
we're
going
to
have
a
look
at
this
is
the
the
governance
and
the
management
of
creating
modern
sites,
and
this
one
is
as
a
scope
tenant.
You
see
on
top
air
scope,
tenant,
so
you'll
see
when
the
auto
settings
come
along,
that
they
have
different
scopes.
So
controlling
modern
team
saturation
is
only
done
at
talent
level.
Now
in
tenant
administration
you
go
to
the
settings
page
and
we'll
show
this
is
a
demo
later
on
in
settings
page.
A
Has
this
section
where
you
can
configure
your
modern
team
side,
curation
experience,
essentially
what
you
can
do
is
first
of
all,
on
top
just
hide
it
at
all.
So
if
you
don't
want
your
end
users
to
be
able
to
create
site
collections,
you
can
simply
prevent
them
from
doing
that.
You
might
have
your
own
site
fishing
solution
and
at
that
point
you
have
different
entry
point
for
users
to
go
and
create
site
collections.
Finally,
you
hide
it.
If
you're
using
the
Ulta
box
experience,
you
typically
will
show
the
west
side
experience
through
your
end
users.
B
A
A
modern
team
site,
which
is
a
sharepoint
online
site,
combined
with
a
group
and
azure
ad
and
with
an
exchange
mailbox
essentially
so
we'll
give
you
all
three
of
that.
However,
with
that
option,
if
the
user
does
not
have
permission
circulating,
muttering
groups,
cursor
groups
in
just
regular
groups
at
that
point
will
fall
back
to
a
classic
site.
So
this
gives
you
a
kind
of
bit
of
both
worlds.
User
can
create
it.
You
get
a
modern
one.
If
not,
you
fall
back
to
classic.
A
If
you,
whoever
would
like
to
really
be
clear
on
I,
always
create
modern
or
create
classic,
you
have
to
choose
either
option
two
or
three
so
option
to
a
site
with
knobs
right
group.
It
only
allows
to
create
a
modern
team
site
if
there's
not
possible
due
to
permissions
or
other
restrictions
of
the
user,
that
pointy
that
the
link
will
not
be
there.
A
The
final
one
is
the
old-school
classic
behavior,
so
the
classic
team
site.
If
you
want
to
keep
on
20
classic
sides,
you
can
do
that
by
selecting
this
thurs
option.
I
pasted
this
link
below
on
a
slide,
which
gives
a
good
few
on
how
to
kind
of
control
who
can
create
modern
groups,
because
it's
not
by
default,
giving
it
every
end.
Users
is
allowed
to
create
a
group
in
your
organization.
So
if
you
notice
that
hey
I'm
admin
I
can
create
a
group
but
I've
enabled
the
switches.
My
end
users
cannot
do
that.
B
This
one,
it
happened,
subspace
super
super
clear
on
this
on
this
controls,
only
the
UI
experience
so
programmatically
you
can
still
create
classic
or
modern.
So
if
you
have
a
self-service,
I
creation
solution
as
an
example,
this
does
not
impact
on
so
that
from
a
AP
at
this
does
not
control
anything
on
our
API
level.
It's
only
the
UI
in
a
point
landing
page
right
here.
Until
yes,.
A
Ok,
moving
on
keeping
up
the
pace.
Let's
talk
about
pages.
The
modern
age
is
so
when
you
create
a
modern
site
by
the
fold,
when
you
add
a
page
size,
it
will
be
a
modern
page
good
now.
Modern
pages
are
also
enable
for
classic
sides.
So
if
you
have
a
classic
team
site-
and
you
do
add
a
page-
you
will
get
a
modern
page
like
a
fluent
responsive
to
H,
where
you
can
put
a
modern
client-side
web
part
on
top
of
the
page.
A
If
you
ever
do
not
light
that
behavior,
you
can
turn
off
on
two
different
scopes
completely
at
ten
on
scope,
so
for
your
complete
down
and
turn
it
off
or
at
individual
web
level,
talent,
level.
Turning
off
go
so
I
again
by
tenant
admin
settings-
and
there
is
this
site
pages
section,
which
is
a
really
confusing
wall
set
in.
A
Using
an
idiot,
if
you
want
to
allow
modern
pages,
you
have
to
choose,
allow
users
to
create
side
pages.
If
you
only
want
to
allow
classic
pages,
you
have
to
choose,
prevent
you
from
creating
side
pages.
So
essentially
you
have
to
read
site
pages
as
modern
pages
in
the
same
UI
and
that's
confusing
so
should
fix
that.
Actually,
ok,
but
suppose
you
have
enabled
to
the
talent
level,
but
you
still
want
to
disable
it
at
certain
sites,
and
you
can
do
that
how
you
do
that
is
by
disabling
the
modern
page
feature.
B
And
one
thing
one
thing
maybe
on
that:
one
is
that
if
you
have
already
existing
significant
amount
of
existing
site
collections
and
sides,
you
might
want
to
actually
keep
on
using
the
classic
wiki
page
experience,
but
then
use
the
modern
for
new
science.
And
then
that's
disabling.
That
feature
in
a
site
level
which
paid
option
to
go
so
disabling.
That
feature
on
all
of
the
classic
size
or
all
of
the
existing
site,
but
then
allowed
the
new
sites
to
be
using
at
the
modern
beta
experience.
It.
A
B
A
A
So,
first
of
all
again
tenant
same
story,
tenant
admin
of
the
settings
in
here
you
have
an
option:
fidgeting
classic
and
new
experience.
Classic
really
means
everything
is
classic.
Everything
is
the
old
SharePoint,
this
library,
user
interface
new.
However,
this
does
not
mean
that
everything
is
in
in
the
modern
experience
there
is
this
auto
detect?
Essentially,
what
it
means
is
that
I'll
try
to
render
your
library
in
the
modern
experience,
but
certain
types
of
libraries-
that's
not
possible.
A
Some
libraries
might
be
using
customizations,
which
are
not
yet
supported
in
the
mobile
experience
and
the
search
will
fall
back
to
classic.
So
we
try
to
always
give
you
the
model
on,
but
if
we
see
like
a
good,
don't
be
done
or
fall
back
to
classics
that
the
current
model,
one
gotcha,
when
you
change
this
setting
at
that
level,
it
takes
some
time
for
the
tenant
to
absorb
the
setting.
Essentially
a
my
testing
I
see
it.
It
can
take
even
up
to
one
hour
or
more
before
the
setting.
Will
it
takes
a
section.
A
A
Okay,
we
talk
to
our
tenant,
then
side
and
web
scope
similar
to
the
to
the
pages
model,
but
this
case
instead
of
disabling
a
future.
We
have
to
enable
a
blocking
feature.
So
we
have
two
new
features:
one
side
and
one
a
web
scope
feature
and
actually
did
the
site
slide,
showing
side.
They
should
be
work.
Two
features
which
you
have
to
enable.
So,
if
features
enabled
the
modern
listen,
I've
experienced
will
be
blocked
at
the
site,
collection,
scope
or
a
particular
web
scope.
A
A
B
B
A
The
checking
works
in
a
way
that
it
will
kind
of
start
running
all
through
all
the
settings
that
control
the
behavior
soon,
as
it
finds
one
that
says
like
okay,
what
Ernest
off
is
good
moderns
off
it
stops
even
with
checking
it
doesn't
continue
anymore.
So
if
it's,
if
you
enable
the
site
level,
you
don't
have
to
do
with
it
at
at
the
web
level.
A
O.K
talked
about
tenant
site
work.
Now,
let's
go
to
the
final
one,
which
is
just
so.
If
you
have
an
abduction
library
or
a
list,
you
can
go
to
list
settings
advanced
settings
and
in
there
you
have
this.
This
experience
options
by
default.
It
will
be
set
to
the
first
one
default
experience
by
the
administrator,
which
essentially
maps
to
the
setting
you
have
in
your
tenant.
So
if
the
tenant
set
the
classic,
this
means
classic
attendance
is
set
to
modern
the
new.
A
A
What
does
it
mean
for
us?
Essentially,
what
can
you
do
with
the
setting?
Besides
just
kind
of
experimenting,
and
the
thing
with
this
one
is
that
this
setting
overrides
all
the
other
settings.
So
if
a
tenant
level,
for
example,
modern,
is
turned
off
for
this
and
I
wish,
and
you
want
to,
let's
say,
do
a
pilot
for
modern
for
a
subset
of
your
users
or
subset
of
your
site
code
sites.
A
You
can
go
to
those
sites
enable
the
setting
with
the
one
on
the
new
experience
and
then
they
will
show
up
the
new
modern,
UI,
there's
also
an
API
call
for
doing
the
surgery.
You
can
perfectly
script
this,
and
this
way
you
can
do
a
kind
of
a
a
face
test.
The
rollout
of
more
than
this
live
experience.
B
A
A
Let's
pump
up
the
sides,
so
are
right,
so
in
athen
a
lot
of
settings
and
very
bottom,
we
have
admin
centers,
which
you
can
expand
and
in
here
does
link
the
sharepoint
admin
so
clicking
that
one
which
will
load
the
sharepoint
admin
side
typically
follow.
This
admin
site
is
using
your
tenant
name,
so,
let's
say
contoso
dash
admin
but
sharepoint
com.
So
if
you
know
your
name,
you
can
just
directly
hit
the
set
sharepoint
talent,
admin
site.
A
Once
in
the
talent
admin
side
you
can
go
to
settings
and
then
settings
you
will
find
the
settings
that
I
talked
about
in
in
the
slides.
So
here
we
have
our
listen
I've
experienced.
If
you
scroll
down
we'll
also
see
site
pages
over
here
at
the
bottom.
We
have
the
site
creation
settings
that
you
can
control
so
fairly
simple.
A
A
B
A
B
A
Sometimes
this
doesn't
work
ability,
so
you
might
experiment
to
the
future
and
its
faces,
especially
if
it
stays
in
classic
it
doesn't
fit
the
modern.
There
is
a
cookie
that
describes
your
preference
essentially
and
if
that's
six
round,
then
you
can
keep
on
flipping
the
switch
with
it
as
long
as
your
peers
around
to
stays
in
classic,
then,
with
the
end
documentation
which
all
shared
link
you
would
you
really
soon
and
contains
some
information
around
how
to
which
cook
it
is
essentially
and
also
how
to
move.
A
A
Back
to
the
slides
and
to
the
closing
light,
so
resources
go
check
out
this
msdn
articles
around
how
to
customize
model
experiences
because
they
also
contain
the
information
you
saw
in
this
webcast
how
to
manage
your
mom
experience.
It
also
contains
two
detectives
around
the
cookie
edge.
I
just
talked
about
it
so
and
we
keep
on
updating
those
articles.
So
we
do
like
almost
weekly
small
changes
to
the
articles,
making
them
better
and
adding
new
elements
to
it
so
great
resource
for
you
to
ruin
about
modern.
B
Not
really,
yes,
I
think
the
webcast
is
great
for
for
showing
the
different
options
when
you
as
a
tenant,
administrator
or
as
an
architect
making
those
decisions,
how
people
are
seeing
the
UI's
of
sharepoint
and
office
365
and
sharepoint
online,
and
you
really
need
to
consider
these
options
so
that
you
can,
you
know
exactly
what's
happening
within
your
tenant,
but
I
think
they
missed
an
article
reference.
What
Burke
mentioned
absolutely
great
one.
That's
also
referencing
support
articles
from
the
support
office,
support
channel
and
for
the
additional
details.
B
So
there's
a
lot
of
the
insights
over
there
how
to
how
to
have
that
control
within
your
tenam,
so
that
you're
not
getting
surprised
by
hey.
How
am
I
seeing
this
kind
of
bad
behavior
but
I
think
that's
it
Thank
You
Bert
for
the
great
demo
as
well,
so
my
friend
I
think
it's
time
to
wrap
up
and
please
give
us
feedback
and
let
us
know
around
the
mornings
and
modern
features,
modern
experiences
and
also
around
if
you
have
any
input
that
run
this
webcast.
But
thank
you
and
bye,
bye.
Everyone
bye.