►
Description
In this PnP webcast we concentrated on the practicalities around transforming on-premises SharePoint customizations to SharePoint Online. More details on covered topics can be found from http://dev.office.com/blogs
A
Welcome
everybody:
this
is
SharePoint
banners
and
practices.
Webcast
and
system
wanted
to
concentrate
on
how
to
transform
your,
let's
say:
on-premises
customizations
to
SharePoint,
Online,
so
kind
of
a
different
aspects
and
different
things
to
consider
when
you're
planning
to
move
your
on-premises
deployments,
including
some
of
the
customizations
to
the
SharePoint
Online,
my
name
is
Sarah
Juana
I'm,
a
Senior
Program
Manager
from
shipment
engineering
and
with
me
today
say
one
of
the
well
known
specialists
on
this
areas.
Well,
everyone
opponent
is
well.
B
A
And
obviously,
because
we're
not
well,
we
want
to
keep
this
as
a
technical
discussion,
we're
not
going
to
really
demo
what
urban
is
doing
online,
but
rancor
has
great
products
on
this
segment
as
well,
which
you
might
want
to
check
out
in
the
future
as
well
now,
so
urban
is
a
product
owner
on
transformation.
Personally,
I've
done
before
moving
into
the
SharePoint
engineering
I
work
two
years
full
time
on
transforming
how
would
I
put
it.
A
That's
a
bit
of
a
warning:
we're
not
going
to
do
any
actual
demos
that
the
reason
for
that
one
is
that
we
want
to
keep
this
webcasts
relatively
short,
not
like
two
hours
and
so
on,
and
so
we're
kind
of
a
talking
about
the
key
points
to
consider
key
transformation
aspects
and
the
process
itself,
rather
than
be
driving
on
individual
challenges
and
AD
patterns
as
well.
All
that
is
documented
in
Emison
in
a
pretty
ok
format.
A
Now,
before
we
actually
go
to
the
actual
discussion,
one
one
key
point
to
understand
when
you're
moving
to
the
SharePoint
Online,
it
does
not
actually
mean
that
they
cannot
be
customizations,
and
this
seems
to
be
something
based
on
a
feedback
or
give
it
getting
every
now.
And
then
the
people
are
slightly
confused.
A
Yes,
you
can
have
customizations
and
customization
typically
can
achieve
up
to
100%
of
the
functional
requirements.
The
thing
is,
though,
that
you
need
to
implement
those
customizations
slightly
differently,
so
you
cannot
use
farm
solutions
or
starts
which
would
contain,
let's
say
feature
xml's,
which
are
deployed
to
the
file
system
in
alpha,
but
from
a
functional,
an
ink
user
perspective.
You
can
absolutely
still
have
the
native
customizations
that
the
way
they're
being
run
into
the
market
is
like
a
different
right.
B
Yeah,
so
what
I
hear
is
over
what
I
usually
say
to
people
is
that
it's
actually
a
different
mindset.
It's
the
same.
You
can
do
the
same
in
the
end.
For
the
end
user
perspective,
it's
it's
almost
one
hour
but
at
the
same
functionality,
but
you
the
way
you
implemented.
It
is
completely
different
and
what
I
hear
a
lot,
for
instance,
is
like
people
yeah,
but
I
need
elevated
privileges.
A
So
they're,
coming
back
on
our
example
elevation
is,
is
a
good,
a
really
good
example.
You
can
actually
elevate
that,
but
you
need
to
implement
that
in
a
slightly
different
way,
exactly
and
and
which
is
absolutely
possible
you,
you
can't
take
your
existing,
let's
say,
form
solution
code
and
just
plug
it
in
to
run
in
a
SharePoint
Online.
That's
never
going
to
happen.
We
can
make
that
happen
in
SharePoint
Online,
because
the
form
solutions
are
running
in
the
context
of
the
farm
and
in
a
single
farm,
a
SharePoint
Online.
A
You
can
have
thousands
of
sounds
so
we
will.
We
would
compromise
to
other
tenants
when
example
is
deploying
a
code
which
is
not
acting
properly,
but
you
can
achieve,
for
example,
elevation
by
call
up
calling
a
web
api
in
Azure
and
then
that's
going
to
call
back
using
elevated
privileges.
So
there
are
multiple
patterns.
How
to
make
these
things
happen,
yeah
good.
So
before
we
actually
move
into
the
process,
discussion
and,
let's
say
the
key
recommendations,
there's
obviously
this
massive
amount
of
those
available,
but
we
wanted
to
raise
few
of
them
within
the
webcast.
A
A
Now
SharePoint
development
options,
so
classic
SharePoint
development
option
was
SS,
B's
farm
solutions
or
mounts,
and
pro
solutions
as
well.
Sandbox
solutions
were
highly
limited,
sandbox
solution.
Code-Behind
is
no
longer
supported
in
SharePoint
Online
and
even
though
technically
you
can
run
declarative
sandbox
solutions
in
SharePoint
Online.
A
It's
definitely
not
the
preferred
option,
because
that
actually
adds
complexity,
there's
no
API
to
activate
those
sandbox
solutions,
inside
collection
and
all
of
them,
and
even
though
there
would
be
there's
additional
implications
of
sandbox
solutions
and
feature
xml's
being
present
on
the
sides
which
would
harm
you
in
the
future.
So
not
definitely
the
best
option
for
SharePoint
Online
and
farm
solutions
or
better,
not
supported
in
office.
365
ego
I,
actually.
A
Thing
it
is,
it
is
and
part
of
this
transition
when
we
took
away
the
code
behind
sample
solutions,
both
in
SharePoint
Online.
We
actually
further
enhance
our
remote
APs,
so
we
we
did
work
together
with
our
ifvs
and
going
through
and
making
sure
that
whatever
sandbox
solutions
they
were
using,
they
can
achieve
exactly
the
same
thing
using
remote,
IPS
using
rest
api,
so
season
8
the
ice.
Now
that's
fun
solution
not
in
office.
365
are
in
SharePoint
Online
and
never
will
be
that's
out
of
question.
A
The
second
option
is
to
add
a
model,
so
adding
model
was
introduced
in
SharePoint.
2013,
absolutely
still
support
it
and
we'll
keep
on
investing
on
this
one.
There
are
scenarios
where
adding
model
is
the
right
choice
in
the
future
as
well,
especially
if
you
want
to
have
that
security
isolation
for
the
customizations,
because
adding
model
is
taking
advantage
of
off
when
it's
executing
anything
within
the
context
of
funding.
There
was,
however,
a
small
carnival
at
our
libraries.
A
A
big
limitation
on
the
adding
model,
which
is
quite
typical
discussion
around
data
model
is
that
the
web
part
experience
knotted.
The
web
part
experience
was
that
the
functionalities
in
iframe,
which
does
not
scale
it's,
doesn't
scale
in
the
responsibly
and
also
so.
People
will
not
really
super
happy
happy
on
that
fun.
From
an
interior
perspective,
you.
B
A
So
you
can't
really
expose
them
in
the
context
of
Farpoint,
but
you
can
actually
build
super
cool-looking,
you
eyes,
which
have
been
allocating,
for
example,
information
from
SharePoint
site
using
the
SharePoint
REST
API,
since
this,
or
maybe
as
an
author
I.
Don't
like
the
big
challenge
of
this.
One,
obviously
is
that
you
are
fully
responsible
for
implementing
to
you
is
to
the
SharePoint
is
just
a
data
layer
in
that
case,
but
you
have
plus
well.
You
have
flexibility
and
outside
of
SharePoint
an.
A
But
the
SharePoint
framework
gives
you
the
flexibility
of
embedding
your
total
script
on
a
SharePoint
Online
in
a
reliable
way.
So
to
say
it
provides
administrative
control
so
that
tenant
tenant
administrator
can
control
who's.
Putting
what
customizations
on
the
sign
and
you're
going
to
trust
that
control
based
on
a
requirement.
It
has
a
flexible
web
part
model
and
which
is
clearly
a
trust
and
that
was
targeted
to
address
the
let's
say
to
feedback
around
add-ins,
because
add-ins,
the
web
part
is
running
in
an
iframe
which
you
have
on
framework.
It
is
not.
A
The
web
part
is
actually
running
in
the
Condors
of
the
page,
but
then
that
has
Oberto
base
implications,
which
is
which
are
impacting
the
security
model.
So
you
need
to
understand
what
is
that
web
part?
What
does
it
actually
do
when
you're
putting
that
on
a
page
and
what
that's
really
the
key
reason
why
it's
cannot
admin
Steve
operation
to
get
those
from
it
in.
B
My
opinion,
within
the
SharePoint
framework,
the
whole
security
model
great,
is
greatly
simplified.
It's
much
easy
to
grasp
what
is
going
on
and
what
is
supposed
to
do,
instead
of
when
they
add-ins,
where
they
add-in
has
its
own
security
needed
rights
to
do
something
on
a
document
library,
it's
likely
that
it
has
the
user
that
has
certain
access
to
it,
etc,
etc.
So
there
were
so
many
layers
with
add-ins
that
you
have
to
keep
track
of
so,
and
they
still
make
sense
in
certain
contexts,
but
with
the
SharePoint
framework,
it
has
been
greatly
simplified.
B
A
Absolutely
super
straightforward
super
understand,
understandable
and
other
products
and
services
are
doing,
create
a
much
the
same
model
as
well.
So
it's
kind
of
easily
understand
what
are
we
doing
here
and
the
SharePoint
framework
is
being
built
using
the
industry
standard
development,
but
also
using
web
stack
and
using
the
whatever
JavaScript
framework
you're
going
to
use
and
all
of
that,
so
it
is
no
doubt
the
most
advanced
model
as
well.
A
One
thing
to
notice
on
a
SharePoint
rainwork,
though
it's
a
UI
framework,
at
least
right
now,
so
whenever
you
need
to
actually
do
something
long-running
operations,
for
example,
then
you
need
to
call
a
plus
a
custom
web
api
or
asha
function
from
a
chef,
my
favorite
part
to
start
the
process
and
then
that's
going
to
do
the
long-running
operations.
So
from
that
perspective
you
are
always
combining
some
additional
technologies
or
might
be
combining
some
additional
technologies
as
well,
not
just
chef.
One
framework,
I
think.
B
It's
also
fair
to
bring
up
the
fact
that,
because
the
SharePoint
framework
is
based
on
the
industry
standards,
they
are
typical
standards
that
have
not
been
used
in
SharePoint
before
so.
If
your
traditional
SharePoint
developer,
you
might
be
a
bit
surprised
because
the
the
whole
flow
of
developing
applications
is
very
different
from
what
you've
been
used
to
with
Visual
Studio
and
c-sharp
code,
etc.
The
shape
and
fabric
is
all
JavaScript
and
has
all
kinds
of
other
tools
connected
to
it
that
you
need
to
use
to
build
them,
deploy
the
solutions.
A
Absolutely
absolutely,
and
and
even
if
you
come
from
a
farm
so
loose
and
let's
say,
server-side
code
development
perspective,
our
still
skills
needed
or,
let's
say,
tasks
which
require
the
stay,
sharp
development,
because
that's
the
back
end
and
that's
the
wet
ap
is
and
whatever
is
running
in
inertia
or,
let's
say
Emma
Stone.
It
doesn't
really
matter
where
the
code
is
running
and
there
people
are
still
writing
server-side
code,
so
we're
not
switching
completed
at
JavaScript.
No,
that's
not
what
this
means.
A
The
UI
layer
is
completely
Chava
Script,
so
it's
fluent
fast
efficient,
but
then
all
of
the
long-running
operations
in
the
creations
and
all
of
that
they
are
still
being
done
using
a
server-side
code.
You
can
use
JavaScript
using
Noches
there
as
well,
but
if
you're
more
familiar
with
G,
sharp
or
vb.net
and
that's
absolutely
doable
as
well,
now
just
making
sure
that
people
are
super
aware
all
these
options
and
are
absolutely
fully
supported,
except
the
form
solutions.
A
Not
subordination
went
online
and
and
quite
often
you
will
combine
multiple
one
of
multiple
of
those
when
you're
actually
fulfilling
that
the
functional
requirement.
So
you
could
use
SharePoint
framework
for
the
UI
elements,
but
then
you
might
be
using
provide
a
hosted,
adding
together
with
your
custom
web
api,
to
then
call
back
on
a
sharepoint
in
elevated
permissions
way
and
all
of
that
so
there's
this
multiple
scenarios
where
we're
combining
audibles,
multiple
options.
Every.
A
Absolutely
absolutely
number
one
thing
is
to
understand:
the
difference
is
what
it
means
what's
possible,
and
then
you
can
use
that
the
right
tool
from
your
tool
belt
to
the
right
purpose
and
that's
kind
of
it's
it's
preaching
after
the
let's
say,
the
more
and
more
to
the
transformation
and
discussion
so
like
mention
when
we
started
the
webcast
I've
personally
done,
let's
say:
30
to
50
transformation
projects
for
a
large
customers.
Some
of
them
have
had
100
hundreds
of
thousands
of
accounts
and
making
them
share
that
they
can
transition
from
on-premises.
A
Just
a
punt
online,
and
one
of
the
things
we
came
up
with
as
part
of
the
process
is
kind
of
a
validated
process
which
will
help
people
to
do
and
to
be
successful
on
the
transformation,
and
this
is
a
five
step
process
which
absolutely
needs
to
start
with
readiness.
So
there
has
to
be
readiness
for
SharePoint
framework
and
adding
model
topics.
You
need
to
understand
the
hosting
decisions.
What
does
it
actually
mean
that
I'm
actually
doing
something?
A
A
hosting
SharePoint
framework,
because
even
with
SharePoint
framework,
not
just
bedding
model,
you
are
hosting
a
cello
suite
file
somewhere,
and
that
has
an
implication.
It
has
has
a
a
reason
or
implicit
technical
actions
behind
about
those
decisions
and
in
the
readiness
box,
the
the
most
important
thing.
What
I
would
say
is
the
development
model
of
readiness.
A
Then,
when
we
have
that
knowledge,
the
number
one
thing
is
assessment.
Oh,
the
second
thing
is
assessment,
and
this
is
where
you
essentially
have
a
look
on
what
we
actually
have
right
now,
within
our
form,
within
our
own
premises
form.
So
what
are
the
customizations
would
have
been
deployed,
but
not
just
concentrating
on
the
technology,
because
quite
often
what
we
saw
based
on
our
analysis
and
based
on
the
projects
and
I'm
sure
the
driving
can
sign
this
off
as
well.
A
It's
quite
often
to
75%
of
those
customizations
are
no
longer
in
use
or
they
are
being
used
by
a
really
subset
of
users,
so
really
understanding
the
usage
wist
of
the
customizations
are
actually
use
and
really
concentrate
on
a
business
and
functional
requirements.
Not
on
the
hey,
here's,
the
content
type.
We
need
to
transform
a
content
type
es
with,
but
when
it
could
transform
a
webpart
more
concentrating
on
okay,
why
does
the
web
part
exist?
Is
it
used?
How
is
it
used?
What
does
it
actually
achieve?
A
B
It's
very
easy
to
just
upload
a
simple
solution
file
and
create
a
functionality
there
and
also
don't
keep
in
mind
that
even
if
a
solution
is
barely
used,
it
could
still
be
business.
Critical,
I've
spoken
to
people
running
in
your
organization,
using
that
specific
solution.
If
you
just
take
it
away
and
simply
ignore
it
or
whatever,
maybe
the
whole
organization
is
getting
crippled.
Because
of
that,
or
so
it's
good
to
understand
that
you
understand
what
are
you
people
doing,
how
are
they
using
it
very,
very
important,
and
what
do
you
have
out
there?
Yes,.
A
And
also
one
thing
which
could
be
a
slightly
difficult
thing
to
analyze:
it's
also
the
external
applications
which
are
connecting
to
the
SharePoint.
So
let
me
going
through
the
organization
and
understanding,
ok,
what
kind
of
applications
you
might
have
which
are
connecting
towards
your
on-premises
SharePoint,
because
you
need
to
figure
the
route
changes
on
them
as
well.
The
authentication
model
between
on-premises,
SharePoint
and
SharePoint
Online
is
different,
so
you
can't
rely
on
those
application
to
be
able
to
connect
the
sharepoint
online
without
any
any
modifications.
So
it's
not
just
about
the
farm
solutions.
A
It's
it's
much
more
than
that.
So
understanding
an
assessment,
no
doubt
number
one
thing
and
like
mention,
concentrate
on
functionalities,
not
on
the
technology.
What
why
is
it
there?
What
does
it
actually
do
it?
And
then,
when
you
have
that
you
understand
what's
available,
what
are
the
usage
scenarios?
How
do
how
people
are
using
these
things?
Then
we
can
actually
do
initial
set
of
planning
and
the
reason
why
I'm
setting
initial
is
that-
and
this
is
the
basic
set
of
planning,
how
we
cannot
approach
achieving
those
functional
requirements.
B
Also,
when
you,
when
you
start
planning,
you
say
this,
this
Buddhist
web
can
be
converted
out
of
the
books
capabilities.
Yes,
keep
in
mind
that
your
if
you're,
moving
to
Shepard
online
you're
moving
to
a
running
target,
SharePoint
Online
is
constantly
improving
and,
as
for
me
out
of
the
books
capabilities
concept,
way
more
available
than
the
on-prem
environment,
clear.
B
Well,
it
might
not
be
available
on
Prem.
It
could
very
well
be
available
already
a
share
but
online
for
you
to
utilize.
Instead
of
building
your
own
customization,
simple
example:
experiences
office,
365
planner,
which
is,
is
melt
available
on
premise,
etc.
So,
there's
a
lot
of
functionality
in
the
cloud
already
there
for
you
waiting
for
you
to
can
be
consumed
and
to
use
in
compared
to
on-premise
absolutely.
A
Absolutely
really
really
important
thing,
so
whoever
is
actually
our
Technical
Architect
or
doing.
The
initial
planning
should
be
aware
of
all
of
this
capabilities
which
are
available
and,
like
Ervin
said
we
do
apologize
from
behalf
of
Microsoft,
putting
my
services
and
sharepoint
engineering
hat
on
we're
actually
releasing
to
fasting
the
capabilities,
so
people
are
having
hard
time
to
give
up,
because
all
the
time,
new
capabilities,
all
the
time
new
enhancements
and
improvements
as
well
now
live
nation.
A
This
is
the
time
when
it
into
accurate
estimate
and
really
the
under
the
key
reason
for
this
one
is
that,
at
this
point,
you
have
understanding
of
what
I'm
actually
trying
to
achieve
with
the
existing
customizations.
There
is
no
such
thing
as
doing
estimates
based
on
the
number
of
form
solutions,
because
guess
what
a
farm
solution
can
pay
five
kilobytes
or
it
can
be
50
megabytes.
So
when
the
number
of
farms
solution
is
not
a
factor,
definitely
not
another
thing
to
consider:
it's
really
around
what's
being
used,
what
are
the
end-users
using?
A
What
are
the
critical
things?
And
what
do
we
want
to
migrate?
The
dollar
sign,
because
one
aspect
on
this
discussion
is
that,
when
you're
doing
this
transformation,
if
this
is
an
awesome
opportunity
to
also
to
make
sure
that
do
we
really
want
to
invest
on
that
customization
if
we
can
achieve
80%
of
that
functionality
from
out-of-the-box
capabilities,
or
something
like
that.
So
thinking
through
that
return
of
an
investment
for
the
customizations
as
well
good
to
the
following
stages
are
pretty
normal
in
the
indle.
A
A
How
to
make
those
happen
and
that's
following
up
on
the
typical
development
process,
including
testing
URLs
that
and
then
the
last
stage,
is
deployment
so
getting
those
customizations
when
they
have
been
tested
getting
them
available
within
a
tenant
waiting
to
tenant
waiting
for
the
content
to
be
my
create
ownership
on
tenant
and
then
well,
there's
multiple
aspects
and
options
on
this
one.
So
some
customers
they've
done
transformation
to
the
modern
technologies,
for
example,
to
adding
model
first
in
on-premises
and
then
they've
moved
in
the
sharepoint
online.
A
That's
one
option,
but
then,
if
you
do
that,
you
need
to
existing
content
to
be
in
quotes
retrofitted.
Essentially,
how
do
I
get
rid
of
the
farm
solution
from
all
of
these
site
collections?
How
do
I
do
that
in
place
extraction
of
the
farm
solution,
capabilities
and
replace
that
with
the
nanny
model?
And
so
that's
one?
Maybe
the
best
approach
is
to
think
through
the
transformation
to
happen
as
part
of
the
content,
migration
and
not
do
it
first
in
on
premises
and
then
move
the
to
sharepoint
online.
A
Further
sync:
it
in
a
way
that
in
on-premises
we
have
set
of
customizations
in
SharePoint
Online.
We
will
have
the
needed
customizations
and
configurations
for
the
tenor
for
the
site
collections
and
we'll
create
the
site
collection,
ready,
we'll,
create
the
content,
type
site
columns
and
all
that's
ready
to
be
waiting
in
SharePoint
Online.
And
then
we
use
my
creation
tool
in
to
get
the
content
moved
from
on
premises
to
the
sharepoint
online.
And
this
way
you
can
actually
start
with
a
small,
a
small
amount
of
site
collections.
A
You
can,
for
example,
a
tree
that
all
of
the
new
site
collections,
the
new
content,
is
being
created
to
the
sharepoint
online.
The
old
stuff
is
getting
gradually
microd
in.
So
it's
not
a
big
bang
transformation.
It's
rather
phased
one
step
at
a
time
my
creation
as
part
of
the
people
moving
into
the
sharepoint
online
and
more,
let's
say
internal.
How
would
I
put
an
internal
selling
node?
A
What
I've
seen
for
a
lot
of
the
customers
doing
is
that
they
they
don't
even
try
to
do
or
even
try
the
micro
everything
from
on-premises
to
the
sharepoint
online
they'd,
rather
start
by
my
creating
on
a
subset
of
the
site
collections
which
are
relevant
on
what
are
still
being
used.
Plus
all
of
the
new
content
is
going
to
create
it
to
the
sharepoint
online.
Quite
often,
what
this
means
is
that
the
site
collection
administrators
in
on-premises.
A
They
actually
want
to
get
access
on
the
on
the
advantages
in
the
sharepoint
online
by
themselves,
and
they
might
actually
do
the
migration
by
themselves
as
well.
So
it
doesn't
have
to
be
a
massive
multi-million
dollar
projects
where
everything
is
being
moved.
It's
going
to
happen
quarterly
as
well.
No.
B
Another
thing:
that
is
a
thing
if
you,
if
you
consider
going
for
a
hybrid
environment
where
you
keep
on
premises
for
some
some
functionality,
and
it
makes
me
make
sense
to
align
your
your
development
process
and
your
your
develop
the
technologies
you're
using
to
keep
them
in
sync
with
the
ones
own
biases.
You
don't
have
completely
different
ways
of
buildings
like
oh,
this
is
the
online
development
style,
and
this
still
this-
and
this
is
the
on
premise-
development
style,
which
is,
if
you
move
to
using
the
same
approach
on
Prem
and
cloud.
B
A
It
makes
a
little
sense
absolutely
and
then
the
end
use
our
impact
won't
pay
that
big
either
so
the
UI
is
won't,
be
changing
all
they
know
exactly.
This
I
really
need
to
be
changed
up
still
Cuture
I.
We
would
strongly
recommend
people
to
have
a
look
on
this
process.
We've
proven
this
with
multi-billion
multi-billion
dollar
revenue,
customers
and
tens
and
denser
process.
So
we
do
know
that
this
process
works,
there's
additional
resources,
even
templates,
and
all
that
available
through
the
SharePoint
BMP
nation.
There.
A
Now
before
the
close-up
on
the
on
the
discussion,
we
wanted
to
kind
of
a
walk
through,
let's
say,
8
key
points
around
transformation
and
what
like
safe,
when
we
start
as
we
came
to
really
deep
dive
on
this
webcast
to
individual
technical.
This
is
what
you
should
be
doing
and
when
you're
doing
x
and
y
and
see
we
do
have
a
lot
of
videos
a
lot
of
guidance
available
on
that
one.
A
But
one
of
the
kind
of
a
pinpoints
8
specific
things
and
start
with
this
for
more
conceptual
discussions,
so
number
one
dropping
all
unnecessary
customizations
so
think
about
the
return
of
an
investment,
and
this
is
an
actually
really
really
important
thing,
because
why
would
you
customize
or
introduce
a
customization
if
it
doesn't
bring
your
value?
So,
like
I
said,
we've
seen
so
many
customizations
being
hanging
in
the
on-premises
form,
but
not
being
used
to
definitely
not
start
by
hey
analyzing
SS
pay
packages
and
hey.
We
have
9
with
pods.
Okay.
A
B
One
another
one
princess
another
customization
that
you
what
I
see
a
lot
that
ISM
is
like
redundant
workflows.
If
you
want
to
call
them
like
that,
so
people
will
have
to
initiate
over
workflow
to
prove
something
that
they
usually
decided.
It's
them
approving
it
themselves,
because
that
reference
was
once
designed
to
have
people
other
than
themselves,
approve
it,
but
then
that
whole
business
flow
was
not
in
it's
not
in
place
anymore,
but
the
the
technical
workflow
is
still
in
place.
A
Absolutely
and
then
use
existing
program
patterns
and
guidance
and
to
support
your
work
so
for
the
transformation
we
have
a
lot
of
existing
videos,
a
lot
of
existing
guidance
available
and
even
though
some
of
them
might
might
have
been
recorded,
let's
say
2015
2014,
they're
absolutely
still
valid,
especially
when
you're
transforming
from
farm
solutions
to
the
adding
model.
Yes,
some
of
that
smart
material
doesn't
mention
shape
on
framework
as
an
option,
but
that's
absolutely
a
valid
option
in
SharePoint
on
well
I
understand
supported
configurations
in
SharePoint
Online.
A
This
is
a
really
important
thing
which
we
updated
on
the
slide
just
before
we
started
actually
recording
because
Evan
actually
raised
this,
and
this
really
comes
down
on
the
fact
that
in
on-premises
you
can
adjust.
You
can
configure
your
farm
button
to
have
exceptions
in
SharePoint
Online,
that's
not
possible.
You
cannot
call
the
sharepoint
online
support
and
say
yeah
for
this
list.
I
want
to
have
an
exception
and
where
we,
I
can
store
more
than
5,000
items
in
this
list
or
whatever
the
alternate
access,
mappings
or
whatever
the
let's
say,
policy.
Permissions.
There's
no
exceptions.
A
You
really
need
to
understand.
What
is
what
are
the
options
which
you
have
and
the
configuration
in
SharePoint
Online
and
what
are
the
configuration
settings
internet
admin?
It
might
be
that
the
thing
what
you're
assuming
should
be
there
might
not
be
there
and
there
might
be
some
additional
settings
and.
B
That's
that's
both
for
money
from
an
end
user
perspective,
how
with
URL
do
they
go
to
etc?
Those
kind
of
things
that's
important,
but
when
you
mention
the
lists,
for
instance,
so
if
you
have
been
changing
the
list
for
opening
settings
on
premises
to
allow
more
than
5,000
items
in
a
query,
you
vote
and
that's
not
possible
in
the
cloud
you
will
have
to
refactor
your
application.
B
You
will
have
to
change
your
business
logic
of
your
solution
in
to
use
multiple
lists
or
into
these
folders
in
that
list
or
whatever
technology
you're
going
for
a
solution.
You're
going
for
to
overcome
that
list
rustling
issue,
but
you
have
to
yeah
it's
very
important
to
understand
what
your
don't
necessarily
called
limitations.
But
what?
What
are
the
the
options
and
the
configurations
are
in
Shepards
online
integer.
A
B
A
Like
mentioned
on
a
previous
slide
estimate
based
on
functional
requirements
and
not
on
a
technical
implantation,
do
you
technically
what
we
saw
with
many
of
the
customers?
Whether
we
went
for
this
process
is
that
quite
often
the
SS
pay
packages
don't
mean
a
thing
Damon,
not
that
we
we
started
out
thinking
few
years
back
when
I
started
the
transformation
initiatives
we
started,
always
by
looking
in
the
farm
solutions
and
quite
fast.
We
realize
that.
Well
here
it
does
kind
of
give
us
a
some
sort
of
a
hunch.
A
What
will
be
there,
but
it
doesn't
tell
what
which
of
the
farm
solutions
are
actually
being
used.
The
fact
that
the
farm
solution
is
being
activated
in
our
form
doesn't
mean
that
it's
actually
being
used
and
that's
a
really
really
important
thing
understand,
what's
being
actually
used
and
what
are
the
functional
requirements
and
business
requirements
behind
those
things
and
then
kind
of
a
for,
let's
say
more
technical
recommendations
which
are
good
to
remember
when
you're
looking
into
the
sharepoint
online,
and
this
might
be
familiar
for
you
or
this
might
be
shocking
for
you
as
well.
A
The
significant
issues
around
these
things,
for
example,
save
slide
as
a
template
and
then
suddenly
the
template
doesn't
work
at
all,
and
then
it
will
cause
your
chances
if
you're
using
remote
API
is
those
issues
won't
be
there.
So
you're
reducing
your
future
challenges
with
the
right
approach,
use
SharePoint
framework
for
the
UI
experiences
for
possible,
so
for
the
UI
elements
or
the
webparts
and
extensions.
Please
use
SharePoint
framework,
absolutely
future
proof
and
super
capable
platform
for
your
customizations
going
to
be.
A
Yes,
as
part
of
the
feature
back
to
really
good
reminder,
because
at
that
point
you
can
do
customizations
once
for
on-prem
and
sharepoint
online
now
do
not
use
custom
if
possible,
to
future-proof
your
deployment.
There
are
exceptions
on
this
rule,
and
this
is
definitely
none
of
this
is
black
and
white.
There
is
no
such
thing
as
best
practices.
It
always
depends
on
what
ira
trying
to
achieve,
but
if
you
can
avoid
a
custom
master
page,
it's
much
better.
Why?
A
Well,
because
the
way
we
introduce
capabilities
in
sharepoint
online
is
that
we,
for
example,
enhance
the
existing
customers
that
they
are
other
folks
master
pages.
So
if
your
site
is
using
a
custom
master
page,
it's
not
getting
any
of
done
Huntsman's
or
it
might
not
get,
or
it
might
get
some
of
them,
but
not
fully,
and
that
might
actually
cause
the
challenges
in
the
future.
So.
A
B
A
That's
a
good
way
of
putting
it,
because
that
will
ask
without
no
doubt
cause
you
additional
costs
in
the
future.
If
it
is
serious
customers
debate
is
now
absolutely
valid
approach,
but
so
or
later
you
will
need
to
make
additional
investments
and
then
the
the
fourth
one
take
advantage
of
our
capabilities
for
long
running
tasks
and
for
other
stuff
as
well
so
or
technically.
A
It
could
be
whatever
cloud
provider,
but
obviously
I
sure
is
the
most
closest
one
to
the
sharepoint
online
and
within
a
show,
if
you
can
easily
use,
for
example,
with
jobs
for
let's
say,
scheduled
tasks,
governance
checking,
governance
of
processes,
I
share
functions
for
a
faster
Operations
service,
boss,
doing
the
great
against
on-premises
and
there's
a
lot
of
multiple
different
ways
of
doing
this
and
a
lot
of
advanced
scenarios
which
you
can
achieve
using
the
official
capabilities
together
with
SharePoint
and
one
good
lot
of
talking
like
the
like
Nations.
We
didn't
want
to
do
this.