►
From YouTube: Microsoft 365 PnP Weekly – Episode 101
Description
In this 1st installment after the 100th installment of the weekly discussion revolving around the latest news and topics on Microsoft 365, hosts – Vesa Juvonen (Microsoft) | @vesajuvonen, Waldek Mastykarz (Microsoft) | @waldekm, are joined by Vincent Biret (Microsoft) | @baywet, MVP alum, blogger, and presently a developer on the Microsoft Graph SDK team. A number of topics were covered – Program Management vs Development at Microsoft, Microsoft Graph investments, how the Community can work with SDK team, and finally “inbox zero.” 15 recently released articles from Microsoft and the PnP Community are highlighted as well. This episode was recorded on Monday, October 19, 2020.
References:
• See the full blog post for this episode at https://aka.ms/M365DevBlog
• Download the podcast for this episode at http://pnpweekly.podbean.com.
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos
A
A
So
bmp
vehicle
is
all
about.
What's
the
latest
within
this
week
across
the
microsoft
365
community
mvp
and
then
typically,
we
have
a
visitor
in
the
show
as
well
before
we
go
there.
My
name
is
spencer
ivan
and
I'm
a
program
manager
in
the
onedrive
sharepoint
engineering
site
and
with
me
as
a
co-host,
is
a
three
weeks
in
microsoft.
Right
now,
person
right.
D
A
Yeah,
it's
it's
been
a
long
ride
anyway,
so
vincent
uber
and
envy
beef
before
you
joined
microsoft.
I
can
see
a
theme
here.
We
used
to
have
another
one
in
this
call
as
well,
who
was
an
mvp
and
then
moving
into
the
microsoft,
and
now
you
pretty
recently
moved
to
a
new
roles.
Can
you
talk
about
quickly?
Who
are
you
running
about
your
background
and
then,
let's
change
that
all
of
that
afterwards.
C
Sure,
a
long
time
ago,
in
a
galaxy
far
far
away,
I
was
a
sharepoint
developer.
I
started
on
full
trust
solutions
in
the
good
old
days
and
as
a
consultant,
obviously,
and
more
and
more
I've
been
blogging
and
involved
with
a
community
and
participating
to
open
source
projects
and
speaking
as
well-
and
this
is
how
I
became
microsoft
vp-
I
guess
six
years
ago
now-
2014
something
like
that
and
and
for
anybody
who's
working
in
the
community
or
contributing
to
open
source.
C
You
should
consider
the
program,
it's
really
good,
to
make
new
connections
to
learn
new
things.
I
would
really
encourage
you
to
check
it
out
and
and
see
if
you
can
be
part
of
a
program
and
after
that,
because
I
was
complaining
so
much
about
things
about
microsoft
graph
I
had
darryl
miller
and
jeremy
fake,
saying
all
right.
You
complained
too
much
come
with
us,
come
fix
it
please,
and
I
eventually
became
a
program
manager
for
microsoft
graph
back
in
january.
Actually,
and
I've
been.
A
B
C
C
A
I'd
say:
that's
a
nice
change
actually,
so
that
was
pretty
pretty
fast
chance.
So
how
did
you
can
you?
Can
you
actually
elaborate
slide?
Let's
go
back
on
the
mvp
discussions
in
a
slightly
later
underscore,
but
what
was
the
main
decision
breaking
thing
for
you
to
move
from
a
pm
role
to
the
developer
role?
Why?
Why
did
this
happen?.
C
C
In
other
companies
you
have
product
owners,
you
have
product
managers,
not
program
managers
right
and
it's
it's
a
bit
different
right
and
I
think
I
first
I
took
for
role
not
fully
understanding
what
it
is
exactly
that's
the
first
thing
and
then,
as
I
learned
for
ropes
and
as
I
discovered
the
role
and
so
on
and
so
forth,
I
discovered
that
yeah.
It
requires
a
few
affinities
or
personal
skills
that
were
not
my
favorite
things.
To
do
things
like
program
management
is
a
lot
about.
C
You
know
influencing
people
and
spending
a
lot
of
time
in
meetings
and-
and
this
is
really
important
right-
if
you
don't
have
a
good
program
manager,
you
are
either
spending
your
time
on
the
wrong
things
or
not
doing
the
things
that
you
should
be
doing
or
not
being
efficient
or
not
coordinated
right.
So
so
so
program
managers
are
really
crucial
to
making
sure
that
something
actually
lands
and
something
happens.
C
B
B
C
Yeah,
so
so
the
way
it's
designed
for
microsoft
graph
is
that
you
have
a
core
of
program
managers
and
developers
that
work
on
platform
features,
for
example,
things
like
changing
notifications
or
change,
tracking
or
programming,
or
oh
data
support,
and
so
on
and
so
forth.
Right
and
then
they
have
to
go
and
convince
the
different
product
teams
like
outlook,
onedrive
and
so
on.
C
A
Yeah
yeah-
and
I
think
especially
now
within
the
cloud-
let's
say:
infrastructure
and
microsoft
365
right
now,
if
you
have
a
look
on
how
we're
focusing
is
that
every
single
feature
we're
trying
to
avoid
that
it
has
a
competiting
feature
exactly
the
same
competitive
feature
across
the
stack.
So
there's
one
taxonomy
service,
there's
a
one,
a
portal
service,
there's
a
one,
let's
say
channel
service
or
whatever.
A
But
basically,
then
that's
getting
integrated
across
multiple
teams,
so
it
in
the
past
as
a
feature
pm,
for
example,
in
sharepoint
from
a
house
where
I'm
from
you
were
able
to
just
focus
on
on
a
one
particular,
let's
say
a
set
of
people
and
communicating
with
them.
But
now
it's
across
the
organization
across
themes,
because
you
want
to
make
sure
that
your
feature
is
getting
used
in
an
efficient
way.
But
but
for
sure
craft
is
probably
the
most
let's
say,
communicated
almost
most.
Let's
say
one
of
the
hardest
things
to
manage,
because
there's.
B
Why?
Because
that
means
efficiency,
because,
instead
of
out
of
team
teams
trying
to
teams
team,
try
to
build
storage,
compliancy
and
all
of
all
the
things
by
themselves
from
scratch?
Well,
they
can
use
something
that
is
already
there
right
yep.
So
it's
on
one
hand,
efficiency,
but
then
sync
loop,
where
you
need
to
talk
to
each
other.
There
is
some
some
other
group
with
their
life
cycle,
their
work
and
you
you
need
to
align
for
both
things
to
actually
work
together.
So.
A
And
then
there's
a
if
you
think
about:
let's
go
back
on
the
actually,
let's
talk
about
slightly
the
pm
role
and
then
then,
because
we
touched
it
a
few
times,
but
in
general,
if
you
think
about
the
pm
role
in
microsoft,
it's
it's
the
person,
who's
responsible
of
creating
specs
and
owning
the
feature,
so
it's
kind
of
the
owning
owning
of
the
solution,
so
kind
of
defining
what
should
be
done
now,
depending
on
organization.
That
might
mean
functionality
or
it
might
actually
mean
the
technical
way
of
implementing
things.
A
C
Yeah,
of
course,
I
mean,
in
microsoft,
graphic
ibm
today
you're
working
on
an
api
right,
so
you
have
to
have
a
strong
development
experience
and
design
architecture,
design,
skills
and
so
on
and
so
forth
and
get
deep
dive
in
the
in
the
designs
of
otherwise
it's
just
not
specific
enough
for
the
teams
to
implement
something.
Basically,.
A
Then,
as
in
the
pm
role,
you
need
to
also
be
in
touch
with
the
customers
and
partners
and
communities.
So
you
need
to
understand
what
actually
is
the
requested
capabilities?
You
need
to
be
able
to
communicate
those
with
your
management
chain
and
in
the
priority
chain.
So
people
actually
can
then
stack
rank
your
feature,
and
so
do
you
actually
get
the
developers.
D
A
B
A
And
then,
as
a
pm,
you're
also
responsible
of
whenever
the
feature
is
ready,
you're,
ultimately
responsible
that
it
actually
matches
what
were
you
speaking
so
making
sure
that
it's
actually
matching
the
capabilities
and
features
and
then
communicating
that
to
the
partners.
So
sure
there
are
technical
writers
who
are
then
specialized
on
the
language
and
all
of
that.
But
you
need
to
explain
for
the
technical
writers,
whatever
you
actually
created,
and
why
does
it
exist?
And
why
is
it
the
coolest
thing
ever
and
then
they
share
that.
B
C
What's
the
right
time
to
make
sure
that
the
feature
or
the
feature
set
lens
right
and
as
as
visa
said,
you
have
this
period
of
negotiation
with
different
teams
to
say
I
need
resources
for
that
to
happen,
and
sometimes
you
don't
get
your
resources.
So
sometimes
you
need
to
bridge
the
gap
a
little
bit.
C
Of
course,
you're
not
gonna
do
as
much
as
a
good
job
as
the
dedicated
team
would
have
done
at
this
point,
but
at
least
it
would
allow
your
feature
to
see
the
day
of
light,
the
light
of
day
and
and
then
right
so
so.
This
is
why
you
kind
of
end
up
doing
a
lot
of
different
things
at
the
same
time,
because
if
something
is
not
coordinated
on
time
or
if
something
is
not
available
for
you
well
you're,
ultimately
the
one
who
it
falls
on
so
yeah.
A
A
You
need
to
still
ship
but
still
kind
of
define
the
role
and
decide
the
development
cycles
and
all
of
that
in
the
way
you
want
them
to
be
so
so
as
an
example,
I
still
remember
with
mikhail
svensson
when
he
moved
into
the
microsoft
search
organization,
because
the
name
of
xmbp
as
well,
he
was
kind
of
amazed
on
hey,
so
nobody's
telling
me
what
I
was
supposed
to
do.
I'm
able
to
define.
A
B
But
I
guess,
but
I
guess
even
there
right,
like
the
depending
how
how
you
join
the
level
where
you
come
you're
joining
new
org,
new
job,
which
you
might
or
might
not
know
right
and
then,
depending
on
that,
like
you
might
be
able
to
do
the
work
by
yourself
already
or
maybe
you
need
some
guidance
saying,
okay,
so
we're
going
this
direction,
and
this
is
how
we
approach
things
so
the
first
reasonable
step
to
towards
that
is
to
do
this.
You
know
it's
like
yeah.
B
C
I
was
responsible
for
three
to
four
features
in
microsoft
graph
and
at
the
end
of
the
day,
but
there
are
some
principal
program
managers,
so
two
levels
above
me
who
had
almost
a
dozen
different
features
and
to
me
this
is
impressive,
because
I
don't
know
how
they
can
coordinate
so
many
things
right
because,
as
you
have
12
features,
you
have
12
times
as
much
on
connection
points,
yeah
emails
and
meetings
and
stuff.
So
I
don't
know
how
they
do
that
to
me,
though,
that's
a
still
big
question
mark,
but.
A
But
that
that's
actually
a
good
way
how
you
defined
it
that
it's,
it's
being
a
pm.
One
of
the
things
which
I
I
well
one
of
the
coming
back
on
my
history
about
things.
So
I
left
my
previous
company
and
moved
to
microsoft,
because
I
ended
up
being
the
guy
who's
getting
connected
on
everything.
So
whenever
there
was
a
question
related
on
the
platform
I
got
tracked
in
and.
B
A
Thank
you,
but
basically,
which
is
precisely
where
I
was
having
heading,
because
I
I
wanted
to
go
to
microsoft,
which
is
such
a
large
company
that
you
can
never
be
on
the
centralized
position,
but
then
being
a
pm
in
a
certain
level.
You
actually
ended
up
being
the
central
point
of
connection,
because
that
is
actually
your
job
and
one
of
the
challenges
of
being
a
pm
is
that
you
need
to
able
to
manage
also
the
fact
that
you
cannot
communicate
or
cannot
even
response
to
all
of
the
people
who
are
reaching
to
you.
A
So
you
need
to
be
able
to
manage
that
prioritization
and
I
think
we're
going
to
talk
about
the
inbox
zero
in
a
few
different
perspectives
later
on.
This
call,
because
I
think
that
relates
on
that.
So,
if,
if
you
are
a
bm
owning
multiple
features
or
a
large
massive
feature
set,
there's
just
no
way
to
get
to
the
inbox
zero
as
an
example,
it's
just
impossible,
and
then
you
need
to
learn
not
to
feel
bad
about.
The
fact
that
you
haven't
had
a
chance
to
respond
which
is
actually
really
hard
and
well.
A
It
depends
on
how
empathetic
you
actually
are
for
the
other
people,
because
basically
there's
people
asking
help
and
you're
like
well
I'd
love
to
help,
but
I
just
can't
so
it's
it's
an
interesting
challenge,
but
now
coming
back
on
your
current
role,
vincent.
So
how
is
it
then
different
for
a
developer
and
engineer
in
microsoft?
So
how
would
you
define
that
sorry,
baldeck?
If
you
had
a
comment
on
there.
C
No,
no,
it's
perfectly
good,
so
the
so
so
an
engineering
role
is
where
you,
your
responsibility,
is
ultimately
to
build.
Oh
well
figure
out
the
solution,
build
test
ship
and
keep
a
live
service
if
you're
a
developer
on
a
service
site
right.
I
work
on
sdks,
so
we
don't
maintain
a
service,
but
but
a
lot
of
in
the
cloud
area
era.
A
lot
of
people
are
building
services
at
the
end
of
the
day.
Right
and-
and
one
thing
I
like
about
that-
is
that
you
get
some
sense
of
ownership.
C
You
get
to
feel
accomplished
about
having
you
know,
built
something
and
shipped
something,
and
you
also
get
to
focus
on
something.
When
my
pm,
who
until
recently
was
daryl
miller,
told
me
hey
vincent,
I
need
you
to
figure
out
why
this
is
broken
in
the
java
sdk
and
how
we
can
fix
it
and
fix
it
and
and
so
on.
Well,
I
just
say
all
right.
Thank
you,
mr
pm.
I'll
go.
Take
this
and
I'll
go
fix
it
right
in
a
month
that
you
can't
do
because
at
some
point
there
is
back.
C
Partners
or
so
yeah,
you
also
need
you
still
like
it's
not
a
completely
ivory
tower
kind
of
role,
an
engineering
role
right.
You
still
need
to
communicate
with
your
peers
with
your
management
with
the
program
managers
to
make
sure
that
we're
all
advancing
in
sync
and
if
there's
any
issues
we
tackle
them
together
and
not
not
individually.
C
A
C
Personal
aspect
right
so
if
your
personality
makes
makes
it
so
that
you,
like
you,
know
influencing
people
talking
to
a
lot
of
people
being
more
on
the
communication
aspect,
go
for
a
camera.
It's
amazing!
You
can
have
a
really
broad
impact
on
on
on
on
the
organizations
and
on
the
planet
right.
It's
just
that
make
sure
you
know
yourself,
and
you
know
about
the
role
before
you
do
that,
because
otherwise.
B
Yeah,
I
think
I
think,
for
a
big
part
that,
like
be
being
effective
in
this
role,
means
that
you
have
to
be
able
to
organize
your
your
yourself
well,
and
then
you
have
to
have
these
enterpreneurial
spirit
of
I
want
to.
I
want
to
take
this
thing
and
to
take
it
from
from
an
idea
all
the
way
to
fruition,
and
that
means
basically
lobbying
for
interest
resources
coming
from
an
idea,
bouncing
it
off
others
and
basically
doing
all
this
work.
B
A
Yeah,
that's
that
is
actually
one
of
the
interesting
things
which
is
probably
not
that
visible.
Also
outside
of
the
engineering
in
microsoft
is
that
there's
there's
actually
quite
a
lot
of
the
start
up
mentality
in
these
teams
and
so
the
the
team's
stuff.
It's
it's.
You
are
part
of
a
bigger
company,
but
basically
the
team
itself,
which
is
building
stuff,
is
always
responsible
of
kind
of
making
that
startup
to
fly
and
then
recruit
the
right
people
in
get
the
right
people
and
then
build
the
stuff
and
then
you're.
Always
you
never
have
enough
resources.
B
B
D
B
In
software
I
mean
imagine
that
at
microsoft,
size
like
the
teams
team
would
like
to
build
something
and
they
need
to
align
with
100
000.
Other
people,
like
you,
wouldn't
do
anything
yeah.
So
it's
it's
in
a
way.
I
think
really.
The
only
way
to
do
something
is
to
make
teams
independent
in
a
way
and
give
them
the
free
choice,
say:
okay,
as
microsoft,
we
we
have
a
vision
mission.
B
C
Yeah,
you
don't
to
figure
out
everything
right.
There
are
some
pieces
that
you
can
reuse
and
actually
our
bonus
structure
is
very
well
organized
in
a
way
that
you
are
reusing
people's
stuff
instead
of
reinventing
the
wheel
all
the
time
right.
So
so
I
guess
that's
one
of
the
main
advantages
of
of
driving
a
product
at
microsoft
versus
doing
it
at
a
smaller
company
right.
So.
B
Well-
and
I
mean
you
can
always
say:
hey,
I
have
a
colleague
who
knows
whatever
it
is,
and
this
is
right
because,
like
there
is
a
chance
that
somebody
in
microsoft
somewhere
knows
about
whatever
it
is
that
you
need
whether
you
need
yaml
or
iot
or
devops,
or
security
or
operating
system
low-level
things
or
android
or
company,
is
so
big
like
that.
There
must
be
someone
somewhere
right,
so
the
only
thing
is
like:
can
you
get
to
that
person
on
time?
Yeah.
A
B
Don't
like
to
be
honest,
I've
never
really
experienced
one
being
prerequisite
for
the
other
so
like
for
me.
I
worked
remotely
for
four
and
a
half
years,
almost
five.
Now
so
for
me,
it's
just
like
realities
of
life.
Yeah,
like
you,
don't
always
get
to
meet
each
other
in
person,
and
I
don't
see
that
as
prerequisite
sure
it
it
takes.
B
It
takes
time
to
build
a
relationship
with
someone
else,
but
I
don't
see
the
in-person
aspect
being
key
factor
in
that
like
if
you,
if
you
put
in
the
effort-
and
you
have
even
calls
right
now
like
that
for
me-
is
also
like
kind
of
current
times
equivalent
of
doing
things
in
person
as
opposed
to
asynchronously
on.
I
am
yeah
right.
C
So
yeah:
well,
I
guess
we're
all
working
remotely
for
numbers
of
years,
so
there
is
nobody
to
conquer
arguments,
but
yeah
going
by
right.
I
completely
agree
and
even
like
the
office
culture
is,
can
only
scale
so
much
like
if
you
for
like.
If
you
look
at
like
if
anybody
listening
who
hasn't
been
to
a
microsoft
campus
in
redmond,
I
encourage
you
to
go
just
on
bing
maps.
Let's
call
it
and
just
zoom
from
a
satellite
view.
C
There
are
hundreds
of
buildings,
multiple
cities,
so
it's
more
likely,
especially
if
you
work
on
microsoft,
graph
that
even
if
you're
in
the
office
in
the
building
physically
you'll
be
talking
about
with
people
across
the
whole
campus
right.
So
so,
at
the
end
of
the
day
you
you
need
to
be
able
to
build
relationships
remotely
and
so
on,
and-
and
I
guess
the
only
big
difference
it
makes
is
after
work,
where,
if
you
work
in
an
office,
you
know
you
can
go,
grab
a
drink
with
your
colleagues
and
so
on
and
so
forth.
C
B
Right,
there's
also
an
interesting
thing
that
I
experienced
the
other
day
right
so,
especially
in
my
team,
like
my
team
is
distributed
across
the
world.
So
for
me
the
only
time
really
where
the
work
stops
is
weekend
yeah,
because
we
have
team
in
us
or
or
I
have
I.
I
have
two
colleagues
in
australia
so
when
they,
when
their
day
finishes
my
starts
and
then
when
my
date
is
finished,
then
the
u.s
starts
and
then
by
the
time
u.s
is
done.
Australia
starts
yeah,
so
it's
like.
B
D
C
B
A
Yeah,
but
I
I
don't
see
myself
actually
in
the
traffic
jams
in
commutes
waiting
for
tribe
this
summer
would
suck
why?
Because
all
of
this,
this
possibilities
are
now
available
and
now
lucky
kind
of
we
do
the
2020
situation.
We
are
forced
to
learn
to
actually
use
this
tooling
efficiently,
which
is
great
because
it
enables
them
people
to
work
remotely
and
and
maybe
have
a
better
and
maybe
healthier
work-life
balance.
Who
knows
in
in
our
case
as
well.
A
We
have
a
development
center
in
china
in
india,
I'm
in
finland
and
then
redmond
it's
like
and
you
I
have
my
sleeping
times
in
the
in
the
calendar.
So
people
know
that
I'm
not
gonna
take
times
for
those,
so
I
have
family
time
also
mark
on
calendar
just
in
case,
so
it's
just
the
easiest
way
to
deal
with
the
with
the
different
time
zones.
So
I
just
gotta
test
this
lamp
recently.
Yesterday
there
was
an
invite
for
midnight
on
friday
heading
to
saturday.
It's
like
yeah.
No
thank
you.
Oh.
A
Articles
and
let's
get
back
on
the
on
the
discussion
after
that
for
a
few
minutes.
So,
let's
and
and
we
have
a
good
discussion
related
on
I'm
waiting
for
the
discussion
related
on
inbox
zero
on
here,
but
let's,
let's
start
with
a
few
blog
posts
and
the
new
ones
from
microsoft.
So
this
one's
the
only
new
one
in
microsoft
teams
block
so
they
say
h
a
I
h.
I.
D
A
Never
mind
so
a
partner
story
related
on
high
five
employee
app,
which
integrates
now
the
microsoft
teams,
so
a
nice
way
of
showing
how
it
integrates-
and
the
key
point
here
again
is
the
application.
You
don't
need
to
go
to
another
location.
The
application
will
be
exposed
in
the
same
location
where
you
are
working.
So
that's
that's.
Actually
the
advantage
of
doing
this
and
integration
options
are
really
easy,
so
you
can
easily
do
this.
A
So
within
a
week
from
now,
depending
on
when
you're
watching
the
video,
it
might
be
that
you
missed
it
now
or
listening
the
podcast.
You
never
know,
and
this
one
is
a
from
the
microsoft
365
developer
blog.
So
a
new
announcement
related
on
general
availability
of
microsoft,
craft
teams,
membership
api,
so
basically
getting
access
on
the
members
in
the
groups
and
and
access
on
there.
So
pretty
cool,
just
a
note,
maybe
for
the
future.
Maybe
we
should
have
actually
talked
about
the
scenarios
and
features
and
why
this
is
important.
C
When
bridge
of
a
gap
provisioning
provisioning
provisioning,
I
don't
know
if
you've
been
working
on
provisioning
solutions,
but
when
you
create
different
aspects
or
different
artifacts
across
microsoft,
365
thanks
to
microsoft,
graph
in
our
awesome
sdks.
If
the
service
takes
time
to
replicate
changes,
it
can
be
really
painful
to
design
your
solution
in
a
way
that
it
has
to
wait
and
check
again
and
come
back.
C
Maybe
when
it's
ready
and-
and
so
these
these
endpoints
are
here
to
all
of
you
that,
where,
when
you
provision
a
team
and
it's
ready
to
to
be
used
instead
of
waiting
from
the
sync
between
azure,
active
directory
and
teams,
to
happens,
but
sometimes
can
be
a
bit
slow,
you
can
talk
right
away
to
microsoft.
Teams
and
they'll
do
a
replication
for
you
and
it
should
be.
It
should
be
much
much
faster,
so
yeah
awesome.
C
B
B
A
Yeah
cool
now
this
one
is
the
the
vincent,
your
blog
post,
related
on
your
personal
experiences
as
a
program
manager
and
switching
back
to
the
development.
I
think
we
touched
pretty
much
all
of
the
topics
in
here,
but
it's
a
good
reading,
written
story
related
on
what
does
a
program
manager
do
and
what
does
the
developer
do
and
who
do
program,
managers
work
with.
A
Absolutely
absolutely
thanks
for
that
one.
These
are
really
good,
because
it's
it's
the
sharing
the
personal
experiences
related
on
roles.
They're
super
super
important,
and
I
can
imagine
that
this
has
a
lot
of
looks
and
a
lot
of
views
so
cute,
and
this
one
is
from
hugo
popular
pmp
repositories,
meaning
much
to
365
community
repositories
and
how
to
get
started
on
contributing
so
all
of
the
different
repos
which
are
available.
A
C
So
that
means
that
next
time
the
microsoft
graph
schema
is
gonna,
be
updated.
We're
gonna
kick
a
new
generation
process
and
it's
gonna
increase
any
manual
changes
that
you
might
have
made.
So
we
want
to
make
sure
that
there
are
clear
boundaries
and
it's
easier.
You
know
there
are
not
thousands
of
classes
and
so
on
and
so
forth.
So
it
makes
it
much
easier
for
the
community
to
navigate
and
contribute
and
to
to
to
the
usd
case
by
separating
the
boundary.
Basically.
A
C
One
suggestion
for
all
of
our
it
pros
bloggers
out
there
if
you're,
writing,
partial
or
bash
or
any
kind
of
shell
experience
here,
put
your
script
on
gist.github.com
and
this
way
you'll
be
able
to
embed
the
script
and
you'll
get
syntax
coloration
highlighting
automatically
right.
So
it
makes
it
easier
for
people
to
read
it,
and
if
people
want
to
copy
your
script,
they
just
need
to
download
the
file
where
it's
hosted.
It
makes
things
much
easier
than
just
you
know.
Scripting
and
plain
text
like
that.
B
A
D
A
But
yeah
good
point
absolutely
now.
Moving
on
on
the
on
the
articles,
this
one
is
from
elio.
What
is
the
right
approach
to
cache
data
in
your
solution?
So
talk
about
the
different
caching
options,
so
the
suggestion
stories
and
local
storage
and
and
what
are
the
limitations
related
on
on
those
things
as
well,
so
good,
good,
good,
blog,
post
elio
is
the
technical
lead
of
the
vallo
internet.
So
he
makes
these
decisions
in
develop.
So
a
lot
of
experiences
around
these
topics
as
well.
B
Yeah,
and
also
like,
like
first
things,
first,
why
would
you
cache?
Well,
you
want
to
because
otherwise
there
is
the
latency.
There
is
the
services
that
you
are
calling
over
and
over
again
trying
to
get
the
same
data,
so
it's
just
way
more
efficient
and
faster.
If
you
have
the
data
once
and
it
didn't
change
well,
then
there
is
no
need
for
you
to.
A
Say
a
simple
example
of
a
caching,
a
super
old
scenario,
but
I'll
still
remember
this,
because
we
it
took
a
while
for
us
to
figure
out
what
was
wrong.
We
were
building
a
global
intranet
for
30
000
employees,
and
then
there
was
a
web
part
which
was
showing
a
survey,
and
this
was
way
behind
like
like
years
and
years
in
a
farm
solution
doesn't
matter,
but
the
web
part
was
showing
a
survey
and
then
it
was
supposed
to
show
the
survey
results.
A
If
the
person
has
already
responded
on
that
and
the
survey
response
survey
results
were
basically
the
results.
We
wanted
them
to
get
refreshed
automatically.
So
whenever
somebody
else
is
replying
on
the
survey
and
because
it's
a
front
page
of
the
portal,
we
want
that
to
be
reflected
on
the
on
the
facebook.
D
A
C
B
B
B
A
A
A
D
A
Anyway,
horror
stories
from
the
past
now
this
one
from
the
from
stefan
how
to
identify
the
fonts
rendered
in
your
process,
a
good
story
actually
related
on,
what's
getting
rendered
and
where
and
and
how
things
are
getting
rendered
in
the
in
the
browsers
as
well,
and
also
how
sharepoint,
as
an
example,
handles
all
of
this,
the
the
fonts
so
and
it
actually.
I
think
this
one
is
the
one
where
he's
calling
out
a
slightly
more
different
differences
between
the
different
tooling
as
well.
A
B
Sure
so
so
oftentimes
when
we
talk
to
developers
or
isvs,
we
kind
of
assume
that
they
know
they
know
about
like.
Why
would
you
build
things
on
m365?
They
they
are,
they
are
already
sold
and
they
are
looking
just
for
okay,
so
how?
But
that
is
like
that
assumption,
isn't
always
right
right.
So
at
times
we
end
up
talking
about
technologies
and
sdks
and
apis
and
whatnot
and
they're
like
yeah.
Well,
why
would
I
do
it?
Why
would
I
be
interested?
What
is
incentive
for
me
to
build
apps
on
that?
B
Why
would
I
would
I
integrate
so
with
that
article?
I
aim
to
explain
like
the
first
steps.
Why
would
you
be
interested
in
that?
What
is
the
benefit
and
then
once
you
think,
like
hey,
that
sounds
interesting.
I
want
to
give
it
a
try.
Well
then,
there
are
the
next
steps
for
sign
up
for
the
dev
program,
try
graph
and
other
things,
but
that
comes
afterwards.
Only
after
you
understood.
A
A
So
and
I
think
in
general,
we
need
to
do
a
better
job
on
explaining
this
exact
story,
so
the
opportunity
around
the
microsoft
365
platform.
This
is
coming
up
in
in
so
many
discussions
with
partners,
and
they
don't
quite
understand
the
opportunity
and
and
what
you
can
do
with
it.
With
the
platform.
Azure
is
much
more,
let's
say,
mature
from
a
messaging
perspective
and
it's
more
clear.
It's
set
of
tools.
B
And
different
kinds
of
rules
exactly
yeah,
it
is
the
building
blocks
in
which
you
integrate,
whereas
here,
whereas
like
there's,
this
huge
data
set
into
which
you
can
tap,
and
that
is
the
value
and
you
can
extend
that
and
you
can
use
it
in
your
own
app.
So
there's
like
20
million
things
that
are
that
you
can
include
in
your
app
and
enrich
your
your
apps
with
other
than
the
raw
building
blocks
like
this
is
where
you
store
the
data.
This
is
your
serverless
here
you
build
an.
D
B
D
A
D
A
Yeah
so,
but
this
is
actually
interesting,
we
did
some
experiments
already
at
that
time,
but
thank
you
for
and
spending
the
time
of
writing
the
actual
story
related
on
the
me
experience
in
microsoft
teams-
and
this
is
basically
under
the
sharepoint
framework
or
built
for
microsoft
teams
and
explaining
how
different
aspects
and
scenarios
and
how
you
built
your
personal
dashboard,
either
using
modern
pages
or
then
creating
a
web
part
or
a
personal
application
to
surface
that
stuff
in
a
multiple
different
ways.
There's
this
different
advantages
and
disadvantages
in
both.
A
B
D
B
So
like
over
the
last
I
think
year
and
a
half
or
so
like
I've
been
in
different
job.
When
I
was,
I
worked
on
a
product
and
as
typically
that's
the
case,
you
have
more
ideas
and
hours
in
a
day.
So
you
end
up
creating
this.
These
to-do
lists
that
fewer
items
go
off.
Then
you
put
on
because
there's
another
idea.
B
B
So
as
so
with
that,
I
I
aim
not
really
the
thing
that,
like
whether
you
keep
everything
in
your
inbox
or
or
move
it
to
archive,
but
but
rather
like
trying
to
be
in
this
race
to
get
everything
done
like,
because
that
is
like.
I
found
out
the
hard
way
that
that
is
really
a
trap,
because
you
will
end
up
working
and
working
and
there's
like
no
matter
how
many
hours
you
put
in
you
will
never
really
be
done,
because
there
will
always
be
more
it
never
in
products.
It
never
stops.
C
I
agree
with
most
of
that.
I
think
I
think
the
the
angle
of
the
inbox,
zero
thinking
is
not
to
give
you
more
work,
though,
to
do
you
know
all
the
work
that
is
possible
but
more
to
to
make
it
so
your
setup
in
a
way
that
you
have
only
the
important
work
coming
and
and
getting
your
attention
and
you
don't
have
a
cognitive
load
anymore
of
things
that
are
not
important
and
and
to
destroy
that
example.
C
I'll
say
that,
for
example,
if
we
take
emails,
I
don't
think
the
goal
is
to
read
every
single
2000
email
that
you
get
every
day
but
more
to
make
it.
So
you
unsubscribe
to
a
few
things
or
you
set
up
automatic
rules
that
if
you
see
a
pattern
of
things
that
doesn't
call
for
action,
doesn't
give
you
an
interesting
information.
You
should
not
be
on
that
email
to
begin
with,
because
of
distribution
list
or
something
like
that.
C
It
depends
on
perspective.
Okay.
By
doing
that,
you
make
sure
that
your
tools
to
track
work
do
not
get
out
of
control,
because
that,
like
having
a
bucket
list
or
a
list
of
things
to
get
done,
that
is
getting
out
of
control,
generates
tremendous
stress
and
also
you
lose
your
ability
to
get
some
context.
Awareness
knowing
that
hey.
That
is
a
priority.
I
need
to
get
attention
and
focus
on
that,
and
that
is
not
a
priority.
C
A
But
then
is
it
an
inbox
zero
or
is
it
something
else
what
works
it
doesn't
actually
matter?
This
is
highly
subjective,
different
methods,
work
for
different
people,
there's
no
absolute
reason.
No.
So
in
my
case
as
an
example,
I
don't
use
inbox
zero,
but
I
have
a
me
folder.
So
whenever
somebody
sends
an
email
where
I'm
actually
in
the
tool
list,
it
lands
on
my
me
folder,
which
is
the
only
folder
where
I
actually
work
and
because,
if
I'm
cc'd
it's
a
carbon
copy,
so
I
don't
need
to
worry
about
that
one.
A
A
B
D
A
That
is
a
brilliant
idea.
I
I
think
that
would
help
on
on
a
lot
of
the
companies
to
reduce
the
the
information
overload,
so
we
yeah.
So
if
somebody
is
listening,
it's
like
hey.
I
need
to
build
that.
Please
do
and
then
and
then
make
a
chilling
out
of
money
of
that.
So
that
is
a
really
good
idea,
so
I'm
pretty
sure
that
in
the
current
world
the
chaotic
world
that
would
be
easily
people
would
actually
adapt
that.
So
that's
that's
actually
great.
B
A
How
that
or
maybe
there
is
already
an
application
with
suspects
which
we're
just
not
aware
of
that
anyway,
and
this
one
is
from
ac
and
through
connell.
How
does
the
sharepoint
framework
work?
We
talked
about
some
of
these
series
articles
already
last
time,
but
I
think
now
the
series
is
full
so
really
having
that.
What
is
the
sharepoint
framework,
what
you
can
build
with
that?
A
Now
this
one
is
from
angness
how
to
deploy
bmp,
modern
search
web
parts
so
really
explaining
where
you
can
get
the
bmp
modern
search
webparts,
which
enables
you
to
build
modern,
sharepoint
experiences,
and
so
this
is
say
a
something.
What
frank
cornell,
mikhail
spencer
and
a
few
other
people
have
been
building
in
the
past
years,
so
really
cool,
stuff
and
angus
is
basically
just
walking
by
step
on
how
to
get
started.
A
And
how
do
you
build
that
experience
so
really
cool,
really
really
cool
and
actually
start
by
creating
the
app
catalog
which
is
required
for
the
solution
to
get
targeted?
We
are
by
the
way
in
progress
of
figuring
out.
How
do
we
pre-provision
at
catalog,
because
we
need
to
so
yeah
making
that
available
for
everybody,
but
that's
a
long
side
discussion,
there's
different
aspects
on
that
that
one
sharepoint
syntax
first
steps
with
intelligent
content
type
and
compliance
from
john
klein,
so
really
cool
stuff
as
well.
A
Walking
through
the
the
scenarios
and
what's
really
cool
about
this
index
content
center
is
that
you
can
actually
create
this
example.
Content
example
structures,
so
you
can
actually
create
this
and
you
can
generate
that
with
an
example
content
and
then
that
will
show
you
how
you
can
detect,
for
example,
the
invoice
related
information
and
do
calculations
and
teach
and
the
syntax
and
then
the
automated
stuff,
so
really
really
cool
stuff.
So
and
then
the
last
from
robert
crane
custom
praised
batches
in
microsoft
teams.
A
So
how
can
you
actually
go
to
the
microsoft
team
and
and
then
in
the
praise
application
settings
you
can
actually
modify
the
different
settings
and
different
batches.
If
you
don't
like
the
out-of-the-box
ones
or
the
default
ones
which
are
available,
you
can
introduce
your
own
with
the
known
images
and
all
that
and
then
you
can
keep
those
price
patches
for
people
really
cool
cute.
That's
the
articles
so
inbox
zero.
Today,
totally
everything.
B
B
C
Lots
of
rooms,
for
example,
we
have
this
notion
of
handlers
in
the
sdk
in
the
core
part
of
the
sdk
and
and
both
handlers
will
handle
things
like
throttling,
for
example,
how
long
should
I
wait
before
I
retry,
or
they
handle
things
like
compression
or
they
handle
other
things
right?
That
are
more
cross-cutting
concerns
right
and
as
much
as
we
have
ideas,
we
might
not
think
about
everything
or
as
much
as
we
have
time.
C
We
also
have
in
the.net
contribute
sdk.
We
have
a
lot
of
helper
methods.
For
example,
you
might
know
that
microsoft
graph
returns
states
with
a
time
zone.
So
there's
this
kind
of
date
time
zone
offset
object.
I
don't
I
never
remember
the
name
of
that
and
and
and
in.net.
We
have
a
lot
of
helper
methods
that
help
you
go
from
that
to
native
daytime
offset
objects
and
so
on
and
so
forth
right,
and
there
is
not
necessarily
the
equivalent
of
that
in
the
other
language.
C
C
C
It
is
already
helping
us
a
lot
as
well,
I'm
thinking
about,
for
example,
the
microsoft
graph
cli
or
the
python
sdk
that
are
very
early
in
their
on
their
days
today,
but
that
should
mature
to
become
really
production,
ready,
basically
right,
so
because
again
that
we
as
developers
have
favorite
languages
and
biases
towards
those
favorite
languages.
So
my
kind
of
thing
in
I
don't
know
python.
For
example,
that
is
a
bit
too
much
dotnet
or
javascript
e,
and
that
doesn't
make
a
lot
of
sense
for
the
python
community,
for
example,
yeah
yeah.
C
C
D
C
C
That
well
go
convince
the
java
devs
to
put
backwards
compatibility
but
yeah,
but
yeah
in
javascript.
You
do
that
you
can
do
that
through
prototype
or
through
type
extension,
with
a
typescript
for
example,
and
so
on
and
so
forth.
There
are
a
number
of
ways
to
also
inject
code
in
the
code
gen
part
without
touching
the
code
chain
files.
A
C
C
So
the
azure
team
came
up
with
this
new
library
which
uses
themselves
under
the
covers
for
most
of
what
we're
they're
doing,
to
standardize
the
way
you
configure
and
use
the
the
authentication
for
through
the
microsoft
identity
platform
or
azure,
and-
and
we
historically
had
those
kind
of
glue,
libraries
of
usd
canning
dash
off
or
something
like
that
to
help
us
glue
between
amsoil
and
our
sdks.
And
then
we
felt
yeah
well
wait
a
minute.
C
Why
are
we
doing
those
glue
libraries
when
azure
already
did
it,
and
it
would
make
much
more
sense
for
the
developers
to
have
one
experience
for
application
and
authorization
and
with
regardless,
where
using
I
don't
know,
azure
about
storage
or
azure,
key
vault
or
microsoft
graph.
It
should
always
be
the
same
code
in
the
same
story.
So
that's
that's
one
thing
where
we're
spending
a
bit
of
time
on
lately
to
make
sure
that
you
have
as
developers
as
consumers
a
consistent
authentication
and
authorization
experience.
A
B
C
Well,
we
can
go
on
the
different
depending
on
the
language,
your
favorite
language.
You
can
go
on
the
different
javascript
or
dotnet,
or
java,
repos
and
so
on
and
so
forth.
The
all
of
that
is
pretty
much
still
work
in
progress
at
this
point,
I
think
maybe
the
dot
that
one
has
something
already
to
use,
but
I'm
not
sure
I
would
have
to
double
check
on
that
again.
We
will
be
reaching
out
to
the
community
and
to
you
guys,
so
you
can
spread
the
message.
Official
viewers.
C
A
C
A
Exactly
it's
one
day,
it's
monday.
Thank
you
vincent
for
this
one
really
good,
really
good
discussion
and
it's
good
to
have
that
discussion
related
on
understand,
sharing,
more
understanding
of
the
differences
between
the
roles
and
how
things
work,
because
I
think
that's
always
super
beneficial
for
people
to
understand
also
externally.
So,
if
somebody
wants
to
go
to
a
microsoft,
that's
at
the
end.
They
understand
what
is
expected
and
as
a
developer,
but
I
think
that's
it
for
this
one.
So
while
they
can
last
for
its
from
your
site,
you
can
close
it
today
thanks.