►
From YouTube: Microsoft 365 PnP Weekly – Episode 104
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 Cameron Dwyer – MVP and CTO at OnePlace Solutions in Australia. Differences between the ISV – SAAS product developer and the Corporate Developer are considered during this session. Topics covered include UX and API tool usage, authentication and identity across workloads, licensing vs subscription management, and more. Twelve recently released articles and videos from Microsoft and the PnP Community are highlighted in this session. This episode was recorded on Monday, November 9, 2020.
References:
• See the full blog post for this episode at https://aka.ms/M365DevBlog
• Download the podcast for this episode at http://pnpweekly.podbean.com.
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos
A
And
action
and
welcome
everybody:
this
is
bmp
weekly
episode,
104,
and
this
time
we
are
unfortunately
at
least
with
this
section.
We
are
without
waldek,
but
before
we
go
there
and
clarify
who
we
have
here
on
the
call
and
let's
talk
about
what
is
bfd
weekly,
so
bmv
weekly
is
our
weekly
show
where
we
talk
about
what
is
the
latest
on
microsoft?
365.
we
go.
Typically,
we
have
a
visitor,
and
then
we
go
through
different
articles
and
updates
from
the
microsoft
and
this
week
we
do
have
a
visitor
and
again
I'm
forgetting
about
this
interest.
A
My
name
is
cesar,
you
wanna
a
program
manager
in
the
onedrive,
sharepoint
engineering
team
and
typically,
while
that
would
be
here
while,
like
mastercard,
who's
a
cloud
advocate,
but
he
has
some
family
things
to
run
unexpected
morning
this
morning,
so
he
had
to
and
will
hopefully
get
him
on
the
later
section
when
we
record
that
later
today,
but
anyway
we
do
have
a
visitor
or
I
have
a
visitor.
We
do
have
a
visitor
in
the
bmv
weekly,
whose
camera
and
trier
so
cameron
will
do
a
quick
intros.
Who
are
you.
B
Awesome
thanks
very
so
great
to
be
able
to
join
you.
Yes,
my
name
is
cameron
dewire.
I
am
based
in
sydney,
australia.
I
am
the
chief
technology
officer
at
an
isb
in
the
microsoft
365
ecosystem
called
one
place
solutions
and
we've
been
around
for
well
over
a
decade,
sort
of
rode,
the
wave
of
the
sharepoint
ecosystem.
C
A
And
and
you're,
actually,
your
company
is
having
the
kind
of
a
typical,
let's
say,
the
growth
model
where
everybody
started
in
sharepoint
at
some
point,
because
sharepoint
was
super
in
on-premises
and
then
we
started
moving
to
the
cloud
and
then
most
of
the
companies
well
not
most
of
the
companies.
But
then
everybody
is
gradually
adapting
all
of
the
other
technologies
as
well,
because
obviously
m365
is
not
just
about
sharepoint,
even
though
that
has
a
big
role
there
as
well.
But
can
you
talk
about
the
the
let's
say,
the
path
to
the
cloud?
B
Sure
so
we
started
with
2007
had
just
come,
come
out.
So
let's
say
prior
to
that.
My
background
is
development
through
and
through.
I
was
a
consultant
for
many
many
years
and
actually,
when
I
joined
this
company,
we
were
just
a
bunch
of
consultants
and
we
do
custom
development
work
all
the
way
through
from
requirements
gathering
to
deployment
training.
B
So
it
was
really
solving
the
same
business
problems
and
just
applying
that
knowledge
to
a
different
technology
stack
and
so
back
in
those
days
there
was
no
cloud,
it
was
all
on-premises,
sharepoint
servers
and,
as
I
say,
we're
doing
the
consulting
with
sharepoint
2003,
but
it
was
really
our
product
started
with
sharepoint
2007
and
our
products
were
all
sort
of
integration
products,
because
at
that
point,
in
time
people
were
used
to
thick
applications
on
a
desktop.
So
you
install
some
thick
application.
B
Usually
there
was
some
heavy
server
back
end
as
well,
but
the
the
client
was
quite
rich
and
everything
happened
on
a
desktop
and
users
had
the
feeling
that
they
were
in
control
and
sharepoint
came
along.
It
was
very
browser-based
and
there
was
this
big
disconnect
between
a
user
doing
their
work
on
their
pc
and
then
having
to
do
this
extra
step
of
sort
of
do
things
in
a
browser
to
get
files
up
there
and
get
files
back
down.
B
So
that's
really
where
we
started
out
is
people
just
weren't
getting
and
ourselves
because
we're
doing
the
consulting
as
well.
In
those
days,
the
biggest
user
adoption
problems
that
we
saw
was
people
just
weren't
using
sharepoint.
It
was
too
hard
to
get
files
up
into
it
and
then,
when
the
files
were
up
in
there,
they
would
feel
like
they
lost
control.
So
it's
all
about
integrating
and
bringing
that
sharepoint
experience
down
onto
the
desktop
and
into
the
tools
that
they
work
with
so
we're
doing.
B
Heavy
integration
in
with
the
office
suite
so
outlook
excel,
word
powerpoint
and
the
windows
file
system
itself,
and
so
all
that
was
you
know,
sort
of
talking
to
the
sharepoint
service
and
that
was
back
in
the
day
front,
page
server,
extensions
and
web
services.
So
the
story's
got
a
lot
nicer
for
sure,
as
we've
gone.
C
B
A
B
And
things
got
a
little
bit
easier
for
us.
It's
just
a
multitude,
a
huge
matrix
of
things
to
need
to
support
different
clients
integrating
with
different
server
backends,
but
our
our
software
and
still
today,
still
today
we're
writing
this
sort
of
this
path
between
installed
client
software,
which,
for
integrating
in
with
the
office,
desktop
clients,
we're
developing
what
are
called
vsto
add-ins
visual
studio
tools
for
office,
add-ins
yeah,
and
I
can
talk
to
you
about
a
bit
about
those
a
bit
later
on.
B
But
for
now
we
they're
our
traditional
products
and
we
still
take
those
forward
and
they're
very
rich
applications,
but
at
the
same
time
the
development
models
we're
evolving
and
changing.
So
we're
also
now
sort
of
reinventing
those
products
under
the
more
modern
technology
stack
and
so
we've
been
sort
of
transitioning
those
and
that's
been
going.
Gosh,
that's
probably
been
four
or
more
years
because,
as
soon
as
the
new
development
models
came
out,
we
were
testing
them
and
it
was
just
a
matter
of
finding
out.
B
Well,
when
is
the
right
time,
when
is
this
commercially
viable
that
we
can
deliver
enough
business
value
that
someone's
going
to
want
to
buy
this?
And
so-
and
it's
also,
you
know
when
you,
when
you're,
going
on
the
bleeding
edge
of
things,
there's
a
huge
cost
to
trying
to
develop
something
that
can
scale
and
be
commercially
viable.
A
B
A
C
A
Now
now
before
we
go
actually
there
and
let's,
let's
obviously,
concentrate
today
on
the
on
the
partner
opportunities
and
the
models,
how
it
works.
But
let's
go
back
in
time
for
the
moment
where
you
decided
that
you
actually
want
to
do
products.
Why
products?
Not?
Why
not
consulting?
What
was
that
decision.
B
Probably
based
well
actually
I'd,
say
twofold:
one
based
financially
having
done
consultancy
for
at
that
point
would
have
been
over
a
decade
of
doing
consulting.
We
realized
that
there's
a
cap
on
how
much
we
can
earn
you're,
basically
selling
your
time.
You
can
package
up
and
reuse.
You
know
bits
of
technology
and
techniques
that
you've
got
and
repackage
them
up
and
sort
of
make
a
profit
off
those.
B
But
really
you
can
just
extrapolate
your
time
out
and
there's
a
cap
on
how
much
you
can
make
out
of
this
going
to
product
sort
of
removes
that
cap,
if
you
like,
there
was
also
it
was
a
point
in
time
where
the
people
I
was
working
with
were
all
of
a
similar
age,
we're
all
starting
to
have.
Children
have
a
family
and
the
consulting
life
you're,
really
at
the
mercy
a
little
bit
of
the
organizations
that
you're
working
for
at
that
time,
we're
going
out
on
site
still.
B
It
was
very
much
you
go
out
to
a
client
type
world
that
we're
living
in
though
they
could
be
long
days
and
you
didn't
have
sort
of
that
ultimate
control.
We
shift
that
into
a
product
company
while
you've
got
a
lot
of
demands
of
you.
You
also
have
a
lot
more
control
over
your
time,
so
it
was
a
bit
of
a
lifestyle
choice
as
well,
and
what
we
saw
when
we
moved
from
the
ibm
world
to
the
sharepoint
world.
B
Is
we
actually
found
that
the
consulting
world,
the
the
the
amount
of
effort
that
you
needed
to
put
in
to
get
stuff
working
and
keep
stuff
working,
because
it
was
a
qui?
It
was
evolving
quite
quickly?
Is
that
there
was.
There
was
more
longevity
in
spending
that
time
doing
product
than
it
was
doing
the
consulting.
There
was
a
lot
to
have
to
get
your
head
around.
A
Yeah,
that's
actually
that's
actually
a
good
point
on
on
also
the
fact
that
you
need
to
keep.
If
you
do
a
customer,
let's
say
as
a
system
integrator
deployments
for
customers,
then
keeping
all
of
that
stuff
up
to
dates
and
making
sure
that
the
customer,
whatever
specific
solution
is
up
to
date,
is
actually
quite
a
lot
of
work
and
so
and
then
as
a
developer.
A
That
might
feel
bad
to
leave
customers
behind,
knowing
that
their
stuff
will,
let's
say,
go
old
in
a
year
or
two
so
rather
than
having
a
sales
service,
which
is
all
the
time
up
to
date,
and
you
can
basically
offer
services,
there's
actually
an
interesting
perspective
as
well.
But
now
coming
back
on
that,
so
you
said
you
basically
have
two
different
transitions
in
the
company.
One
was
the
one
that
you
started
doing
cloud
and
and
first
you
were
probably
then
doing
the
customer
specific
deployments
right,
and
then
you
moved
in
the
disaster
this.
B
When
we
first
started
doing
the
sas
we
weren't
set
up
to
be
billing
under
a
sas
model
with
subscriptions,
it
was
very
much
still
you're
buying
a
perpetual
license
and
you'd
blowing
support
and
maintenance,
even
though
we
were
running
the
thing
as
a
sas,
so
we've
actually
flipped
that
on
its
head
now
and
all
of
our
revenue
is
sas.
So
even
our
customers
that
have
got
the
installed
software
they're
still
buying
it
on
a
subscription.
B
A
Yeah,
how
hard
was
the
transition,
because,
obviously
I
think
there's
a
lot
of
other
partners
are
looking
potentially
doing
the
subscription
model
as
well,
and
then
that
requires,
like
you,
said,
technical
work,
and
then
it
requires
process,
work
and
all
of
that
stuff.
How
long
did
it
take
or
how
hard
was
it.
A
B
Actually
do
this
there's
a
lot
of
companies
now
offering
software
as
a
service?
How
on
earth
are
they
doing
the
billing
and
what
we
found
was
that
and
the
penny
dropped
to
me
after
the
first
round
or
two
of
looking?
Is
that
there's
a
difference
between
subscription
management
and
license
management
so
well,
there
yeah
there
is-
and
there
definitely
is
when
you're
talking
about
doing
a
b2b
offering
where
an
organization
might
be
buying
10
000
licenses.
B
So
what
there
was.
There
was
a
lot
of
subscription
platforms
out
there
that
were
doing
b2c
where
it's
a
one-to-one
relationship,
a
customer
can
come
online
sign
up
for
something
and
they're
just
buying
one
user
license
or
something
and
the
management
sort
of
aspect
of
it's
not
not
needed
under
that
scenario.
B
B
So
it
takes
care
of
signing
up
an
organization
and
you
loading
your
products
into
that
into
that
subscription
platform,
and
it
takes
care
of
the
renewals
and
sort
of
tracking
your
churn
and
that
sort
of
information,
but
what
it
doesn't
do
is
it
doesn't
know
if
it
if
the,
if
your
subscription
is
based
on
users,
it
doesn't
really
know
what
to
do
with
that
information.
All
can
do
is
give
you
your
development
team.
The
answer
to
that
question,
if
your
your
software
wants
to
know,
is
this
user
licensed.
B
He
can't
tell
you
that
all
I
can
tell
you
is
that
this
organization
has
a
subscription
for
this
many
users
or
for
this
threshold
of
throughput.
So
it's
really
just
the
definition
of
the
subscription
and
then
it's
really
up
to
you
to
implement
the
licensing.
Well,
it
was
for
us.
We
couldn't
find
something
that
would
give
us
both.
So
we
kind
of
had
to
do
the
user
management,
so
our
software
works
on
a
user
basis.
A
Okay,
but
but
technically,
what
you're
saying
is
that
you,
you
have
a
third-party
service
which
you
use
for
the
the
money
and
subscription
handling
and
all
of
that
stuff.
So
you
don't
have
to
worry
about
that
correct,
correct,
which
is
actually
quite
smart
because
again
office
loading,
the
the
thing
which
is
not
core
for
your
business,
because
I
don't
think
customers
are
looking
into
buying
your
service
because
of
the
subscription
model
they're
buying
because
of
the
other
reason
so
that's
been
working
out
for
you
then
really
well.
B
Well,
I
see
it
as
providing
two
things.
Fundamentally,
one
is
a
deployment
model
to
get
your
software
in
the
hands
of
users
and
that's
what
we
use
it
for,
but
the
other
is.
You
can
actually
use
that
as
your
subscription
engine
if
it
works
for
you,
so
people
can
buy
and
act
right
to
your
software
through
that
storefront
as
well,
and
then
you
integrate
in
with
that
and
that
sort
of
tells
you
the
same
information
it
can
tell
you.
This
organization
has
bought
this
subscription.
B
A
Yeah
yeah
now
now
that's
actually
really
interesting
and
also
and
good
direction
and
guidance
for
others
to
looking
into
how
to
make
these
things
happen.
What
about
then
the
transition
to
the
let's
say:
microsoft,
365
in
general?
How
do
you
see
that
the
opportunity
and
what
how
do
this
is
actually
I'm
putting
you
on
a
spot?
How
would
you
define
the
opportunity
for
partner
ecosystem
in
microsoft,
365,
and
I
get
that
we
as
a
microsoft
should
be
doing
a
good
job
of
explaining
that?
But
but
what's
your
perspective
on
on
the
opportunity.
B
But
for
me,
look
at
just
looking
at
that
traditional
the
user
base
that
we've
had
is.
The
opportunity
is
really
that
microsoft
is
doing
extremely
well
as
a
cloud
provider
as
providing
business
tools
on
top
of
the
cloud
and
doing
it
in
a
way
that
enterprise
is
adopting
it.
I
mean
it's
one
thing:
to
get
consumers
on
board
and
small
seats,
but
when
you've
got
major
companies
having
the
trust
in
microsoft
to
put
their
data
on
the
platform,
then
that's
a
really
really
good
indication
that
you
know
this
this.
B
B
A
Yeah
and
and
of
course,
if
we
think
about
this
from
a
microsoft
perspective,
we've
been
going
through
this
interfaces
as
well
with
customers.
So
one
of
one
of
the
big
big
big
thing
was
that
whenever
we
get
the
customers
their
azure
ad
in
place,
then
their
identity
is
in
a
cloud,
because
that's
been
that
at
some
point
that
was
really
really.
A
B
You
know
I
go
out,
and
I
do
the
developer
boot
camps
and
help
out
here
there
and
everywhere.
But
what
I
see
time
and
time
again
is
authentication
and
identity
just
being
that
barrier
for
developers
getting
in
often
the
training,
material
and
stuff
will
gloss
over
that
or
take
a
shortcut
way
of
getting
you
past
the
auth,
because
we
know
it's
going
to
be
such
a
difficult
topic
that
people
get
stuck
on
and
it's
also
doing
it
properly
is,
is
I
wouldn't
say,
difficult
or
challenging
it's
it's
almost
something
that
I
as
a
developer.
B
I
don't
I'm
not
a
security
expert
in
the
way
that
I
would
want
to
be
to
feel
confident
to
write
my
own,
the
library's
getting
better
the
msl
libraries
are
getting
better,
but
there
for
a
long
time.
You
would
cut
and
paste
snippets
that
microsoft
gave
you
and
you
would
follow
the
instructions
you
could
put
it
all
in
place,
but
that's
not
a
library
that
gets
taken
forward
when
security
vulnerabilities
are
found,
because
that
when
you
copy
and
paste
it
that's
now,
yours
you've
got
to
take
care
of
that
and
water.
It.
B
It's
not
a
it's,
not
a
proper
library
thing.
Thankfully,
the
msl
libraries
have
come
along
and
a
lot
of
that
has
been
replaced
by
standard
libraries
that
we
can
call
for
the
longest
time.
We
had
a
a
big
issue
and
a
lot
of
our
a
lot
about,
but
the
ui
pieces
of
it
we've
still
written
ourselves
because
we're
an
office
add-in,
a
lot
of
the
msl
prompting
didn't
work
for
us
because
of
the
way
office
add-ins
are
hosted
inside
of
the
office
products
themselves,
they're
sandboxed
iframes.
B
You
can't
pop
up
dialogue,
so
the
msl
libraries
sort
of
aren't
designed
to
work
inside
of
that
sort
of
container
and
framework.
So
that
story
is
evolving.
It's
coming
along
single
sign-on
is
coming
along
as
well,
but
some
of
that
probably
won't
solve
our
problems
either,
and
that's
that's
actually
an
interesting
one.
B
Let's
dive
in
on
that
quickly,
so
as
a
yeah,
so
something
like
single
sign-on
is
as
a
product
company
there's,
there's
really
yeah,
there's
two
things:
they
sort
of
come
from
different
sides:
let's
take
single
sign-on
to
get
single
sign-on
to
work.
Something
has
to
be
trusted
by
your
organization
and
consented
to
for
the
security
to
flow
through.
B
So
you've
kind
of
at
a
point
where,
from
an
isb's
perspective,
in
order
to
get
an
organization
to
try
your
product
or
to
get
it
just
in
front
of
one
user,
you've
sort
of
kind
of
bottlenecked
on
someone
giving
security
permissions
to
your
application,
they
want
to
know
all
about
your
application.
Have
trust
in
your
application
before
they
approve
it.
So
that
sort
of
rules
out
single
sign-on
for
just
trialing
things,
which
is
from
an
isb,
because
often
you
think
of
an
isps.
Are
there
a
product
company?
B
Yes,
they'll,
be
able
to
get
that
sso
stuff
and
that's
not
a
problem,
but
it
really
doesn't
work
like
that.
The
way
that
it
works
is
that
people
just
want
to
kick
the
tires,
someone
one
person
in
an
organization,
it's
typically
the
business
user.
That's
got
the
use
case.
They
will
want
to
just
try
your
product
out.
They'll
just
want
to
download
it.
A
What
we
keep
on
having
is
that
we
don't
want
to
grant
default
permissions
for
any
application,
and-
and
that's
really
then
causing
the
problem
that
well,
you
need
to
be
an
administrator
to
grant
certain
level
of
permissions
or
all
of
that,
and
maybe
in
other
platforms
they
actually
grant
basic
set
of
permissions
and
it
it
is
more
flexible
than
just
install
that
and
start
using
it.
What's?
What's
your
thinking
on
that.
B
That's
good,
I
don't
I
don't
know
what
the
end
solution
is
today
for
us
for
us
from
a
developer's
point
of
view
on
the
way
the
ecosystem
is
at
the
moment.
To
me,
I
just
think
well,
sso
is
great,
but
it's
not
the
answer
for
trialing.
So
for
us
we
go
through.
We
just
take
it
through
sso.
We
just
it
just
means
we
have
to
handle
the
identity
ourselves.
Other
things
that
I
sort
of
thought
of
over
time
were
doing
time-based
consent.
B
So
you
know
someone
trials
something
for
a
day
a
week
a
month,
but
only
give
the
consent
for
that
period
of
time,
because
a
lot
of
what
happens
is
once
consent's,
given
that
the
sort
of
the
horses
yeah,
then
we're
never
going
to
get
that
back
yeah.
So
I
it
is
a
tough
one,
and
actually
this
is
again.
This
is
probably
something
that
we
didn't
hit
until
we
started
moving
into
cloud
and
modern
authentication
is
just
the
whole
issue
of
trust
and
security.
B
A
B
B
No,
it's
not
it's,
not
the
messy.
It's
weird.
I
think
it's
just
a
a
shift
in
the
way
that
we've
always
done
things,
because
let's
well
yeah.
So
if
you
wanted
to
do
a
modern
application
today,
then
your
consent
is
gonna.
Go
through
azure,
active
directory
and
you're
asking
for
granular
permissions.
Now.
C
B
Are
use
used
to
this
because
on
their
mobile
phone,
something
will
ask
to
use
your
camera
it'll
ask
for
your
contacts
details
and
this
sort
of
granular
permission
is
what
we
see
through
azure
active
directory
asking
for
for
your
data,
that's
stored
inside
of
microsoft,
365
and
it's
kind
of
from
an
organization's
point
of
view.
It's
never
been
clearer
because
the
applications
have
to
spill
out
at
a
very
granular
level
what
they
want
access
to
and
we
sort
of
go
out
of
our
way
to
document.
Well.
Why
do
we
need
that?
B
A
B
A
B
Microsoft's,
a
very
large
they've
got
a
lot
of
certifications
behind
them,
and
microsoft
has
rightly
earned
the
trust
of
the
large
organizations,
the
protection
of
their
data
and
the
handling
practices
of
that
data,
but
that
trust
doesn't
flow
through
to
the
isp
community.
Nor
should
it
because
there
could
be
bad
actors
out
there
so
for
those
that
are
getting
into
into
the
ecosystem.
B
A
Yeah
makes
sense
makes
sense
now.
Okay,
identity
is
one
thing
where
we
need
to
well.
Obviously
we
we're
we're
on
this
journey
of
making
it
easier
we're
increasing
the
abstraction
so
that
it
will
be
super
super
easier
for
the
developers
to
take
advantage
of
that,
because
identity
is
something
like
you
said:
it
should
just
work
and
kind
of
a
plug-and-play
to
your
clear
solution.
In
your
case
just
recapping
or
re-paraphrasing,
you
actually
have
a
separate
identity
signing
in
your
solution
right.
A
So
whenever
you're
exposing
the
solution
you
ask
them
to
sign
in
and
then
that's
going
to
be
the
identity
model
sure
what
else?
What
else?
What's
the
other
areas
where
we
should
be
improving?
We
can
talk
about.
For
example,
microsoft
craft
is
a
absolutely
brilliant
platform
for
accessing
information
and-
and
I
think
everybody
knows
that
we
need
to
do
further
investments
on
the
microsoft
graph
api
surface.
I
think
that's
heading
to
the
right
direction
for
sure.
So,
a
lot
of
a
lot
of
stuff
across
the
different
services
make
it
super
easy
to
access
the
information.
B
C
B
There's
a
long
history
and
we
do
a
lot
of
integration
with
sharepoint.
It's
probably
one
of
the
largest
existing
apis,
that's
out
there
so
and
that
takes
time
to
move
across,
and
we
understand
that,
but
the
graph,
the
the
idea,
the
concept
that
you
can
just
do
once
one
authenticate
once
to
the
graph
and
get
access
to
all
the
workloads.
The
fact
that
you
can
just
do
one
set
of
error,
handling
and
yeah
just
train
your
developers
on
one
api
is
just
amazing.
B
Probably
one
of
the
things
that
isn't
immediately
over
obvious
when
you
go
to
the
graph
is
how
discoverable
it
makes
things
from
a
development
perspective.
Because,
let's
say
you
like,
take
our
solution.
We
need
to
get
users
details
which
would
be
historically
an
aad
we
integrate
with
mail
and
calendar,
which
would
be
an
exchange.
B
We
hit
files
in
sharepoint
and
and
we
do
integration
with
teams
as
well.
Now,
if
these
were
all
separate,
apis
and
separate
products,
we'd
have
to
deal
with
auth
and
everything.
But
the
big
thing
is:
how
do
you
know?
How
do
you
know
where
those
servers
are
like
if
this
was
on
premises?
How
would
we
know
where
their
exchange
server
is?
How
would
we
know
what
the
name
of
their
aad
is?
A
B
A
lot
today
is
that
you
start
up
a
piece
of
software,
and
the
first
thing
it
asks
for
you
is
to
put
in
the
name
of
your
server
or
a
url
or
they're
these
technical
things
that
business
users
don't
have
the
answers
to
when
you
move
across
to
the
graph.
All
you
need
to
do
because
everything's
graf.microsoft.com
is
your
api.
It
doesn't
change.
B
All
you've
got
to
ask
the
user
for
is
to
log
in
they
know
what
their
email
address
is
because
you're
not
asking
them
for
a
new
credentials,
you're
asking
them
to
log
in
as
their
microsoft
identity,
so
they
know
their
username.
They
know
their
password.
Once
you
get
there,
you
can
discover
where
everything
else
is,
and
so
from
an
onboarding
perspective
from
a
first
use
perspective
of
someone
using
your
software
is
incredibly
smooth
compared
to
what
it
used
to
be
because
there
used
to
be
so
many
technical
questions
you
needed
to
ask
yeah.
A
Yeah,
absolutely
that
that
certainly
is
one
of
the
key
benefits
of
the
graph
and
and
and
we
are
investing
on
the
craft
surface
across
the
board,
but,
like
I
said
one
of
the
good
examples
as
being
the
the
good
old
and
people,
some
people
call
it
legacy.
Some
people
call
it
the
most
widely
used
api,
which
is
the
sharepoint,
because
the
sharepoint
api
is
just
massive
in
csm
and
rest
apis
and
then
getting
all
of
that
moved
to
the
craft
is
surprisingly
painful,
but
we're
on
a
journey
on
that.
A
B
B
A
B
Be
able
to
do
that
whole
chain
of
things
usually
with
one
api,
because
if
you
can't
and
you
sort
of
get
halfway
through
and
then
you
go
and
switch
to
another
switch
to
another
one,
the
performance
isn't
great
and
what
you
might
find
is
that,
well,
why
call
the
graph,
when
I've
got
a
fallback
to
see
some
and
the
actual
calls
I
can
make?
I
can
actually
make
one
call
across
the
wire
to
do
it
all.
B
B
So
yeah
there's
it's
it's.
It's
certainly
coming
along
and
yeah,
the
more
that
the
more
stuff
that
hits
the
graph
and
that
mentality
of
graph
first
within
microsoft,
the
more
that
mentality
actually
resonates
through
the
apis,
the
smoother
it's
going
to
be
to
get
developers
onto
it,
especially
us
from
this
probably
happens
more
from
an
isp
perspective
than
it
does
from
an
enterprise
dev
perspective
in
that,
if
something,
let's
say
you
take
a
sharepoint
api.
B
If
microsoft
launches
a
new
feature,
here's
an
example
of
one
the
lists,
the
new
lists,
new
old,
mainly
old,
but
there
were
some
new
apis
around
this.
So
my
recent
list,
my
favorite
lists
things
like
that.
That
hits
the
that
hit
the
sharepoint
api
first,
which,
from
an
engineering
perspective,
you
can
understand
why
it
hasn't
played
through
to
the
graph
yet
but
from
a
isp
perspective,
you're
kind
of
forced
to
use
the
api
where
the
functionality
comes
out
in
first,
because
if
we
don't
our
competitors
will.
B
C
A
An
interesting
challenge
and
that's
something
which
we've
been
actively
trying
to
figure
out.
How
do
we
do
this
in
a
right
way
because,
obviously,
like
I
said
it,
makes
sense
theoretically
provide
that
api
first
in
aa,
for
example,
in
the
sharepoint
scan
center
sharepoint
rest
api,
because
the
first
body
experience
the
ones
with
microsoft
implements
their
primary
purpose
is
to
get
functionality
out
and
and
then
the
secondary
objective
is
actually
offer
that
functionality
for
the
partners.
A
A
B
Probably
a
good
plug
there
for
pnp
libraries
as
well
in
that
sometimes
that
can
act
as
the
proxy
between
those
underlying
layers.
So
some
of
the
pnp
libraries
and
the
calls
will
be
using
sharepoint
calls
today,
but
over
time
those
calls
may
happen
in
those
libraries
get
transferred
over
to
be
graph.
Calls
we've
seen
that
happen
in
the
past.
A
And
and
that's
obviously
from
even
from
a
day,
one
related
on
bmb
liferays,
why
did
we
create
them?
Well,
we
saw
that
there
are
gaps
and,
let's
not
build
27
000,
unique
libraries
across
the
partner
ecosystem.
Let's
build
one
together
and
then,
whenever
we
update
things
there,
everybody
will
benefit
and
it
has,
though,
its
own
challenges
for
sure.
But
the
thinking
is
that,
whenever
something
moves
across
the
api,
it's
completely
seamless
potentially
for
the
partner
ecosystem
that
then
to
use
a
more
polished,
api
or
more
advanced
api,
now
moving
away
from
api
layer.
A
A
B
B
So
what
what
our
client
utilities
do?
One
of
the
parts
that
they
do
is
they
allow
you
to
edit
all
the
sharepoint
metadata
and
all
that
prompting
all
that
columns
of
information
and
content
types.
Those
taxonomy
pickers
all
of
that
sort
of
stuff.
We'd
rebuild
all
of
that
client
side
to
integrate
it
in
with
the
office
suite
and
we're
faced
with
doing
that
again
under
web
technologies,
and
we,
I
really
didn't,
want
to
have
to
go
to
the
pains
of
doing
that
all
ourselves.
B
In
the
end
we
have
and
we've
rebuilt
all
of
those
components,
but
look
I
love
the
direction
and
I've
been
doing
a
little
bit.
I've
been
working
with
the
microsoft
graph
toolkit
team
there
at
microsoft
and
outside
of
microsoft.
There's
been
other
people
in
the
community
as
well,
because
I
really
love
the
direction
that
the
graph
toolkit's
going
in,
because
I
was
familiar
with
the
different
microsoft
initiatives
on
the
ux
layer.
I
can
talk
quickly
to
the
problems
or
not
necessarily
problems,
so
we
what
we
wanted
we
needed.
B
We
knew
we
needed
to
build
all
these
controls
ourselves.
We
wanted
them
to
look
like
office
components
if
we
could
so
yeah.
We
knew
that
you
guys
had
built
them
for
sharepoint
I
was
like.
Can
we
reuse
any
of
these
components
that
are
inside
the
pmp
libraries
or
that
are
in
sharepoint
natively
or
like?
Can
we
somehow
use
some
of
this
stuff?
How
we
can
now
use
powerapps
that
takes
a
rendition
of
the
controls?
Can
we
leverage
any
of
that?
B
B
The
other
thing
I
love
about
the
graph
toolkit,
which
is
different
to
the
fluent
libraries,
is
that
the
the
graph
toolkit
is
web
web
components
like
real
legit
web
components
and
what
web
components
are
is
they
are
something
that
any
browser
modern
browser
can
understand,
and
you
can
use
them
inside
of
any
sort
of
web
project,
whether
it's
vanilla,
html,
javascript,
css
or
jquery,
or
if
you're,
using
a
full-blown
framework
like
angular
or
react.
You
can
use
those
components
which
is
fantastic
and
that's
the
direction.
B
I
would
have
liked
to
have
seen
the
fluent
and
back
in
the
day,
the
office
ui
fabric.
That
was
kind
of
my
feedback,
because
in
those
times
we
had
to
make
a
call
very
early
on
what
we
were
going
to
use
as
a
framework
to
develop
our
web
technology
off,
and
we
went
with
angular
at
that
point
in
time
that
was
kind
of
the
direction
that
microsoft
was
going
in
as
well.
B
It
came
as
a
bit
of
a
surprise
when,
when
the
direction
changed
to
react-
and
it
was
still
we
didn't
know-
which
way
that
would
go,
because
not
all
decisions
sort
of
pan
out
for
the
long
term
either.
So
we
we've
built
all
of
our
stuff
in
angular
and
we've,
we've
steered
clear
of
the
fluent
components
because
the
office
ui
fabric.
B
Initially
it
was
javascript,
so
it
would
work
anywhere
and
then
the
more
advanced
components
came
out
in
react
and
we
sort
of
stayed
on
some
of
the
core
and
we
still
use
it
for
the
styling
hit
the
colors,
the
fonts,
the
themes
we
still
leverage,
all
of
that
from
the
from
the
sort
of
the
core
of
it.
But
yeah.
We
never
used
the
more
elaborate
components
because
we
were
on
angular
not
react.
B
B
A
B
So
yeah
our
lookout
in
works
on
ios
and
android
phone,
but
when
you
think
of
the
styling
out
there,
the
styling
guidelines
is
don't
make
it
look
like
office.
It
needs
to
look
like
a
native
android
application
or
a
native
ios
application,
and
I'm
not
sure
if
that
has
been
addressed
in
fluent.
Yet
it
certainly
wasn't
in
the
office
ui
fabric.
So
it
would
mean
that
if
we
were
to
use
the
office
ui
fabric
we'd
be
able
to
use
all
those
controls
for
like
at
the.
B
Versions
of
office
and
on
the
desktop
and
on
the
mac,
it
would
probably
you'd
probably
get
away
with
it.
But
you
would
not.
You
would
have
to
use
something
totally
different
on
those
other
devices
so
by
building
the
components
ourselves
we're
able
to
get
the
functionality
we
need
and
it's
simply
a
style
sheet
change
across
the
different
forms,
form
factors,
there's
different
operating
environments
and
we're
able
to
achieve
those
design,
guidelines
and.
A
B
A
B
It's
it
works
both
ways
as
well
like
as
a
isp,
and
an
organization
like
the
the
power
of
community
is
very
strong
and
we
seriously
looked
at
taking
the
microsoft
libraries,
forking
them
and
using
those
as
our
base.
But
as
I
say,
because
the
direction
at
that
time
wasn't
in
our
technology
space,
it
just
didn't
make
sense.
B
Had
that
been
under
web
components,
then
maybe
we
would
have
done
something
differently
and
being
able
to
build
those
out,
because
there
has
been
a
similar,
and
I
know
that
yulia
street
has
done
a
lot
of
work
on
sort
of
the
the
property
controls,
pain
for
web
parts
and
things
a
lot
of
those
controls
exactly
what
we've
developed.
It's
this
very
similar,
similar
things
that
we
we
needed
to
go
through
and
yeah,
that's
yeah.
It
was
touch
and
go
if
the
technology
was
different,
we
might
have
been.
A
A
As
an
example,
there
was
a
more
focus
on
the
first
party
experience
than
a
third
party
experience,
and
I
know
we're
now
having
discussions
with
fluent
fluent
ux
team
and
they're
building
their
own
new
components
and
and
trying
to
figure
out
that
they
prioritize
the
third
party
and
partner
ecosystem
as
well,
so
because,
if
they
would
be
web
components
like
I
said,
then
they
will
work
in
the
angular.
They
will
work
in
react.
A
They
will
work
in
in
any
technology
which
is
which
is
great
so,
but
let's
see
so
anyway,
no
no
definite
answers
there.
Now
we've
been
chatting
almost
too
long
already.
I
think
we
need
to
start
closing
closing
it.
Our
target
is
always
one
hour
together
with
articles,
but
but
just
putting
you
on
a
spot
for
a
live
one
last
discussion
point
which
says:
if
I'm
a
partner
and
across
the
world
wherever.
Why
would
I
want
to
have
a
look
on
the
microsoft
365
ecosystem?
B
Your
addressable
audience
is
massive
and
you've
already
got
people
that
have
the
software
installed
and
you're,
usually
you're
you're
you're,
adding
on
to
you're
you're,
adding
on
to
something
that
companies
have
already
invested
in
and
they're
already
realizing
the
value
of,
and
that's
a
much
easier
proposition
to
come
in.
On.
A
B
And
I
just
as
I
said,
made
the
comment
before
the
the
the
microsoft
cloud
and
that
sort
of
goes
even
beyond
microsoft,
365
and
out
into
sort
of
the
azure
platform
on
which
a
lot
of
it's
built.
It.
Really
it's
really
strong
from
an
enterprise
perspective
and
being
able
to
scale
and
confidently
build
solutions
that
are
targeting
everyone
from
the
small
sort
of
mum
and
dad
shops
right
up
to
fortune.
500
companies
and.
A
B
A
That's
actually
great
closing
for
the
for
the
this
discussion.
That
was
a
really
good,
so
thank
you,
cameron
on
that
one,
so
really
great
stuff
now
as
well
so
anyway.
So
thanks
for
everybody
for
watching
and
thanks
everybody
for
listening,
if
you're
choosing
the
broadcast
option,
which
is
available
as
well,
we
will
be
back
with
a
next
bmp
weekly
within
a
week,
so
surprise,
surprise.
A
So,
unless
both
of
us
have
any
blocking
things
so
hopefully
not
so
I
think
we
can
deal
with
this
so
and
while
that
will
be
most
likely
back
within
a
week
as
well,
but
thank
you
cameron,
thank
you.
Everybody
who's
watching
and
we'll
be
definitely
in
touch.
Bye-Bye
welcome
well
deck,
and
you
missed
the
discussion
with
cameron
earlier
today
and
do
family
reasons,
but
it's
all
good.
So.
C
A
A
Outside
yeah,
it
is
well
it's
it's
november,
finland,
oh,
it's
dark
yeah
anyway,
so
let's
do
some
articles
and
they
actually
quieted
silent
week
on
the
microsoft
side,
which
was
by
design
because
there
was
the
us
election
and
there
was
a
rules
inside
of
microsoft
that
we
shouldn't
be
actually
publishing
in
certain
days.
We
do
understandable
reasons
now,
let's
not
concentrate
on
politics.
Let's
talk
about
articles
so
anyway.
A
C
So
every
month
release
new
version.
This
time
around,
we
spent
a
lot
of
time,
refactoring
the
you
could
call
it
the
engine
of
cli,
so
we
moved
from
a
package
that
we
used
for
over
almost
two
and
a
half
years
now
to
build
cli
upon
it
got
deprecated
out
of
date,
so
we
remove
it
refactored
number
of
things
I'm
always
like.
Well,
I
know
one
of
the
the
gems
that
we
didn't
even
include
in
notes
is
reworking
of
our
help.
C
C
C
C
A
More
concentrating
on
the
consistency,
consistency,
consistency
just
keep
on
releasing
keep
on
rolling,
so
yeah.
This
one
isn't
necessarily
a
small
release,
so
not
taking
anything
away
from
it.
Now
this
one
is
really
cool
from
rupiah.
Earlier
today
we
talked
about
this
one
which
brought
me
up
quite
a
few
times
on
in
offline
or
online.
Where
is
it
online?
So.
A
No
actually
good
point
good
point,
maybe
I'll
just
fly
over.
No,
I
can't
never
mind
now,
but
basically
and
there's
there's
a
few
different.
Let
me
zoom
in
a
few
diff
you
actually
one
that
wrote
about
the
me
experience,
which
we
brainstormed
quite
technically
at
some
point,
which
is
really
cool
and
then
there's
a
great
story
on
how
you
implement
that
one
in
microsoft
teams
and
then
there's
a
example
already
how
to
do
that
as
a
sas
application.
A
But
what
ruby
is
now
showing
here
is
that
how
do
you
do
it
with
an
spfx
and
microsoft
craft
toolkit,
so
really
cool,
setups
and
teams,
and
obviously
in
teams?
Yes,
so
you
can
really
easily
build
this
cool,
looking
ux
with
few
lines
of
code,
so
super
super
simple
and
then
you
have
multiple
different
tabs,
for
example,
planning
and
insights
and
then
settings
and
configurations
for
it.
A
So
super
cool
thing
or
we
are
already
kind
of
planning
and
having
a
high
level
discussions
that
maybe
we
should
write
a
a
to
small
tutorial
series
on
this
one,
so
kind
of
setting
it
up,
because
it's
using
react
as
well
and
it's
it's
actually.
So
really
nice
setup.
Overall,
I
think
it's
using
react.
Yes,
it
is.
A
Away,
yeah
yeah:
it's
if
it's
set
react
on
the
page.
You
know
it's
it's,
but
you
understand
that
only
if
you
read
anyway
so,
but
basically
really
cool
setup
and
also
showing
the
theming
and
all
of
that
so
really
really
cool
stuff
shower
mender's.
Getting
credits
also
on
that
one
show
is
just
absolutely
brilliant
on
the
on
the
ux
implementation
in
spfx,
as
well,
so
really
really
cool
stuff
and
getting
shared
as
an
open
source
solution.
C
So
this
is
just
a
quick
piece
of
code,
basically
showing
you
like
how
to
get
the
real
image
behind
either
a
person
or
a
group
in
graph
right.
So
when
you
build
an
application,
you
might
want
to
show
people
or
groups,
and
you
want
to
show
often
the
picture
of
that
to
make
it
easier
for
people
to
find
the
right
person
or
a
group.
I
found
that
there
is
no
end-to-end
piece
of
code
showing
you
like
how
you
exactly
do
that,
and
there
are
quite
a
few
things
you
have
to
do
right.
C
So
so
you
have
to
have
the
response
type.
You
have
to
get
the
blob
converted
to
an
url,
so
there
are
a
few
things
that
you
have
to
get
just
right
and
I
found
that
these
things
at
least
right
right
now
are
not
explained
in
the
docs
right.
So
I
hope
that
that
we
will
be
able
to
address
that
soon.
But
until
then,
here
you
have
a
complete
piece
of
code.
You
can
just
use
in
your
application
and
to
get
that
image
and
show
it
in
your
app.
A
Yep,
absolutely
absolutely
cool
stuff.
Now
paul
bullock
had
a
interesting
story
related
the
many
ways
of
set
uk
local
well,
technically
any
local
in
sharepoint,
so
and
really
talking
about
the
different
options
and
how
they
change
the
experience
and
settings
and
the
language
and
dates,
and
all
of
that
stuff.
So
there's
quite
a
few
different
ways
of
doing
this,
and
how
does
it
then
impact
on
the
onedrive
or
in
files
and
in
office,
and
all
of
that
stuff,
so
really
really
good
clarification
on
how
things
actually
work.
A
Now
this
one
is
from
tomomi
a
beginner's
guide
for
microsoft
teams,
development
messaging
action
so
really
talking
about
it's
it's
a
series
of
things,
and
this
is
the
third
one.
So
how
do
we
build
a
messaging
extension
and
how
do
we
take
advantage
of
that?
One?
Are
we
talking
about
cats?
No,
not
it
does
but
morse
code
yeah,
not
cats,
where's,
the
cats
where's
the
cat.
No,
but
due
to
clarification,
how
to
make
things
happen
and
really
nice
story
on
on
how
does
it
actually
work?
A
What
do
you
need
to
do
and
all
of
that
stuff
now
this
one
is
from
terry
matula:
it's
about
microsoft,
teams
and
graph
api
all
about
scopes
and
really
kind
of
clarifying
what
the
scopes
actually
mean,
because
again,
if
you're,
not
if
you
are
new
on
these
things,
maybe
you're
not
familiar
on
how
the
scopes
mean
and
what
does
it
actually
mean
and
how?
What
does
it
mean
from
a
trending
perspective
as
well?
A
A
Yes,
everything
is
always
interesting.
Now
this
one
is
from
I'm
going
to
get
the
morrison
wash
chef's
host.
Thank
you
really
about.
How
do
we
do
mocking
of
the
ai
http
provider
for
microsoft
craft
when
you're
doing
sbfx
development,
so
really
really
cool
stuff
as
well?
So
super
super
useful
for
people
to
take
advantage
really
really
cool.
Thank
you
for
that
one.
Then
we
have
two
videos.
A
A
A
topic
obviously
azure,
ad
b2c
yeah.
That's
super
important
topic,
so
really
cool
video
as
well
so
seven
minutes
on
on
the
topic,
and
these
are
really
cool
videos
on
catching
up
on.
Okay,
that's
how
it
works.
Okay,
fine,
another
two
long
things
as
well
beats
kelly,
had
a
good
blog
post
related
on
share
sp
caf
rules
across
the
project
using
azure
devops,
multiple
repo
builds,
you
might
actually
know.
While
that
mod
is
an
sp
caf.
Can
you
explain.
C
C
Is
your
solution
up
to
par?
Is
there
anything
you
could
improve?
Are
there
any
risks
that
you
have
and
so
forth
and
so
on
and
here
in
the
article
pete
explains
how
you
can
store
them,
steps
centrally
and
then
apply
them
to
many
different
projects
without
having
to
recopy
them,
re-clone
them
and
so
forth,
and
so
on.
A
Yeah
so
really
cool
stuff,
an
an
absolutely
a
useful
set
of
rules
for
any
development
for
sure,
so
really
really
cool
and
then
the
last
piece
is
the
five
rules
of
the
field
for
file
server,
migrations,
the
microsoft
trees.
Sd5
please
go
to
the
cloud,
go
to
the
loadout,
go
to
the
roads,
but
it's
basically
just
oh.
C
A
That's
the
five
roles,
yes,
but
yeah,
so
so,
basically,
there's
actually
good
learning
so
before
you
start
delete
so
because
you
don't
want
to
actually
move
all
of
the
things
so
and
because
that's
just
not
how
typically
half
of
the
stuff
is
not
even
used,
so
you
really
want
to
focus
on
those
things
which,
which
I
used
put
everything
in
the
right
place.
The
role
of
three
the
permission
mantra
and
my
covenant
so
really
walking
through
the
different
from
the
real
world
scenarios,
so
really
cool
stuff
from
alex
on
that
one.
A
C
C
Thunder
cloud:
yes,
exactly
cool
nimbus,
exactly
right,
so
and
for
all
all
these
different
different
clouds.
Why,
while
they're
still
on
microsoft
cloud,
they
use
different
names
for
resources,
different
urls
to
authenticate,
escrow
and
so
on.
So
we
got
a
request,
or
somebody
saw
that
we
don't
properly
deal
in
cli
with
the
us
government
cloud.
C
A
A
C
C
That
was
exactly
the
same
thing
for
me
until
I
came
to
the
point
like
I
need
to
organize
myself,
I
need
to
better
understand
what
I'm
doing
so.
Then
I
created
a
mind:
map
of
okay.
What
are
the
different
things
that
I
have
on
my
plate
and
then
okay,
what
are
things
that
are
blocked
because
I'm
waiting
for
some
money
versus
what
are
the
things
that
I
can
do
and
that
allows
me
to
not
drop
any
balls.
C
So,
yes,
I'm
gonna
do
this,
because
I'm
waiting
and
they're
like
every
just
like
reshuffle,
okay,
is
this
still
on?
Is
this
still
up
to
date
or
not
because
otherwise
it's
exactly,
as
you
say
like,
and
that's
also,
I
think
typical
for
our
jobs
I
can
say,
is
that
I'm
not
doing
one
thing,
I'm
working
on
10
things
in
parallel
and
every
day
I'm
pushing
them
a
little
bit.
Yeah!
That's
true!.
A
C
A
True,
that
is
true,
but
now,
let's
actually
close
this
one.
So
thank
you,
everybody
for
watching.
Thank
you,
everybody
for
listening
and
watching,
depending
on
what
format
you're
using
we'll
be
back
within
the
the
within
a
week.
So
yes,
it's
a
weekly
show
but
have
a
great
week
and
we'll
be
in
touch
bye-bye
bye.
Thank.