►
Description
In this installment of the weekly discussion revolving around the latest news and topics on Microsoft 365, hosts – Vesa Juvonen (Microsoft) | @vesajuvonen and Waldek Mastykarz (Microsoft) | @waldekm, are joined by Montréal based Sr Product Manager on the Microsoft Graph team Sébastien Levert | @sebastienlevert. The discussion covered the importance of delivering a great developer experience, using data and personal conversations to substantiate development decisions, the most rewarding part of Seb’s job and tips to prospective product managers. Microsoft and PnP Community delivered 17 articles/videos (many Build related) in the last week! This session was recorded on Monday, May 30, 2022.
References
• See the full blog post for this episode in the Microsoft 365 Platform Community blog at https://aka.ms/m365pnp/blog
• Download the podcast for this episode at http://pnpweekly.podbean.com.
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - http://aka.ms/m365/community
A
A
Summer
is
coming.
This
is
so
good
today,
we'll
we'll
meet
with
sep
sebastian,
livert
or
seb
who's,
actually
leading
the
work
related
on
microsoft,
craft
toolkit,
so
the
controls
which
are
natively
connected
to
microsoft,
craft
and
what
else
are
we
going
to
talk
about
today?
The
latest
on
microsoft,
build.
B
Also
sap
also
leads
microsoft,
js
sdk,
so
it
will
be
interesting
to
hear
to
hear
about
what
happened
the
last
few
months,
where
we
are
where
we're
going
and
so
forth
and
so
on,
and
we
haven't
really
talked
to
him
since
he
went
to
this
role.
So
it
will
be
interesting
to
hear
from
him
how
he
experienced
moving
in
this
or
becoming
pm
in
in
graph,
and
only
two
products.
Yep.
A
And
on
top
of
that
he
just
got
a
baby
and
so
he's
been
away
for
a
while,
but
now
coming
back
and
being
been
working
for
a
while.
So
it's
actually
good
to
hear
about
that
one
as
well,
so
balancing
out
the
family
and
work
right,
new
new
new,
yes,
no,
no!
No!
No!
No!
So
in
the
bmp
week
they
always
talk
about
the
latest.
On
microsoft,
365.
we
have
a
visitor.
Like
said
this
week.
Is
sebastian
libert.
B
A
A
A
A
C
I
am
a
senior
product
manager
here
at
microsoft,
in
the
microsoft
graph
organization,
I'm
focusing
on
the
developer
experience
so
delighting
developers
to
use
microsoft,
graph,
tooling,
documentation
and
everything
that
really
is
tailored
for
for
dev
that
we're
building
here
on
the
graph
side,
I've
been
at
microsoft
now
for
kind
of
18
months.
Now
it's
been
a
long
time
already,
you're.
C
C
Great
error:
I
started
as
a
customer
and
partner
experience
pm,
so
I
was
working
with
customers
and
partners.
Now
I
moved
on
to
this,
which
basically
for
now
today
means
I'm
working
a
lot
on
sdks
a
lot
on
mgt
and
all
of
our
relationship
between
adaptive
cards
and
microsoft
graph.
So
that's
our.
Those
are
the
things
that
I'm
working
on
today
and
I'm
having
quite
a
bit
of
fun.
A
Is
it
the
transition
from
the
isv
team,
it's
more
on
the
ice
with
them?
I
guess
it
was
more
one-to-one
engagement
and
one-to-one
kind
of
helping
and
and
doing
demos
and
proof
of
concepts
and
helping
people
to
succeed.
But
now
you're
kind
of
irresponsible
and
then
creating
tools
and
sdks
and
communicating
broadly,
is-
is
that
a
fair
kind
of
a
statement.
C
100
that
that's
in
and
that
changes
basically
everything
the
way
that
we're
doing
the
we're
building
relationships
is
is
very
different
when
you
are
working
with
isvs
you,
you
almost
become
friends
with
these
folks,
because
you're
meeting
them
like
weekly
and
and
you're
really
seeing
the
progress
when
you're
you're
building
tools,
let's
call
it
for
the
masses
if
the
the
way
you
engage
with
these
folks
is
very
different.
It's
a
it's!
It's
more
difficult
to
actually
get
a
lot
of
insights,
but
the
impact
is
also
really
really
fun
to
see
grow.
C
Absolutely
different.
Trolls.
When
I
I
joined
microsoft,
I
loved
my
team.
I
started
to
miss
a
little
bit.
Building
I
created
building
stuff
from
the
ground
up,
and
the
last
year
has
proven
to
be
quite
a
a
journey
to
go
where
we
are
right
now,
with
our
sdk
story
and
and
and
all
of
that,
I'm
I'm
I'm
looking
forward
to
to
talk
to
you
a
little
bit
more
about
that.
But
definitely
building
is
is
back
in
into
my
dna
and
I'm
quite
happy
about
it.
A
Yeah
and
from
historical
things
like
you
were
in
an
isv
building
stuff
as
well,
so
it's
kind
of
a
it's
it's
an
exciting
well,
even
as
an
isp
or
when
you're,
not
working
in
microsoft,
as
well.
Even
in
microsoft,
there's
always
the
options
of
doing
customer
one-to-one
customers
and
partners
or
then
the
prod
and,
like
I
said,
I
think
that
when
you
do
broad
engagement
and
sdks
and
product
communication,
you
don't
necessarily
it's
a
bit
more
harder
to
get
a
hunch
on.
A
C
I
have
a
close
enough
relationship
with
my
customers
and
my
partners
that
I
can
actually
sense
what
like
what
we
should
be
doing
when
you're
it's
got
a
smaller
isvs.
We
had
hundreds
of
customers,
but
hundreds
of
customers
is
not
like
millions
of
developers
using
your
tools,
so
the
scale
is
very
different.
Now
the
one
of
the
best
source
of
data
is
well
of.
Information
is
collecting
that
data
and
analyzing
that
data-
and
it's
been.
C
We
have
like
amazing
telemetry
on
what
we're,
building
and
understanding
the
behaviors
makes
our
tools
better
in
the
future,
because
we
can
finally
act
on
areas
where
we
don't
succeed
or
in
areas
where
we
see
people
dropping
in
our
developer
portal.
People
are
not
going
where
we
want
them
to
go,
meaning
that
exactly
they
don't
get
the
value.
C
B
That's
an
interesting
part
right
because,
because,
like
you
measure
the
things
you
have
like,
you
cannot
measure
a
feature
you
don't
have
right.
So
I
wonder
how
you
balance
out.
Well,
the
data
says
this,
but
your
idea
is
about
that
like
how
do
you
balance
new
ideas
that
you
cannot
prove
with
telemetry?
You
have
because
the
feature
isn't
there,
so
there's
nothing
to
track
yet.
So
how
do
you
balance
that
out?
C
It
was
a
weird
table,
but
and
in
our
sdk
round
table
we
had
four
questions,
super
open,
ending
and
what
we
got
out
of
this
was
probably
worth
six
months
of
understanding
and
thinking
and
debating
within
our
team.
We
got
the
real
users
telling
us
what
are
their
real
struggles
rather
than
us
kind
of
figuring
out
exactly,
and
there
was
no
assumption
in
that.
C
So
for
for
honestly,
these
are,
I
think,
one
of
the
best
ways
to
actually
get
a
better
gut
feeling
on
it
kind
of
validates
your
hypothesis
and
then
you
can
okay.
Now
we
can
do
an
experiment.
Let's
build
this.
Let's
make
sure
that
there's
data
in
it,
so
we
can
measure
it
and
then
couple
weeks
months
later,
we're
like
okay.
So
we
aren't
on
the
right
track
and
you
know
what
we
might
be
on
the
wrong
track,
and
that
is
also
okay.
That's
something
that
I
learned
in
product
management.
C
A
So
if
you
prove
that
that
path
wasn't
successful
and
then
and
it's
completely
fine,
it's
part
of
the
game,
like
albert
einstein,
said
when
you
have
what
was
it
for
1
000
times
you
try
something
yeah,
it's
not
1
000
times
failure.
You
know
999
times
when
it
didn't
work,
and
then
you
know
the
one
time
when
it
worked
so.
A
Something
about
an
outcome
right:
the
1000,
different
versions
of
the
same
thing,
outcoming
a
failure
so
anyway,
so
separate,
but
yeah
so,
and
that's
actually
kind
of
an
interesting
thing
as
well.
That
relates
on
the
on
the
discussion.
We've
been
chatting
here
quite
a
few
times,
which
is
the
minimal
viable
product
versions,
which
is
quite
it's
partly
even
frustrating
for
customers
and
partners
every
now
and
then
because
they
keep
on
saying
that
well,
while
releasing
the
stupid
feature
because
it's
not
complete,
which
is
like
no
no.
No.
B
But
what's
right
and
I
mean
I
worked
in
product
a
while
back
for
a
bit
and
one
of
the
hardest
part
was
always
trying
to
envision
the
next
thing
you
wanted
to
build,
and
you
wanting
to
avoid
like
talking
to
folks
about
the
what
ifs
and
what
would
you?
Because
you
know,
you're
going
to
get
a
theory
exercise
it's
going
to
be
all
fun,
but
then,
at
the
end
of
the
day
of
the
day,
you
will
get
advice,
that's
worthless,
because
it's
not
based
on
any
actual
need.
People
have
so
sad
question
to
you.
B
C
That
there's,
I
think,
there's
multiple
ways
that
we're
actually
doing
it.
One
of
one
of
the
first
thing
we
we're
doing,
and
I'm
going
to
talk
about
one
of
the
products
that
I
own,
which
is
the
microsoft
graph
toolkit
is
we
tend
to
ship
quickly
fast,
very,
very
small,
increments,
meaning
that
once
I
ship
a
new
thing,
I
I
just
ship
like
not
even
like.
Sometimes
I
would
not
even
call
them
v1.
C
I
will
call
them
like
experiments
that
you
can
use
that
are
available
that
are
there
and
then
do
this,
and
then
we
can
measure
and
we
have
the
feedback,
especially
in
open
source
communities
or
people
come
back
and
say
hey
this
worked,
or
this
absolutely
does
not
work
it
you're
missing.
All
of
this
before
it
even
becomes
useful.
Having
these
feedback
loops
is
super
important,
but
if
you
don't
put
that
in
front
of
the
users,
they
won't
do
it
a
good
example
of
this
is.
I
can
talk
about
our
our
design
for
sdks
forever.
C
If
a
developer
cannot
touch
it
and
have
like
a
pr
first
success
to
to
graph
in
less
than
30
seconds
it.
It's
not
gonna
work,
so
we
need
to
give
some
like
a
and
that's
really
how
I,
I
really
think
very
deeply
is
especially
in
our
space,
where
we're
talking
to
developers
the
developers
if
we're
telling
them
this
is
preview.
This
is
not
production
ready,
it
might
be
a
little
bit
broken,
but
here
you
go,
have
fun
they're
going
to
be
willing
to
take
a
bet
and
test
it
out
a
little
bit?
C
C
B
B
So
now
you
mentioned
something:
that's
really
intriguing
right,
because
you
mentioned
developer
experience,
developer
experience
is
a
really
broad
thing,
because
it's
it's
another
thing.
You
said
end
to
end
right.
So
if
I
think
about
well
it's
how
people
discover
how
they
and
started
how
they
find
out
more
and
you
might
want
to
a
a
b,
all
of
all
of
that
or
every
single
point
or
combination.
So
it's.
B
C
In
in
this
case,
it's
isolated
experimentations,
so
we
are
going
to
say
we
want
to
improve
this
specific
area
where
we
think
we
can
do
better
and
then
we're
going
to
do
an
a
b
testing
on
that
we
would
not
be
able
to
do
an
a
b
testing
of
a
to
z.
From
the
first
time
you
land
on
graph.microsoft.com,
which
is
our
developer
portal,
to
your
first
sdk
call
like
this.
This
journey
is
such
a
long
journey
that
we
we
don't
want
to
have
an
a
b
testing
in
every
single
options.
There.
B
A
C
Cool,
but
it's
we
want
to
do
very,
very
specific.
We
and
we
have
to
be
deliberate
in
what
we
want
to
measure
we
can.
We
can
improve
everything.
Everything
is
improvable,
there's
not
an
experience
anywhere.
That
is
perfect.
Now,
sometimes
good
enough
is
good
enough
and
that's
something
that
we
have
to
I'm
a
I'm
a
perfectionist.
I
always
want
to
go
like
above
and
beyond
everything
I
do,
but
sometimes
is
it
really
worth
it.
So
this
is
the
areas
where
we're
looking
at.
Where
are
we
losing
folks
where
our
developers
are
telling
us?
B
C
It
really
enables
us
to
make
the
to
flip
on
the
right
switches
based
on
what
is
the
outcome
that
we're
looking
for,
and
I
think
that's
the
best
part
of
of
of
our
role.
Is
it
we're
really
enabled
to
to
do
that
as
we
own
the
entire
stack
from
the
portal
to
the
sdks
to
the
samples
to
the
the
repos
to
everything.
B
A
C
I
think
you
always
have
to
remember
who
you're
building
for
before
you
decide
what
you're
building.
So
when
we're
discussing
with
our
our
devs
that
are
using
some
of
the
tooling,
we
want
to
help
them
being
more
productive
being
more
successful.
So
that's
how
we
start
when
we
think
about
a
new
product
or
when
we
think
about
a
new
experience.
Okay,
that's
we
have
to
make
this
a
thing.
We
have
to
make
this
more
productive
for
the
dev.
C
We
we
basically
don't
have
a
lot
of
that
data,
so
this
is
where
we
become
a
partner
with
a
lot
of
other
teams
at
microsoft
that
are
working
with
these
large
organizations,
partners,
sis
isvs
whatever,
and
they
we
read
some
of
the
reports
and
we're
like.
Oh
there's,
a
big
gap
there
and
we've
heard
it
from
this
part
at
this
point
at
this
partner,
this
partner,
we
correlate
all
of
that.
C
We
weight
a
feedback
based
on
the
number
of
customers,
the
number
of
tenants,
or
sometimes
just
a
number
of
feedbacks,
like
specific
feedbacks,
when
we're
hearing
from
25
different
partners
that
we
should
have
an
api
that
calls
into
this
product,
we
have
to
think
about.
Why
do
we
get
25
feedback
for
this
product?
So
for
sdks?
That's
exactly
what
happened!
A
lot
of
we're
in
a
quest
right
now
to
renew
our
approach
to
sdk
you
had
in
the
past.
C
You
you
discuss
kyota
with
some
of
our
rpms
and
kyota
is
one
of
the
promise
that
brings
sdk
on
demand
for
any
endpoints
on
graph,
and
a
lot
of
our
partners
were
saying
my
package,
my
sdk
is
so
big
and
so
broad
and
the
developers
don't
want
to
work
with
six
thousand
points.
They
want
to
work
with
the
three
endpoints
we're
using
in
our
products,
not
everything.
C
So
our
we
get
the
feedback
that
sdks
were
too
big.
As
the
case
was
too
complex,
there
was
too
many
endpoints
now.
What
does
it
mean
like?
This
is
where
our
work
starts
and
we
decide.
Okay,
this
is
a
priority.
It's
going
to
help
us
internally,
be
more
agile
in
ways
of
shipping
sdks,
but
also
it's
going
to
empower
developers
to
have
more
flexibility
and
agility
in
the
way
that
they
generate
their
own
sdks
and
we
went
there.
So
it's
there's
also
like
we
have
to
remember
it.
C
For
this.
We
need
to
have
part
in
our
group.
We
need
to
be
more
productive
at
building
sdks,
also,
so
there's
also
a
weight,
some
kind
of
a
a
point
system
that,
yes,
internally
sometimes
internal
engineering
counts
in
what
we're
deciding
to
build,
because
if
we
help
ourselves,
we
might
also
help
our.
A
And
it's
interesting
to
see
how
the
evolution
is
changing
the
challenge,
what
you
have
in
the
microsoft
graph,
because,
let's
face
it
a
while
back,
the
challenge
was
not
all
of
the
apis
are
in
craft
or
only
a
subset
of
api
starting
craft.
Now
the
ap
api
surface
and
graph
is
just
out
of
this
world.
You
can
do.
C
C
Absolutely
and
we're
not
expecting
anything
to
slow
down
from
a
graph
standpoint
like
the
graph
like
we're
seeing
teams
coming
to
our
api
reviews
from
everywhere
around
our
organization
on
a
daily
basis.
Coming
in
and
saying
hey,
we
have
a
really
cool
api
for
graph,
we'd
love
to
get
it
on,
and,
and
sometimes
this
api
is,
will
will
bring
180
new
endpoints
to,
and
it
also
means
180
new
methods
and
chaining
patterns
in
our
sdks
and.
C
C
B
Though
that
was
a
thing
I
was
just
about
to
ask
like
what
is
what
do
you
find
the
most
most
rewarding
part
of
your
job,
and
I
guess
in
a
way
you
answered
that
already
with
the
scale
and
the
impact,
but
is
there?
Is
there
anything
else?
Is
there
anything
else
you
have
on
your
mind
when
it
comes
to
you
know
the
the
really
true
true
rewarding
aspect
of
your
job.
C
C
With
with
that
data,
and
because
of
your
brand
new
sdk,
which
was
our
go
sdk,
I
was
able
to
complete
my
work
in
less
than
10
days,
which
my
I
told
my
boss
would
take
around
six
months
to
get
all
that
data,
because
before
that
we
didn't
have
any
go
sdk,
so
they
had
to
go
through
everything
and
when
you're
new
to
m365,
when
you've
been
in
the
business
of
m365
forever
graph
makes
so
much
sense.
Like
it's
easy,
you
know
where
you're
going.
You
know
this
message.
C
C
What
like,
what
is
the
difference
between
a
chat
message
and
a
channel
message,
yeah
what
it
there's
so
many
of
them
and
within
10
days
they
were
able
to
deliver
what
they
wanted,
and
they
actually
did
a
testimony
during
our
our
roundtable
just
to
say,
hey
folks,
thank
you
so
much
we
were
able
to
do
that
and
it
was
based
on
the
needs
of
we
don't
have
a
go.
Sdk
go
is
becoming
very
popular,
we're
getting
demand
from
even
from
internal
microsoft,
we're
getting
demand
from
for
go
and
we're
getting
it
also
from
partners.
C
We
delivered
it
within
six
months,
it's
now
in
preview,
and
somebody
was
able
to
succeed
with
a
preview
build
of
our
our
go
sdk,
which
this
is
where
it's
really
rewarding
and
I'm
taking
the
credit.
It's
not
even
my
product,
like
it,
it's
a
product
that
is
managed
by
another
team.
Member
of
my
team.
It's
my
esa
that
handles
that,
and
but
just
the
fact
that
our
sdk
story
now
empowers
people.
I
think
this
is
where
it's
the
most
rewarding.
A
So,
on
the
on
the
on
the
sdk,
we
thought
that's
the
sdk
as
we
talked
about
the
craft
tool.
Can
you
talk
about
bit
about
what
does
it
mean
that
you're
leading
sdk
and
a
craft
tool
get
work?
We
talked
about
the
fact
that
it's
a
lot
of
meeting
coordination
of
things
data
analytics,
but
in
practice,
if
there
would
be
any
youngsters
out
there,
who
would
be
looking
into
I'm
going
to
be
a
program
manager
in
the
microsoft
when.
C
That's
that's
actually
a
good
question.
I
think
the
first
thing
you
have
to,
I
think
what
is
being
a
product
manager
is
to
be
able
to
feel
empathy
for
your
audience
and
try
to
deliver
the
value
that
they're
expecting
or
that
that
that
they
need
to
be
more
productive,
and
that
is
even
in
technical
audiences,
which
is
mine,
like
I'm,
my
audience
is
developers,
but
if
you
are,
you
want
to
aim
at
accountants
or
or
any
other
type
of
roles
or
whatsoever.
C
Yeah-
but
this
is
a
very,
very
limited
like
folks,
but
when
a
developer
is
using,
one
of
our
tools
is
because
they
want
to
do
something
else.
They
want
to
build
a
tool
that
will
empower
every
single
employee
in
their
organization
to
be
more
productive,
and
this
is
where
this
is
like.
It's
kind
of
the
flywheel
flywheel
effect.
When
you
empower
one
person,
usually
it
it
just
starts
it
spins
and
everybody
gets
more
productive
and
I
think,
if
you're
into
helping
the
others
you
have
like
you,
love
tech,
I
think,
being
a
product
manager.
C
You
need
to
love
some
aspect
of
tech
because
I
think
that's
what
you're
building
in
the
end.
Yes,
there
are
meetings.
Yes,
there
are
emails,
there's
their
countless
chat
messages.
Yes,
there
are
challenges
with
time
zones,
because
you're
working
here
we're
working
in
three
different
time
zones,
some
in
europe,
some
here
in
america,
but
you
know
what
this
is
actually
for
me,
that's
the
other
side
of
it,
which
is
the
beauty
of
it
it
it.
C
It
makes
you
meet
tons
of
people
from
around
the
world,
especially
an
organization
like
microsoft,
where
you
just
meet
people
from
all
around
the
world.
Every
single
day,
you
empower
your
users,
you
have
fun
at
work,
I
think
that's.
What
a
product
manager
is
and
that's
why
you
want
to
become
a
product
manager,
yeah.
B
You
mentioned
you
mentioned
something
that,
like
you,
want
to
be
on
a
mission
to
help
others,
and
that
makes
me
think,
especially
the
these
days.
We
see
a
lot
of
impatience.
You
want
to
do
something
like
you
want
to
watch
a
movie,
there's
streaming
service
on
and
it's
there
like.
We
don't
need
to
wait.
We
barely
need
to
wait
for
anything
at
all.
B
To
what
extent
do
you
need
to
say
like
hey,
I
have
this
ambition
in
my
head
and
I'm
okay
that
that's
going
to
take
two
three
five
years,
maybe
a
career
even
to
fix
that,
but
that's
okay,
I'm
going
to
commit
to
it
sure,
along
the
way
we
will
have
wins.
Maybe
we'll
lose
some,
but
I
dedicate
myself
to
this
as
opposed
to
you
know,
I'm
going
to
do
this
thing
six
months,
I'm
bored,
I'm
gonna,
do
another
thing.
B
C
I
think
you
need
to
embrace
these
the
vision,
the
culture,
the
the
mission
of
that
organization,
and
I
think
every
single
decision
move
product
feature
that
you're
shipping
should
play
a
role
in
that
bigger
mission.
But
don't
think-
and
especially
don't
stress
that
or
don't
over
stress
with
the
fact
that
what
you're
building
right
now
might
be
a
drop
in
the
pound.
C
C
C
Be
loud,
be
bold,
talk
about
it,
be
collaborative
with
your
folks,
and
I
think
that's
how
the
mission
is
reminded
to
everybody
and
how
and
that's
how
you
basically
say
this
is
how
I
embrace
my
mission.
This
is
how
I
move
forward
with
that
mission
that
we're
gonna
achieve
at
some
point,
but
usually
a
mission.
C
A
But
that
does
for
sure
requires
a
certain
mindset
and
to
be
able
to
think
that
way
that
you're
basically
well,
I
I
love
the
one
statement
which
is
you're
changing
the
world
one
person
at
the
time
sure
it
might
be
multiple
persons
still
in
the
day
it
might
be
hundreds
of
thousands
or
thousands
of
persons
in
a
day,
but
as
for
humans,
we're
still
reacting
on
humans,
so
you're
basically
changing
one
person
at
the
time,
and
then
that
starts
the
the
the
snowball
effect
to
actually
rolling.
So
there.
B
Was
the
other
day
there
was
the
other
day
this
interesting
discussion
that,
where
some
someone
says
like
on
the
outside,
it
seems
it
comes
off
on
a
cross
as
if
a
cultural
change
happens
like
overnight,
like
there's
a
boom
big
bang
thing.
In
reality,
it
happens.
One
discussion
at
a
time
like
we
talked
it's
like,
we
spark
a
thought
and
then
we
will
talk
to
other
folks
and
that
will
then
end
up
eventually
becoming
that
change
that
we
want
to
drive.
B
C
B
A
A
Header,
exactly
just
to
mention
header
they're
downing
here,
because
we're
stealing
that
message,
but
do
things
tell
people
it's
not
technically,
if
you
want
to
change
the
world,
if
you
wanna,
do
a
bigger
impact
on
things
doing
things
absolutely,
but
you
need
to
also
tell
people
that
you're
doing
things,
because
otherwise
people
cannot
relate
and
they
cannot
commit
on
that
mission.
They
don't
understand
necessarily.
Why
we're
doing
that.
But
then.
A
Only
telling
not
doing
that's
like
well
that
doesn't
work
either,
so
you
need
to
actually
do
both
to
be
successful.
So
and
that's
one
thing
what
people
unfortunately
quite
often
forget
about
is,
is
well.
We
keep
on
shipping
cool,
but
you
need
to
be
really
vocal
on
what
you're
doing,
because
otherwise,
how
would
do
other
people
know
it's
not
in
their
day-to-day
interest
to
scan
internet
or
in
github
or
whatever,
when
there's
a
new
version
available,
you
just
need
to
be
vocal.
A
C
Very
interesting,
and
even
sometimes
you're
like
oh
yeah,
but
that's
such
a
tiny
feature,
but
there's
there
might
be
one
dev
somewhere
that
has
spent
the
last
week
fiddling
with
your
thing,
yep
and
he's
been
failing
and
failing
and
failing
and
now,
if
you
tell
him
that
that
one
thing
is
fixed,
then
it'll
be.
Finally
I
can
go
on
my
weekend.
Exactly
I'm
gonna
have
like
I'm
gonna,
be
totally
fine
with
it
and
you
changed
one
person
this
week.
As
you
said
yeah
next
week,
it's
going
to
be
another
set
of
folks,
so
yep
then.
A
A
I
guess
it's
the
persistency
and
and
consistency
and
and
just
keep
on
communicating
and
shipping,
of
course,
as
well.
Having
that
right
balance
of
things
and
to
be
able
to
make
things
happen,
now
we're
starting
to
run
out
of
time
a
bit
from
a
time
in
perspective,
it's
just
making
sure
that
we
don't
run
overboard
because
of
the
other
meetings
as
well.
Now,
what's
gonna
anything
interesting,
what's
happening
on
your
world
except
during
this
week,
what's
happening
anything
what
you're
gonna
talk
about
now
the
build
is
done.
C
A
little
bit
of
that
to
be
fairly
honest,
there's
that
this
week
is
a
a
very
interesting
week,
we're
gonna,
probably
close
on
our
planning
for
the
next
semester
on
the
microsoft
graph
team.
So
that's
really
really
cool.
Now
that
we
had
all
the
feedback
we
needed
that
we
needed,
but
all
the
feedback
we
got
from
build
super
useful
to
infuse
that
feedback
in
some
of
the
plans
that
we
want
to
to
ship.
So
definitely
that's
going
to
be
this.
C
I'm
going
to
also
prepare
myself
to
travel,
something
something
incredible.
So
I
am
traveling
to
redmond
next
week,
where
we're
going
to
have
our
first
off
site
of
the
microsoft
craft
team
in
forever,
I've
been
in
the
team
for
a
year
and
a
half
never
actually
met
more
than
90
of
my
colleagues
face
to
face.
So
that's
going
to
be
great
to
finally
meet
somebody.
How.
A
C
C
B
C
B
Always
always
always
interesting
stuff,
so
this
week
we
are
closing
in
on
may,
which
means
a
new
release
of
cli
for
microsoft,
365
with
new
features
and
improvements
and
enhancements,
and
it's
really
cool
to
see
right.
So
in
may
we
welcome
two
new
maintainers
and
it's
always
like
it
never
really
occurred
to
me
but
like
in
a
way
like
we're
running
a
company
in
a
sense
that
well
we're
welcoming
new
people.
B
They
join
the
team
sure
like
we're,
not
hiring
and
paying
and
all
that,
but
it's
still
a
team
with
people
with
whom
you
work
and
always
there's
always
this
thing
where
new
people
join
you're
always
like.
Will
it
work
like
what
will
be
their
impact
on
everybody
else
on
a
team
folks,
who've
been
longer
because
enemies,
change
and
it's
so
really
cool
to
see.
You
know
the
energy
goes
up.
We
get
new
people
and
they're
like
I
want
to
help.
Where
do
we
go
and
they
come
with
tons
new
ideas?
So
like
we're
like?
B
Oh
my
god,
this
is
so
cool
like.
Why
haven't
we
done
that
this?
Earlier
I
mean
in
a
way.
It's
always
this.
The
the
balance
where
you
want
to
grow
organically,
like
you,
you
you
don't
just
want
to
keep
adding
more
people,
because,
like
more
people,
means
more
communication
lines
and
alignment
and
all
of
that,
but
in
this
case
it
panned
out
perfectly
like
we
couldn't
have
wished
for
more.
B
So
it's
really
awesome
to
see
the
effect
of
that
on
all
the
work
that
we
do
on
the
engagement
on
github
prs,
our
internal
comps
within
a
team,
new
ideas
and
all
that
is
coming
to
fruition
now
in
the
release
and
and
beyond
that.
So
that
is
really
cool,
and
with
that
like
we,
we
hope
that
we
will
be
able
to.
B
You
know
ship
even
more,
like
be
faster,
be
more
responsive,
get
back
to
folks
in
time
when
they
have
questions
when
they're
stuck
where
they
have
prs
just
to
you
know,
make
it
a
great
experience
for
everybody
in
involved
and
other
than
that
internally,
at
microsoft,
it
is
planning
time.
So
you
know
thinking
a
lot
together
with
other
teams,
what
ideas
they
have
where
we
can
work
together.
B
What
are
different
things
that
we
think
they
could
take
into
account
we're
making
their
own
plans.
So
it's
very
much
the
time
where,
maybe
you
won't
see
us
dude
or
ship
that
much
but
we're
preparing
now,
so
that
we
can
go
twice
as
fast.
Then
you
know
when
we're
hamster
and
we're
there.
So
that
is
that
interesting
time
of
year
plus
you
need
catching
breath
after
build.
A
B
Also
cool
right
that
we're
not
limited
to
just
that,
because
we
work
and
our
teams,
I
guess,
are
all
over
the
world
right,
like
my
team,
spends
from
hawaii
to
australia,
we're
literally
all
over
the
globe.
So
there
is
no
stopping
and
not
shipping,
because
well,
somebody
is
working
like
one
team
has
has
a
vacation.
The
other
does
not
right.
B
So
there's
also
this
cool
thing
that
we
can
better
cater
to
our
audience's
needs
because,
like
some
of
us
are
away
when
that
audience
is
away,
but
that
audience
is
in
the
way
and
that's
cool,
because
a
part
of
our
team
is
in
a
way
too.
So
there's
always
somebody
to
you
know
pick
up
the
the
phone.
If
you
like.
A
Yeah,
absolutely
absolutely,
but
again
so
considering
what
we
were
just
saying:
it's
a
bit
of
a
slow
time
period
because
everybody
has
been
doing
planning
and
a
bit
of
a
a
less
shipping.
Of
course
it's
it's!
It's
not
like.
Everybody
goes
away
and
nothing's
going
to
happen.
There's
a
lot
of
stuff
happening
still
yeah
sharepoint
framework
1.15
is
coming
out
within
two
weeks
release
candidate
coming
out
of
this
week,
so
with
javascript
sdk
3.0
support
for
craft
as
an
example.
A
C
C
A
A
C
B
A
A
I
don't
want
it
well,
it's
okay,
but
anyway,
thank
you.
Seb
on
this
one.
After
this
interview,
we'll
jump
on
the
weekly
articles,
we
got
a
lot
of
quickly
through
a
lot
of
the
announcements
in
build
from
last
week.
There's
a
lot
of
stuff
getting
announced,
which
is
super
super
cool
as
well,
but
thank
you,
zep,
really
cool
discussion
and
we'll
follow
up
on
the
episode
200.
now
you're
booked
for
hosting
this.
A
C
A
A
You
awesome
cheers
bye-bye
excellent.
Thank
you,
sip
on
that
one
really
really
cool
and
I'm
good
to
catch
up,
I'm
good
to
have
a
discussion
on
the
future
direction
as
well.
So
it's
it's
actually
really
cool
to
have
a
discussion
right
after
build,
so
we
can
actually
open
and
talk
about
all
the
latest
and
coolest
thing
right.
So,
yes,
rather
than
we
have
cool
stuff,
we
can't
talk
about
it.
So.
B
A
Now,
just
from
a
timing
perspective,
let's
actually
jump
on
the
articles
as
well,
and
we
will
cover
a
lot
of
a
lot
of
a
lot
of
the
build
announcements
and
just
to
recap
where
those
announcements
are
being
listed.
We're
not
gonna
go
all
of
them
through
one
by
one,
because
that
would
not
make
any
sense.
But
let's
call
a
few
of
the
the
main
announcements
and
main
cool
things
which
we
clearly
have
seen
have
got
a
lot
of
attention
within
last
week.
We
are
recording
this
on
13th
so
week
after
the
build.
A
So
first
of
all
the
primary
build
announcement.
Article
was
around
from
jeff
deeper,
around
build
cooperative
apps
with
microsoft
teams
and
really
focuses
well,
not
only
on
microsoft
teams,
of
course,
across
the
microsoft
365
platform,
which
might
be
a
bit
confusing
because
we
we
seem
to
be
now
using
teams,
teams,
teams,
teams
first,
but
quite
often
it's
much
more
than
that.
So
teams
is
a
super,
critical
and
strategic
application
for
us
and
that's
why
it's
being
always
in
the
front
of
in
the
messaging.
A
But
there's
a
lot
of
a
lot
of
announcement
in
in
other
areas
as
well,
and
many
of
them,
of
course,
are
associating
and
as
related
on
the
microsoft
teams
for
sure.
So,
first
of
all
we
have
the
live
share,
which
is
really
really
cool.
It
is
a
really
cool
video
showing
how
people
can
actually
integrate
well
collaborate
together
in
a
live
share
mode,
so
they
can
basically
at
the
same
document.
A
They
can
see
other
people
actually
working
on
the
same
thing,
which
is
really
really
cool,
absolutely
brilliant
concept
of
not
having
just
a
meeting
chatting
with
people
but
actually
working
in
the
meeting
on
those
assets
and
designs,
and
all
of
that
stuff,
which
is
really
really
cool,
fluid
framing,
can
actually
float
relay
general
availability.
Fluid
framework
has
been
in
works
for
quite
a
few
years.
I
will
announce
that
in
I
would.
A
Whenever
we
were
still
in
in-person
builds
as
the
first
time
as
a
preview,
and
now
it's
actually
going
to
go
in
ga,
which
is
great,
so
congratulations,
floyd,
framework
team
and
there's
also
a
create
loop
components
by
you.
Updating
adaptive
components
by
updating
out
of
the
course
create
loop
components
by
updating,
look
interesting
title
anyway.
A
What
it
means
is
that
you
can
use
loop
components
in
your
adapter
cards
in
the
teams
and
in
in
other
solutions
as
well
and
which,
which
basically
fluid
framework,
is
the
technology
which
the
loop
components
are
using
just
to
clarify
that
one
as
well
and
then
introducing
microsoft,
azure
communication
services
sample
app
builder.
That's
basically
for
integrating
your
solution
to
microsoft,
teams
without
running
in
the
teams.
So
here
we
can
see
the
integration
between
the,
for
example,
the
person
who's
using
the
microsoft
teams
and
then
connecting
to
a
business
from
a
website.
A
So
that's
the
doctor
you're
connecting
to
so
actually
pretty
cool
setup.
The
microsoft
azure
communication
service
is
really
interesting,
actually
makes
it
super
easy
to
consume.
Microsoft,
teams
capabilities
a
lot
of
improvements
in
craft
there's,
a
new
version
coming
from
sharepoint
framework,
microsoft,
viva
connection
quite
soon,
as
well
as
a
lot
of
investments
there
as
well
approvals,
extensibility
and
then,
of
course,
the
team's
toolkit
and
the
implementations
type
of
teams
application.
A
A
A
Announcements
in
builds
right,
maldek,
so
a
lot
of
that
new
stuff
in
there
as
well
and,
of
course,
the
monetization
a
lot
of
stuff
and
in
announcements
there
on
that
side
as
well
and
a
lot
of
light
of
light
of
light
of
additional
references,
like
I
said,
we're
not
going
to
go
super
detailed
on
all
the
articles
today
and
because
we
don't
want
to
spend
time
on
recapping,
because
this
is
kind
of
the
primary
list
of
things
and
then
the
secondary
primary
announcement.
I
guess
is
this
one.
B
Right
so
basically,
we
have
this
new
way
to
build
summer
facing
or
public
facing
pages
on
power
platform,
and
it's
it's
a
great
step
towards
empowering
makers
to
build
customer
facing
resources
right
because
up
until
now,
it
was
very
much
inside
right.
So
like
you
would
build
a
power
app
that
helps
you
or
your
team
or
your
org,
to
improve
the
workflow,
and
with
this
step
like
we
have
now
the
ability
to
build
externally
facing
assets.
A
Yep,
that's
really
really
cool
stuff,
as
well
now
related
on
all
of
this
announcement.
Then
we
have
a
specific
blog
post
on
a
specific
areas
of
the
build
and
also
so.
There
was
a
lot
of
other
news
announcements
last
week
related
on
build,
for
example,
on
the
preview
on
the
virtual
environment
craft
apis.
It's
a
good
blog
post
in
the
teams,
blog
related
on
all
of
those
capabilities.
A
We
also
had
a
specific
blog
post
related
on
the
live
share,
which
we
already
talked
about
within
the
jeff's
note.
We
also
have
a
specific
blog
post
from
built
from
ben
summers
related
on
all
of
the
different
microsoft
craft
announcements,
which
is
really
cool
a
lot
of
a
lot
of
improvements
there
with
additional
videos
as
well.
So
this
is
actually
quite
really
really
cool,
so
I
got
ica.
A
What
what
happens
is
that
we're
announcing
all
of
the
new
stuff
in
built,
and
then
this
overwhelming
amount
of
new
features
right
from
microsoft,
drive,
connectors
and
update
on
that
side
as
well,
a
lot
of
lot
of
connectivity,
improvements
and
and
features
and
capabilities
there
as
well.
Thank
you
james
on
that
update
and
then
tomomi.
Con
really
focuses
on
the
microsoft
teams
toolkit
for
resource
studio
code,
which
is
the
ga
version.
The
visual
studio,
ide
version
of
microsoft.
A
B
Yeah
correct,
so
I
think
that
this
goal
life
coincides
with
build
so
ad
build
or
dream
build
time
frame.
We
released
this
new
set
of
dogs
right
that
are
really
meant
to
guide
enterprise,
app
leaders
bdms
to
to
think
about
how
can
they
build
applications
or
microsoft
cloud
like
what
is
what
what
are
the
different
options
and
really
not
in
the
you
know
very
low
level
tech
stack
but
more
in
about
like
what
is
the
offering
of
the
microsoft
cloud
and
what
is
it
like?
B
How
would
you
use
in
an
enterprise
combination
of
azure
power
platform,
github
devops,
micro365
mx
right,
so
how
would
you
tie
all
of
them
into
an
application
that
you
would
build
for
your
org?
So
this
is
a
very
interesting
set
of
dogs
that
are
meant
more
as
a
guidance
in
thinking.
And
how
would
you
architect
that,
and
not
really
like
specific
things
for
devs
with
code
examples,
so
we.
B
A
A
Now,
on
the
list
funding
site,
we
we
had
thatcher,
I
had
a
blog
post
in
microsoft,
traces
to
our
platform,
community
block
related
on
view,
the
contents
of
a
file
with
the
preview
card-
and
this
is
really
really
cool
list-
formatting,
so
basically
not
a
pop-up,
but
a
panel
kind
of
a
pop-up.
It's
not
a
windows,
but
a
panel
pop-up
in
the
window
in
the
files
to
be
able
to
preview.
What's
in
inside
of
specific
files,
that's
a
really
really
cool
layout.
B
Exactly
so
a
new
sample
around
teams,
apps
that
are
made
for
use
in
meetings
and
this
time
around
it's
about
voting
and
and-
and
I
think,
if
I'm
I'm
not
mistaken-
it's
about
using
the
stage
view
to
how
can
you
vote
on
movies?
I
think
that-
and
that
is
the
use
case
here
and
again
it's
a
great
example
that
goes
really
deep
into
the
code
showing
exactly
the
code.
You
would
build
and
write.
B
A
Job
stuff
once
again
marcus.
So
thank
you
for
that
and
then
peter
wenstra
had
a
blog
post
related
and
create
an
app
using
a
new
image
import
in
powerapps,
and
this
was
one
of
the
announcements
from
microsoft:
build
where
you
can
actually
draw
a
file
and
draw
a
drawing,
which
is
basically
then
being
scanned
inside
of
the
powerapps.
A
A
B
As
explaining
so
in
scss
that
you
use
in
spfx
there's
this
ability
that
you
can
import
other
style
sheets
with
tilde
right,
so
this
character
at
the
front
of
the
path,
and
he
explains
what
it's
for,
how
it
works
when
you
would
use
it.
So
if
you
work
with
spfx,
there's
definitely
good
thing
to
know,
even
though
you
might
not
use
it
immediately.
B
A
B
Exactly
and
she
again
also,
this
is
a
video
that
shows
the
new
ability
to
again
import
drawings,
to
power
apps
to
start
building
your
app
right.
So
if
your
drawing
skills
are
like
mine,
you
know
you
don't
go
beyond
the
stick
figures
and
all
that
you
could
become
a
designer
of
apps
right.
You
could
really
easily
build
apps,
I
mean
in
in
real
world.
I
can
imagine
like
this
being
a
really
great
way
to
take
the
you
know
back
of
a
napkin
designs
and
turn
it
into
a
workable
app
right.
A
Yep,
absolutely
absolutely:
it
will
certainly
speed
up
the
product,
prototyping
of
things
and
proof
of
concepts
and
proving
that
things
are,
you
know,
workable,
so
really
very
close
down
and
then
the
final
final
video
and
from
shane
young
is
around
ai
builder
invoice
processing
for
power,
apps
and
power
automate.
So
how
do
we
actually
integrate
a
bit
of
artificial
intelligence
on
handling
the
files
as
the
files
are
coming
in?
In
this
case?
We're
using
the
scenario
is
around
the
files
within
a
sharepoint,
so
we're
basically
adding
a
file
into
sharepoint.
A
Then
we
are
scanning
the
file.
We
are
automating,
the
the
creation
of
the
attributes
and
detecting
the
values
and
then
doing
approvals
of
all
of
that,
so
real,
really
cool
stuff
and
a
cool
looking
application
for
sure.
Really
nice
looking
ui
we're
getting
there,
it's
getting
better
and
better
actually
with
our
apps
cool.
Anyway,
that's
all
of
the
video
or
not
videos
that
all
of
the
articles
this
week,
primarily
really
focusing
on
the
on
the
microsoft
build.