►
From YouTube: Microsoft 365 PnP Weekly – Episode 130
Description
In this 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 the Software Engineer behind the Microsoft Graph Toolkit, Nikola Metulev (Microsoft) | @metulev. Topics discussed – Microsoft’s commitment to Community and open source, Nikola’s evangelist roots and open-source learnings, how Microsoft Graph Toolkit (MGT) came about and 6-month roadmap. Each participant outlines their week’s focus – how about a new Teams SSO provider! Microsoft and PnP Community delivered 18 articles in the last week! This session was recorded on Monday, June 7, 2021
References:
• See the full blog post for this episode at https://aka.ms/m365pnp/community/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
B
Welcome
everybody:
this
has
been
for
weekly
episode,
130,
it
is
7th
of
june
2021
and
let's
actually
get
started
in
the
pmp
weekly.
We
talk
about
the
latest
on
microsoft,
365
areas,
concentrating
on
the
platform
and
non-platform
topics.
My
name
is
cersei
evan
and
I'm
a
program
manager
in
the
microsoft
resistive
platform
areas
with
me
as
a
co-host.
This
waldek,
who
are.
C
A
C
B
A
Are
one
microsoft
right,
microsoft,
365
includes
windows
includes
office
includes
all
kinds
of
things.
My
role
at
microsoft
is
to
work
with
the
developer
community
and
to
find
patterns
and
things
where
we
could
help
the
developer
community.
You
know,
do
things
faster?
How
can
they
get
accelerated
and
get
started
from?
I
have
an
idea
and
want
to
implement
an
idea
and
not
get
stuck
into
the
weeds
of
implementing
authentication
or
trying
to
get
pulled
data
in
you
know.
How
do
I
get?
A
So
that's
kind
of
the
approach
that
we
take
is
we
help
everybody
we're
not
focused
just
on
a
small
sliver
of
developers
that
we
kind
of
focus
on
in
our
organization
just
because
we're
on
microsoft,
we
want
to
make
sure
that
everybody
is
handled.
Everyone
is
taken
care
of
and
that's
kind
of
how
we
approached
our
open
source
initiatives
so
far,.
B
A
B
C
A
Think
I
got
lucky,
I
think,
that's
what
it
is.
I
don't
think
it
was
anything
special.
I
got
recruited
out
of
college
and
I
joined
strata
college
into
our
at
the
time
was
an
evangelism
organization.
It
was
dp
and
that
was
called
dx.
So
my
role
was
essentially
just
be
an
evangelist
go
and
talk
to
students.
Go
talk
to
people
go
build
demos.
A
A
We
made
videos,
blog
posts,
all
kinds
of
stuff,
so
my
history
has
always
been
working
with
the
community
and
kind
of
partnering
with
the
community.
I
was
never
a
traditional
program
manager
or
a
software
engineer,
and
I'm
still
not
it's
just
my
talent,
software
engineer
and
my
role
has
slowly
evolved
over
the
years
to
do
different
things.
I've
worked
on
startable
windows
8
at
the
time,
worked
on
xbox
one
when
it
first
came
out,
so
I
was
in
advantage
for
xbox
one
and
worked
with
our
xbox
one
partners,
app
partners,
building
applications
for
xbox.
A
Then
windows
10
came
around,
so
it
was
a
windows,
10
sort
of
evangelist.
We
created
the
windows
community
toolkit
at
the
time,
which
was
our
first
big
open
source
project,
which
is
now
really
big,
and
about
few
years
ago
I
switched
over
to
focus
more
on
the
graph
on
microsoft
graph,
I'm
still
in
the
same
team,
and
we
created
the
microsoft
graph
token
at
a
time.
A
So
it's
kind
of
been
very
boring
but
kind
of
moved
on
many
different
things,
while
still
working
on
the
exact
same
team
and
I
feel
like
I've
been
lucky
to
be
on
a
team
that
has
the
flexibility
to
work
on
so
many
different
things
and
kind
of
work
with.
So
many
amazing
people-
and
you
know
it's
it's
just
luck
honestly.
A
B
Actually,
quite
a
nice
journey
on
seeing
all
of
the
different
things,
and
and-
and
I
guess
one
of
the
reasons
why
it's
getting
why
you
are
kind
of
in
the
microsoft
graph
and
microsoft.
365
areas
is
that
the
windows
is
now
part
of
the
larger
microsoft
365.
So
it
kind
of
makes
sense
that
we're
all
in
this
pickup
family
and
anyway,
I
personally
now,
I'm
closing
into
15
years
in
microsoft,
there's
more
and
more
than
one
microsoft
mentality,
which
is
really
good.
B
A
I
think
part
of
my
organization
in
the
windows
org.
We
have
a
thing
saying
say
that
says
pick
an
ore.
Basically
meaning
you
know
help
others,
you
know
don't
kind
of
sit
and
watch,
but
if
you
think
you
can
help
just
grab
an
ore
and
just
gonna
go
with
them
and
go
help
them
out,
and
I
think
that's
how
I
see
my
role
is:
go
help
wherever
I
can
use
my
talents
and
my
skills
kind
of
help,
others
going
to
be
successful
and
that's
kind
of
what
we
do.
B
A
A
Do
you
have
anything
that
you
know
I
could
be
kind
of
doing
something
else
and
he
said
well,
you
know
the
microsoft
graph
is
now
becoming
pretty
big
and
let's
see,
if
there's
something
we
can
do
and
help
there
can
you
go
and
kind
of
work
with
the
microsoft
graph
team
and
go
figure
out.
How
can
we
help
so?
I
went-
and
I
basically
spoke
with
with
ena
and
other
folks
on
the
microsoft
graph
team
said:
hey.
How
can
we
help?
A
What
is
it
that
we
could
do
to
kind
of
help
you
out
going
to
bring
our
skills
into
this
and
working
on
the
windows?
New
toolkit
controls
was
kind
of
the
main
thing
that
we
did
and
kind
of
went
from
that
aspect
from
is
like.
Maybe
I
can
do
something
similar
there.
So
I
talked
to
the
graph
team.
They
pointed
me
to
some
partners.
I
talked
to
some
partners.
A
I
talked
to
a
bunch
of
meps
and
kind
of
started,
getting
feedback
of
what
is
it
that
what
are
some
of
the
pain
points
that
people
are
seeing
with
the
graph
that
intersect
with
the
skills
and
capabilities
that
we
have
on
my
team,
and
it
turned
out
that
there
was.
We
always
heard.
You
know,
authentication
is
not
easiest,
it
could
be.
You
know
I
want
to
get
started
faster
authentication,
and
you
know
we.
We
love
the
existing
controls
that
already
exist,
but
they're
in
react
right
now
and
they're
not
functional.
We.
A
A
So
it
was
just
like
okay,
let's
try
this
out,
so
we
built
a
the
toolkit
as
a
prototype
early
2019
and
we
demoed
it
to
the
mvps
first,
I
think
at
the
mmp
summit
and
we
got
really
positive
feedback
for
it
and
that
kind
of
gave
us
encouragement
you're
going
to
keep
going
and
we
announced
the
preview
at
build
that
ear.
We
got
even
more
positive
encouragement
from
that,
and
then
it
was
a
full
1.0
release
that
same
year.
A
I
think
in
september,
at
ignite
where
we
announced
it
and
ever
since
then
we
got
more
and
more
adoption
and
exponential
adoption
in
fact,
and
people
have
been
loving
it,
so
it
feels
like
it's
been
a
good
good
bet
on
our
end
going
to
go
with
that.
It
seems
that
people
want
to
do
this.
They,
like
the
flexibility
and
easiness
of
the
toolkit.
B
Absolutely
and-
and
you
have
the
well
the
the
number
one
pain
point-
what
I
said
that
comes
up
we're
having,
for
example,
one-to-one
discussions
with
long-term
partners
together
with
waldeck
and
the
the
number
one
thing
that
everybody
comes
up
with
is
the
authentication
and
and
the
the
how
difficult
it
is
to
make
things
happen.
But
how
did
you
solve
that?
And
there
you
there's
some
sort
of
a
provider
model.
A
You
know
what
I
don't
think
I
solve
authentication
at
all.
I
don't,
I
don't
think
the
solving
authentication
we
just
took
the
the
95,
whatever
making
up
a
percentage
here,
but
the
majority
of
what
people
need
from
authentication
the
code
they
need
to
write.
We
kind
of
just
packaged
it
into
a
very
nicely
we'll
call
a
provider
where
you
just
one
line
of
code.
You
put
on
your
page
the
code
where
you
would
have
to
write
anyway.
A
You
just
put
it
on
there
and
then
you
put
it
on
your
page.
It
works
for
vast
majority
of
people.
That's
all
they
need
now.
If
you
want
to
do
more,
if
you
want
to
advance,
of
course,
you
you
still
use
all
the
usual
authentication
libraries,
but
we
build
everything.
On
top
of
m
cell,
we
built
everything
on
top
of
the
existing
attachment
library.
We
just
write
all
that
code.
That
developers
would
have
to
write
themselves
anyway
and
we
can
abstract
that
away
from
them.
It's
it's
that
easy.
A
We
made
the
decision
to
abstract
away,
how
authentication
works
and
how
components
work.
So
you
don't
have
to
think
about
like
how
do
I
now
get
data
into
my
components?
How
do
I
now
call
the
graph?
How
do
I
know
I'm
authenticated?
How
do
I
know
I
need
to
sign
in
or
sign
out
so
we
made
it
so
you
just
put
a
provider
on
your
page.
A
You
put
a
component
on
the
page
and
they
kind
of
magically
know
how
to
talk
to
each
other
and
they
need
to
kind
of
call
each
other
and
that
actually
worked
pretty
well
right
now
and
we
separated
the
two
so
a
developer.
If
they
have
authentication,
they
can
still
use
the
components
they
just
have
to
write
a
function
that
just
tells
the
components
how
to
get
tokens
or
if
you
just
want
to
use
the
authentication
without
the
components
you
can
do
that
as
well.
So
you
can
just
start
getting.
A
All
they
did
all
the
hard
work,
but
they
just
want
the
components
they
just
want
an
agenda
on
the
page.
They
just
want
a
peel
picker
and
it
just
works
really
well,
so
we
kind
of
focus
on
those
type
of
scenarios,
so
you
can
quickly
and
easily
add
whatever
they
need
from
the
toolkit
without
requiring
everything
right.
B
Now
related
on
that
one,
actually,
that's
that's
a
good
point.
This
is
you
kind
of
mentioned
this
already
in
the
between
the
lines
on
your
previous
answer.
But
how
does
this
now
then
relates
on
the
fluent
components,
because
the
fluent
is
the
ux
components
and
the
buttons
and
everything
else.
So
is
this
the
competing
set
of
controls?
What
what
is
happening?
This
is
so
confusing.
So.
A
No,
the
way
we
see
the
graph
toolkit
is
built
on
top
of
the
fluent
components
right
so
you're,
using
fluent
ui
in
and
on
top
of
that
you're
using
the
graph
toolkit.
You
don't
have
to
use
them
at
the
same
time,
but
they
work
best
when
they're
used
at
the
same
time,
just
because
the
graph
toolkit
is
built
on
top
of
the
same
ui
and
same
design
system
as
fluent
ui
and
then
in
the
future.
We're
actually
even
blurring
the
lines,
not
blurring,
but
we
actually
work
even
closer
together
with
the
fluent
ui
folks.
A
In
the
past
there
wasn't
because
we're
built
on
web
components.
We
couldn't
use
the
react,
fluent
ui
components,
but
now
that
the
fluent
team
has
built
web
components
we're
working
with
them
to
actually
build
all
of
our
components
off
of
the
fluent
ui
web
components.
So
now
the
same
teaming
will
work.
The
same
styles
will
work
and
everything
will
be
exactly
the
same.
So
you
use
fluent
ui
and
you
just
add
a
toolkit
component
and
you
install
it
the
exact
same
way.
A
It's
built
on
top
of
the
exact
same
components
and
the
way
we
see
ourselves
is
we
look
at
the
the
functionality
we
bring
as
part
of
the
toolkit,
not
the
ui
components
themselves
like
there's
all
these
components
that
the
fluent
ur
provides
that
don't
need
to
be
functional.
We
provide
the
more
complex
functional
parts
of
of
that
that
people
need
patterns
that
people
need
inside
their
applications.
B
B
Yeah
yeah
makes
perfect
sense
cool.
Now.
How
do
you
so
so,
of
course,
the
craft
surface
is
massive,
so
we
can
imagine
from
a
community
perspective
and
customer
important
perspective
that
you
probably
have
a
set
of
controls
like
50
60
road
map
controls
available
in
the
in
the
back
end.
How
do
you
prioritize
all
of
this?
How
do
you
come
up
with?
Where
are
we
investing
first
or
second
or
third.
A
Most
of
our
work
has
currently
been
prioritized
by
the
work
we
do
with
the
community
and
the
isps
partners.
So
we
the
way
we
work
with
partners
is
we
go
and
talk
to
them
like
what
would
they
need
and
if
there's
something
that
they
need,
that
we
don't
have
in
the
toolkit?
We
prioritize
that
first
and
the
way
we
prioritize
it.
We
only
build
it
if
we
can
build
it
in
a
way
that
can
be
used
by
everybody,
we're
not
going
to
build
a
control.
A
That's
super
specific
for
a
specific
scenario:
we're
only
going
to
build
a
component
that
works
for
everybody,
we're
not
going
to
build
this
little
widget
that
I
need
in
my
application
that
this
is
a
very
specific
thing.
We're
not
going
to
build
anything
like
that.
But
if
somebody
needs
like
a
file
list
who
recently
was
asked
a
few
months
ago,
we
said
well
yeah.
We
can
see
a
lot
of
people
needing
a
file
list.
You
can
see
this
being
styled.
A
We've
seen
this
being
customized
to
be
fit
into
different
scenarios,
we'll
go
ahead
and
build
this.
This
component
and
kind
of
help
everybody.
We
also
work
with
the
community.
The
community
goes
on
our
issues
and
they
suggest
components
and
we
talk
to
them
and
we
figure
out.
What
is
it
that?
Why?
How
do
you
see
this
component
being
used
by
other
developers?
Is
this
something
that
only
you
need,
or
do
you
see
others
needing
this?
A
Then
we
ask
others
to
come
in
and
contribute
to
that
discussion
and
say:
hey
do
others
need
this,
and
if
we
see
a
signal
that
this
is
something
that
more
than
than
a
handful
of
people
need
this
then
we'll
go
ahead
and
invest
in
it
or
we'll
work
with
the
community
to
build
it.
We
are
open
source
in
a
way
not
you
know,
we
build
things
in
the
open,
but
we
work
with
the
community.
B
A
C
A
You
know
for
all
the
production
stuff
that
I've
built
has
always
been
open
source.
I
think
we've
always
started
open
source.
We've
contributed
code,
closed
source
to
windows,
we've
contributed
code
to
other
projects,
we've
contributed
code
to
partners
which
have
closed
source,
but
for
the
work
that
we
do,
it's
always
been
open
source
because
we
like
to
scale
things
we
everything
we
build.
We
want
to
have
an
impact
across
the
entire
community
and
we
don't
want
to
have
something.
That's
only
for
a
specific
thing
right
unless
it's
going
to
help
everybody.
A
C
Right
and
so
because
the
reason
I
asked
is
like
different
folks
who
come
from
different
backgrounds,
have
different
experiences
with
open
source
and,
like
many
folks
start
really
in
their
shared
passion
like
yeah.
Let's
do
open
source
and
then
they're
like
oh
yeah,
but
there's
like
random
people,
submitting
issues.
There
are
pr's
and
we
need
to
do
something
about
where
we
have
to
have
opinion
or
things
right
so
and
it
pretty
quickly
becomes
the
reality
that
it
requires
a
mindset.
It
requires.
C
A
You
know
what
it's
something
that
we've
learned
over
time.
Our
approach
has
we
never
really
thought
about
the
future
in
the
past.
If
that
makes
sense,
it's
evangelist
you're
going
to
think
at
the
moment.
It's
like
what
is
this
that
I
think
I
can
build
right
now
and
can
I
get
people
to
use
and
obviously
you
kind
of
push
thing
on
to
github.
You
push
a
sample
to
github,
you
push
whatever
to
github
and
when
our
first
big
project
was
the
windows
community
toolkit,
we
first
started
going
open
source.
A
We
didn't
have
any
experience
with
actually
maintaining
a
project.
We
didn't
have
any
experiences
having
an
open
source
project
and
we
learned
a
lot
from
that
working
with
the
community
and
working
with.
I
think
we
had
several
mvps
early
on
before
we
even
went
public
kind
of
gave
us
feedback
was
like
hey.
We
want
to
do
this
open
source.
We
want
to
do
this
completely
with
everybody.
A
A
When
the
windows
community
toolkit
first
came
out
and
which
encouraged
others
once
they
saw
the
success
of
of
what
open
source
can
do
and
how
much
interaction
you
can
get
with
the
community
to
encourage
other
projects
in
windows,
org
to
start
going
open
source
and
starting
to
kind
of
adopt
that
same
model,
and
but
this
is
something
that
we,
like
microsoft,
started
doing
this
even
before
we
did
like
we
weren't
the
first
one
in
microsoft,
so
like
the.net
team
and
everybody
else
did
this
a
long
time
ago.
So
there's
other
ones.
A
B
A
You
know
being
responsive,
I
don't
know
if
it's
a
surprise
or
anything
but
being
responsive
and
being
nice
and
asking
questions.
It's
something
that
we're
not
that
we
weren't
that
used
to
at
microsoft.
I
think,
having
that
two-way
conversation
before
it
was
really
hard
like
before
we
were
used
to
kind
of
just
leaving
something
out
out
there
and
kind
of
say
hey.
We
built
this
thing,
go,
use
it
or
check
this
out
or
go
do
it.
A
But
having
that
two-way
conversation
and
getting
used
to
to
be
very
responsive
and
being
open
to
criticism
by
the
community,
it
was
something
that
took
getting
used
to
for
a
bit.
I
think
something
that
I
wasn't
really
expecting,
because
when
you
do
this
and
you're
not
really
expecting
what
to
happen,
you
just
I'm
gonna,
leave
this
out
there
and
see
what
happens.
A
Yes,
that
took
a
while
the
time
it
takes
to
build
something
in
the
open
versus
to
build
it.
You
know
closed.
Is.
Is
this
much?
It
requires
more
time.
It
requires
more
commitment
and
requires
you
know
more
focus.
It's
it's
a
whole
different
way
of
kind
of
building
things
and
something
that's
been
hard
for
a
leadership
to
also
understand
it's.
Like
hey,
you're
working
with
the
community,
the
community's
gonna
do
this
work.
You
know
it's
fine,
you
know
you
don't
need
to
work.
A
You
know
that
took
some
time
to
kind
of
get
even
our
leadership
to
kind
of
understand.
It's
like
no,
it's
actually
more
work
working
with
the
community,
it's
more
time
commitment,
but
it's
worth
it
because
we
get
back
so
much
from
doing
that
and
spending
putting
that
investment
into
into
the
work
that
we
do
with
the
community.
B
Is
this
really
true
or
not
exactly
yeah
so,
but
that
that's
actually
a
good
point
related
on
the
feedback
and
being
open
for
negative
feedback
as
well,
because
that
is
certainly
something
which
we've
seen
with
all
of
the
community
work,
whatever
they're
having?
And
you
really
need
to
grow
a
thick
skin
as
well,
which
is
because
it's
not
personal,
it's
just
when
you
do
stuff
as
an
open
source
and
with
community
there's
a
lot
of
anonymous
accounts
which
come
and
just
plainly
try
their
trolls
they're,
trying
to
just
have
fun,
be
on
your
coast.
B
C
Well,
and
also,
I
guess
that
with
github
in
place,
I
think
that
really
commoditized,
like
the
ease
with
which
people
can
criticize
submit
feedback
issues
and
at
times
people
have
bad
days,
and
they
will
react
to
it
by
submitting
an
issue,
whereas
in
the
past
like
if
they
would
have
to
go
through.
I
don't
know
20
hoops
like
by
the
time
they
went.
C
C
A
No
yeah,
that's
necessarily
right,
and
the
best
thing
we
can
do
is
just
be
calm
and
always
kind
of
respond
with
respect.
I
think
that's
the
biggest
thing.
It's
just
respect
and
no
matter
where
the
people
are
coming
from
and
just
treat
everybody
with
respect
as
a
maintainer
and
kind
of
say:
hey,
I'm
sorry
about
this.
How
can
we
make
this
better
and
can
I
go
from
there.
B
Because
it's
not
really
at
least
how
I
always
approach
this
is
that
it's
it's
not
never
a
personal
thing.
They
have
a
bad
day.
They
have
a
bad
feeling,
they
have
something.
And
yes
they
might
even
call
you
out
in
a
name.
But
then
the
easiest
way
to
calm
people
down
is
to
ask
and
apologize.
Because
me
apologizing
is
nothing
away
from
me.
B
It's
just
clearly
the
person
subjectively
is
being
hurt,
so
apologizing
is
not
a
bad
thing
and
then
asking
how
can
we
help?
So
it's
what
you
said:
being
human
right
yeah
exactly
exactly
now,
let's
jump
on
the
articles
and
then
come
back
on
a
discussion
after
that.
So
let's
go
through
some
of
the
news.
What
has
happened
throughout
the
week-
and
we
didn't
didn't-
actually
have
news
from
the
team's
marketing
this
week.
B
So
there's
no
news
from
the
team's
blog
but
sharepoint
released
their
may
2021
update
on
the
first
day
of
june,
but
anyway.
So
I
that
was
monday.
So
I
guess
that's
understandable
after
the
build
and
everything
else,
but
there's
a
good
discussion
with
yokesh
he's
a
one
of
the
the
migration
pm's
principal
program
manager
on
the
migration
site.
B
So
a
good
discussion
on
that
and
a
lot
of
a
lot
of,
let's
say,
improvements
on
the
sharepoint
side
and
as
we
can
see
from
here,
it
starts
with
the
yammer
conversation
insights.
So
a
lot
of
this
stuff
is
getting
now
more
and
more
merged
across
the
organizations
as
well.
So
it's
not
precisely,
maybe
the
back
end
the
sharepoint
or
maybe
the
back-end
in
teams,
but
then
it's
being
surfaced
in
multiple
locations,
which
I
think
it's
a
really
really
good
thing.
B
B
What
do
we
have
here?
External
sharing
and
lists
improvements
in
their
recommended
files
and
office
for
windows
and
microsoft?
365
we're
already
under
on
the
side
the
the
supported
things
a
lot,
a
lot
of
on
admin
side
as
well,
and
a
lot
of
updates
on
the
related
technology
in
the
build
right
now,
as
it's
like
week
after
two
weeks
after
build
not
a
massive
amount
of
new
announcements.
A
few
teasers
power
apps
can
now
display
images,
microsoft
list
and
sharepoint
center
homepage.
Insights
dashboards
is
coming
over
there
and
a
lot.
B
My
create
content
from
box
dropbox,
google
workspace,
microsoft,
365,
release
update,
so
there's
updates
related
on
the
migration
manager
in
the
sharepoint
admin
center.
So
you
can
actually
manage
your
migration
directly
from
the
admin
center,
which
is
really
cool
and
you
can
see
actually
the
the
status
and
all
of
that,
so
a
lot
of
a
lot
of
investments
and
improvements
in
here
as
well,
for
making
it
easier
for
people
to
migrate
on
the
microsoft
365..
B
Now
this
one
scroll
up
deep
dive
on,
we
are
learning
at
the
learning
transformation
briefing
so
update
on
the
viva
learning.
It's
still
in.
I
think
it's
in
private
preview
and
it's
not
available
yet
even
for
a
preview.
So
a
selected
group
of
partners
are
able
to
get
there
and
then
this
is
basically
an
update
on
what's
happening
on
the
vivo
learning
and
and
the
partners
and
some
feedback
from
them
now
maximizing
results
with
collaborative
work
management
in
microsoft.
365.,
that's
a
interesting
title,
really
impressive
title!
B
Isn't
it
but
a
lot
of
basically
a
summary
on
the
different
tooling,
and
how
do
you
actually
work
and
focusing
more
on
the
value
of
the
and
the
solutions
and
working
ways
of
doing
it
rather
than
the
products
which
is
a
good
thing?
I
think
this
is
a
natural
direction
where
we're
heading
with
microsoft,
viva,
and
so
we
don't
talk
about
the
explicit
products
necessarily
anymore.
We
talk
about
more
on
the.
B
B
Infographics,
thank
you.
So
a
lot
of
a
lot
of
different
kind
of
infographics,
as
well
now
available
on
around
this
stuff,
now
choose
the
right
microsoft
tool
for
managing
your
work
again,
similar
kind
of
message.
So
what
to
do
where,
as
an
example,
so
what's
the
difference
between
task,
app,
planner
and
tutor
versus
planner
list
and
project,
so
what
it
went
to
choose
once-
and
I
think
these
are
really
good,
because
quite
often
we
get
the
question
on.
Why
are
you
releasing
competing
products
which
we
don't
really.
B
Outlook,
you
know
there
is
a
reason
and
there's
a
kind
of
a
primary
objective
for
all
of
them
and
some
of
them
sometimes
some
of
the
features
are
overlapping
as
well
for
sure
it's
like
to-do
and
planner
and
tasks
which
anyway,
not
going
to
read
that
one
now
on
the
microsoft,
365
developer,
block
change
notification
extended
for
video
re-federated,
chats
so
updates
on
that
one
on
the
microsoft
class
side
of
the
house
are
really
cool
as
well.
So
just
follow
up
on
the
on
the
previous
announcement.
B
Then
there
was
a
universal
actions
in
adaptive,
cars
on
microsoft
teams
and
basically
aligning
the
outlook
and
teams
on
the
universe.
The
action
we
actually
did
have
a
demo
on
this
one
in
a
relative.
What
was
it
it
was
in
the
may,
microsoft
teams
community
call
as
well
now
so
was
just
explaining
this
and
covering
things
as
well.
This
was
basically
officially
then
announced
and
built
and
demonstrated
there
getting
started
with
craft
api
with
spfx
reports
from
chandani.
B
Shandani
has
been
blocking
quite
nicely
actually
in
the
microsoft
365
bmp
block,
and
that's
really
focusing
on.
How
do
you
do
things?
How
do
you
first
test
out
how
things
are
working
in
the
in
the
craft
toolkit
how
to
solve
the
permissions,
which
is
the
one
thing
which
might
be
always
a
difficult
thing
to
do?
What
are
the
permissions
needed
for
this
api
and
then
how
do
you
implement
the
things
and
how
do
you
write
the
code
to
hit
the
graph
apis?
B
B
A
No,
it's
2.2
yeah.
We
had
a
new
update
2.2,
it's
actually
the
biggest
update.
I
think
we've
ever
had,
because
it
has
so
many
new
things.
The
msl2
provider,
which
is
using
amstel
browser
behind
the
scenes
now
something
that
was
requested
heavily
by
the
community,
uses
a
much
more
secure
way
to
authenticate
in
single
page
applications.
A
It
also
enables
things
like
sso.
So
if
I'm
authenticating
on
the
back
end-
and
I
want
to
use
the
graph
to
put
on
the
front
end-
I
can
use
ssl
to
sign
in
on
the
front
end
as
well,
and
then
I
can
just
call
the
graph
directly
from
my
front
end
without
having
to
go
through
my
back
end
to
do.
That
also
adds
the
new
file
components,
which
are
also
very
heavily
requested,
like
the
file
in
the
file
list.
A
So
you
can
just
add
a
mgt
dash
file
dash
list
and
it
will
pull
in
your
onedrive
files
or
your
sharepoint
files
or
your
shared
files
or
your
inside
files,
whatever
it
is,
and
you
can
do
whatever
you
want
to
do
with
that
and
then
another
big
one
is
the
sharepoint
library,
thanks
to
waldek.
Actually,
who
built
this
yes,
which
fixes
the
issue
of
if
you
have
multiple
web
parts
that
use
the
graph
toolkit
on
a
page,
they
actually
conflicted
with
each
other
and
by
using
the
sharepoint
framework
library.
A
Now
you
can
actually
have
a
shared
mgt
instance
that
can
be
used
across
multiple
web
parts,
so
they
all
use
the
same
instance.
So
it
also
saves
you
know
space.
Oh
sorry,
sorry,
the!
How
much
how
big
your
web
parts
are
because
you're
not
shipping,
the
toolkit
with
your
web
part
and
you're,
using
one
that's
already
installed
on
that
sharepoint
page
yeah,
a
lot
of
good
stuff,
really
cool
stuff.
I
I
can't
wait
to
play
with
this.
B
So,
what's
going
on,
let's
talk
about
that
one
after
the
article.
So
what's
going
to
happen
next,
but
now
quick
recap
on
the
other
article
samba
script
quickly
remove
pending
ship
and
api
permission
requests.
So
basically,
if
you
have
been
in
a
craft
api
requests,
how
can
you
clean
up
that
pending
requests
using
cli
from
microsoft,
365.,
so
good
summary
on
that
one
from
this
guy
called
waldek,
so
using
sp
core
library
with
chest
from
martin
voshi
from
valo?
B
So
basically,
how
do
you
test
how
to
do
testing,
and
here
we
are
having
a
discussion
around
the
unit
testing
learnings,
what
he
has
he's
a
really
awesome
developer,
and
how
can
we
improve
that
within
the
product
and
also
externally,
for
the
third
party
now
earlier
today,
bert
johnson
released
a
the
new
version
1.12
on
the
bmp
core
sdk
and
basically
it's
a
wrapper
on
the
craft
and
sharepoint
rest
api.
So
this
is
basically
intended
to
make
it
easier
for
classic
sharepoint
solutions
which
are
using
sharepoint.
B
Rest
api
see
some
apis
to
start
transforming
to
the
spikes
of
graph,
so
making
it
easier
for
basically
abstraction
layer
on
top
of
those
apis.
So
everything
is
about
abstraction
layers
right
so
and
how
many
abstraction
layers
we
actually
built.
So
all
of
them
we
kind
of
built
all
of
them.
Now.
This
is
from
bj
kumar,
spfx
watch,
color,
ui
fabric
control
example.
So,
basically
how
to
build
this
kind
of
a
sample
and
update,
then
the
color,
the
buttons
and
the
colors
based
on
that
theming.
B
So
a
quick
blog
post
on
that
one
alex
sedumlux
had
a
blog
post
related
on
issue
with
bmpjs
ssb
site
exists,
called
when
debate
url,
condes
hashes-
and
this
is
basically
when
you're
using
spfx
one
of
those
super
widely
used
components
and
javascript
library
is
bmpjs
and
then
a
blog
post
related
on
a
potential
issue
there.
And
how
do
you
work
around
on
that?
B
So
how
do
you
solve
if
the
bias
site
exists
or
site
doesn't
exist,
so
basically
the
old
one
on
there
and
then
elio
had
a
blog
post
related
on
def
hack,
get
the
shared
file
info
for
microsoft
craft.
So
how
do
you
get
that
information,
and
how
do
you
make
things
happen
so
in
here,
peter
vinstra
had
a
blog
post
with
a
fancy
picture
power
automate
approvals
on
dataverse.
So
how
do
that
works,
cool,
graphics,
apparently
they're
by
the
way
doing
a
sequel
on
on.
B
C
B
Message
on
them,
anyway,
so
database
and
power
power,
automated
approvals,
getting
distracted
on
the
pictures
and
then
the
last
one
from
the
recording
365
from
danielle
and
daryl
around
the
custom
backgrounds.
Microsoft
teams,
together
mode,
which
is
the
classic
discussion
point,
has
been
from
a
day
one
that
whenever
we
get
this
somebody's
going
to
build
the
muppet
show,
and
of
course
that
has
been
built
now
technically.
B
B
B
A
You
know
what's
so
much,
I'm
you
know
I
can
ask
the
community
tell
us
what
they
want
to
see
in
there,
but
I'll
tell
you
what
weird
thing
I'm
thinking
of
and
what
the
roadmap
looks
like
the
next
six
months.
At
least
the
big
thing
that
the
new
msl2
provider
has
enabled
us
to
do
now
is
to
enable
to
support
multiple
accounts
and
something
I'm
really
excited
about.
A
So
we
have
actually
a
preview
of
a
login
component
that
enables
multiple
users
to
sign
in,
at
the
same
time,
an
application,
and,
if
folks
want
to
know
about
that,
they
can
kind
of
reach
out
to
me
on
twitter
and
then
I'll
point
you
to
the
right
branches
to
do
that.
But
it's
really
cool
like
you,
don't
have
to
do
anything
else.
Just
use
the
new
login
component
and
then
you
can
sign
in
as
many
users
account
as
you
want
on
your
application,
something
that
was
really
really
hard
before
to
do.
A
A
Speaking
of
I
mentioned
earlier
that
the
fluent
ui
team
has
released
the
web
components
fluently
web
components,
so
our
big
investment
for
the
next
I
wanna
say
six
months
at
least-
is
going
to
be
adopting
those
new
fluent
ur
web
components
and
building
the
entire
toolkit
on
top
of
those
lentil
web
components
that
it's
going
to
make
it
really
more
cohesive
with
the
fluent
ui
system.
So
for
folks
that
are
using
fluent
and
fluent
ui
and
the
web
components,
it
will
be
just
as
if
you're,
using
the
fluidic
web
components
with
just
same
thing.
A
It's
going
to
be
a
big
investment
that
we're
doing
it's
going
to
require
us
to
rewrite
a
lot
of
different
things,
to
kind
of
adopt
those
things,
but
it's
going
to
make
it
really
faster
for
us
to
build
new
components,
because
before
we
had
to
write
our
own
components,
we
had
to
write
all
the
small
things
we
had
to
write
an
input
box
to
write
a
button
but
to
write
all
the
different
things
that
didn't
exist.
Now
that
full
neural
web
components
exist,
we
can
move
much
faster
to
iterate
and
build
new
components.
A
On
top
of
that,
of
course,
we're
going
to
continue
working
on
new
components,
there
was
a
suggestion
by
waldick
actually
for
a
new
upload
file.
Upload
component
and
there's
interest
from
the
community
sounds
like
that.
Somebody
wants
to
implement,
or
at
least
work
on,
a
specs,
so
we're
kind
of
pushing
that
through
and
hopefully
we're
going
to
see
something
like
that
in
the
future
file
file,
picker
and
other
things.
A
A
So
if
people
search
for
help
wanted
or
good
first
issues,
we
have
a
bunch
of
those
for
folks
to
kind
of
pick
up
and
kind
of
work
on
things
with
us
and
kind
of
just
hang
out
with
us,
and
you
know,
stay
in
the
issues
or
hang
out
with
us
ask
questions
chat.
You
know
we're
kind
of
lonely
working
by
ourselves.
Sometimes
so
it's
good
to
have
friends.
B
A
A
A
A
C
No,
so
actually
what
have
we
done?
So
we
have
updated
recently
the
learn
for
mgt2.
We
have
updated
the
docs
where
we
documented
the
required
scopes
for
mgt.
So
us
all
that
it's
easier
for
you
to
decide
or
know
even
which
scopes
you
need
up
front.
If,
if
you
want
to
do
pre-consent
other
than
that
yeah,
what's
coming,
we're
we're
going
to
work
on
new
version
of
cli
we're
working
on
a
new
idea
that
allows
you
to
basically
pass
a
blob
of
html
to
it
and
cli
would
give
you
an
sppkg.
C
With
a
web
part,
so
kind
of
a
different
way
of
embedding
yeah
so
that,
if
all
you
want
to
do
is
embed
a
a
big
maps
on
your
web
page
right,
like
you,
don't
need
to
install
yeoman
and
gulp
and
toolkit
and
fiddle
with
javascript
and
typescript
and
building.
And
no
you
just
you
want
to
you,
get
a
piece
of
html
from
somewhere
pass
it
on
onto
cli
and
get
out
of
a
package
that
you
can
then
give
to
your
admin
to
install
intent.
B
C
Yeah,
exactly
exactly
I
mean
so
and
and
also
so,
including
that,
like
we
want
to
also
ensure
that
people
will
be
able
to
use
things
like
mgt,
where
there's
like
additional
script,
you
need
to
load
on
time.
So
it's
just
not
like
the
basic
html
things
like
iframe,
but
also
having
the
ability
to
access
things
like
the
context
of
the
page
or
the
context
of
teams
and
tap
into
that
and
also
including
mgt.
So
all
of
that
is
coming
hopefully
soon.
Oh,
that
sounds
so
cool.
B
That's
really
really
cool
and
now
anyway,
so
on
our
side,
I
think
the
big
focus
continues
for
sharepoint
framework
and
odsp,
especially,
is
the
the
vivo
connection.
So
vivo
connection
is
in
preview.
We
have
already
350
people
sign
up
for
the
preview,
which
is
just
and
the
overhead
of
actually
controlling
the
preview.
Access
is
getting
out
of
control,
but
it's
a
positive
profile
right.
So
more
people
being
excited
on
that
and
building
mobile
experiences.
B
Native
mobile
experience
is
rendered
in
native
react
format
and
directly
in
the
microsoft
theme,
so
that's
really
really
cool
for
sure,
and
then
what
else
is
happening
on
community
sites
to
community
calls
a
lot
of
stuff
happening
over
there.
I
also
actually
booked
my
summer
vacation
that
today
earlier
today,
which
is
really
really
good.
So
right.
B
B
Five
months
yeah,
yes,
I
was
thinking
this
earlier
today.
The
one
thing
what
I
actually
realized,
I'm
closing
to
15
years
in
microsoft-
and
this
is
the
first
time
actually
I'm
booking
a
proper
european
summer
vacation
and
without
feeling,
let's
say,
threatened,
losing
my
job,
because
because
of
that,
so
which
is
weird
it's
the
imposter
syndrome,
because
you
you're
always
like
afraid
of
yeah
yeah.
But
I'm
not
good
enough
and
I
think
a
lot
of
the
idea.
People
have
the
same
problem
and
it
doesn't
matter
how
many
years
you've
been
in
microsoft.
B
You'll
never
get
rid
of
it.
But
now
it's.
I
was
just
thinking
this.
The
first
time
ever
to
be
fair
with
a
supportive
manager
as
well.
People
are
being
told
actually
take
time
off,
which
is
really
good.
So
it's
been
a
tough
year
for
many
many
reasons
for
many
people,
so
having
a
some
time
off
on
vacation
and
focusing
on
family
is
a
good
thing
so
that
everybody
can
focus
then
on
execution
on
autumn,
and
so.
A
B
Makes
a
lot
of
sense
yeah
exactly
absolutely
absolutely
so,
and
for
those
who
are
watching
and
listening.
Remember
that
that's
a
really
well
sign,
but
thank
you
nicola
for
joining
us
today.
We
will
be
pushing
out
the
the
obviously
the
the
recordings
and
everything
out
pretty
soon,
but
those
who
are
watching
and
listening
they
kind
of,
are
watching
the
recording.
So
it's
kind
of
a.