►
Description
Customer story on PnP Partner Pack usage at Weleda AG (http://www.weleda.com). Experts Inside (http://expertsinside.com) implemented a customer deployment by using PnP Partner Pack (https://github.com/OfficeDev/PnP-Partner-Pack) as a starter kit for customer specific deployment.
More details from https://dev.office.com/blogs/pnp-customer-story-using-pnp-partner-pack-at-weleda-ag
A
First
of
all,
my
nemesis
are
you
Vernon
I'm,
Senior,
Program,
Manager
from
Microsoft
and
ship
and
engineering,
and
with
me
today
on
the
two
guys
who
are
responsible
of
the
of
the
implementation.
Well,
those
other
people
as
well,
but
they're,
representing
the
actual
implementation
team
from
the
experts
inside
so
Nikki
and
Kevin.
And
will
you
need
to
do
the
intros
first.
B
Yes,
of
course,
Thank
You
visa.
My
name
is
Nikki
Burrell
I'm,
just
managing
consultant
experts
inside
a
miami
p
for
office
server
and
services
and
worked
around
with
a
pnp
staff
for
one
year
actually
now
and
yeah.
We
use
it
at
a
customer
site
and
on
the
other
side
there
is
my
colleague
Kevin,
so
Kevin
some
words
for
you,
yeah.
C
A
You
Kevin
camp.
Thank
you,
nikki
is
so
before
we
actually
go
to
the
actual
content.
Let's
do
a
quick
intro
on
the
B&B,
because
there's
always
people
who
are
not
necessarily
familiar
of
the
sharepoint
EMP,
so
the
sharepoint
patterns
and
practices
is
here
to
help
field,
as
in
the
customers
and
partners
to
learn
the
right
ways
of
doing
customizations
for
sharepoint
online
and
also
for
sharepoint
on-premises.
We
provide
code
samples,
Karnas
documentation.
A
B
Thanks
with
so,
we
have
two
main
parts
in
this
web
curse.
The
first
part
is
what
I
just
doing
is
talking
a
lot
about
what
are
the
customer
requirements
and
what
is
the
solution
we
built
on
base
on
top
of
a
PMP
partner
pack
and
in
the
second
part
Kevin
will
just
talk
about
the
customizations
and
the
code
we
used.
B
So
let's
talk
about
the
customer
requirements,
so
customer
requirements
are
definitely
really
really
typical
for
office
365
for
SharePoint
projects.
But
first
of
all,
let's
talk
about
the
customer.
Customer
is
the
validity.
It
is
one
of
the
world
leading
companies
for
natural
cosmetic
and
is
found
it
and
located
in
Switzerland
and
get
subsidiaries
all
over
the
world
if
you're
interested
in
a
deeper
informations.
What
balita
is
doing
with
the
Microsoft
Technology?
There
is
the
link
to
a
customer
success
story
on
a
Microsoft
website.
B
Okay,
but
now,
let's
talk
about
what
we
did
it
in
the
context
of
the
PMP
partner
pack
from
customer
requirements,
as
I
said,
are
definitely
typical.
Now
I
want
to
create
team
sites
based
on
their
own
templates.
They
want
to
use
their
own
composed
look
within
their
team
sites.
They
have
some
requirements
about
life
cycle
management,
deletion
of
unused
sites,
definitely
because
of
we
are
working
with
sharepoint
online
and
office.
365
mobile
use
and
also
the
use
on
tablets
or
phones
is
definitely
one
of
the
big
points
we
have
to
solve.
B
So
these
are
first
part.
You
see
in
these
lists
is
stuff
that
the
PMP
partner
pack
can
cover
out
of
the
box.
On
the
other
side,
we
get
just
the
need
to
create
our
own
stuff
because
of
the
customer
just
using
Yammer
really
really
frequently.
They
started
their
journey
in
office
365
with
the
Yammer
enterprise
network
and
so
for.
Every
team
side
we
were,
the
user
is
creating.
B
He
get
a
chance
to
say,
can
I
get
also
a
Yammer
group
for
this
team
side
and
when
the
team
said
is
ready
provisioned,
he
wants
to
see
a
amer
threat
as
a
part
of
his
landing
page
of
the
team
side.
So
this
first
points
are
definitely
standard,
pnp
technology,
but
this
one
is
a
custom
stuff.
We
have
to
do
and
we
had
to
develop,
and
this
is
what
Kevin
is
talking
about
in
a
couple
of
minutes
before
we
go
to
the
demo.
B
Let
me
just
talk
a
little
bit
about
the
architecture
of
pnp
partner
pack,
so
you
can
hear
see
the
link
on
github
we're
all
this.
What
I
explain
now
and
what
I
show
you
in
the
demo
is
just
written
down
in
how
to
script
and
you
can
get
the
sources
to
play,
apply
it
on
your
own
office,
365
and
Azure.
So,
first
of
all,
when
we
talk
about
the
cloud
version,
we
have
office
365
and
we
have
a
better
subscription
and
in
every
subscription
you
have
create
some
some
some
services,
some
some
stuff.
B
B
So,
for
example,
the
templates
the
side
collection
templates
are
located
in
these
thin
side
and
also
the
provisioning
chops
created
by
the
users
are
just
located
there
and
when
you
set
up
the
partner
pack
following
the
step-by-step
introduction
you
can
find
on
these
get
up
side.
Then
you
create
an
app
in
the
active
directory,
which
is
then
integrated
in
your
app
launcher,
and
if
the
user
is
clicking
on
this
app
in
the
background,
he
is
redirected
to
a
shiur
website.
So
you
can
see
it
in
the
demo
a
couple
of
minutes.
B
It
looks
really
really
familiar
the
two-year
office
365.
So
for
a
normal
user.
He
didn't
recognize
that
he
is
leaving
the
office
365
and
is
now
in
Azure.
And
then
you
go
to
the
dialogue
and
if
you
create
click
Submit
in
the
background
there
are
jobs
created
and
the
team
site
is
created
and
provisioned
based
on
these
are
jobs
in
your
office
365.
So
this
is
how
it
works
from
a
high-level
overview
architecture
perspective
and
for
now,
I
just
switch
in
to
the
demo
and
show
you
what
I
talked
about
in
a
customer
implementation.
B
Okay,
that's
burst
this
arm,
as
you
can
see
here,
I'm
in
office,
365
and
mutter
Lolita,
and
what
I
want
to
show.
You
is
first
of
all,
we
got
here
in
the
app
launcher,
our
provisioning
app
and
when
I
just
click
to
this
app
I
come
to
this
page
and
for
every
one
of
you
who
knows
the
PMP
partner
pack,
when
you
deploy
it
from
from
a
default
configuration,
you
see
that
we
localize
this
page.
We
gather
our
own
intro
text.
Look
at
our
own
logos.
You
can
fully
customize
this
our
next
step.
B
You
will
see
this
in
a
more
detailed
version.
So
what
we
definitely
customized.
A
lot
is
just
the
dialogue
for
creating
a
new
team
site.
It
is
in
German.
We
use
our
own
logo
actually
in
this
environment,
only
one
team
site
template
is
available.
We
can
choose
it
and
when
we
go
now
to
the
next
button,
you
see
that
we
just
customized
this.
B
Definitely
a
lot
on
this
point
you
can
see,
are
the
option
for
the
users
creating
the
team's
I'd
to
say:
I
want
also
a
Yammer
group,
yes
or
no
with
this
check
box,
and
that's
it
no
more
stuff
what
a
user
had
to
fill
out
here.
So
we
are
got
also
on
an
automatism
that
when
I
fill
in
here
these
title
that
is
automatically
taken
as
observer,
absolutely
customizing.
What
we
get
in
a
standard
version.
We
get
rid
of
all
the
additional
informations
which
is
more
confusing
for
the
end
user,
yeah.
A
The
test
kind
of
a
kind
of
elaborating
on
that
one.
What
nick
is
saying
that
the
out-of-the-box
PMP
part
and
back
has
a
lot
of
additional
options
as
well.
You
can
actually
define
if
the
site
is
responsive,
it's
going
to
be
respond
and
not
and
a
few
additional
settings
will
it
have
external
sharing,
enabled
and
all
of
them,
and
in
this
case,
for
this
particular
customer
customer
has
decided
that
we
don't
want
to
actually
expose
those
settings.
We
want
them
to
be
by
default
in
certain
ways.
A
So
as
an
example,
all
of
these
themed
sites
will
have
a
responsive
experience
so
that
it
scales
between
the
different
devices
accessing
the
team
sign.
So
all
of
those
settings
has
been
a
kind
of
a
hidden
from
this
page
or
modified
not
to
be
on
the
page
so
that
the
end
user
experience
is
is
pretty
slick
than
and
simple.
B
Yes,
so
I
assure
you,
the
outcome
of
these
teams
are
provisioning
in
a
couple
of
minutes
and
you
can
see
that
the
partner
that
the
response,
if
your
ipaq
is
automatically
also
deployed,
but
first
of
all,
let's
have
a
quick
look
at
the
error
environment.
So,
as
you
can
see
here
we're
in
an
error
active
directory
and
in
its
active
directory,
we
have
these
application.
B
The
will
lead
a
provisioning
app,
we
call
it
just
registered
and
this
is
why
we
got
these
entry
in
the
app
launcher
and
on
the
other
side,
we
have
to
create
some
dom
rep
chops.
But
this
is
all
part
of
the
pnp
partner
pack
and
it's
definitely
a
documented
step-by-step
how
to
set
up
this
environments,
how
to
create
the
certificates
and
handle
all
this
so
by
the
way
pnp
partner
pack
remote
provisioning
is
not
running
in
the
user
context.
B
It's
just
running
in
app
context,
so
you
do
not
need
a
special
technical
user
account
or
something
like
that's
in
the
background.
Okay,
so
here
in
this
case,
we
got
to
schedule
time
shop,
which
is
running
every
five
minutes.
Looking
in
the
infrastructure
side
collection
to
see
if
there
are
new
parishioner
chops
and
then
creating
the
websites
and
outcome,
I
can
show
you
here.
It's
just
looking
like
this,
so
it
is
really
clear
is
really
simple:
it
is
the
first
version
of
team
sites.
B
B
You
is
that
you
also
deploy
the
responsive
package
so
just
dealing
with
this
and,
as
you
can
see,
if
I
just
smaller
this
down,
we
get
in
this
point
where
it's
collapsing
and
all
the
web
parts
are
just
in
one
row
and
the
navigation
is
collapsing,
and
this
is
definitely
deployed
by
default
with
the
Lucian
we
created
based
on
the
PM.
People
are
in
effect
for
the
customer.
Okay.
So
now,
let's
switch
back
to
the
slides
yeah.
So
far
from
my
side
from
my
demo,
okay
Kevin,
can
you
take
over.
C
So
the
extensibility
handler
is
actually
quite
simple.
What
it
does
is
it
stores
the
Yama
group
name
and
the
Yammer
group
administrator
as
a
template
parameter
and
then
human
provisioning.
It
tries
to
create
the
Java
group
on
behalf
of
that
administrator
and
if
it's
already
exists,
it
just
reduced
the
krupa,
deeds
group,
ID
and
stabbed,
and
in
the
end
it
starts
the
group
ID
at
the
property
back
off
the
team
side,
so
that
the
web
part
can
actually
work
with
the
group
ID
on.
A
So
if
the
yammer
in
the
creation
is
not
natively
implemented
in
the
PM
paper,
provisioning
engine
and
we're
not
actually
planning
to
do
dance,
at
least
for
now,
in
this
case,
customer
has
wanted
to
have
this
kind
of
a
custom
operation
to
be
executed
as
part
of
the
template
provisioning,
and
that's
why
kevin
has
implemented
the
CMR
thing,
which
is
hooked
into
the
template
just
to
clarify
now,
I
got
to
really
create
scenario
actually
to
get
implemented
as
an
extensibility
hunter.
No
doubt
cool.
A
I
would
say
quickly
that,
even
though
you're
saying
that
it's
a
simple
but
it's
super
super
powerful
and
typically
the
simple
solutions
are
always
the
most
all
the
best
ones
as
well
yeah-
and
this
is
a
well
the
JavaScript
Yammer
embed
embed
capability
is
something
which
well
it's
quite
easily
adaptable,
but
I
think
it's
a
clever
way
of
extending
that
by
having
the
property
back
query
against
the
property
back
in
a
site
and
then
selecting
the
group
ID,
so
they
create
implementation.
No
doubt
that's.
A
That's
why
place
that's
a
good
point
and
if
you
need
to
for
some
reason,
let's
say,
consolidates
Yammer
groups
at
some
point,
you
can
do
that
as
well.
Just
been
getting
all
of
the
sites
in
the
same
group
there's
multiple
kind
of
a
let's
say
that
this
always
the
emer
people
are
saying
that
maybe
you
shouldn't
be
creating
one
Krug
for
every
single
team
site.
Maybe
you
should
share
the
same
group
for
multiple
sites
and
it's
debatable
I,
don't
think
we're
at
the
right
people
to
make
that
decision.
A
C
Them
cool
so,
and
the
last
part
is
scheduled,
scowl
schedule,
good
job
that
is
implemented
as
a
pimp,
eat,
I'ma
drop
and
what
it
does
is
for
each
team
side
that
has
am
accrue.
It
treats
all
users
from
here,
yeah
my
crew
and
from
the
associated
groups
in
the
team
side,
and
it
just
keeps
the
users
in
sync.
So
if
you
know
people
get
added
to
the
deep
side,
they
also
get
added
to
the
other
group
whenever
the
drop
runs.
A
On
this
one
chest
again
slightly
elaborate
on
that
one,
the
PMP
time'
job
is
referring
to
the
BMP
damage
of
framework,
so
we
do
have
in
the
a
big
core
component.
We
have
this
framework
which
is
giving
you,
for
example,
multithreading
support
and
easy
access.
All
of
the
sites
within
your
tenant
create
at
work,
and
it's
a
it's
a
great
free
work
to
get
advantage
or
take
advantage,
and
then
yeah
in
this
case,
kevin
has
been
able
to
concentrate
on
the
business
logic
rather
than
concentrating
on.
How
do
I
get
access
on
the
sides?
A
So
all
of
that
is
taken
care
of
and
that
the
follower
thing
obviously,
is
that
the
team
sites
and
yemek
group-
they
don't
have
a
native
sync
between
the
members
and
that's.
Why
there's
this
automated
soon
between
them,
at
least
for
now,
sooner
or
later,
there
might
be
some
new
capabilities
in
the
future.
A
Who
knows,
then
we're
not
kind
of
disclose
anything
or
like
that
within
this
webcast
anyway,
but
for
now
at
least
when
we
do
is
recorded,
there's
no,
let's
say
12
one
between
a
yarmulke
rip
and
a
theme
site,
and
that's
why
the
synchronization
process
is
there.
The
top
is
running
in
15
minutes
just
out
of
curiosity.
Well,
obviously,
the
BMP
time
into
a
framework
gives
multithreading,
but
it's
every
single
15
minutes
too
often,
or
is
it
it
depends
on
the
amount
of
sites
which
are
there.
C
A
C
And
so
last
thing
I
want
to
show
you
is
the
actual
llamaba
part
on
the
team
side.
So
this
is
the
nodal
team
that
has
created
with
the
mr
extension
enabled
and,
as
you
can
see,
on
the
right
side,
there's
this
llamar
apart
and
it's
just
rubbing
how
we
expect
you
to
work
right.
So
I
can
just
say:
can
just
post
inside
my
Emma
group
and
it's
working
actually
I
don't
see
more
miles
so
I
can
click
Auto,
druggy,
Crossfield.
A
A
Giving
so,
let's
actually
do
a
quick
summary
on
on
what
did
we
see
here?
So
what
Nicky
and
kevin
has
essentially
done
is
that
they
followed
up
on
the
date
taken
advantage
of
the
PMP
parton
pack,
which
is
available
for
any
customer
and
any
partner
to
take
innovation,
take
inspiration
and
build
their
own
solution.
On
top
of
it.
The
BNP
parking
back
is
an
open
source,
community
treatment
initiative
or
project
in
a
github
and
you're
more
than
willing
to
also
contribute
back.
A
So
if
you
find
any
issues,
we
absolutely
would
welcome
that
feedback
in
the
PMP
partner
back
as
well.
But
what
the
really
the
key
point
of
the
BNP
porting
back
is
to
is
to
make
sure
that
there's
a
starting
point
for
the
customers
important,
is
to
start
building
their
customizations
on
top
of
existing
and
validated
solution
where
we
have
ten
sentence
of
contributors,
making
sure
that
the
quality
is
on
the
right
stage
and
from
a
ship
on
the
engineering
perspective.
A
We've
been
using
BMP
part
and
back-end,
oh
and
the
BMP
provisioning
engine
to
the
BMP
provisioning
ends
and
its
really
kind
of
an
inspiration
for
SharePoint
engineering
as
well,
even
though
that
sounds
weird,
but
that's
currently
the
realities
of
life
so
that
in
the
SharePoint
site,
the
native
SharePoint
site
provisioning
has
been
slightly
lacking
behind
on
the
on
the
best
possible
capabilities.
And
engineering
is
now
heavily
investing
on
that.
A
But
today,
like
mentioned,
we
saw
the
BMP
partner
back
taken
and
then
modified
based
on
the
business
requirements
of
the
customers
like
adding
the
the
removing
some
of
the
configuration
options
from
the
you
is
adding
the
customer
branding
to
it
and
then
also
including
the
Yammer
integration
on
it
and
the
really
nice
clean
implementation
for
this
particular
customer
and
anything
Kevin
or
Nikki.
What
I
missed
from
a
summary
perspective.
B
Me
say:
if
we
go
to
the
customer
and
the
project
and
say
maybe
for
for
your
needs,
we
can
use
the
PMP
partner
pack,
so
everyone
is
just
looking
with
big
eyes
and
say
what
is
a
PMP
partner
pack.
So
we
have
to
introduce
what
we're
doing
here
and
then
what
other
ideas,
but
when
they
understand
the
power
of
the
solutions,
they're,
absolutely
fine
and
just
really
interesting
in
just
implemented
and
use
it
yeah.
Yes,.
A
We
do
know
that
within
the
last
three
months
there
have
been
six
hundred
production
tenants
where
the
BMP
provisioning
engine
has
been
executed,
so
Nikki
an
and
giving
they're,
not
the
only
persons
who
are
using
the
PMP
barking
back.
There's
a
lot
of
other
customers
using
that
as
well.
So
it's
a
relatively
safe
solution
to
be
used
by
other
customers
as
well,
but
I
think
I
think
that's
wrapped
up
the
webcast.
So
thank
you,
nikki.