►
From YouTube: SharePoint PnP Partner Story - How Solvion is using PnP assets in their customer deployments
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
everybody:
this
is
SharePoint
Patterson
practices,
customer
case
presentation,
so
with
these
ones
and
these
videos,
what
we're
going
to
do
is
actually
show
you
in
practice
how
the
BMP
provisioning
engine,
all
the
other
aspects
of
the
of
the
BMP
reusable
components,
are
used
in
a
real-world
projects.
This
time,
we're
here
with
Sullivan
and
Tommy
for
atomic
Hellas
from
Sullivan,
actually
doing
the
really
the
demonstration
of
how
they
are
using
the
BnB
and
what
they're
being
able
to
build
on
top
of
it.
My
name
is
Ivan
and
I'm.
A
A
Excellent
thanks
Tommy
and
that's
really
good
good
perspective
as
well,
because
there's
a
lot
of
lot
of
partners
who
are
actually
moving
from
the
classic
form
solution
based
or
on-premises,
based
customizations
to
the
cloud.
So
from
that
perspective,
the
super
interesting
webcast
before
we
go
to
the
actual
content
and
I'll
fully
give
Tommy
the
the
lead
permission.
Let's
quickly
explain
what
is
the
sharepoint
medicine
practices
in
a
few
seconds,
so
shipment
Pelisson
practices
is
shipment,
engineering,
owned
and
coordinated,
open
source
community
driven
initiative,
and
so
what
we
do
is
that
we
share
code
samples
guidance.
A
We
have
community
calls
and
actually
bi-weekly
special
interest
calls
as
well.
We
do
have
case
studies.
The
themes
are
in
SharePoint
framework,
which
is
the
new
stuff
which
is
going
live
on
SharePoint
Online,
pretty
soon,
and
also
on-premises
later
this
year,
Chevonne
that
ins
much
of
graph
and
office
365
api's,
so
the
guidance
will
be
applicable
of
the
both
shipment
online
and
on-premises
were
suitable.
A
B
So
in
terms
of
who
we
are
and
and
what
we
did
just
give
me
a
one
minute
to
set
the
scene
right
on
what
we
are
working
with.
Sargon
is
the
company
working
in
Internet
Solutions
for
the
last
15
years,
and
we
are
focusing
on
microsoft
technology
now
for
for
12
years,
so
only
working
with
the
Lobos
you
see
on
the
bottom
here.
Basically,
we
have
two
types
of
teams.
B
We
have
one
that's
around
office,
365,
focusing
on
skype
and
Lync,
and
one
that's
around
office
65
and
focusing
on
SharePoint
and
on
top
of
these
technologies
we
build
solution
for
what
we
call
a
modern
workplace.
We
have
our
own
consulting
team
that
is
doing
transition,
consulting
so
helping
our
customers
moving
from
a
non
digital
work
to
a
more
and
more
digital
work
in
types
of
their
workflow,
and
we
have
two
two
products
so
to
speak.
B
One
is
our
soul
in
work
box
and
one
is
from
from
our
partners
in
investing
65
for
Skype
for
business
dialogue
management.
So
that's
just
a
short
introduction
in
terms
of
what
sort
of
units
you
find
all
the
links
and
how
to
reach
me
or
to
get
to
know
to
me
like
Twitter
or
my
blog.
So
if
you
interested
just
stop
by
before.
A
They
actually
Thomas.
You
can't
go
forward
from
here,
just
quick
question
on
the
let's
say
the
solvent
slice,
so
in
the
in
this
case
we
kind
of
talked
about
the
PMP
use,
it's
insolvent,
so
how
many
customers
you
actually
have
using
this
kind
of
a
solutions
in
the
on-premises
or
the
classic
solutions,
or
then
the
PMP
best
solution
to
set
the
sound.
A
B
Great
just
to
give
you
some
background
information
we,
as
the
company
started
I,
think
five
or
six
years
ago
in
terms
of
providing
our
our
customers
a
self-service
saturation
solution,
and
what
we
built
is
what
we
internally
called
or
calling
are
now
again
its
action
framework
and
the
action
framework,
basically
is
a
bunch
of
actions
deployed
via
these
peopIe
catch.
So
fortress
called
solution
running
on
a
shipment
of
premises,
farm
and
you
can
see
it
here
in
the
settings
of
one
of
our
shipment
lists.
B
We
have
some
additional
menu
entries
like
certain
economic
events
and
ribbon
extensions,
so
we
were
able
to
just
by
configuring
XML
style,
config
files
directly
in
the
shipment
settings.
We
were
able
to
add
items
in
the
ribbon
or
do
more
sophisticated
stuff
like
creating
psycho
elections,
creating
suburbs
setting
permissions
breaking
role
inheritance,
because
what
we
basically
ended
up
doing
is,
if
you
see
like
here,
we
have
some
action
configuration
and
the
action.
B
But
in
some
point
of
time,
office
365
showed
up
and
of
course,
you're
not
able
to
deploy
these
people
catch
to
office
365.
So
we
had
to
come
up
with
a
different
architecture
to
provision
cycle
actions
or
sub
webs
also
in
office
365,
and
that's
the
main
point
of
today.
How
we
transitions
is
knowledge
right
up
to
the
cloud
totally.
B
I
think
I
think
everyone
that
does
more
SharePoint
work
at
some
space
in
time
starts
creating
something
like
provisioning
engines
event
there
are.
There
are
probably
hundreds
out
there,
but
yeah.
It's
also
a
good
one.
We
can
use-
and
this
is
this
is
the
thing
we
can
up
with,
because
what
we,
what
we
try
to
create,
was
an
architecture
there,
a
user
can
start
somewhere
in
a
SharePoint
service
and
browse
over
to
what
we
call
our
our
team
box
dashboard
and
basically
start
there
by
creating
a
new
collaboration
space
in
our
wording.
B
You're,
always
speaking
of
boxes,
because
this
is
our
main
word-
we
came
up,
you
can
call
it
a
space
box
site
or
whatever,
but
basically
it's
a
SharePoint
site
collection
or
SharePoint
SAP
web.
What
we
call
up
and
the
user
enters
all
the
data
like
project
title,
who
is
the
requester
and
some
metadata
about
the
site
that
should
be
provisioned
and
our
dashboard
sourced
the
stuff
as
a
simple
SharePoint
list:
entry
in
a
SharePoint
site
collection?
That's
our
infrastructure
cycle
action
for
the
solution.
B
You
can
also
create
cycle
actions
on
premises,
so
you
have
one
dashboard
there,
just
based
on
the
metadata.
Your
users
end
up
creating
stuff
directly
in
the
cloud
like
an
office,
265
group
or
because
they
have
some
different
options
available
in
the
dashboard.
They
also
are
able
to
create
on
premise
a
site
collection.
B
B
For
example,
we
have
one
customer
that
has
a
process
in
CRM
online
if
a
new
customer
of
theirs
gets
promoted
to
a
new
stage,
they
sync
per
cm
with
the
local
EAP
system
and
this
process
also
that's
just
this
rest
code
to
store
an
entry
in
the
shipment
list
in
the
team
box
infrastructure
list,
and
then
our
solution
kicks
in
and
provides
the
user
with
a
new
sign
collection
in
his
collaboration
space
based
on
the
data
basically
provided
by
the
CM
system.
That's.
A
Actually,
really
really
great
design.
So
let's
spend
a
few
moments
on
this
one
because
there's
few
items
which
I
wanted
to
kind
of
a
clarify
on
and
get
noted.
So
you
are
storing
those
those
requests
in
a
SharePoint
list
and
we
actually
mentioned
that
really
well,
but
I
wanna
kind
of
reiterate
the
message,
the
one
of
the
advantages
of
doing.
That
is
the
fact
that
you
have
a
native
API
to
access
the
list
data.
A
So
if
you
would
be
restoring
this
requests,
let's
say
in
a
document
DB
or
sinkhole
assure
you
would
have
to
implement
interfaces
for
alternative
devices
or
systems
to
get
access
on
the
list
or
adding
items
to
the
data
cure.
So
that's
a
really
really
good
point
and
on
the
advantages
of
using
a
SharePoint
list
as
long
as
the
amount
of
data
in
the
list
isn't
too
much
right,
the
really
good
point
so
from
a
let's
say,
future
development
or
request
perspective.
A
B
A
That's
a
really
really
great
point,
because
then
only
thing
what
you
need
to
concentrate
is
essentially
the
UI
implementation
of
the
device
app,
because
authentication
is
coming
from
sure.
The
SharePoint
list
is
actually
store.
It's
it's
exposing
to
API.
It's
already,
that's
a
really
good
one.
At
the
second
point,
what
I
wanted
to
kind
of
a
quickly
touch?
First,
is
the
the
shipment
on
lines
out
of
the
provisioning
of
the
of
the
sides.
You
mentioned
that
you
can
choose
a
template
and
a
provision
attempt
line,
and
these
are
essentially
right.
A
B
Have
some
templating
side
connections
so
for
every
for
every
type
of
of
team
box
in
our
ratings,
quick
team
work,
group
or
project,
we
have
a
template
site
collections
that
a
customer
can
add
stuff
to
this
template
and
the
web
shop.
Actually,
every
time
you
create
a
site,
collection
goes
to
just
two
decides
reads
out
the
information
in
terms
of
the
PNP
model.
So
we
we
and
we
end
up
like
have
a
real-time
template,
yeah,
just
reading
the
configuration
and
applying
it
to
the
new
site
collection.
B
A
The
last
point
on
this
one
I'm
sorry
for
taking
hit
some
time
on
the
slide,
because
the
architectural
designs
are
always
really
cool
before
we
actually
say
this
live
and
this
the
number
six
point,
which
is
the
dough
on
premises,
side
of
the
story.
Yeah
one
of
the
key
advantages
in
this
design
actually
clearly
is
the
fact
that
you
actually
host
this
application
in
the
Microsoft
Azure
side,
and
that
means
that
you
do
not
have
to
have
additional
hardware
or
customizations
in
on-premises
SharePoint.
A
B
This
this
is
a
two-part
answer
here.
Yeah,
the
the
first
step
is,
if
the
if
the
customer
is
okay,
with
his
SharePoint,
be
exposed
to
the
Internet,
we
just
used
the
as
a
web
site
to
reach
into
your
on-premises
form
and
create
the
stuff
based
on
the
Unruh
software.
That's
that's
available
like,
for
example,
the
client
and
object
model
to
create
the
stuff,
but
with
this
with
this
architecture,
we
are
also
able
to
run
what
is
in
the
normal
case
that
is
running
an
Asian
website.
B
We
are
also
able
to
deploy
stuff
to
local
is
website.
So
we
have.
We
have
two
customers
that
say:
ok,
I
I,
don't
have
my
SharePoint
exposed
to
the
Internet,
so
I'm,
totally
strict
on
network
trafficking,
so
I
just
have
a
locally
IAS
website,
and
that
is
speaking
with
Japan.
That's
also
possible.
Basically
you
can.
You
can
store
this
this
time
of
type
of
timer
shop,
first
and
foremost
in
Asia
websites,
but
also
just
deployed
in
a
local,
is
machine.
Absolutely.
A
B
The
page
is
filed
up
here
and,
if
I
need
to
add
someone
to
marketing
and
search
for
team
marketing
click
on
members
and
then
I
get
a
list
of
all
the
users
that
are
configured
in
this
team
box.
Never
need
to
invite
a
parent,
I,
just
click
invite
users
search
for
all
my
colleagues
that
the
named
and
pick
the
right
one,
and
then
we
have
the
permissions
levels.
B
Okay,
he
is
in
sales,
so
I'm
only
been
giving
read
access
and
then
I
actually
can
invite,
and
as
soon
as
this
is
happening,
I'm
finished
I
can
close
the
outlook
and
in
and
can
answer
the
question
say:
ok
permission
granted
and
has
no
access.
So
what
we?
What
we
saw
here
is
basically
our
editing
for
for
our
solution
that
kicks
in
every
time.
You
click
on
this
team.
B
Percy
65
I
can
and
do
not
only
are
able
to
create
to
edit
boxes
or
something
like
this,
but
you
also
can
do
the
whole
process
and
the
whole
process
in
terms
of
a
web
interface
looks
like
something
like
this,
because
what
you're
seeing
and
what
you
see
I'm
here
now
is
our
main
for
our
cooperation
spaces.
So
we
have
a
solution.
B
What
we
call
solving
black
box
and
what
we're
focusing
on
today
is
the
teen
box,
part
of
it
that
we
try
to
focus
on
all
staffs
around
self-service,
actuation
and
self,
serving
permissions
for
the
project
managers
or
for
the
the
owners
of
the
different
collaboration
spaces.
And
what
we
created
is
a
nice
interface
where
they
can
say.
B
Let's
say
for
Vesta,
for
example,
so
I
can
browse
here
for
a
different
user
and
trade
this
and
then,
if
I
click
on
request,
based
on
the
under
configuration
of
the
different
types
we
are
providing
here,
the
engine
kicks
in
and
creates,
for
example,
a
SharePoint
site
collection
or
an
office
365
group
or
on-premise
I
collection
or
everything
you
can.
You
can
imagine
in
terms
of
SharePoint
artifacts,
it's
possible
to
configure
behind
this
thing
smoothly.
What
we
did
here
is
that
we
we
tried
to
to
stay
with
the
the
newest
user
interface.
B
Microsoft
is
providing
in
there
saturation
process,
so
all
different
templates,
for
example,
projects.
You
have
this
nice
nice
little
wizard,
where
you
enter
data
on
the
one
side.
I
have
some
metadata
here
and
then
jump
over
to
the
next
yeah
wizard
step,
because
you,
the
users,
are
so
able
to
have
only
three
to
five
metadata
input
fields
on
one
side
of
the
wizard
and
can
step
through
the
different
artifacts
and
also
what
in
terms
of
an
architecture.
B
What
is
what
is
the
cool
thing
if
you
think
of
cycle
actions,
and
sometimes
it's
taking
SharePoint
Online
some
seconds
to
spin
up
in
your
site
collection?
You
already.
Can
fire
up
the
process
of
getting
the
site
collection,
the
first
thing
in
the
first,
no
user
clicks
and
the
first
next
button
and
then
apply
all
other
managed
metadata
on
the
end
of
the
process.
So
you
know
in
an
yeah
optimal
timeframe.
The
user
starts
with
the
visit
and
as
soon
as
it's
finished,
the
site
collection
is
already
ready.
A
Is
which
is
by
the
way,
what
we
donated
natively
in
a
SharePoint
in
the
modern
creation
as
well
just
sort
of
careers
today,
I
think
people
watching
the
video
might
be
asking.
They
are
thinking
that
hey
wait,
a
minute
that
looks
like
a
SharePoint
control,
the
modern
SharePoint
equation
controller.
So
is
that
as
some
sort
of
a
native
shipment
component
or
is
it
something
that
the
whole
thing
what
you've
implemented
as
custom
implementation?
A
B
Is
implemented
by
us,
but
we
are
using
all
the
things
that
are
provided
by
the
community
are
provided
by
Microsoft
itself.
For
example,
all
the
user
interface
here
is
based
on
office
UI
fabric.
So
we
recreate
the
the
whole
solution,
has
an
angular
app
using
office,
UI
fabric
and
all
the
styles
that
are
provided
with
it.
So
the
goal
was
that
the
user
interface
looks
familiar
to
everyone
using
office
365,
and
you
don't
have
to
do
some
additional
training
or
some
additional
documentation.
Yes,.
A
B
Ok,
what
we,
what
you
are
able
to
do
with
this
dashboard
is
that
we
show
to
the
user
all
his
collaboration
spaces.
He
created.
We
just
applied
some
some
basic
theming
for
this
webcast
in
terms
of
Microsoft
colors
and
pimpy
colors.
So
you
have
a
feeling
of
what
it
can
look
like
in
the
real
life
scenario.
B
Okay,
in
terms
of
life
cycle,
we
are
able
to
create
the
different
artifacts
based
on
the
under
metadata.
The
user
provides
us
so,
for
example,
as
a
user,
you
can
create
a
quick
theme
of
your
project
and,
as
an
IT
department
for
a
large
custom
of
example,
you
can
define
that
only
people
that
are
stored
in
a
special
Active,
Directory
group
or
SharePoint
group
are
able
to
create
wiki
teams,
because
quick
teams
probably
is
configured
to
deploy
a
new
office.
B
365
group-
and
you
just
want
to
make
sure
that
only
the
guys
that
should
play
around
with
this
new
technology
are
able
to
create
it
and
all
your
your
normal
projects
are
created
with.
If
the
customer
template
you
provide
your
users
with,
so
you
can
play
here
with
which
governance
features
and
only
make
templates
available
to
the
user
group.
They
should
be
able
to
create
their
own
templates.
B
What
we
are
also
able
to
do
here
is
that
we
can
edit
and
change
things
on
the
different
sides.
For
example,
if
I
click
on
the
team
marketing
content
here,
I
can
add
members
afterwards.
So
I
can
let,
as
we
saw
it
in
the
in
the
outlook
at
in
trade,
also
new
users
are
providing
users
access
directly
in
the
dashboard,
and
what
we
are
also
able
to
do
is
that
we
can
change
the
requester.
For
example,
I
can
say
in
in
this
demo.
B
Carmen
was
responsive
for
the
team
marketing
box
and,
for
example,
she
has
a
she
leave
a
story
on
or
off
whatever
reason.
I
can
say:
ok
and
neither
successful
for
her
for
being
able
to
handle
all
the
documents
and
the
team
box
itself.
I
can
choose
between
giving
back
the
the
side
to
IT
or
hand
over
the
side
to
her
manager
or
I
can
select
a
user
in
our
in
our
Monument
and,
for
example,
I
can
hand
it
over
to
Stefan,
for
example,
and
then
we
have
it.
If
you
have
it
here
as
well.
B
So
that's
also
in
terms
of
governance.
We
have
a
nice
little
workflow
that
kicks
in
in
terms
of
an
archiving
perspective,
so
you
can
configure
these
team
boxes
to
be
able
to.
Let's
say
after
60
days,
the
team
box
kicks
in
and
says.
Ok,
you
are,
you
are
out
of
your
time.
Do
you
still
need
more
more
time
for
your
collaboration
space
and
then
the
user
can
say
I'm.
B
What's
actually
on
your
mind
right
now
in
terms
of
of
what
we,
what
we
are
able
to
provide
you
with
is,
if
I
go
to
the
team
marketing
here,
I
already
prepared
the
cycle
action,
you
see
just
a
plain
SharePoint
Online,
SCI
collection
that
is
created
and
what
we.
What
we
do
in
terms
of
governance
is
that
we,
we
say,
or
we
provide
or
the
the
the
box
with
with
a
given
URL.
B
So
we
are
just
using
some
yeah
operations
or
some
some
number
stuff
in
terms
like
the
code
for
the
site
collection,
so
the
user
can
easily
change
its
naming
afterwards,
but
all
the
hyperlinks
and
all
the
stuff
that
this
link
to
this
I
collection
stays
with
the
actual
name.
Because
in
terms
of
archiving,
we
are
just
putting
this
I
collection
to
read-only
mode
and
still
all
the
hyperlinks
and
all
the
all.
The
documents
that
are
linking
to
the
different
areas
are
ok
and
working.
B
Fine
and
they're
only
yeah
managing
the
the
read
permissions
and
that's
also
a
good
approach,
because
we
came
across
some
use
cases
where
someone
said
okay,
I
need
to
archive
this
stuff,
and
then
three
months
later
they
say.
Ok,
indeed,
now
back
working,
and
so
we
have
a
flow
that
we
can
just
say.
Ok,
read
mode
or
edit
mode
with
our
interface
yeah.
A
B
So
we
have
this
functionality
that
you
can
say:
okay,
I
need
to
remove
the
user,
and
then
you
just
search
for
the
user
and
they
can
remove
and
the
provisioning
engine
kicks
in
and
goes
through
all
the
different
sites
and
make
sure
that
this
user
is
always
said
to
read
exist.
None
because
we
don't
want
to
get
rid
of
the
user,
because
in
terms
of
the
audit
lock
or
we
still
need
the
information
that
at
some
point
in
time
the
user
was
given
access
to
the
sides.
B
B
You
see
it
in
the
the
modern
user
interface
in
in
SharePoint,
Online,
more
and
more
yeah
wizards
or
configuration
parts
are
flying
in
from
from
the
right
side
of
your
browser,
and
that's
also
what
we
would
you
start
doing
here,
so
everything
you
you
can
do
with
with
a
team
box,
for
example,
if
two
main
areas
there
fear
this.
This
action
bar
like
in
a
modern
shopping
list.
B
They
can
say:
okay,
I
need
to
change
my
members,
for
example,
and
then,
from
the
right
hand,
side
some
visit,
clicks
in
and
provides
you
with
the
user
interface
for
just
this
particular
action
and
also
if,
for
example,
I'm
now
in
the
in
the
admin
role.
If
I
say,
ok,
I
need
all
the
boxes,
Thomas
created,
I
can
just
filter
it
here
and
say:
ok
just
in
this
one
and
then
I
have
also
the
same
functionality
of
changing
requesters
or
adding
members
as
an
admin
for
everyone
on
the
space.
B
So
it's
just
a
plain
list:
item
entry
and
the
dashboard
simply
just
provides
a
data
access
to
this
list.
Entry
and
our
Asha
webshop
is
listening
to
this
list
and
kicks
in
every
every
few
minutes
and
checks.
Ok,
do
I
need
to
do
something
here
and
then
grab
all
the
stuff
here
and
provides
the
actions
that
we
that
we
should
do
for
the
user.
A
A
B
So
this
is
one
of
our
2016
farms
that
we
that
we
use
here
so
with
with
one
with
one
dashboard
I'm
seeing
here
corporation
spaces
that
are
just
SharePoint
site
collections
on
premises
that
are
site
collections
as
in
SharePoint
cloud,
environment
and
also
I,
can
go
here
and
say:
ok,
let's
have
a
look
at
this
is
PC
thing.
We
end
up
in
a
SharePoint
group
in
our
office,
365
group.
Sorry,
so
we
are
able
to
integrate
all
the
different
collaboration
artifacts
that
are
possible
in
in
office,
65,
environment
and
the
user.
B
A
On
that
particular
topic,
this
is
actually
a
really
great
approach:
an
economy,
architectural
direction,
because
quite
often,
when
I
used
to
be
in
the
field
as
a
consultant
in
Microsoft,
when
we
did
migrations
to
the
SharePoint
Online,
quite
a
lot
of
customers
were
saying
that
hey,
but
we
have
the
SharePoint
already
in
on-premises.
We
can't
move
because
to
my
creation,
my
creation
takes
so
long
and
it's
super
expensive
and
which
is
true.
A
B
B
Okay,
I
want
to
get
rid
of
this
thing
in
this
thing,
but
only
an
administrator
has
the
the
right
permission
to
really
get
to
the
point
where
you
say:
okay
needs,
I
collection
or
delete
side
because
out
of
experience,
we
know
that
that
users
click
on
delete,
and
then
they
came
back.
I,
don't
know
two
weeks
after
this
click
and
say:
oh
and
I
still
need
this
site.
So
we
have
some
additional
governance.
B
B
B
We
we
started
the
demo
case
with
our
in
its
just
a
regular
outlook
it
in
providing
the
the
basic
functionality
of
the
responsive,
key
box
dashboard
to
our
users,
based
on
on
the
new
office
and
in
model
to
just
the
UL
configuration
and
all
the
things
you
are
able
to
do
on
the
the
pic
dashboard
you're,
also
able
to
do
just
in
your
outlook,
adding
or
on
your
mobile
phone
or
on
your
tablet
or
whatever
screen
size.
You
prefer
working
with
one.
A
Point
one
point
actually
to
pinpoint
on
the
previous
slide:
there
was
a
create
as
well,
which
is
good.
So
so,
yes,
somebody
because
typically
people
send
emails
still
and
they
they
require
a
new
site
collection.
Then
you
can
just
quickly
create
hey
I'll
trade,
you
a
site
collection
from
my
Outlook
and
that's
really
convenient
so.
B
And
the
next
thing
we
are
we
are
working
on
is
that
you
also
can
drag
and
drop
things
from
Outlook
through
your
theme
box,
because,
if
you
think
of
the
responsive
cycle,
it'll
just
from
one
technique
perspective,
it's
an
azure
website
and
of
course
we
can
enable
this.
This
container
here
also
for
being
able
to
drag
and
drop
stuff,
and
you
can
define
a
document
library
where
stuff
should
end
up
being
stored
and
just
put
an
attachment
or
put
in
an
email
here
and
store
it
to
your
institution.
B
A
B
Okay,
in
terms
of
the
dashboard,
we
saw
that
different
functionalities
and
the
user
interface
that
we
try
to
implement.
So
we
we
working
in
a
in
use
interface,
way
that
it
looks
familiar
to
what
Microsoft
provides
with
office
265
out
of
the
box,
but
we
using
office
UI
fabric
and
the
different
functionalities.
We
have
with
the
styling
to
provide
a
solution
that
looks
like
office
is
65,
although
it
sits
in
some
some
Asia
website.
B
For
example,
yeah
we
can
edit
the
users-
and
we
have
some
some
short
slides
here
for
what
it
looks
like
on
on
a
mobile
phone.
So
it's
it's
totally
responsive
I,
just
resize
my
browser
window
here
for
this
screenshot,
but
it's
also
working
on
on
your
phone
or
your
tablet.
Just
because
it's
a
responsive
design
here
in
terms
of
hybrid
solution,
I
want
to
make
sure
that
you
see
the
difference
in
here,
because
we
are
working
on
as
a
website
here
and
also
are
able
to
modify
or
to
create
a
collections
on
premises.
B
B
I
created
those
tools
and
the
drop
down
box
was
filtered
to
my
name
and
then
and
I
think
and
go
here
and
in
here
and
say:
okay
I
want
to
put
this
in
boxes
back
to
the
hands
of
IT
or
I,
want
to
put
it
in
the
manager's
hands
or
it
select
a
user
and
say.
Ok,
these
team
box
needs
to
go
to
Stefan,
and
these
team
box
needs
to
go
to
flowers,
for
example.
So
we
have
the
the
real
governance
workflow
here
and
in
terms
of
clutter.
B
If
you
configure
the
solution,
for
example,
for
a
two
gigabyte
quota,
you
can
just
by
entering
a
configuration
in
our
in
structure,
lists
that
we
saw
earlier
just
say:
let's
say
at
80%
solution
kicks
in
and
sends
out
an
information
that
the
starch
will
be
yeah
you'll
be
running
out
of
storage.
Basically,
and
then
you
can
kick
in
and
say:
okay,
I
need
more
time.
I
need
more
storage,
just
give
me
another
another
gigabyte
or
another
space
to
do
my
work
and
also
we're
reaching
out
to
the
user
in
terms
of
archiving
configuration
base.
B
For
example,
the
normal
thing
is
that
we
say:
quick
themes
are
only
available
for
60
days
and
after
50
days
we
reach
out
for
the
user
and
make
sure
he
knows.
Okay,
your
your
quick
team
will
be
closed
soon
and
then
you
can
configure
the
solution
and
how?
How
often
the
user
can
say.
Okay
I
need
more
time.
I
need
more
space
and
give
me
another
30
days
so
give
me
another
60
days,
that's
all
based
on
the
configuration
so
via.
So
we
are
open
on
this
stuff
from
the
work
from
the
governance
workflow.
B
The
customers
like,
okay,
what
we
also
came
up
with
in
terms
of
user
interface,
and
we
just
want
to
to
also
show
you
something
we
build
for
for
Emma,
because
we
don't
only
created
a
solution
that
works
in
the
cooperation
space.
We
are
also
having
some
some
artifacts
and
some
they
are
some
base
layer
in
terms
for
internet
solution
or
a
communication
solution.
So,
on
the
left
hand
side,
you
see
our
basic
demo
environment
in
terms
of
what
an
Internet
can
look
like,
and
this
screen
focuses
on
the
integration
we
build
for
Emma.
B
The
flow
is,
like
you
see
the
the
main
page,
the
global
landing
page.
Would
we
call
it
and
then
you
have
here
an
article
page
that
shows
you
some
some
demo
content
from
our
environment
and
then
you
have
this
this
blue
gamer
logo
here
and
if
you
click
on
the
same
and
logo
also
from
the
right
wizard
kicks
in,
and
this
drop-down
box
shows
you
all
the
demo
groups,
you
are
a
part
of
and
then
based
on
the
permissions
in
the
Emma
group.
B
For
example,
if
you're
an
admin
of
am
a
group,
you
can
provide
the
user
with
an
announcement.
So
you
click.
This
check
box,
provide
some
information
for
the
headline
and
for
the
teaser
text
and
click
click
publishing
and
what
happens
is
that
we
create
and
offers
265
graph
object
with
the
URL
of
this
special
content
page
and
down
here
you
see
the
integration
part
from
the
on
the
side
perspective.
You
see
all
the
comments
that
were
created
for
this
particular
page
and
directly.
Here.
A
B
And
the
nicest
part,
basically
is
the
announcement
stuff,
because
if
you,
if
you
think
of
mobile
phones
as
soon
as
you
click
an
announcement,
everyone
that
this
member
of
this
of
this
Yemma
group
gets
an
yeah,
a
short
peep
on
his
mobile
phone.
Can't
knows
there
is
a
new
and
new
notification
and
no
there's
a
new
stuff
in
the
internet
or
in
the
Emma
group.
Yes
to.
A
A
We'll
get
that
one
also
in
the
video
notes,
so
that
people
can
easily
access
the
the
additional
information.
This
was
kind
of
bad.
We
talked
to
Thomas
on
this
particular
step,
but
this
is
so
cool
and
it
actually
integrates
nicely
shipment
online
and
Yammer
from
a
UI
perspective
and
end
user
perspective.
So
we
wanted
to
kind
of
a
touch
and
keep
the
slide
in.
There
is
guidance
on
how
to
make
happen
out
there
in
the
internet
and
and
Thomas
his
blog
post
is
explaining
model
so
and.
B
A
Absolutely
and
that's
cool
and
and
by
the
way
on
on
the
Yammer
integration,
this
actually
works
into
own
premises
as
well
as
long
as
your
end.
Users
have
internet
access,
so
you
can
absolutely
use
Yammer
in
on-premises
in
the
stimulus
way
like
like
this
in
here.
As
long
as
there
is
an
internet
access
from
the
all
of
the
machines,
sir
yeah
teach
that
was
actually
the
last
step
of
the
of
the
story
was
intent.
Yes,
closing
up
on
the
on
the
thread
cast
and
obviously
so
we
in
the
BMP
in
the
SharePoint
Patterson
practices.
A
We
it's
great
to
see
how
the
engine
is
actually
used
behind
the
scenes,
and
that's
really
what
we
want
to
do.
We
want
to
provide
a
reusable
component,
reusable
tooling,
which
isn't
necessarily
visible
for
the
end
users,
but
it
provides
consistently
consistency
on
the
implementations
and
Thomas
on
from
your
perspective.
Now,
if
we
think
about
the
the
new
implementation,
the
us
are
absolutely
brilliant.
I
need
to
thank
your
UI
designers
for
them,
but
why
did
you
choose
to
use
the
BMP
provisioning
engine
in
the
background?
A
B
We
have
to
history,
we
have
the
history
of
creating
I,
think
two
or
three
different
types
of
provisioning
engines
already
by
ourselves,
and
the
big
deal
here
is
that
we
that
we
trust
the
PNP
group
in
terms
of
going
forward
with
all
the
stuff
that
is
around
obviously
65.
So
basically
what
what
we
from
a
strategic
perspective
we
just
say
to
our
customers:
we
will
integrate
the
newest
things
officer.
B
65
provides
us
as
soon
as
the
PMP
has
the
possibility
to
do
so
because
I
as
a
team
lead,
has
some
responsibility
in
terms
of
new
technology
and
minutes.
Then
it's
a
good
decision
to
go
to
the
cutting
edge
technology
stuff,
but
normally
I
try
to
have
a
plan
like
let's
say
officer,
65
releases,
something
in
May
team
P
is
also
working
on
it
and
is
able
to
provide
a
new
interface
or
a
new
API
in
June.
B
Then
we
will
kick
in
and
say:
ok,
let's,
let's
look
at
it
for
the
next
one
or
two
months
and
then
we're
gonna
to
use
it,
because
it
makes
no
sense
that
we
that
we
try
to
build
this
ourselves,
because
obviously
you
guys
have
have
the
experience
and
have
the
the
broader
view
on
the
roadmap
and
what
what
is
happening
in
the
background.
So
we
just
stay
back
and
and
wait
and
we
just
yeah
adopting
and/or
putting
new
new
stuff
on
top
of
it
in
terms
of
the
feedback
we
get
from
our
customers,
absolutely
Nana.
A
Here
and
obviously
one
one
thing
to
consider
with
the
PNP
provisioning
engine
it
is,
it
is
fully
open
source
and
we
do
have
community
contributions.
We
actually
have
250
contributions,
contributors
in
the
PNP
in
general,
so
and
it
is
evolving
extremely
fast,
and
maybe
if
people
are
thinking
well,
it
isn't
actually
that
big
of
a
deal
to
implement
that
kind
of
an
engine.
B
A
Yes,
and
to
be
fair,
I
do
remember
when
we
we
were
in
the
PNP
team,
we
were
longtime
kind
of
a
thinking.
How
do
we
actually
make
this
happen,
and
and
when
we
started
implementing
the
the
original
engine
now
two
years
ago,
which
was
actually
a
third
engine,
probably
which
we
came
up
with
as
well?
The
thinking
was
that
well,
if
this
isn't
actually
that
hard,
it's
not
a
massive
deal
to
implement
that.
A
But
then
you
start
realizing
all
of
the
different
variations
and
complexity
and
within
the
lists
and
lists
and
libraries
and
fields
and
content
types
and
whatever
it's
a
it's
surprisingly
big
a
big
deal.
So
really
what
we
want
to
do
with
the
BMP
provisioning
engine
is
that
it
is
actually
controlled
by
sharepoint
engineering.
So
the
sharepoint
engineering
is
behind
all
of
these
decisions
as
well.
What
are
we
implement
there
and
if
something
goes
completely
sour,
we
are.
We
also
absolutely
steppin
with
additional
resources,
but
what
we
want
to
do
with
that.
A
We
really
do
with
that.
One
is
to
have
a
proper
community
so
that
everybody
can
contribute
and
it
evolves
faster,
and
it
has
the
capabilities
as
fast
as
possible,
and
we
know
that
there
has
been
some
box
and
there's
always
some
box
when
you're
doing
software
development,
but
all
those
we're
trying
to
address
those
as
fast
as
possible
as
well
and
what's
before.
We
close
because
there
might
be
somebody
kind
of
considering
the
the
taking
the
B&B
engine
into
you.
B
The
next
thing
is
that
we
say
okay,
this
is
this
is
in
an
inner
state.
We
have
a
closer
look,
because
if
it
fails
on
our
basic
stuff
and
I,
don't
care
where
the
problem
is
in
the
deep.
But
if
you
fade
out
basic
stuff
with
a
new
library,
this
top
turns.
Okay,
there
is
something
normally
we
don't
have
the
time
to
do
the
proper
investigations
we
just
wait
for
for
our
next
release.
B
On
the
other
hand,
if
we,
if
you
really
need
to
get
to
detective
research
for
the
for
the
thing,
that
is
the
dis
problem
and
the
the
main
issue,
or
one
of
the
main
issues
that
we
experienced
with
all
the
stuff,
is
that
the
change
of
of
the
architecture,
because
we
are
speaking
now
often
of
an
async
architecture
and
in
SharePoint
on-premises.
Everything
was
for
sacredness.
That
was
the
the
main
thing
we
needed
to
get
to
know
how
we
should
handle
all
the
different
things
with
with
web
books
or
web
service
requests
there.
B
They
get
a
timeout
or
something
like
this,
and
how
we
do,
though,
the
workflow
and
the
user
flow.
If
something
breaks
in
between
how
do
you
notify
the
user
that,
for
example,
he
kicks
create
and
the
cycle
action
couldn't
be
created?
In
the
background,
this
was
the
the
main
difference
in
terms
of
on
premises.
Okay,.
A
And
makes
a
lot
of
sense
and
that
that
is
no
doubt
the
main
difference
from
my
architectural
perspective,
good
I
think
we
contrary
the
existing
solution.
We
talked
about
the
architecture
and
the
start.
The
demo
was
actually
pretty
entirely
like
the
UI
design
of
the
stuff,
and
we
talked
about
where
the
usages
I
think
we
were
going
through
the
whole
topic,
so
maybe
it's
time
to
actually
close
up,
but
we'll
add
all
of
the
URLs
which
we
mentioned
in
the
in
the
video.
A
The
two
video
notes
will
also
reference
our
PMP
Partin
pack,
which
is
essentially
a
starter
kit,
to
build
something
like
this.
It
doesn't
actually
have
this
fancy
UI,
but
it
has
the
the
plumbing
behind
of
the
scenes
and
it's
showing
the
a
synchronous
process
and
requests
and
all
stone.
So
that
is
good
solution
to
kind
of
adapt
or
learn
how
to
do
similar
kind
of
implementations
as
well,
but
I
think
that's
it.
It's
almost.
Unless
do
you
have
anything
to
close
up
on
this
one.
B
Not
just
just
one
thing
that
came
into
my
mind
right
now
is
that
we
that
we
may
be
also
need
to
include
into
the
into
the
notes
of
the
webcast
that
the
user
interface
you
saw
today
is
also
based
on
the
design
guide,
Stephan
power
MVP
from
Austria.
Great
point
yes
built,
so
we
worked
with
Stefan
together
in
the
last
year
and
we
were
able
to
get
up
to
speed
on
how
he
thinks
this
design
designs
in
office.
B
A
The
guy
here
absolutely
and
Stefan
has
created
this
awesome
design
guide
like
Thomas
mentioned,
so
we
cannot
link
that
one
and
in
the
notes,
no
doubt
super
valuable
for
anybody,
who's
implementing
anything
on
SharePoint,
Online,
but
I
think
that's
it
for
them.
So
thank
you,
thomas
for
great
presentation
great,
to
have
see
in
practice
how
real
products
are
being
used
and
implemented
on
top
of
the
table
of
the
PMP
provisioning
engine
as
well,
but
thank
you
and
will
be
who
will
come
up
with
a
new
webcasts
as
soon
early.
Thank
you,
bye,
bye.
Thank
you.