►
From YouTube: Microsoft 365 PnP Weekly – Episode 103
Description
In this weekly discussion of latest news and topics around Microsoft 365, hosts – Vesa Juvonen (Microsoft) | @vesajuvonen, Waldek Mastykarz (Microsoft) | @waldekm, are joined by Darrel Miller (Microsoft) | @darrel_miller – API Architect on the Microsoft Graph team. Discussion on challenges driving use, _v2 property, evolution of the SDK, Microsoft Identity Web.MicrosoftGraph, auto generated code, and the Graph “no breaking change policy.” Graph makes life easier for developers by driving consistency across API Surface. 17 recently released articles and videos from Microsoft and the Microsoft 365 Community are highlighted as well. This episode was recorded on Monday, November 2, 2020.
References:
• See the full blog post for this episode at https://aka.ms/m365pnp-blog
• 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
And
action
it
is
vmp
weekly
episode,
103,
it
is
the
2nd
of
november
2020
and
and
in
the
bmp
week
we
always
talk
about
what's
happening
within
the
last
week,
related
microsoft,
365
in
general,
I'm
concentrating
mainly
well,
not
mainly,
but
also
on
the
on
the
platform
side
of
the
house.
My
name
is
jose
ivan
I'm
a
program
manager
from
the
onedrive
sharepoint
site
and
with
me,
as
the
co-host
is
baldeck
waldek.
Who
are
you.
B
C
A
A
C
C
So
I
sit
on
the
api
review
board
and
help
teams
when
they
have
their
api
designs,
provide
them
guidance,
and
we
also
work
with
our
sister
half
of
the
team
over
in
identity,
which
also
own
a
fun,
a
bunch
of
microsoft,
graph
capabilities
who
they
take
care
of
the
onboarding
of
teams
onto
graph.
So
it's
it's
kind
of
a
portfolio
team.
We
do
a
whole
bunch
of
stuff
and
we
are
growing
quite
enthusiastically
at
the
moment,
which
is.
A
C
A
B
A
For
third-party
developers
for
sure
and
to
be
able
always
to
figure
out
on
which
sdk
which
apis?
How
does
this
work
and
what
about
authentication
and
all
that,
so
I
think
we're
in
a
heading
hitting
for
sure
the
right
direction,
having
a
standardized
basically
layer
for
all
of
the
information
which
is
available
now
before
we
direct
actually
go
to
two
months
on
on
what
you
do
right
now,
can
you
can
you
explain
what
is
your
background?
Where
did
you?
When
did
you
join
microsoft,
and
what
did
you
do
before
this.
C
I've
been
at
microsoft
for
about
four
and
a
half
years
now
I
actually
joined
as
an
evangelist
for
azure
api
management,
which
is
a
management
gateway
over
in
the
azure
side,
and
that
was
right
before
the
developer
advocates
team
that
waldak
you're
now
working
with
jeff
sandquist
organization,
and
there
was
a
plan
to
centralize.
So
they
said
to
me:
daryl,
we
don't
need
evangelists
anymore,
I'm
like
oh
okay.
They
said.
C
Yes,
that's
right,
I
said
I
guess
I've
done
all
the
evangelizing.
That
is
needed,
no
we're
going
to
spin
up
a
whole
new
division
of
evangelist
so
anyway,
so
I
I
changed
and
I
became
a
developer
on
the
api
management
team.
I
mean
it's
not
like
I'd
started
like
I
didn't,
suddenly
decide
to
be
a
developer
before
microsoft.
C
It's
it's
very
close
between
the
apis
in
azure
and
and
graph
so
but
yeah,
it's
great
and
and
we
work
we're
starting
to
work
much
more
closely
with
the
azure
team.
They
there
was
the
microsoft
api
guidelines
that
came
out
a
few
years
ago.
That
was
an
attempt
to
be
consistent
across
microsoft
and
we
are
still
working
towards
following
those
and
we
do
work
regularly
with
the
azure
sdk
team
and
the
other.
A
C
C
Some
services
we
pass
right
through
and
the
response
gets
passed
right
through
some
services,
get
a
response
back
and
there's
little
transformations
like
in
the
past.
Some
apis
used
to
use
pascal
case
well
graph
uses
camel
case
for
all
of
his
properties,
so
some
services,
still
we
do
little
things
like
that,
just
to
provide
that
consistency
across
across
all
the
api
surface
areas,
so
no
graph
doesn't
actually
provide
any
services,
and
that's
why
sometimes,
when
you
ask
us
questions
about,
why
does
this
graph
api
not
work?
C
C
So
we
we
are
that
centralized
team
that
provide
those
things
that
we
can
centralize
like
deploying
and
managing
of
the
docs.
Again,
we
don't
actually
write
the
docs,
but
things
like
sdks
because
we
can
build
and
auto
generate
those
off
metadata.
We
we,
we
generate
those
things
so
yeah
we
we
are.
We
are
the
central
gateway
team,
as
you
would
say,
to
all
of
the
awesome
services
that
all
of
the
other
teams
build
and
they
bring
those
apis.
C
As
I
mentioned
to
this
api
review
board-
and
we
say
yeah,
this
is
not
quite
the
way
we
do
it
on
the
graph,
oh
by
the
way,
there's
another
team
over
here
that
are
doing
something
very,
very
similar
or
oh.
By
the
way
you
just
created.
Another
error
detail
object.
We
already
have
one
of
those
things.
Please
don't
create
another
one,
and
so
we're
kind
of
that
catch-all
to
try
and
ensure
that
we
don't
do
the
same
thing
three
different
times.
We
fail.
C
A
So
kind
of
representing
also
the
partner
and
ecosystem
and
community
towards
send
the
product
team
and
say
no:
no,
no,
no
don't
do
those
crazy
things.
We
have
standards
and
you
need
to
implement
stuff
in
the
right
way,
so
that
the
customers
and
partners
can
benefit
out
of
it
good
way
of
defining
that.
C
Yes,
it's
very
much
part
of
that
role,
because
a
lot
of
those
apis
initially
aren't
built
intentionally
for
third
party
they're
in
they're,
built
for
first
party
type
stuff
and
we'll
look
at
apis
and
and
they'll
go.
What
is
that
property?
Oh
well,
that's
a
smoogly
id
that
is
used
in
such
a
weekly
blah
blah
blah
we're
like
yeah.
No
devs
are
going
to
have
no
clue
what
that
is
or-
or
this
is
this
blob
of
jason-
that
we
haven't
schematized
at
all
and
we're
like
no.
C
We
want
that
experience
to
be
as
easy
as
possible
and
in
the
long
term,
like
building
that
api
to
the
quality
that
third-party
developers
need
benefits
first
party,
it
absolutely
frustrates
certain
people
who
have
deadlines
and
they
want
to
ship
features
and
they
want
to
get
stuff
out
fast
and
they're
like
well.
But
we
don't
need
that,
but
yeah
yeah.
A
On
that
one,
because
that's
a
really
good
way
of
putting
that
as
well.
So
unfortunately,
there
are
organizations
and
themes
in
microsoft
who
consider
the
first
party
minimal,
viable
product,
feature
much
more
important
than
the
the
let's
say:
the
quality
of
the
api
surface.
So
as
long
as
there's
something
from
the
api
which
can
achieve
then
the
ux,
whatever
the
shiny
thing,
is
they're
happy
and
then
the
the
quality
of
the
the
api
is
not
good
about
a
focus
point
which
then
causes,
let's
say,
friction
points
and
debates
between
the
themes.
A
C
And
we
have
the
no
breaking
change
policy
right.
We
don't
allow
breaking
changes
on
graph,
whereas
if
you
have
you're
talking
with
your
sister
team
who's
building
some
product-
and
you
want
to
make
a
change,
you
can
go
over
to
that
team
and
say:
hey
we're
going
to
fix.
Do
this
change.
Could
you
just
coordinate
the
rollout
right
which,
which
you
know
you
can
do
you
can't
do
that
when
you
have
an
ecosystem
of
thousands
and
thousands
of
apps
deployed
in
many
many
different
companies?
You
can't
just
go
by
the
way.
C
A
It's
doesn't
that
work
out,
so
it
doesn't
work
like
that
for
sure.
So,
but
yeah
it
is
what's.
The
kind
of
in
your
role
is:
is
that
one
of
the
the
difficult
things
or
what
would
be
the
difficult
thing
from
from
getting
people
to
understand
the
purpose
and,
let's
say
the
importance
of
the
craft?
From
your
perspective,.
C
Yeah,
I
I
think
that
is
an
important
aspect,
and
it's
it's
a
reality
of
the
entire
api
industry
like
the
web
is
mature.
The
web
browsers
are
mature,
we're
understanding,
although
we
evolve
that
regularly,
but
using
the
web
and
the
internet
as
a
substrate.
A
medium
for
http
apis
is
something
that
is
just
starting
to
mature
now
and
although
we've
had
a
number
of
companies
for
a
few
years,
who
really
are
api
as
a
product,
large
companies
are
only
just
starting
to
understand
the
value
of
saying,
okay.
No,
this
is
this.
C
Api
itself
is
a
product
and
we
need
to
build
it
with
the
same
level
of
care
and
ux
focus
that
we
build
that
we
work
with
all
of
our
other
products.
So
when
teams
are
purely
focused
on
shipping
things
to
their
own
internal
parties,
it's
not
immediately
apparent,
and
if
you
don't
talk
with
third-party
consumers
on
a
day-to-day
basis,
because
it
isn't
part
of
your
day-to-day
role,
then
you
don't
understand
those
impacts.
C
C
Well,
the
still
hasn't
figured
out
what
a
breaking
change
for
an
api
is
when
we
use
a
programming
language,
we
know
it's
a
breaking
change,
because
our
compiler
throws
his
arms
up
and
says
you
have
an
error
right,
but
when
it
comes
to
an
http
api,
you
know
I
reorder
two
properties
in
an
object.
Is
that
or
isn't
it
a
breaking
change?
It
depends
on
the
client
and
how
it
consumes
it,
so
it
can
get
really
really
hard.
We
sit
there
sometimes
with
certain
changes
going.
C
A
B
So
that
you
wouldn't
actually
break
the
people
yeah
exactly,
I
guess
like
so
so.
If,
if
you
think
about
all
these
things,
it
goes
a
long
way
from
just
thinking
about
features
and
product
like
there's
a
whole
dimension
to
designing
an
api,
maintaining
it
over
time,
consistent
and
so
forth,
and
so
on,
as
opposed
to
just
okay.
This
is
a
product
that
I
want
to
build.
These
are
the
few
features
and
shipping
yeah.
C
C
And
this
comes
back
to
our
conversation
about
we're
a
gateway
right.
We
aren't
one
product
team,
we
are
50
product
teams
and
if
you
move
to,
if
you
introduce
a
v2,
how
do
you
call?
How
do
you
coordinate
all
of
those
50
teams
to
be
ready
at
once
to
say?
Oh,
yes,
we
have
some
breaking
change
that
we'd
like
to
do
some
old
legacy
that
we'd
like
to
get
rid
of
and
okay.
So
when
will
you
be
ready?
C
Well
we'll
be
ready
on
this
date
and
then
you
talk
to
another
team
like
oh,
no,
we
can't
make
that
date,
right,
yeah
and
and
so
like
well,
okay,
but
that
well
so
we'll
move
some
things
into
v2
and
when
other
things
are
ready,
we'll
move
those
into
v2.
Well,
then,
what
does
a
developer
do
like
you
have
to
start
using
half
the
stuff,
that's
in
v2
and
half
the
stuff
and
then
you've
got
links
and
you're
using
this
feature
that
points
to
a
user.
C
Well,
is
that
a
user
in
v1
or
a
user
in
v2
with
this
other
playing
arm
thing,
also
points
to
a
user
like
it
just
becomes
a
nightmare.
So
we
worked
really
a
lot
on
this
late
late
last
year,
and
so
one
of
the
things
that
people
are
going
to
start
seeing
in
graph
is
and
they're
going
to
look
at
it
and
go.
C
Oh,
my
that's
ugly,
but
you're
going
to
start
seeing
properties
in
potentially
path
segments
that
have
underscore
v2
on
the
end
and
we
call
it
the
breaking
suffix
approach
now,
most
of
the
time
when
you're
evolving
an
api
right,
you
can
come
in
and
like
there's
a
property,
you
want
to
make
a
change
to
it
and
you're
like
oh
well.
We
want
to
make
it
more
specific.
It's
an
address.
It
has
one
address.
C
Well,
we
want
two
addresses
well,
we'll
create
a
new
property
called
addresses
and
we'll
make
it
an
array
right
which
is
no
problem,
because
it's
a
different
name
and
we
now
have
the
ability
to
deprecate
and
we
can
mark
things
as
deprecate
and
you're
gonna
get
deprecation
headers
and
we're
going
to
enable
all
the
sdks
and
graph
explorer
to
tell
you
if
you're
ever
using
deprecated
stuff.
You've
got
two
years
when
we
mark
something
as
deprecated
and
we'll
make
sure
you
understand
that
that
thing
has
gone
away
and
there's
a
new
thing
to
replace
it.
C
C
You
want
to
keep
that
name
for
clarity,
but
you
want
to
change
it
and
actually
change
its
behavior
in
a
breaking
way.
And
so
the
idea
is,
you
add,
on
underscore
v2.
So,
first
of
all,
it's
a
signal
that
this
new
thing
replaces
that
old
thing
you
can
continue
using
that
old
thing.
You've
got
two
years
no
and
start
using
that
new
thing.
C
All
you
need
to
do
is
just
use
this
different
property
name
and
what
that
allows
our
ecosystem
to
do
is
to
start
adopting.
All
this
new
capabilities
effectively
would
be
bringing
changes,
but
not
breaking
changes
anymore,
because
we
just
changed
the
name
and
then,
when
we
get
our
ducks
in
a
row
and
we
actually
managed
to
move
to
v2
we've
well,
we
have
two
choices
either.
Once
the
two
years
are
up
just
introduce
the
old
property,
we
can
get
rid
of
the
old
property
name
and
reintroduce
that
property.
C
So
we're
allowing
consumers
of
the
api
to
incrementally
adopt
these
new
breaking
changes
over
time
and
then
the
move
to
v2
will
be
much
more
mechanical,
so
it
won't
be
scary,
like
you
know,
you
have
this
whenever
there's
a
new
major
version.
What's
the
first
thing
we
all
do
he's
got
like.
Oh
I've
got
all
these
breaking
changes
lined
up
right.
C
Bigger
and
bigger
and
bigger,
and
then
the
poor
person
who
has
to
upgrade
from
v1
to
v2
is
like.
Oh,
I
got
to
make
all
these
changes
in
areas
that
I
don't
really
care
about,
because
they've
piled
on
all
these
massive
things
right.
So
the
idea
is
we're
allowing
you
to
in
phase
in
breaking
changes
incrementally
over
time.
So
keep
your
eyes
open
for
those
ugly
underscore
v2s
they're
ugly,
for.
B
B
You
will
get
all
these
locations
in
your
code
where
you
need
to
upgrade
immediately
like
it
would
be
just
build
errors,
whereas
a
rest
call
well,
unless
you
have
a
test
suite
that
will
actually
call
the
api,
like
you,
won't
see
it
until
then
right
so
an
sdk
like
gives
you
the
head
start
in
whatever
upgrade
you
want
to
do
like
hey.
These
are
the
five
things
in
your
code.
You
have
to
change
because
now
you
went
from
view
one
to
two.
C
A
Now
now
coming
back
on
the
the
sdk
discussion,
that's
actually
a
super
important
discussion
because
I
know
daryl
is
super.
Super
passionate
about
generating
sdks
from
the
api
surface
can
actually,
let's
talk
about
that
one
as
well,
because
it's
super
important
that
people
understand
why
it's
auto
generated,
which
I
think
darrell.
You
agree
that
in
certain
cases,
is
not
always
the
most
beautiful
looking
code
as
such.
C
Don't
think
anybody
really
likes
auto
generated
code
right
it,
it
really
is
a
necessary
evil.
It's
it's!
The
fact
that
the
the
graph
surface
area
is
large
and
literally
it
updates
on
a
weekly
basis
and
when
you
combine
the
v1
and
the
or,
if
you
look
at
the
beta
api,
there's
literally
thousands
and
thousands
of
endpoints
and,
as
I
say,
there's
lots
more
in
the
pipeline
that
are
coming
and
that
just
it
would
require
a
team
ten
times
the
size
to
be
able
to
create
a
hand
generated
thing.
C
You
know,
having
said
that,
one
of
the
first
things
that
that
we
did
a
couple
of
years
ago
was
recognized
that
some
people
don't
want
to
use
those
auto-generated
models
and
we
explicitly
went
through
all
the
sdks.
Well,
not
all
yet,
but
we're
getting
there.
The
main
languages,
the
c
sharp
the
java,
the
javascript
and
broke
them
into
two
libraries,
a
core
and
a
service
library
and
the
core
is
the
part
that
provides
all
those
kind
of
cross-cutting
concerns
that
the
retry
handling
the
throttling
the
the
authentication
mechanism.
C
I
talk
about
customizing,
the
the
the
the
net
sdk
and
how
you
can
get
under
the
covers
and
just
don't
need
to
use
the
model
classes
at
all,
and
our
goal
with
regards
to
the
service
library
is
to
create
it
as
thin
as
possible.
It
is
really
just
a
shell
of
types
for
the
models
and
request
builders
and
request.
Builders
are
just
there
to
help
you
construct
a
valid
uri
and
help
you
construct
a
valid
payload
and
really,
if
you
don't
want
to
use
it,
it's
fine.
C
If
you
want
to
use
it
to
create
something
and
then
completely
customize,
that
request
with
your
own
variation
on
that,
you
want
to
insert
your
own
middleware
controls
that
do
cross-cutting
concerns
absolutely
completely
valid.
There
should
no
be
that
the
problem
that
people
come
up
with
with
sdks
is
it
it.
They
usually
take
some
kind
of
opinionated
stance
on
how
you
should
be
calling
the
api.
C
And
as
soon
as
that
opinion
doesn't
work
for
one
scenario:
it's
like
oh
wait.
I
have
to
start
from
scratch
and
build
more
of
my
own
infrastructure
and
then
it's
like
well.
I've
built
all
my
own
infrastructure
to
do
this.
One
scenario:
why
don't
I
just
use
all
my
info
on
infrastructure
for
everything
that
I
need
and
they
end
up,
throwing
the
sdk
away
and
that's
absolutely
what
we
wanted
to
get
away
with.
You
need
to
be
able
to
peel
the
onion
and
use
just
the
parts
that
you
want
to
use.
B
Yeah
plus,
I
guess
there's
another
thing
to
say
that
many
developers
know
this,
especially
especially
in
a
cloud
like
people.
Don't
always
know,
complexity
like
how
to
properly
deal
with
throttling
how
to
properly
deal
with
all
possible
exceptions
that
you
might
have
with
service
that
you
do
not
own
and
you
don't
always
know
how
it
exactly
works
under
the
hood
right.
So
an
sdk,
like
you,
said
the
core
piece
abstracts
all
of
that
away,
and
does
it
the
right
way
and
allows
you
to
focus
on
your
app
as
opposed
to
plumbing.
C
Yeah-
and
I
mean
there's
so
many
subtleties
like
just
like
a
redirect
rex-
are
simple
right:
yeah,
no
big
deal
right.
We
can
follow
redirects.
Well,
oh
yeah,
but
sometimes
libraries
will
handle
that
for
us
automatically.net.
They
handle
it
for
us
automatically,
but
then
the
the
basic
redirect
drops
the
auth
header
okay.
C
Well
then,
I
need
to
what
happens
all
of
a
sudden
I'm
getting
not
a
valid
auth,
but
then,
if
you're
going
and
downloading
a
onedrive
file,
if
you
bring
the
auth
header
with
you,
it
breaks
you
go
it
breaks
or
if
you
bring
another
header
with
you,
it
breaks
because
of
course
right
so
there's
a
whole
bunch
of
little
subtleties
and
then
you
know
you're
in
javascript
on
node.js
versus
using
the
fetch.
That's
there
versus
the
fetch
in
the
browser.
C
How
does
the
redirect
happen
in
those
kind
of
cases
and
and
yeah
throttling
is
an
even
more
tricky
situation
so
and
the
idea
is
that
somebody
shouldn't
need
to
know
all
the
peculiarities
of
the
http
spec
I
mean.
Caching
is
another
one.
It's
one
thing
that
we
haven't
got
around
to
yet
providing
an
out-of-the-box
client-side.
Caching
piece
of
infrastructure,
but
I
would
love
to
be
able
to
do
that
and
it's
just
not
obvious
how
to
make
that
work
transparently.
But
you
can.
A
Yeah
yeah
cool
just
from
a
timing
perspective.
Let's
do
some
articles,
let's
get
back
on
the
on
the
discussion.
So
that's
because
we
do
have
a
heart,
stop
have
passed
and
why
am
I
saying
have
passed
out
loud
because
nobody
can't
really
understand
what
it
means
when
they're
watching
or
listening
this.
A
Okay,
cool
some
new
articles
from
last
week,
some
cool
stuff
for
the
microsoft
themes,
a
monthly
summary,
a
lot
of
cool
stuff
happening.
The
meeting
and
calling
and
meeting
applications
are
coming
as
well,
but
there's
a
lot
of
lot
of
out-of-the-box
capabilities
and
this
one
is
actually
pretty
cool
as
well
you,
so
you
can
explicitly
animate
people
if
you
have
your
attendees
muted
by
default,
which
is
actually
really
cool,
helps
under
our
community
course
as
well.
If
we
want
to
go
there,
but
I
think
especially
for
education,
services
and
navigation
setups.
I
think
that's.
A
That's
super
super
important
now
scrolling
in
here
down
there's
a
lot
of
a
lot
of
cool
stuff
available
for
the
microsoft
teams
and
then
obviously
there's
a
lot
of
new
stuff.
Also
in
the
platform
side
of
the
house,
there's
a
few
things
which
I
wanted
to
actually
mention
and
call
them
up
so
power
automate
and
there's
an
awesome
integration.
There,
organizational
branding
line
of
business
teams,
application
catalog,
apparently
a
big
thing
to
get
your
logo
of
visible
there.
Well,
okay,
fine,
not
necessarily
a
huge
thing,
but
this
is
actually
really
cool.
A
But
okay,
yes,
basically
specific
consent
is
now
g8,
and
so
you
can
actually
grant
permission
only
to
a
specific
team
which
is
actually
whatever
or
channel
or
whatever
it
is
yes
indeed
and
sharepoint
is,
is
actually
adapting
this
gradually
as
well.
So
there
will
be
then
at
some
points
we'll,
hopefully
have
the
sharepoint
site
behind
of
the
teams
cram
that
in
the
same
level,
and
all
of
that
so
but
again,
multiple
teams
makes
life
much
more
difficult,
different
priorities
and
all
of
that
stuff.
A
So
if
things
are
moving
in
different,
let's
say:
pace
app,
certification,
publishing,
publisher
verification.
I
think
this
one
also
super
important
thing
as
well,
because
it's
actually
free
for
partners
just
to
get
the
verification
right
now,
at
least
it's
completely
free.
So
it's
a
really
great
way
of
getting
acknowledged
and
verified
by
the
microsoft
as
well,
so
really
really
cool
stuff
as
well.
So
the
customers
and
consumer
side
of
the
application
will
know
that.
A
Okay,
this
company,
like
here
the
contoso
organizer,
has
been
confirmed
to
be
contoso
because
technically
you
never
know
unless
it
has
been
explicitly
confirmed
now
on
sharepoint
side
of
the
house.
A
lot
of
stuff
there's
a
lot
of
out-of-the-box
stuff,
sharepoint
syntax
is
now
gonna
gonna
get
more
and
more
visible.
A
I
think
it's
now
g8,
since
ignite
will
actually
do
a
getting
started
on
syntax
in
the
week
from
now
on,
a
sharepoint
monthly
community
call,
which
is
pretty
cool,
so
sean
squires
is
gonna
drop
by
a
lot
of
out
of
out
of
the
box
capabilities
improvements.
Microsoft
lists
all
of
this
stuff.
Everything
is
available
to
get
surfaced
properly
in
microsoft,
teams,
which
is
almost
in
the
direction
where
everybody
is
now
heading.
So
getting
everything
inside
of
the
themes.
Is
it
microsoft,
lists
or
not?
A
You
can
surface
that
in
the
microsoft
teams,
as
well,
onedrive
widget
for
iphone,
that's
actually
pretty
cool
as
well.
So
this
relatively
reasoning,
more
a
consumer
side
of
the
house,
but
on
this
day
photos-
and
I
just
these-
are
really
good
because
it's
almost
like
the
facebook
on
this
day
or
the
historical
thing,
but
it's
on
your
photos
without
the
social
media
burden
and
without
getting
access
on
and
sharing
things.
So
it's
just
photos
which
you've
taken
in
the
phone.
A
That
was
when
in
there
and
there
I
went
over,
I
wonder
what
happens
anyway,
a
lot
of
a
lot
of
stuff
happening
on
that
side
as
well.
Now
there
was
also
a
new
microsoft
teams,
toolkit
version
coming
out
last
week.
So
a
version
one
point
one
point
one:
it
was
actually
one
point,
one
the
actually
that
there's
apparently
under
as
a
small
update
on
that
one
as
well.
A
I
think
it
was
monday
and
then
wednesday,
a
small
update
on
that
and
there's
a
changelog
available,
which
is
basically
then
listing
all
of
the
the
different
updates
which
is
happening.
So
it's
really
cool,
it's
good,
that
this
is
moving
forward
as
well,
slightly
related,
not
a
competing
thing,
your
teams.
So
if
you
choose
to
use
typescript
and
node.js
as
the
back-end,
that's
when
you
use
your
teams
and
there's
this
basically,
the
the
microsoft
teams,
toolkit
users,
then
javascript,
and
it
has
a
slightly
different
way
of
implementing
things.
This
one.
B
Sure
so
we've
done
two
big
things
which
is
one
is
we
had
to
replace
the
in
our
inner
workings
of
cli?
If
all
is
well
as
a
user,
you
will
not
see
anything
from
it,
but
over
time.
So
when
we
would
start
working
on
cli
three
years
back,
we
chose
a
package
to
offer
us
the
ability
to
have
commands
and
help
and
everything,
and
over
time
we
saw
that
that
package
wasn't
maintained
anymore.
So
we
decided
like
okay,
so
that
is
too
much
for
us.
Let's,
let's
just
do
the
few
things
that
we
need.
B
A
Cool
cool
things
are
moving
on
that
side
as
well.
Now
that's
an
interesting.
The
the
removal
of
warpl
is
an
interesting
example
of
the
open
source
community
in
their
system.
Everybody
across
the
world
that's
using
open
source
and
building
their
stuff,
but
then
you
had
a
dependency
on
something
which
is
a
fully
open
source
and
all
of
a
sudden
nobody's.
Updating
that
or
the
whole
team
is
gone,
and
it's
like
well.
A
C
Now,
when
you
move
into
like
the
web
world
and
asp.net,
it
gets
a
little
bit
more
complicated
because
what
you're
doing
is
you're
taking
some
kind
of
credentials
that
came
in
on
the
inbound,
I.e
like
if
you're
building
a
web
app
somebody
signs
in
with
an
oauth
2
flow
or,
if
you're
doing
an
api
they're,
making
a
call
with
a
token
to
that
particular
api.
But
then
what
happens?
C
If
you
want
to
call
another
api
on
the
background
in
in
behind
the
scenes,
you
need
to
do
a
token
exchange
or
you
need
to
get
a
new
token
for
the
back
end
api
based
on
the
credentials
that
came
in
from
the
front
end,
and
so
that's
what
microsoft
identity.web
does
now.
If
it
turns
out
that
you
want
to
call
microsoft
graph
on
the
back
end,
you
can
layer
this
extra
microsoft.identity.web.microsoftgraph
in
there
and
it
just
allows
you
in
an
asp.net
web
app
to
just
as
you're
setting
up
the
security
say.
A
That's
that's
completely
natural
because
it's
all
about
abstraction
layers
and
making
it
easier
for
people
to
consume
things.
It's
just
then.
The
only
challenge
is
always
to
educating
people
that
hey
now,
there's
even
easier
way
to
do
things
and
then
making
sure
that
they
can
see
the
guidance
of
that
there's
an
easier
way
to
do
things
so
yep.
C
A
Excellent
excellent
cool
now
and
there's
a
a
release,
notes
and
that's.
This
is
basically
then
walking
through
and
the
latest
release
and
what's
actually
happening
over
there
as
well.
Now,
a
few
community
articles
from
mvps,
so
joe
ferreira
had
a
how
to
create
an
rss
reader
using
sharepoint
news,
a
a
kind
of
a
good
list
of
things
and
clarification.
How
to
make
things
happen,
using
power
automate
right.
B
A
A
A
Something
yeah
and
could
be
this
way
of
doing
that,
but
now
he
included
here
a
craft
sdk
in
the
console,
so
you
can
actually
easily
do
then
calls
directly
in
the
in
that
tooling
and
that's
a
chrome
extension
which
work
in
the
edge
chrome
as
well
and-
and
you
can
easily
access
information,
do
modifications
on
live
files
behind
of
the
scenes
and
all
of
that
stuff.
It's
actually
surprisingly
flexible
tool,
and
I
know
that,
as
an
example,
volo
intranet
to
build
stuff
for
microsoft.
A
A
Good
patrick
lambert
had
a
deploy,
spfx
web
part
using
github
actions
and
the
cli
for
microsoft,
resistive,
five
and
so
the
cli
for
microsoft,
365,
there's
quite
a
lot
of
actually
automations
related
on
ci
cd
operations
right
welding,
yes-
and
this
is
basically
walking
through
then.
How
do
you
do
that?
A
How
do
I
make
that
automation
work
not
doing
things
manually,
but
automating
deployments
here
we
have
an
entry
from
ram,
creating
user
scope,
property
and
spfx
web
parts,
so
basically
dynamically
changing
the
webpart
behavior
on
the
user,
which
is
pretty
cool
as
well,
and
a
video
format
before
and
more
videos
which
community
is
doing,
which
is
actually
great
as
well
and
walking
through
that
implementation
in
typescript.
So
pretty
cool
and
there's
a
sample
available
as
well,
and
this
one
is
from
our
design
guard.
A
A
Ui
container
scratch
and
then
walking
through
the
different
layouting
and
scaling
on
that
one.
So
that's
really
cool
as
well
and
he
had
another
one
actually
more
than
a
week
ago
with
where
he
walks
through
how
the
background
section
design
should
be
implemented
in
spfx
web
parts,
and
this
is
something
which
is
actually
more
advanced
than
our
official
documentation,
which
will
be
then
updated
based
on
this.
So
we
already
talked
about
that
one
of
stefan
so
because
it's
a
much
cleaner
implementation.
What
we
officially
recommended
so
ideally.
A
But
people
can
take
those
into
account
and
install
their
tenants
and
they're
using
the
microsoft
craft
behind
the
scenes
and
there's
a
few
set
of
a
few
things
which
you
always
need
to
do
is
like
like
setting
up
the
applications
in
azure
and
all
of
that,
then
this
walks
through
the
different
requirements
making
it
super
easy
and
what
to
set
it
up
in
the
tenant
and
then
start
actually
testing
things.
So
really
cool,
and
you
know
by
weekly
community
course
we're
actually
covering
every
single
time
of
one.
A
Microsoft
themes
have
templates,
it's
pretty
cool
as
well,
so
on
the
one
of
the
bi-weekly
calls
on
thursdays.
Now,
one
more
from
ferreira.
He
had
three
articles
from
this
week
all
tagged
with
a
hashtag
bmp
weekly.
So
we
want
to
make
sure
that
we
covered
them,
but
how
to
post
sharepoint
newslink
programmatically,
so
basically
how
to
post
the
sharepoint
news
article
using
an
api
which
isn't
officially,
however,
documented-
and
this
is
one
of
those
things
where
daryl
is-
is.
A
So
basically,
this
is
a
native
sharepoint
online
api
which
the
quite
typically
partners
are
then
reverse
engineering,
and
then
they
can
use
it.
But
we
do
not.
Since
it's
not
documented,
we
do
not
guarantee
that
not
be
broken
in
the
future
and
then,
although
also
the
right
way
would
be
to
have
all
of
this
in
the
microsoft
craft,
so
that
the
first
body,
the
future
feature
engineers
who
are
responsible
of
this
capability,
would
implement
that
directly
in
the
microsoft
craft.
And
then
everybody.
A
A
And
this
one
is
really
good
from
sarah
huss
and
what
is
a
a
a
project
cortex
and
what
is
the
sharepoint
syntax?
So
what's
the
difference
between
two,
these
two
things
so
really
walking
through
that
one,
and
I
have
a
discussion
with
the
other
people
in
the
recording
365
on
that.
So
really
good
extra
clarification.
What
it
is
so
briefly,
just
explaining
sharepoint
context
as
soon
as
a
separate
context
is.
A
And
then
the
final
video
from
youtube
is
from
aisha
bus,
a
build
and
one
productivity
hub
solution
using
microsoft
teams,
microsoft,
craft
toolkit,
it's
a
really
cool
setup
and
a
summary-
and
I
think
this
isn't
super
super
long.
Just
a
couple
seconds.
36
minutes
walking
through
how
to
make
things
happen,
so
really
really
cool
stuff
as
well.
A
A
C
Oh
no,
this
is
the
week
that
everything
exciting
happens.
Yes,
I'm
actually
hacking
around
on
on
building
tooling,
to
help
our
api
review
process
so
that
we
can
better
visualize.
When
teams
come
to
us
with
api
reviews,
we
can
understand
how
it
impacts
the
larger
graph
api
and
be
able
to
provide
quicker
and
more
accurate
guidance
to
the
team.
So
that's
what
I'm
playing
around
with
this
week.
B
A
A
A
So
you
can
actually
come
up
with
a
hobby
hobby
project
and
build
that
and
then
show
it
off
on
the
end
of
the
week
or
next
week,
and
and
there
are
actually
really
huge
products
in
microsoft,
portfolio
which
have
come
and
started
from
somebody
actually
doing
a
fixed
section
week
and
then
people
are
like
well.
This
is
awesome.
We're
gonna
make
this
huge.
So
I
think
it's
an
awesome
opportunity
for
everybody
in
microsoft
to
actually
really
innovate
and
do
something
crazy.
So.
B
B
I'm
hoping
that
we
will
be
able
to
publish
a
new
quick
start
for
the
microsoft
graph
toolkit
and
and
react,
so
I'm
trying
to
explain
better
how
it
works.
How
you
can
can
use
that
in
react,
apps
other
than
that
I've
just
submitted
apr
to
update
the
sharepoint
starter
kit.
One
of
the
web
parts
to
use
mgt
react
other
than
that
there
are
a
few
things
still
in
flux,
so
no
announcement
there
yet,
but
things
will
be
coming
out
hacking
away.
A
Yeah
there's
a
lot
of
a
lot
of
stuff
which
we're
being
built
on
by
end
of
this
year.
We
need
to
get
stuff
ready
and
so
that
the
second
half
we
can
restart
from
a
clean
slate
so
to
say
so,
but
there's
a
lot
of
kind
of
cool
stuff
happening
as
well.
I'm
not
gonna.
Actually
I
can't
talk
about
what
I'm
doing
this
week,
because
yeah
right
anything.
So
I
cannot
talk
about
it.
Yes,
yes,
anyway.
Thank
you,
daryl
for
joining
us
for
the
quick
check.