►
Description
Recording of the SharePoint – General development Special Interest Group (SIG) community call from January 23, 2020.
Topics covered:
Latest news from Microsoft SharePoint engineering around PnP CSOM Core extension, PnP PowerShell and on modernization tooling. Three demos were delivered by PnP community members and are published separately in addition to being delivered during this meeting. The call was hosted by Vesa Juvonen (Microsoft).
- Demo: Updates on the sp-dev-docs issue list support model | Andrew Connell (Voitanos) | @andrewconnell
- Demo: Using column and view formatting in lists and libraries at Microsoft Teams | Chris Kent (DMI) | @theChrisKent
- Demo: Reference implementation / tutorial on complex workplace provisioning automation | Vincent Biret (Microsoft) | @baywet & Franck Cornu (aequos) | @FranckCornu
Additional details on topics covered during this call may be found in the SharePoint Developer Blog post for this call at: http://aka.ms/spdev-blog.
All previously recorded SharePoint Dev monthly community calls: https://www.youtube.com/playlist?list=PLR9nK3mnD-OVC4_ut9bUi6ffRXLVuF0_g
All SharePoint PnP Developer Community demos: https://www.youtube.com/playlist?list=PLR9nK3mnD-OWSbg0o9a7mx_E7s2u7h_o2
SharePoint PnP Developer Community channel on YouTube: https://aka.ms/spdev-videos
More information on SharePoint Framework library components is available at: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/library-component-overview.
You can download an invite for this bi-weekly community call at: http://aka.ms/spdev-sig-call.
For details around the open-source work being done by the SharePoint PnP Development Community, visit http://aka.ms/sppnp
A
Welcome
everybody:
this
is
general
SharePoint
development,
special
interest
group,
and
this
is
the
bi-weekly
sync
and
it
is
23rd
of
January
2020,
which
is
pretty
cool
now.
This
is
the
general
shape
on
development
sake,
which
means
that
we
talk
about
everything
else
except
SharePoint
framework,
but
also
we
can
touch
that
in
the
topics
as
well
and
probably
we're
going
to
touch
that
today
in
in
certain
areas
as
well,
but
that
we
do
have
a
separate
SharePoint
framework,
a
special
interest
group
and
BMPs
special
interest
groups
happening
bi-weekly
and
Thursdays.
A
So
every
single
Thursday
at
this
time
there's
always
a
community
call
who
and
apparently
based
on
the
community,
call
surveys
and
discussions,
and
the
polls
which
we
did.
You
do
not
actually
mind
that
there's
quite
a
few
costs,
and
so
some
people
obviously
didn't
want
to
have
this
many
calls
and
they
can't
join
all
of
the
cost.
Maturity
of
you
were
saying
that,
actually,
it
is
a
good
thing.
A
You
have
enough
course
you
don't
necessarily
want
to
have
more
of
them,
but
the
existing
amount
is
good
and
you're
willing
to
at
least
check
to
some
of
the
recordings
later
on,
which
is
a
good
thing,
so
we're
ready
to
provide
you
additional
content
where
it's
suitable.
Now,
let's
actually
go
to
today's
agenda,
so
we're
going
to
do
a
quick
recap
on
the
bmp-2
season.
We're
heading
with
BNP,
see
some
core
site:
BMP,
partial
and
the
orientation
tooling.
A
So
just
updating
everybody
what's
happening
on
that
side,
making
sure
that
you
are
aware
of
the
goodness
and
everything
else
what's
happening
there.
So
if
you
are
using
any
of
those
doors,
you
are
up-to-date
on
things
we
can
kind
of
a
potentially
hint
where
we
are
heading
during
the
spring,
potentially
on
those
sections.
There's
there's
some
interesting
development
on
that
area,
which
seems
really
interesting
and
but
that's
going
to
take
still
some
time
and
I
haven't
agreed
anything
to
talk
about
these
things
with
Burt
and
and
urban.
A
So,
let's
see,
if
you
can
actually
just
that
now
today,
we
will
have
also
three
different
demos:
we're
gonna
talk
about
sand
updates
on
the
SPF
Dukes
issue
list,
support
model
which
we
actually
applied
yesterday
on
the
SPF
issue
list,
and
we
wanted
to
clear
out
and
do
a
kind
of
a
reset
on
the
things
which
haven't
been
moving
or
we
haven't
actually
working
on
them
in
the
engineering
side.
So
we
need
to
do
a
quick
reset
of
things
which
is
beneficial
for
everybody.
A
So
that
means
that
we
are
cleaning
up,
stuff
isn't
moving
and
that's
that's
definitely
a
good
thing,
and
the
purpose
of
that
one
is
that
we
have
more
time
on
the
relevant
issues
and
if
we
accidentally
by
the
way,
close
some
of
your
issues
which
are
still
valid,
please
do
reopen
them.
That
wasn't
our
intention,
but
we
needed
to
clear
some
air
over
there
as
well
and
I'm.
A
Gonna
do
similar
exercises
on
the
other
repositories
in
the
future
as
well,
because
we
to
be
fair,
we
haven't
done
a
good
job
on
on
staying
up
to
date
on
all
of
the
incoming
questions
and
asked
and
everything
else,
and
we
need
to
figure
out
how
to
do
that.
Some
of
that
will
be
automated
something
else
in
the
future
and
because
we
definitely
want
to
help
you
with
this
Thanks
no
ii
emma
is
from
the
dear
christians.
We
agreed
that
even
I
don't
know
what
he's
gonna
present.
So
this
is
gonna,
be
a
surprise.
A
We're
gonna
take
a
massive
rukia
risk
with
microsoft,
so
we're
gonna.
Let
christians
to
do
a
surprise
demo
on
that
one.
Well,
no
increase
I!
Think
it's
a
it's
a
good
thing
to
do,
and
then
the
main
demo
so
to
say
not
taking
anything
away
from
entry
and
Chris
is
definitely
Vincent
and
Frank
have
been
pretty
recently
moved
into
Microsoft.
A
So
he
wasn't,
namely
be
on
the
office
dev
side
and
then
moved
into
Microsoft,
but
before
he
moved,
he
worked
together
with
Frank
corner
to
create
a
reference
implementations
last
tutorial
on
a
complex
workplace,
provisioning
automation,
this
really
cool
stuff,
which
is
that
cross.
The
Microsoft
recess,
divided,
if
let's
say
platform
as
a
virtual
teams
and
SharePoint,
and
all
that
stuff,
so
really
really
cool,
really
cool
stuff,
which
will
be
highly
beneficial.
A
Probably
for
many
of
you
because
I
think
that's
quite
a
typical
scenario,
but
the
enterprise
customers
one
or
what
your
IT
might
ask
you
to
do
for
them
or
well,
not
IT.
The
business
typically
asks
an
IT
delivers,
but
that's
a
separate
discussion.
No
quick,
quick,
quick
recap
on
the
opportunities
and
by
the
way
on
the
surveys,
we
did
get
some
feedback
on.
Why
on
earth
you're,
always
recapping
the
existing
resources
and
that's
by
design,
because
quite
often
in
this
course,
even
up
to
half
of
the
people
in
this
course
are
new.
A
A
We
do
welcome
community
rivers,
demos,
we
encourage
community
demos,
that's
probably
the
easiest
way,
also
to
if
you're
looking
into
getting
an
MVP
status
for
doing
presentations
in
their
school,
something
actually
want
to
Community
Design.
Definitely
the
easiest
way
to
do
that
and
that
easiest
way
to
actually
get
a
queued
up
to
be
a
demo
is
to
being
me
battery
bird,
some
of
the
core
team
members,
and
there
will
schedule
we
schedule
you
on
any
of
the
upcoming
sports.
A
Contributing
in
kids
are
absolutely
welcome
as
well,
because
we
actually
get
a
lot
of
issues
and
a
lot
of
things
going
to
the
issue
list
and
helping
with
the
incoming
load
and
definitely
helps
and
incoming
questions
and
ask
and
answering
those
or
contributing
on
potential
issues
as
well.
A
lot
of
the
I
would
say:
99%
of
the
people
who
are
active
in
archetype
repositories
are
not
actually
getting
paid
and
sure
this
is
as
an
example
for
my
job.
A
This
is
part
of
my
job,
but
a
lot
of
the
people
who
are
actually
contributing
in
this
open
source
efforts
or
do
not
get
paid.
So
it's
not
like
we
can.
You
can
expect
the
Microsoft
to
fix
things,
because,
actually,
quite
often
it's
not
Microsoft
who's
even
built
the
solution
which
you
are
using
so
we're
building
these
together
as
a
community,
which
is
a
lot
of
benefits
as
well.
Last
thing
here
is
the
provide
feedback,
provide
feedback,
provide
feedback.
So
we
need
to
know
if
something
isn't
working,
please
let
us
know
if
something
is
working.
A
Please
do
let
us
know
as
well,
and
we
as
human
beings
tend
to
always
promote
negative
things.
So
positive
feedback
is
welcome
as
well.
So
let
us
know
what
works
and
what's
interesting
and
how
that
seems.
It's
something
which
you
should
bid
on
will
give
us
a
sign,
an
indication
that
that's
an
area
where
we
should
be
investing
in
the
future
as
well.
Good,
quick
recap
also
on
the
resources,
a
game,
SSB,
Dib,
Docs
or
documentation,
we're
working
on
an
updated
tutorial,
videos
and
tutorials.
There
was
a
lot
of
updates
there.
A
Recently,
a
chemist
has
made
their
videos
new
stuff
getting
released
actually
every
single
day,
which
is
pretty
cool
thing.
It
came
speed
of
issues
for
issue
list
or
any
day
of
issue.
Go
there
submit
an
issue.
Let
us
know
we'll
try
to
help
you
and
then
the
kids
hop
open-source
github.com
SharePoint
and
get
a
PMP
a
lot
of
stuff
happening
over
there.
Don't
start
from
scratch,
go
and
check
out
what
we
have
available
and
start
you
using
the
existing
assets.
All
of
that
stuff
is
being
provided
using
MIT
license,
which
basically
means
take.
A
It
use
it
and
make
money
out
of
it
as
well.
We
don't
really
care
it's
there
for
you
to
benefit
now,
quick
recap,
also
on
the
github
site
and
community
site.
We
do
have
this
awesome
initiative.
Sharing
is
caring
initiative
from
david
warner
and
there's
multiple
other
people
helping
in
here
as
well,
but
if
you
don't
feel
comfortable
of
contributing,
please
please
go
and
have
a
look
on
what
the
sharing
is
caring
initiative
is
all
about
and
that's
going
to
help
you
to
get
started.
A
So
if
the
whole
point
of
this
one
is
making
sure
that
you
feel
comfortable
enough
to
submit
pull,
requests
or
and
make
changes
and
assist,
and
the
other
ones
in
the
community
and
really
really
is
where
to
get
started
so
really
great
stuff
from
david
corner
of
water
on
that
side.
But
let's
go
to
the
BMC,
see
some
current
library,
quick
recap
on
what's
happening
here:
Bert
I
saw
you
on
a
clock.
Yes,.
B
B
So
what
is
in
there
that
version
from
4.5,
which
has
it
has
been
like
fortified
from
the
early
days
from
the
beginning?
Actually,
two
four
six
one
two
enable
us
to
use
additional
and
you
get
packages,
then
the
other
big
thing
is
this:
the
pages
API
has
system
updates,
both
in
the
API
as
in
the
provisioning
engine.
For
two
reasons.
The
main
reason
is
this
multilingual
page
support,
so
we
are
actually
rolling
out
multilingual
in
this
quarter.
B
It
should
hit
your
authorities
quite
soon
already,
maybe
it
already
its
authorities
I,
don't
have
an
exact
schedule,
but
they're
really
really
soon,
and
once
you
have
that
we
allow
you
to
actually
create
multilingual
solutions
packages
with
a
visioning
template,
for
example,
or
use
the
API
to
where
to
trigger
the
creation
of
translations
of
existing
pages
etc.
So
all
of
that
is
there
the
same
category.
There's
spaces
support
or
be
not
so
widely
used.
A
Just
quickly
clarifying
their
work,
this
kind
of
an
interesting
situation
where
we
we
do
not
have
a
way
of
introducing
capabilities
in
the
provisioning
engine,
which
would
not
would
be
only
available
internally
in
Microsoft.
So
now
that
we
are
already
internally
using
Microsoft
spaces
and
testing
things,
we
we
added
that
support
in
here,
so
we're
able
to
use
it
in
in
internal
usage.
A
A
Now
that's
too
much
on
this
one,
but
also
quick
teaser.
Maybe
I
hinted
this
one
when
we
started
to
agenda
so
we
do
have
an
active
movement
on
that
standard
and
and
this
kind
of
a
new
modern
ways
of
doing
dotnet,
waste
implementation,
but
I,
don't
we
don't
have
an
ETA
yet
and
we
don't
have
an
exact
timelines,
but
there's
no
really
really
really
active
plans
internally,
so
things
are
moving,
so
that's
kind
of
a
teaser
for
those
who
are
waiting
for
the
dotnet
standard
and
also
done
the
standard
see
some
core
version.
A
C
A
C
A
C
Consumers
he's
helping
me
with
this,
because
there
were
so
many
PRS
waiting
and
we
had
a
backlog.
A
long
backlog
of
things
to
work
through
he's
been
a
great
help,
so
a
lot
of
things
have
been
worst.
Of
course,
everything
that
has
been
done
in
the
core
library
automatically
drills
down
to
be
PowerShell.
So
all
the
new
things
that
Bette
mentioned
for
my
friends-
spaces,
no,
that's
kind
of
stuff
that
is
automatically
available
in
PNP
PowerShell.
We
don't
have
to
do
anything
for
that.
A
lot
of
other
things,
small
small
changes,
somewhat
bigger
change.
C
This
new
command
lets
a
lot
of
things
going
on
there
very
happily
continuing
working
our
way
through
D
and
E
PRS,
the
outstanding
PRS,
and
sometimes
we
have
to
move
it's
a
very
old
PR.
Sadly
enough,
so
you
will,
if
you
still
have
an
outstanding
PR,
we
will
look
into
them
and
try
to
merge
them
if
relevant,
cool.
A
B
Again,
the
January
drop
from
last
week
that
favorite
version
bump
like
same
in
PowerShell
and
because
these
things
are
kind
of
connected
each
other,
some
2010
were
parked
handling
improvements
and
internal
refactoring
to
be
able
to
use
like
an
IDE,
restricted
cash
interface
all
caching
eats,
which
then
enables
you
is
the
tooling
in
this
field
scenario.
So
if
you
on
the
plug-in
we
discuss
here
or
other
types
of
distributed,
cache
solutions
what's
coming
next
for
the
transformation
framework
for
patient
summation.
More
specifically,
that's
some
improvements
in
table
handling
and
image,
especially
when
tables
are
malformed.
B
B
We
go
yeah
stick
is
taken
and
that
one
has
a
new
feature
if
a
new
scan
mode
called
the
home
page
only
scan
which
it's
like
a
page
scan
which
was
there
before,
but
only
for
home
pages,
and
that
one
also
produces
a
list
additional
file,
all
the
sites
with
and
customized
home
pages.
So
now
you
might
wonder
like
why.
Why
do
we
need
that
file
for
her?
B
So
the
file
and
the
scanner
changed
kind
of
is
linked
to
a
broad
homepage,
monetization
effort,
that's
going
from
Microsoft,
and
this
helps
you
understand
better,
like
which
home
pages
will
be
potentially
modernized
and
how
to
work
around
that.
If
you
don't
want
that,
that's
why
this
one
will
be
helpful
and
then
the
last
thing
I
keep
repeating
this,
because
it's
important
Dell
of
blogs
are
retired.
We
will
actually
just
remove
them
from
the
platform.
If
you
still
have
Dell
of
blocks,
you
can
modernize
those
blocks
into
regular,
modern
pages.
B
A
Excellent,
thank
you
Thank
You
bird
for
the
updates
and
urban
as
well.
Even
though
I
try
to
confuse
you
as
much
as
possible.
So
let's
actually
jump
a
see
if
you
are
ready
to
go
to
do
a
quick
update
on
what's
happening,
but
there
was
a
good
question
from
Christian
already
on
hey.
Was
there
an
accident
related
on
which
issue
and
all
of
that
so
let's
actually
walk
this
chair
together.
D
Thank
you,
so
I'm
gonna
drop
a
link,
real
quick
into
the
chat
or
refer
to
that
in
just
a
minute.
So
asbestos
said
at
the
beginning
of
the
call.
We
made
a
bunch
of
changes
to
the
issue
list.
Just
there,
some
process,
some
policy
and
some
actual
changes
that
we
made
it
looks
like
I
made
all
these
changes
and
I
just
want
to
make
sure
it's
very
clear
to
everybody.
This
is
not
some
unilateral
thing
that
I
did
I'm
simply
the
actor
or
the
one
that
whose
user
account
got
tagged
with
everything.
D
So
it
looks
like
I
was
the
kind
of
going
through
it
like
crazy
in
the
issue
list.
These
are
all
these
are
all
things
that
I'm
gonna
share
with
you.
Well,
it
looks
like
I
did
them.
They
were
all
done
with
a
lot
of
conversation
with
Microsoft.
There
was
a
lot
of
debate
with
this.
It
was
not
a.
It
was
not
something
that
was
done
and
a
very
off-the-cuff.
We
did
this
for
many
many.
D
We
talked
about
this
for
many
many
many
weeks
internally
before
we
did
this
so
and
everything
was
approved
by
Microsoft
definitely
open
to
feedback.
So
let
me
kind
of
explain
what
we
did
here.
There's
a
handful
of
things
that
we
ended
up
doing
so.
Would
you
see
here
I've
got
the
issue
list
here.
First
of
all,
if
you
jump
over
to
the
wiki,
there
are
now
a
few
new
pages
in
the
wiki.
You'll
see
them
in
the
section
in
the
navigation
off
on
the
left-hand
side.
D
So,
first
of
all
the
issue
list
and
then
there's
a
handful
of
other
things
that
we
have
listed
over
here.
If
you
take
a
look
at
the
issue
list
page
this
kind
of
explains
what
the
general
like
policy
and
is
with
the
issue
list.
As
far
as
Microsoft
looks
at
it
specifically
like
what
does
belong
in
the
issue
list,
what
does
not
belong
in
the
issue
list?
D
The
approach
to
closed
issues,
the
approach
to
locked
issues,
I'll
talk
about
those
in
just
a
minute
as
well
as
some
issue
templates
now:
I'm,
not
gonna,
walk
through
all
this
stuff,
I'm
gonna
kind
of.
Let
you
look
at
this
that
you're
on
your
own
at
your
own
time,
and
we
will
continue
to
update
this
as
needed.
The
special
oxygen
section
I
have
at
the
very
bottom
is
the
link
that
I
posted
to
the
chat
just
a
minute
ago,
and
this
explains
all
the
stuff
that
happened
yesterday.
D
So
specifically
what
we
did
and
I'm
gonna
jump.
I'll
come
back
to
this
in
just
a
minute,
but
one
of
the
big
things
are
big
additions
that
we
have
to
the
issue
list
is
that
now,
when
you
go
over
to
the
issues
and
you
go
to
create
a
brand
new
issue,
you
will
be
presented
with
a
first,
the
first
step
here
of
what
kind
of
an
issue
you're
going
to
create.
Is
it
a
bug
or
an
error
report?
Is
it
a
generic
issue?
D
That's
kinda
like
what
we
had
before
this
generic
question
or
generic
issue
is
gonna,
be
the
same
thing
if
you
click
on
this
blank
issue,
a
feature
request
just
as
a
heads
up
as
we
explained
in
the
wiki
feature,
requests
don't
belong
in
the
issue
list.
We
want
those
going
to
user
voice
because
that's
where
Microsoft
engineering
triage
is
new
feature
requests
to
add
them
to
the
to
their
backlog.
So
as
it
explains
in
the
issue,
if
you
go
to
create
it,
it
will
fly
out.
D
I'll,
explain
it
going
to
preview
here
that
it
will
say
that
if
you,
if
you
do,
submit
this
as
a
feature
request,
it
will
automatically
labeled
as
a
feature
request,
and
it
will
be
automatically
closed,
which
will
point
you
to
user
voice,
feel
free
to
use
this.
If
user
voice
isn't
gonna,
give
you
the
formatting
and
stuff
that
you
want,
and
you
want
to
reference
the
issue
that
was
created,
but
we
just
trying
to
guide
people
in
that
direction,
that
you
will
be
automatically
tagged
and
closed
with
the
user
voice
requests.
D
The
other
thing,
too,
is
that
that
you
see
down
here
is
that
there
are.
There
are
things
that
we
don't
that
this
issue
list
is
not
for
so
it
is
primarily
for
developer
issues
or
develop
or
development
SharePoint
development
issues.
If
this
is
an
issue
that
is
related
to
end
user
administrator,
the
end
user
experience
admin
stuff,
those
things
belong
in
the
tech
community
site.
If
it
is
a
feature
request
again,
it
goes
as
user
voice
as
well.
So
all
of
that
stuff
is
going
to
end
up.
D
D
This
thing
please
delete
this
guidance
that
you
see
here
in
this
line,
delete
this
one
line
before
you
submit
it
and
then,
at
the
very
end
we
even
put
like
you
know,
developer
environment,
stuff
that
we're
looking
for
all
this
stuff
helps
us
quite
a
bit
in
helping
you
the
more
information
you
can
provide
the
better.
It
is
now
some
of
the
big
things
that
we
ended
up
doing
some
big
changes
that
we
ended
up
doing
to
the
issue
list.
D
First,
there
was
a
sweeping
action
that
affected
and
look
at
my
notes,
roughly
250,
of
our
760,
to
open
issues.
So
what
we
ended
up
doing
is
there
was
a
time
last
year,
really
break
falls
down
into
three
different
categories.
First
of
all,
there
was
a
time
last
year
when
the
labeling
capability
that
we
have
in
our
issue
list
wasn't
working,
and
so
we
had
roughly
80
some
issues
that
had
no
labels
assigned
to
them.
D
Instead
of
walking
through
each
one
of
those
issues
that
to
figure
out
what
this
was,
what
category
can
we
apply
it
to?
In
addition,
those
80
issues:
they
had
no
activity
on
them
for
way
over
six
months,
so
we
took
the
approach
of
instead
of
taking
the
time
to
detail
each
individual
issue
and
trying
to
triage
each
of
those
80
individual
issues
that
a
lot
of
them
very
well
may
no
longer
be
a
problem
or
an
issue
or
whatever
we're
gonna
go
ahead
and
close
them.
D
But
when
we
closed
everything
that
everything
got
a
comment
assigned
to
it
with
a
link
to
one
of
the
new
sections
in
the
wiki,
that
explains
what
we
did.
Why
we
did
it
and
how
you
can
remediate
that
process?
So
if
an
issue
of
yours
was
automatically
closed
or
if
it
was
automatically
locked,
which
I'll
explain
in
a
second,
we
explained
how
you
can
remediate
that
it's
not
like
the
last
straw
that
you
see
when
that
happens.
So
that
was
one
change.
D
We
did
another
change
that
we
did
is
that
we
went
back
and
we
looked
at
all
issues
that
had
that
were
open,
that
had
no
activity
on
them
in
over
seven
months,
and
that
means
there
been
no.
There
were
no
updates
to
it.
There
were
no
questions
that
were
asked.
Nobody
did
anything
with
these
issues.
They
were
effectively
old
things
that
nobody
was
doing
it
very
well
could
have
been
that
some
of
these
were
are
still
relevant
today,
that
there's
still
bugs
that
are
out
there
and
they
haven't
been
addressed
totally
get
it.
D
We've
we've
seen
a
couple
I've
seen
a
couple
issues
get
submitted
by
people
overnight,
I'll
go
to
these
clothes
issues,
you'll
see
where
someone
said
this
thing
that
you
know:
hey
here's,
how
I
want
to
go
I
want
to
get
that
issue
open
back
up,
so
they
referenced
the
issue
and
then
we
went
back
and
we've
we've
already
gone
back
to
this
issue
and
we've
already
unlocked
it
and
opened
it
back
up
I
scroll
down
here.
We
opened,
we
unlocked
it
and
open
it
back
up
to
where
the
issue
can
can.
D
We
can
keep
discussing
it
now.
Another
challenge
that
we've
had
with
the
issue
list
lately
is
that
when
an
issue
is
closed
generally
speaking,
I
know
not.
Everybody
believes
this,
but
generally
speaking
on
an
open
repo
like
what
we
have
here
when
an
issue
is
closed,
people
generally
see
that
as
resolved
or
conversation
over,
and
you
may
not
agree
with
that,
but
that's
the
vast
majority
of
how
people
see
stuff
when
we
had
a
closed
issue
and
someone
would
go
in
after
six
months
and
say
I'm
having
this
problem,
can
someone
help
me?
D
Nobody
was
seeing
that
and
that's
leaving
a
really
bad
experience
for
that
one
user,
or
at
least
nobody
is
seeing
it
that
was
not
contribute.
That
was
not
already
involved
with
that
issue.
So
if
I
was
involved
in
the
conversation
and
the
original
issue,
then
yeah
I'm
gonna
get
an
email
update,
but
if
I
wasn't
then
I'm
never
gonna
see
what
this
person
asked
and
they're
gonna
think
that
nobody
cares.
D
So
what
we
did
is
we
followed
a
process
that
a
lot
of
other
repositories
do
and
we
went
ahead
and
lock
those
any
issues
that
were
closed
and
they've
had
no
activity
in
seven
days.
So,
if
it
is,
she
gets
closed
and
then
has
no
activity
in
seven
days
it
gets
locked,
and
that
means
that
nobody
can
add
any
more
comments
to
it.
Women
that
happens.
D
We
also
add
a
comment
saying
here's:
why
we
locked
it
if
you,
if
you
don't
agree
that
this
should
have
been
locked,
then
here's
how
you
can
go
back
and
remediated,
and
you
see
here
I'm
even
on
the
screenshot
I,
have
a
link
here
going
to
our
wiki.
That
explains
here's
how
you
do
that
and
effectively.
It's
just
go
open
a
new
issue
reference.
D
This
one
tell
us
why
alright
and
we're
not
going
to
we're
not
trying
to
keep
people
from
posting
stuff
we're
just
trying
to
make
it
a
more
efficient
place
to
go
through
and
to
address
people's
feedback.
Okay,
there
are
also
automations
that
have
been
set
up
so
that
this
will
happen
automatically
in
the
future.
So
if
you
received
a
whole
bunch
of
emails
over
night,
that
said
issues
were
closed
and
then
you
deleted
all
those
notifications-
and
you
saw
a
bunch
more
show
up.
This
automation
runs
every
24
hours
and
it
will
check
to
see.
D
Are
there
any
issues
that
have
been
closed,
that
also
have
no
activity
on
them
and
if
so,
go
ahead
and
lock
them
you'll
see
stuff
that
that's
being
done
by
this
bot,
and
we
have
a
couple
other
little
automations
and
stuff.
That's
like
that
as
well.
That's
generally,
the
the
big
changes
that
we've
made.
We've
also
got
some
nice
pages
here
that
we've
added
about
how
to
create
a
good
issue,
things
that
you
should
do
things
that
you
shouldn't
do
how
to
create
a
PR
as
well.
D
We
put
that
in
there
as
well
and
some
extra
explanation
on
some
of
our
issue:
labels
that
we
use
and
such
so
I
want
to
turn
this
back
over
to
the
next
presenter,
but
again
I'll
be
on
the
chat
and
I'm
happy
to
answer
any
detailed
questions
about
this,
and
if
you
have
any
feedback
on
stuff
that
we
did,
that
you
don't
like
or
stuff
that
we
did,
that.
You
would
suggest
that
we
should
also
consider
and
do
again.
The
idea
here
is
this
issue.
Is
we
want
to
make
it
engaging?
D
We
want
to
make
it
the
best
resource
for
you
to
be
able
to
ask
questions
and
submit
issues
and
errors
that
you
find
with
the
SharePoint
developer
experience,
but
we
also
have
to
follow
a
couple
little
rules
here
to
make
sure
that
we
can
do
stuff-
and
someone
tells
me
that
hey
I
ran
I,
did
this
in
the
power
and
the
SharePoint
admin
center
and
it
didn't
work.
How
do
I
fix
this?
It's
like.
D
A
There
wasn't
actually
too
many
questions
of
chat
for
now.
Let's,
let's
see,
if
we
get
more
when
Chris
starts,
presenting
I
want
to
recap
and
true
kernels
wasn't
a
person
who
created
the
process.
He
wasn't
the
person
who
made
the
decisions,
he
wasn't
a
person
who
who
now
accidentally
closed
your
issue.
It
was
a
decision
by
Microsoft
and
we
work
with
a
lot
of
the
MVPs
and
because
that's
how
we
scale.
A
So
if
we
buy
an
accident
closed
any
other
issue,
there
is
again
remediation
or
instructions
and
we
do
apologize,
but
this
is
for
the
common
good
for
everybody.
So
let's
reset
and
move
on
move
forward
from
there
and
I
do
apologize.
Save
is
some
pre-cut
offended
on
that
anyway,
let's
actually
jump
on
Chris's
table
chris
is
the
the
movie
actor
feature
for
coming
soon.
Yeah.
E
Let's
get
going
alright,
we've
got
a
list,
formatting
surprise
all
right.
Let's
do
again
there
we
go
so
got
a
classic
warrior
horse
aside,
of
course,
as
you
guys
may
or
may
not
know,
horses,
especially
warrior
horses
are
highly
collaborative
right,
so
they
have
things
like
Microsoft
teams
where
they
can
collaborate
in
now
in
the
past
is
hated
it
because
they
love
list
formatting,
so
very
much,
but
now
there's
some
new,
exciting
things,
at
least
in
target
and
release.
E
So
if
we
go
over
to
our
warrior
horses
team
site,
there's
gonna
do
it
on
the
web
here,
so
I
don't
mess
up
my
presentation
and
we
come
in
here
and
we
take
a
look
at
the
stable
right
go
to
general
tab.
We
come
over
our
files
tab
here
we
can
start
to
see.
There's
a
slightly
new
view
here
and
you
know:
you've
got
the
new
view
if
you're,
open
and
SharePoint
is
not
teal
just
as
an
FYI.
So,
for
instance,
my
standard
release,
template
I
forgot,
the
teal
and
the
formatting
doesn't
work
there.
E
But
here
oh
we've
got
it
in
my
targeted
released
in
it.
So
you
can
see
I've
added
a
nice
column
here
called
point
horses.
These
are
the
people
responsible
for
these
documents.
All
right,
so
that's
helpful,
be
able
to
add
additional
columns
and
do
some
cool
stuff.
So
let's
add
some
formatting
in
here
to
make
this
even
more
valuable.
Now
the
first
thing
you'll
notice
is
we're
gonna
column,
settings
I,
don't
have
any
option
to
format
this
column
here
within
teams.
E
So
that's
where
I
got
to
use
that
open
and
SharePoint,
but
so
I
click
that
and
we
go
to
the
lovely
team
site
similar
list
now
I
have
noticed
a
couple
of
weirdness.
In
the
past
few
days,
we've
had
several
issues
submitted
on
it.
There
are
some
strange
behaviors,
some
of
those
for
running
we're
not
really
experiencing.
Most
of
those
here
are
my
targeted
released
tenant,
but
I
am
seeing
some
strangeness
like
you
can
see
right
here.
It's
jammed
all
these
all
these
names
together
without
any
formatting
applied
or
as
generally
it
looks
like
this.
E
So
there's
a
couple
of
strange
things
happening
right
now:
shouldn't
affect
the
demo
here,
but
if
you're
running
into
something,
let
me
know
open
an
issue:
I
don't
work
for
Microsoft,
so
I
can't
do
much,
but
I
will
feel
sad
with
you
how's
that
oh
wait.
So
we
come
over
here
and
now.
The
first
thing
we're
to
do
is
just
kind
of
show
basic
formatting.
E
So
if
we
format
the
current
view,
we're
just
gonna
take
the
one
that
kind
of
defaults
suggest
alternate
rows
styles,
which
adds
that
every
other
row
is
gray
and
how
do
you
go
away?
We'll
save
that
and
now,
if
we
save
that
and
come
back
over
here,
we'll
switch
over
to
a
post
tab,
we'll
come
back
to
our
files.
Tab
you'll,
see
that
is
reflected
here
right.
So
our
view
formatting
is
fully
supported,
that's
nice!
So
what
about
called
formatting?
So
I've
got
this.
E
You
know
multi-person
field
here,
so
I'm
gonna
go
over
here
to
our
SP
dev
list,
formatting
repo.
So
this
is
over
and
github
again.
We've
got
nearly
70
samples
in
here
of
how
to
do
different
column,
samples
and
view
samples,
and
it's
a
great
starting
off
point.
But
I
highly
suggest
you
go
over
here
and
all
you
got
to
do
to
navigate
is
go
down
here
to
column
samples
and
then
I'm
gonna,
look
for
the
field.
Type
of
got
multi-person
face
pile!
E
Oh,
this
is
one
we've
shown
off
before,
but
I
like
it,
because
it
is
going
to
show
a
couple
things
and
couple
differences
in
teams
so
right
here
in
github,
I'm,
just
gonna
grab
all
of
that
right.
Click,
I'm,
gonna
copy
that
and
I'm
gonna
go
back
and
I'm
gonna
go
here
to
my
column,
column,
settings
format,
this
column
and
then
this
nice
window
here
just
kind
of
paste.
What
I
got
from
github
and
I'm
gonna
save
on
that
alright.
So
let's
get
rid
of
that.
So
you
see
now.
We've
got
a
nice
format.
E
It
really
shows
off
for
multi
people,
fields
right.
You
can
hover
over
and
see
their
names
right.
You
can
see
the
additional
people
died.
So
Kylene
setup
looks
really
nice
and
a
comb
over
here
and
again.
We'll
come
after
the
tab
we
can
see
now
our
column
format
is
showing
up,
which
is
great,
I,
also
notice.
The
strange
thing
is
that
the
sort
is
always
applied
here,
even
though
it's
not
a
part
of
the
view,
weird
strange
but
fun.
Oh
wait
now
a
couple
of
things
to
know
with
this.
E
So
if
we
take
a
look
here,
so
we
see
that
showing
up
at
teams
which
is
awesome
here
on
the
web.
It
also
show
up
in
the
main
client
no
problem,
but
if
we
take
a
look
at
something
like
the
mobile,
maybe
later
all
right,
so
we
take
a
look
at
our
our
mobile
devices.
Here
we
go
over
to
general
and
we
switch
over
to
our
files.
E
Tab
you'll
see
that
we
don't
get
that
same
kind
of
experience,
so
just
be
aware
that
the
list
format
of
the
view
formatting
is
currently
at
least
I
haven't
heard
otherwise,
but
currently
is
not
supported
in
the
team's
mobile
app
I'm,
showing
the
iOS,
but
the
Android
is
the
same.
Another
thing
to
note
is
that
if
we
add
a
new
tab
right
where
you
know
you
wouldn't
do
this
particular
scenario-
we've
got
a
document
library,
alright,
we're
going
to
choose
the
the
stable
where
it's
gonna
grab
that
same
under
the
files.
Tab.
E
Alright,
we're
gonna
go
here.
That's
fine,
you'll
notice
that
when
we
add
that
we
get
that
kind
of
class
experiences
what
I
mean
by
the
open
and
SharePoint
steel,
we
don't
get
any
of
those
pieces
there.
This
is
kind
of
a
specialized
team
for
you
alright.
So
when
you
come
in
here,
we
don't
even
see
our
additional
column.
You
just
have
to
be
aware
of
there's
still
some
limitations
here,
but
it
is
coming
soon
and
we
don't
want
that
junk.
So
come
back
here
to
our
files.
Tab
couple
other
things
to
note.
E
So
we've
got
the
the
format
it's
working.
It's
great
I've
chosen
this
format,
though,
specifically
because
it
demonstrates
a
couple
of
differences
between
Microsoft
team's
of
you
and
with
your
modern
ListView
and
just
come
in
just
be
aware
of
in
your
format.
So
if
we
format
this-
and
here
again
we're
gonna
ignore
some
of
the.
So
if
we
come
down
here,
I've
added
this
vertical
line
base
line
to
the
image.
Now,
if
I
delete
that
here
and
we
save
that
you'll
notice,
it
changes
zero
things
here
in
just
a
moment.
E
Did
you
save
them?
It's
very
complex
format,
apparently
that
a
second
here,
but
while
that's
doing
that
what's
gonna
happen
is
you'll
notice
that
nothing
happens
here,
but
in
teams
you'll
notice
a
slight
shift
because
of
how
that's
working
that's
going
on.
Oh
man,
let's
just
go
ahead
and
try
and
refresh
that,
while
that's
saving,
maybe
it
saved
we'll
see
if
we
got
it
applied,
so
we
said
yeah.
We
can
already
see
the
difference
here.
You'll
notice,
the
rounding
is
different,
so
there's
some
definite
CSS
kind
of
defaults
that
are
different.
In
this
case.
E
The
image
element
type
has
a
vertical
line
set
to
middle
in
teams
by
default,
whereas
in
SharePoint
Online
it
disappears.
We
set
to
baseline
so
again,
not
something
you
do
not
to
worry
about.
But
the
idea
here
is
test
your
formats
and
both
if
you
tend
to
apply
them
in
both
the
other
one
here
would
be
the
app
current
web.
So
that's
something
we've
used
before
where
we're
pulling
these
images
right.
E
So
here
you
can
see
we're
pulling
them
from
the
layouts
user
photo
and
if
we
were
to
create
that
you
know
the
current
web
we'll
put
the
absolute
web
URL
on
there.
But
if
we
took
that
away
all
right,
we
just
had
to
do
a
relative
link.
All
right,
we'll
save
that
here
you
know
so
we're
just
fine
in
SharePoint,
because
it's
just
gonna
grab
that
first
part
of
our
sites
and
everything's
good.
But
again,
if
we
come
back
here
and
we
refresh
our
files
tab
now,
we
are
sad
very,
very
sad.
E
So
just
keep
that
in
mind
as
you're
working
the
team's
to
make
sure
you're
doing
things
like
absolute
links
with
the
current
web
and
then
just
testing
things
to
see
that
there
are
some
very,
very
minor
CSS
differences.
There's
also
varying
levels
of
support
for
the
UI
fabric
themes.
Here
so
for
our
theme,
colors
and
other
stuff,
you'll
you'll,
tend
to
see
those
show
up
as
purple
rather
than
your
theme
colors,
and
it's
kind
of
ignoring
some
of
that
all
right.
So
that's
cool,
that's
great
for
Matt's
show,
but
let's
do
something.
E
A
little
more
team
specific
here,
so
I've
got
another
sample
here
we
go
back
right
into
the
hello.
Our
face
pile,
give
a
multi-person
team's
chat
link,
so
we're
gonna
grab
this
for
Matt.
Let's
take
a
look
at
what
it
does.
Oh
it's
actually
a
fairly
simple
format:
let's
copy
it
apply
it
and
we
can
take
a
look
at
what
it
does
paste
that
sucker
save
that.
So
what
it's
really
doing
is
we
take
a
look?
E
It's
just
a
link
and
it's
got
a
icon
here
all
right
and
then
it's
got
text
says:
ask
a
question.
The
key
here
is
in
the
href
for
the
link
right.
So
it's
building
this
deep
link
into
teams
chapt
by
combining
our
fields
here.
So
it's
joining
all
the
current
field,
email
and
building
that
in
and
then
it's
also
bringing
the
topic
name.
Is
the
file
leaf
ref?
So
that's
the
name
of
the
file
and
then
it's
automatically
side
of
the
message.
So
what
does
that
really
look
like
right?
E
So
if
we
take
a
look,
if
we
click
on,
say
dinosaur,
coloring
book,
you
can
click
that
we're
gonna
stay
just
join
on
the
web,
again
close
our
other
one
just
for
fun,
so
that
second,
what
we
did
was
we
automatically
started
a
chat
right
with
the
four
people.
We
said
we're
responsible
for
that
particular
document.
We
gave
the
title
of
the
challenge
three
more
people
up
here,
so
dinosaur
coloring
book.
We
have
a
starter
message
of
neigh.
Alright,
so
that's
pretty
awesome.
E
So
the
idea
that
you
can
deep
link
in
the
chat
and
integrate
that
directly
with
your
list
is
really
really
powerful.
There's
a
bunch
of
other
stuff.
You
can
do
there.
So
this
is
people.
You
can
do
a
chat
that
you
can
deeply
two
tabs.
Even
your
custom
tabs.
You
can
deep
link
to
the
schedule
and
dialogue
and
so
on.
So
it's
quite
a
bit.
You
can
do
there
and
it's
very,
very
cool
one
caution
with
that.
Is
that
the
deep
linking
when
you're
already
inside
teams
right?
E
So
if
I
go
over
to
file
it's
slightly
strange,
because
teams
expects
the
deep
link
come
to
JavaScript,
and
so,
if
you
really
wants
that
truly
integrated
experience,
where
it's
not
gonna,
ask
you
to
do
this.
You'll
need
to
use
something
like
a
field
customizer,
but
that's
probably
the
lower
killed.
This
is
pretty
easy
to
go
or
and
create
those
chats.
Okay,
all
right,
so
awesome
stuff.
Again,
that's
a
sample!
It's
already
available
to
check
it
out.
Quick
recap!
E
E
You
know
adding
a
list
tab
to
teams
and
then
providing
those
formats
is
a
great
way
to
make
a
very
simple
application
right
there
and
you're
kind
of
your
main
pane
of
glass
that
people
are
using
all
day
long,
I'm
a
great
way
to
really
simplify
things
and
emphasize
what
they
should
be
doing
right
there.
So
419
saves
the
day
again
so
check
it
out.
Here
you
go
check
out
the
full
documentation.
E
A
F
Everybody,
my
name
is
Frank:
oh
no,
I'm
a
developer
and
founder
of
my
company
called
echoes
and
based
in
Montreal.
Today
we
will
show
you
a
quick
tutorial
that
we've
made
with
fan
sent
a
couple
of
weeks
ago
about
workspace
provisioning,
especially
the
office
365
groups,
provisioning,
but
first
Vincent.
Why
don't
you
introduce
yourself
sure.
G
So
I
everyone-
some
of
you
might
know
me
from
the
days
that
used
to
be
an
MVP.
You
know
p.m.
on
the
Microsoft
graph
team.
So
if
you
have
any
questions
or
feedback
about
Microsoft
graph,
you
can
contact
me
if
you
want
interesting
enough
since
I
joined,
Microsoft
I
don't
have
access
to
a
chat
on
the
PNP
calls.
So
if
you
want
run
jokes
about
me,
go
and
go
chat.
I
cannot
see
them.
That's
all
good!
G
So
to
provide
a
little
bit
of
context
about
this
new
repository
and
this
effort
we
put
together
with
with
Frank
Frank
and
I
on
our
own
separate
sides
over
time.
We
are
multiple
provisioning
engines
that
reflect
for
some
customers.
Their
line
of
business
requirements
around
hey
I
want
provision
things,
but
according
to
my
line
of
business
scenarios,
because
I
have
a
set
of
rules
because
I
have
a
set
of
things
that
need
to
happen
and
it
needs
to
be
consistent
cell
service.
G
And
if
you
are
things
like
that-
and
we
got
the
opportunity
almost
two
months
ago
now
to
animate
to
workshop
together
to
go
animate
the
workshop
together
around.
How
do
you
go
and
start
building
your
project
engine
doesn't
matter
your
business
requirements
doesn't
matter
what
you're
doing
you
have
you
fundamentals
if
you
want,
but
you
need
to
set
in
place,
so
you
can
build
a
provisioning
engine
and
be
successful
with
it
in
your
company
and
with
that
I
will
hand
it
back
to
Frank.
G
F
You
Vincent,
so
yes,
first
thing
you
have
dedicated
to
be
positively
on
github,
so
yeah
URL
here.
So
basically,
this
is
a
solution
coming
from
a
real
good,
a
real
customer
project,
so
it
provides
very
basic
building
blocks
to
create
a
provisioning
solution,
especially
the
365
groups,
provisioning
solution.
F
So
the
initial
context
was
my
case
to
avoid,
let's
say
the
shopping
sites,
probably
because
you
know
when
you
create
the
55
groups,
through
teams
or
through
team
size,
so
it
creates
shopping
sites,
and
sometimes
you
want
to
apply
a
template
to
the
shopping
site,
let's
say
to
create
sub
metadata
columns
and
the
classification
and
so
on.
So
this
is
for
the
context.
F
You
can
also
read
a
blog
post
by
Laura
Karenin
about
the
provisioning
concerns,
so
give
you
more
context
about
this,
so
I
will
jump
to
the
architectures
first,
so
the
architecture
is
pretty
simple.
So,
first
of
all,
we
have
a
workspace
request
this,
which
is
a
shopping
list.
Of
course,
this
one
can
be
updated
or
enhanced
by
a
perhaps
application
or
a
specific
web
part
to
take
the
information
to
grab
the
information
from
the
user.
F
So
the
the
workspace
name
and
so
on,
then
we
are
some
artifacts,
so
the
first
one
would
be
a
way
bookshop
able
to
catch
the
event
of
the
new
item
creation.
Then
we
are
logic,
apps
logic
application,
so
this
will
be
to
wrap
and
provisioning
routine
through
automation,
Rob
Renwick,
with
PowerShell,
using
PNP
templates
templates
and
the
communication
between
sharepoint
and
graph
api
will
be
done
by
another
activity,
vector
V
application,
and
we
have
also
a
team's
configuration
yeah.
F
F
G
And
then,
while
you
do
that,
the
very
interesting
about
visits
again,
it's
basic
concepts
on
how
you
do
you
go
about
setting
profession
engines.
If
you
look
at
the
category
and
the
and
the
taxonomy
we're
using,
then
you
can
leverage
that
in
your
engine
interns
to
do
things
like
apply
retention,
labels
and
policies,
attack
some
items
for
search
and
discovery
or
use
that,
for
you
could
build
a
web
part
to
you
know
to
discover
the
different
different
workspaces
that
are
already
in
place.
G
Yeah
that
unlock
some
set
of
scenarios
that
you
can
use
and
implement
at
your
company
and
the
goal
of
this
content
and
training
is
to
show
you.
How
do
you
go
about
what
what
alternatives
and
options
you
have
to
implement
those
basic
blocks
for
getting
requests,
automating
things
creating
things
on
on
different
different
places
like
SharePoint
or
office,
365
or
teams,
and
so
on
and
so
forth.
Yeah.
F
So
I
don't
wait
for
the
creation,
but
I
will
take
previously
creating
one
so
P
and
the
science
or
a
new
of
this
treaty
shall
be
created
with
sharp
incisors.
It's
not
very
impressive
here,
but
basically
a
template
has
been
applied
with
some
metadata.
Some
columns
and
also
a
teams
has
been
created
with
specific
channels
and
so
on.
So
I
will
go
to
the
technical
part
of
this
thing.
So,
first
of
all,
you
will
have
to
create
a
new
engine
ready
application.
F
So
if
I
go
to
my
hazard
tenant,
so
I
created
a
new
algiedi
application
with
specific
permissions,
so
make
sure
you
use
the
same
as
your
tenant
as
your
office
365
tenant.
So
you
will
need
growth,
permission
and
sharpen
permission,
I
configure
with
application
permission
and
not
delegated
permission.
So
these
are
the
minimum
permission
that
you
will
need
to
set
up
to
get
it
work.
F
So
this
services
are
not
affect,
can
be
created
in
that
in
another
as
written
and
if
you
want
this
is
the
case
here.
So
I've
created
ty
go
back
to
the
architecture.
The
first
thing
I
have
created
is
the
sharpen
wave
as
a
function,
so
I've
created
an
efficient
provisioning
group.
Then
I
add
another
function.
F
Basically,
here's
your
function,
yep,
so
there's
a
fashion
ear
is
to
implement
the
shop
on
flipbook.
You
will
see
this
is
minified
code
and
to
get
the
to
create
your
own
code.
I
provide
you
the
code
here
into
the
repository,
so
you
have
a
SP
trigger
function,
so
this
function
is
written
in
using
typescript
because
I'm,
a
terrific
guide
so
I
like
to
write
type,
it
everywhere,
back-end
and
front-end.
F
So
the
purpose
of
this
function
is
just
to
get
the
new
event
the
new
item
event
and
pass
it
to
the
logic
app
to
the
logic
application.
So
why,
using
a
web
book
over
a
logical
trigger
because
you're
doing
when
using
logic
app,
you
can
use
the
the
built-in
trigger
when
a
new
item
is
created
in
a
list.
It's
about
the
strategy
and
the
cost
involved
in
in
this
situation
when
using
the
default
trigger.
F
This
will
be
a
polling
strategy,
meaning
the
system
will
which
will
make
a
call
every
10
seconds
to
get
a
new
item.
This
will
be
counted
as
an
action
with
with
with
integer,
so
you'll
be
charged
for
that,
instead
of
doing
that,
and
because
it's
school
we've
made,
we
made
a
web
book
so
instead
of
following
the
system
regularly,
we
will
be
notified
by
shot
point.
There
is
a
new
item
in
the
list,
so
terms
of.
Of
course,
it's
it's
small
optimized.
So
basically,
this
function
gets
rich
with
the
new
items.
F
So
we
just
want
the
add
operation
here
and
send
the
only
the
idea
of
the
new
item
in
the
list.
Then
this
ID
will
be
used
by
the
logic
application.
So
if
I
go
back
to
my
official
as
your
group
doji
cap
here,
so
basically
the
logic
up
take
an
HTTP
request
with
only
the
each
item
ID
of
the
support
item,
then
we
just
get
the
information
about
this
item
set
the
provisioning
status
and
the
interested
part
is
using
a
run.
Boot
create
a
new
job
running
a
polish
l1
book.
F
So
in
this
workbook,
basically,
you
will
have
Porsche
script.
So
go
back
to
my
code.
Here
you
have
a
polish
shell
script
called
new
workspace
that
ps1.
Basically
it's
a
regular
Porsche
script
using
pin
people
Rochelle
to
apply
provisioning
templates
and
configure
the
shopping
sites.
So
basically
what
you
have
to
to
know
the
important
parts
here
are
the
connection
to
the
graph
so
to
communicate
with
the
graph,
you
will
need
an
application
idea
and
application
secrets
and
to
communicate
with
char
point.
F
Deploying
this
solution
will
have
to
create
a
self-signed
certificates,
then
configure
it
to
your
own
book
so
support,
so
you
can
just
communicate
with
support
using
these
certificates.
This
is
all
explained
in
the
the
tutorial,
so
the
the
communication
will
be
with
the
section.
So
basically
we
create
a
new
unified
group
here,
so
it
would
be
a
new
office.
365
group
and
an
interesting
thing
here
is
because
this
script
is
run
as
the
application
identity.
F
The
office
successful
group
owners
will
be
the
application,
the
entire
application.
So
that's
not
what
we
want
here.
So
what
we
need
to
do
is
to
set
the
owner
manually
after
the
creation
and
this
operation-
it's
it's
not
instantaneous,
so
it
can
be
weird
for
the
users,
they
create
the
create
a
workspace
and
they
are
not.
You
know
right
now.
They
have
to
wait
a
couple
of
minutes
because,
under
the
behind
the
scenes,
the
permission
are
synchronized
between
all
the
the
were
closed
behind
the
office,
365
groups.
F
Then
you
just
apply
a
new
provision
in
template
to
the
site
very
simple
ear
and
we
configure
text
and
min
value,
so
you
configure
metadata
for
this
site.
So
for
this
we
use
the
property
bag
of
the
site,
collection
and
I.
Give
you
a
tricky
here,
so
you
can
just
reuse
the
same
format
as
a
texting,
texting
value
for
the
photo
search.
So
you
will
be
able
to
use
this
Catterick
categorization
for
the
search
and
especially
the
more
than
modern
search
web
part.
F
So
just
follow
this
format
represent
that
represent
the
text,
enemy
value
and
you
will
be,
you
will
be
able
to
use
it
within
the
modern
search
yeah
and
basically
you
can
do
whatever
you
want
in
this
script.
You
have
the
connection
setup
and
and
the
template
provided
it's
a
very
simple
template.
So
you
can
just
add
it
add
a
new
serve
here
and
if
I
go
back
to
public
education,
so
we
just
pass
this
parameter
to
my
to
my
script,
wait
for
job
to
finish
and
then
notify
the
user.
F
We
also
create
some
Microsoft
tips
under
load
and
we
configure
some
channels
just
to
give
you
an
example:
how
to
create
and
configure
my
Christine
inside
Microsoft
team.
So
for
that
Vincent
wrote
a
quick
function
and
as
a
function
as
well
written
in
C
shocks,
so
you
can
have
the
code
right
here
seems
continue
function
and
basically
this
will
create
new
channel
according
to
your
to
your
template
within
a
specific
group
and
the
teams
behind.
Yet
so,
basically,
you
can
adapt
the
logic,
application,
equality
requirements.
F
You
have
the
code,
you
have
all
the
tutorial
here
so
make
sure
you
have
all
the
prerequisites
before
running.
This
is
tutorial
and
it's
very
detailed.
We
we've
made
a
live
presentation
of
this
doing
a
workshop.
It
works,
so
you
can
just
go
through
all
the
steps
and
see
all
the
screenshots
associated
with
all
the
steps,
and
if
your
issues
are
just
reservations
in
the
initial
eats
within
this,
this
repository
and
of.
E
B
G
G
Let's
call
it
this
way,
and
everyone
went
through
the
tutorial
at
the
end
of
the
day
in
one
day,
even
if
you're
not
super
interested
about
provisioning,
it's
a
very
good
way
to
get
exposure
to
dot
that
core
typescript
development
as
your
functions
as
your
logic,
apps,
and
a
lot
of
our
technologies
like
microsoft,
graph
and
PMT,
partial
and
campy
provisioning,
it's
kind
of
a
mash
up
of
a
lot
of
technologies.
You
will
see-
and
it's
very
interesting
for
you
to
ramp
up
on
all
those
different
technologies
at
once.
A
A
So
really
really
awesome
stuff
super
useful.
Like
said,
it
is
an
awesome
exercise
to
learn
how
to
get
started
on
things
and
it's
a
self-service
guidance
or
you
can
actually
even
reuse
that
as
your
workshop,
even
potentially,
but
do
on.
Obviously,
let's
Franken
and
Vincent.
You
know
if
there's
an
issues
and
that's
a
trillion
trillion
trillion
stuff.
Now
you
can
problem,
see
my
slides
just
to
recap.
The
next
shape
on
Def
special
interest
group
call
is
on
February
6th.
A
So
within
two
weeks
and
the
next
shape
and
framework
and
crew
alcohol
is
within
a
week,
we
do
have
already
community
the
most
queued
up
on
these
and
obviously
updates
from
Microsoft
as
we
move
along
on
this
journey
and
introduce
new
things,
stay
up
to
date
on
what
we
do
in
social
media
and
please,
if
there's
any
feedback.
Anything
please
please,
please
let
us
know
how
we
can
improve
our
community
engagement
and
if
something
is
missing,
please
let
us
know.
Learn
we
use
share
sharing
is
caring,
a
chemist,
SP
BMP.
Thank
you.
Thank
you.