►
Description
Microsoft 365 platform community call delivered on June 14th. Three demos - Latest on deprecating basic auth for Exchange, Introduction to Microsoft Graph .Net SDK v5, and Introduction to Microsoft Graph Postman collection. Introduced a Microsoft Community Initiative to build a unified Microsoft Cloud Community model with Microsoft 365 and Azure.
Released Microsoft 365 Platform Community (PnP) - June 2022 update and 8 articles/documents. Register for Power Platform Samples Contributor and Writing for the Web events this month. The host of this call was Brian T. Jackett (Microsoft) | @BrianTJackett. Q&A takes place in chat throughout and live at end of the call.
Learn more
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/m365pnp/blog
• Download invite for this weekly Microsoft 365 Platform community call: https://aka.ms/m365-dev-call
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - https://aka.ms/m365/community
A
Good
morning,
good
afternoon,
good
evening,
everybody
this
is
the
microsoft
365
platform
community
call.
I
am
brian
d
jacket
your
host
for
today
on
today's
agenda.
We've
got
great
presentations,
we're
doing
before
we
get
to
those,
though
we'll
do
a
quick
little
round
of
news
in
the
soft
side
platform
area,
we'll
talk
about
our
monthly
contributors.
Thank
everyone
for
joining
in
for
those
things
and
we'll
do
our
together
mode
picture
as
usual.
A
A
So,
if
you're
working
with
team
solutions,
if
you're
building
sharepoint
framework
solutions,
power
platform
and
more
we've
got
lots
of
different
galleries
available
to
you
and
as
always,
if
you
don't
want
to
get
overwhelmed
by
all
these
different
urls
that
are
out
there,
we
do
have
our
one-stop
shop.
Aka.Ms
m365pnp,
where
you
can
find
all
of
the
different
meeting,
invites
all
the
different
resources
links
and
so
forth
great
way
to
get
plugged
into
the
environment
and
be
able
to
contribute
back
in
now,
in
addition
to
our
own
m365
developer
community
call
here.
A
This
is
a
weekly
call
on
tuesdays.
Do
note
that
we
will
be
taking
a
break
during
the
months
of
july
and
august.
This
is
for
summer
break
for
a
lot
of
folks
in
the
northern
hemisphere.
It's
a
little
bit
more
difficult
to
schedule
folks,
so
we
will
be
taking
breaks
during
july
and
august.
We
will
be
coming
back
in
september,
though,
so
please
do
look
for
us
in
that
month.
A
Aside
from
this
call,
though,
we
do
have
a
number
of
other
ones
that
are
out
there
available
things
for
adaptive
cards
for
identity
platform,
office,
add-ins
power
platform,
viva
connections,
sharepoint
and
more.
You
can
find
all
these
different
invites
at
ak
dot.
Ms
slash
m365
slash
calls
now,
if
you're
looking
to
get
started
in
the
m365
ecosystem,
a
lot
of
great
resources
available
to
you
out
there,
two
that
we
do
want
to
highlight
on
here
on
the
page.
A
The
first
is
our
microsoft
365
developer
program
with
this
you
can
get
a
free,
e5
developer
tenant.
This
is
great
for
being
able
to
do
some
sandbox
deployments
be
able
to
test
things
out
literally
as
a
tenant
administrator.
So
really
you
have
full
control
to
that
tenant
and
it
comes
with
content
as
well
as
those
e5
licenses.
You
can
find
more
at
aka
dot.
Ms
slash
m365
dev
program
sign
up
today
and
get
your
tenant
available
to
you.
A
Also.
We
have
a
lot
of
great
training
material
up
there
as
well
on
microsoft,
learn.
This
is
a
lot
of
great
things
in
terms
of
being
able
to
see
some
learning
paths
and
different
training
modules.
Other
things
you
can
actually
go
and
see
all
for
free,
so
there
is
no
charge
for
this
training.
You
can
find
this
at
ak
dot.
Ms
slash
m365
dev,
slash,
learn.
A
And
we
also
have
our
mux365
pmp
weekly,
hosted
by
vesa
and
wall
deck,
great
information
that
they're
sharing
in
terms
of
the
community.
What
things
are
going
on
talking
to
product
group
members
a
great
way
to
get
to
see
what
is
available
to
us
inside
of
the
m365
ecosystem?
You
can
find
more
at
videos
at
the
ak
dot,
ms
slash,
pnp,
weekly
or
also
the
podcast
on
pmpweekly.podbean.com.
A
Now,
in
terms
of
our
samples,
as
I
mentioned
on
the
earlier
side,
we've
got
a
lot
of
different
samples
that
are
available
to
us
out
there
from
a
lot
of
different
technologies
from
graph
to
viva,
to
office
add-ins
to
pmp
to
spfx
and
more.
We
are
actually
at
1099
samples,
literally
one
away
from
breaking
that
1100
mark.
I
remember
months
back
when
we
were
doing
this
call.
We
were
in,
like
the
hundreds,
like
500
600,
so
great,
to
see
this
growth
that
we've
had
over
the
past
months.
A
B
David
is
not
actually
here
because
he
has
an
in
richmond
it's
that
time
of
the
year,
so
everybody's
traveling,
but
as
you
might
be
wondering
how
do
you?
How
do
I
get
started
with
those
samples
or
how
to
get
started
on
contributing,
maybe
in
our
community
side
and
that's
why
we
actually
created
already
well
back,
is
caring
initiative
and
from
akms?
Not
sharing
is
caring.
B
You
can
find
more
details
around
this,
and
this
is
really
helping
hands
on
helping
you
hands-on
on
getting
started
on
either
using
some
of
the
technologies
which
we
have
in
microsoft,
365
or
contributing
in
github
or
consuming
the
material
in
a
guitar.
Now.
The
next
event
in
here
is
around
power
platform,
and
that's
going
to
be
two
time
events.
B
So
there's
going
to
be
two
separate
events
to
go
through
that
hosted
by
hugo
hugo,
bernier
and
david
warner,
but
through
the
summer
time
you
will
not
see
as
many
events
happening
in
the
sharing
is
caring
initiative,
but
we'll
get
back
on,
let's
say
in
a
normal
flow
of
business
in
the
august
time
frame,
but
please
take
advantage
of
this.
They
are
really
really
awesome.
Events
and
people
like
give
always
such
a
great
feedback
on
this
back
to
you,
praying
actually.
B
Yeah,
so
something
that
we're
working
together
with
microsoft,
365
and
azure
is
that
we're
working
to
introduce
this
microsoft
community
initiative,
the
microsoft
cloud
community
initiative-
and
this
is
really
about
us
for
microsoft-
helping
the
community
to
make
events
and
and
coordinate
events
and
make
things
happen.
So
we
are
looking
into
having
this
one
unified,
let's
say
door
to
everything
around
microsoft,
community
and
that's
looking
also
for
community
members.
So
we
will
have
a
community
advisory
board,
which
is
basically
a
selected
group
of
people
for
is
it
12
to
18
months?
B
I
can't
remember,
and
then
we
will
re-elect
people
in
that
board
after
a
while
right
now
as
we're
starting
this,
we
want
to
have
volunteers
to
submit
to
be
a
volunteer
in
the
community
advisory
board,
and
it
can
be
you
so
anybody
in
this
call
who's
interested
about
community
and
empowering
other
people
sharing
is
caring
mentality.
Please
please
please
sign
in
to
that
form,
and
let
us
know
that
you're
interested
in
being
part
of
that
we're
looking
into
all
of
the
different
people
across
the
world
to
be
involved.
B
So
we
also
released
today-
and
this
is
actually
from
a
social
media
perspective.
This
is
going
to
be
released
within
30
minutes.
We
have
the
update
of
june
2022
on
the
microsoft
365
platform
community,
and
this
is
the
one
blog
post
where
we're
listing
all
of
the
videos
and
samples
and
edits
and
guidances
and
references
what
has
happened
within
last
month
and
not
forgetting
about
all
of
the
contributors.
So
all
of
the
community
contributors
and
microsoft
contributors
have
been
involved
in
our
open
source
and
community
efforts.
B
We
are
starting
to
list
all
of
the
community
members,
so
we
want
to.
We
will
not
call
you
out
in
the
school,
but
we
want
to
thank
you
all
for
being
actively
involved
within
last
within
within
the
last
month,
within
our
open
source
and
community
efforts,
so
basically
contributing
in
docs
in
github,
in
samples
doing
a
videos,
demos,
whatever
is
available
for
you
to
take
advantage.
B
C
B
B
These
are
also
the
companies
which
we
have
a
permission
to
show
their
logo.
So
if
your
name
was
listed
in
the
previous
slides,
your
your
company
logo
is
not
here,
please
being
us
on
linkedin
or
in
twitter
or
in
whatever
the
form.
It
is
and
gives
us
your
permission
to
show
their
company
logo
and
we'll
promote
the
company
here
as
well.
B
So
these
are
the
companies
who
allow
their
employees
to
activate
be
active
on
the
community
side,
and
this
is
then
the
list
of
all
of
the
microsoft
employees
which
have
been
involved
in
the
open
source
community
site
across
the
microsoft
365
platform,
community
efforts.
So
thank
you.
Thank
you
for
microsoft,
employees
as
well.
Many
of
them
are
spending
their
evenings
and
weekends
to
making
these
things
happen,
so
it's
not
necessarily
that
it's
part
of
their
role.
So
thank
you.
Thank
you
for
that
and
I
guess
that's
the
quick
summary
on
all
of
the
community
assets.
A
Your
price
all
right,
thank
you
so
much
vasa
and
yes,
echoing
that,
a
big
thanks
to
everyone
who
has
been
in
our
community
contributing
back
we'd
love
to
see
all
of
your
wonderful
contributions,
and
we
appreciate
them
so
much
now,
moving
to
some
of
the
different
news
items
that
we've
got
going
on
in
the
community.
First,
we'll
go
to
the
microsoft
65
developer
blog.
We
have
two
different
blog
posts
on
here.
The
first
one
is
for
the
microsoft
teams,
js
sdk
version
2.,
just
a
little
bit
of
a
mouthful.
This
is
now
generally
available.
A
What's
great
about
this.
Is
we're
now
actually
taking
that
ability
to
deploy
teams
apps
now
into
additional
hubs?
So
first
things.
First,
targeting
things
like
outlook.
It's
a
great
way
to
be
able
to
see
those
apps
being
able
to
have
native
integrations
so
basically
build
once
and
run
in
multiple
locations.
A
This
is
the
first
release
of
this
again.
We
are
starting
to
add
more
and
more
capabilities
over
time.
Please
do
take
a
look
at
that
blog
post
and
see
what
is
available
for
the
manifest
for
the
sdk
and
other
updates
that
are
available
with
it.
Also
another
update
coming
from
the
microsoft
bookings
team.
They
have
released
application
permissions
for
their
api
on
graph.
We
love
to
see
that
additional
support
for
other
types
of
permissions
on
here.
A
Turning
over
to
the
team
side
of
the
house,
we
do
have
five
different
updates
and
blog
posts
out
there
that
we
want
to
share
out
there.
First
with
the
inside
microsoft
podcast,
they
did
some
interviews
with
a
coffee
roaster,
as
well
as
a
power
bi
data
analytics
team
really
kind
of
showing
what
did
they
do
during
pandemic
in
terms
of
adapting
their
businesses
being
able
to
continue
to
be
productive
and
supporting
their
customers,
so
really
good
insights
just
into
how
things
kind
of
function
and
they
were
able
to
adapt
and
continue
to
thrive
out
there.
A
Also,
we
got
some
updated
guidance
and
information
coming
from
two
of
our
partners,
confluence
and
zendesk.
They
show
some
increasing,
integrations
they've
got
with
the
teams
platform
so
showing
the
different
updates
that
they've
applied
to
this
and
are
rolling
out
to
customers
good
to
see
our
partners
integrating
into
the
ecosystem,
as
well
as
the
ways
that
they're
leveraging
the
platform
to
help
folks
out
next,
in
terms
of
hybrid
meetings,
you
may
have
seen
some
different
blog
posts
out
there
about
the
microsoft
teams.
A
They
got
these
things
called
teams
rooms-
there's
some
insights
into
here
about
how
microsoft
itself
is
actually
incorporating
those
types
of
best
practices,
different
technologies
and
also
updates
just
the
team's
platform
to
help
make
it
a
very
inclusive
kind
of
process
for
folks
that
are
potentially
attending
a
meeting
remotely.
I
actually
did
get
a
chance
to
test
this
out
myself
last
week,
while
I
was
on
site
very
cool
to
see
some
different
technology
and
ways
that
we're
supporting
folks
to
really
have
those
inclusive
meetings.
A
A
And
lastly,
there
are
two
updates,
just
in
terms
of
teams
meetings
being
able
to
have
some
kind
of
improvements
we
have
from
the
ai
side
of
things
in
terms
of
noise
cancellation,
in
terms
of
being
able
to
have
call
quality,
make
sure
things
sure
that
people's
voices
are
heard
as
clearly
as
possible,
also
the
video
feeds
coming
through
without
artifacts
and
so
forth.
So
a
lot
of
great
little
highlights
and
tips
that
they
show
about
this
in
the
two
last
blog
posts
on
there.
A
D
Okay,
thanks
brian
hello,
everyone
I
will
walk
to
the
team's
platform
updates,
starting
with
the
sending
welcome
message
to
the
selected
channel.
Welcome
messages
from
your
conversation.
Apps
are
the
first
thing:
users
fees
after
the
installation.
They
play
a
core
part
in
highlighting
your
app's
main
features,
starting
the
setup
flow
and
onboarding
users.
D
Before
this
feature,
apps
welcome
messages
was
always
sent
to
the
general
channel
and
not
to
the
user's
selected
channel.
With
this
update,
welcome
messages
will
be
automatically
routed
to
the
user
selected
channel
host
installation
when
an
app
is
installed
in
teams.
Contacts
from
the
client,
the
user
selected
channel
id
from
the
installation
flow
would
now
be
set
to
the
conversation
id
for
the
installation
update
and
the
conversation
update
event.
D
There
are
no
changes
required
for
the
bots
that
are
currently
using
reply
id
using
installation
update
and
the
conversation
update
event
using
the
conversation
id.
This
should
be
the
case
for
most
of
the
apps
bots
that
are
not
using
provided
conversation
id
to
send
a
welcome
message
in
teams
can
be
updated
to
reply
using
this
value.
To
take
the
advantage
note
that
this
is
currently
available
only
in
developer
preview
going
to
the
second
update,
it's
on
app
studio,
duplication
absolutely
will
be
deprecated
by
june
30..
D
Now
you
can
configure,
distribute
and
manage
your
team's
app
within
the
new
developer
portal.
Your
existing
apps
will
be
available
in
developer
portal
under
apps,
slash,
app
studio
section.
You
can
upgrade
these
apps
to
the
latest
configurations
so
that
you
can
start
using
them
in
developer
portal.
So
these
were
the
platform
updates.
If
you
have
any
feedback
or
any
situation,
please
post
on
ak
dot
ms
teams
platform
feedback,
the
link
is
available
in
the
footer.
You
could
also
follow
us
on
twitter
and
configure
the
rss
feed
to
get
the
regular
platform
updates.
A
Thank
you
so
much
rajin
and
with
this
we'll
turn
things
over
to
our
group
picture
time.
So
if
we
would
like
to
please
turn
on
your
video
cameras,
we'd
love
to
see
your
bright
and
smiling
shiny
faces
already
seen
a
bunch
coming
in
there
excellent
that's!
If
you
want
to
switch
over
to
do
the
recording
from
yours.
A
All
right,
thank
you
so
much.
I
will
pull
back
up
the
presentation
now
we'll
move
into
the
actual
stars
for
today's
show.
We've
got
our
demos
from
greg.
Give
us
a
little
bit
about
basic
authentication
andrew
on
graph.net,
sdk5
and
seb.
Do
a
little
bit
about
the
graph
postman
collection.
First
things:
first,
we'll
kick
off
with
greg
the
floor
is
yours.
E
Terrific
thank
you
very
much.
I
will
endeavor
to
share
my
slides
and
I'll
say
hi.
Everyone
thank
you
for
letting
me
come
and
have
the
opportunity
to
talk
about
something
rather
important
that
we're
doing
with
basic
author
exchange
online,
something
that
involves
customers,
developers,
partners,
everybody,
it's
a
fairly
impactful
change
and,
frankly,
as
much
help
as
we
can
get
from
everyone,
the
better.
E
E
How
we
are
telling
customers
to
go,
find
the
usage
that
they
have
and
what
they,
what
it
means,
what
they're
going
to
do
about
it
and
then
there's
a
bunch
of
useful
links
as
well,
so
I'm
going
to
run
through
as
quickly
as
I
can
happy
to
follow
up
with
questions
in
the
chat
or
wherever,
okay.
So
here's
the
is
the
real
low
down
so
beginning
october,
1st
2022.
We
are
going
to
start
to
turn
off
basic
all
for
a
number
of
protocols
for
eight
different
protocols.
E
I'm
going
to
highlight
a
few
key
words
because
some
of
the
communication
customers,
however,
clearly
put
it.
Some
customers
will
interpret
it
to
mean
something
different.
So
I'm
going
to
say
the
word
beginning
october
1st,
we
will
begin
to
turn
off
basic
author
as
a
number
of
protocols.
That
means
we
will
not
turn
everyone
off
on
october
1st.
That
would
be
a
pretty
awful
day
to
work
in
microsoft.
Support
if
that
were
the
case,
we're
also
not
turning
off
the
protocols
themselves.
E
Just
be
super
clear
on
that
active
sync,
as
a
great
example
keeps
coming
up.
People
keep
asking
so
you're
turning
off
active
sync,
no
we're
turning
off
basic
auth
for
exchange
activision,
so
those
iphones
and
on
androids
will
continue
to
work,
but
they
just
can't
use
basic
all
so
we're
turning
off
pop
and
imap.
You
may
or
may
not
be
surprised.
There
are
still
a
lot
of
people
using
pop
and
imap,
primarily
applications,
not
really
client.
You
know
client
day-to-day
usage
for
email.
B
E
Another
thing
that
we
announced
we
were
going
to
do
would
be.
We
would
interrupt
basic
auth
for
customers
between
now
and
october.
As
we
rolled
this
out,
I
will
tell
you
that
that's
primarily
focused
at
the
smb
end
of
the
market
smb
and
edu
customers,
primarily
smb
customers,
they're,
not
the
ones
that
read
the
message
center.
They
don't
read
the
blogs,
they
don't
hang
on.
Every
word
I
put
out
on
basic
auth,
so
there
will
be
some
interruptions
of
service.
There
are
ways
customers
can
go
and
opt
out
of
that.
E
We
are
doing
it
to
quite
a
few
customers
at
the
moment
and
I'm
hearing
a
few
screams
and
that's
okay
right
customers
can
turn
it
back
on
again
after
october,
though
that's
it,
okay,
so
the
other
one
I
want
to
really
call
out
as
well
is
smtp
auth
used
for
sending
mail
outbound.
We
have
already
turned
off
smtp
all
for
customers
that
don't
use
it
basic
auth
and
we've
turned
it
off
for
millions
of
tenants.
I'll
tell
you
all
right.
E
We've
turned
off
basically
for
millions
of
times
right
now
who
don't
use
it,
but
for
whom
it
was
enabled,
so
we're
actually
protecting
customers
by
turning
it
off
but
smtp.
If
it
is
still
in
use,
we
are
not
going
to
touch
it
even
if
we
turn
it
off.
You
can
turn
smtp
back
on
and
the
main
reason
for
that
is,
there
are
a
ton
of
devices
and-
and
you
know,
hardware
devices
that
really
can't
be
updated
to
support
or
flows.
So
we
will
allow
smtp
auth
for
the
foreseeable
future.
We
have
no.
B
E
To
turn
that
off,
so
the
question
that
most
customers
ask
is
how
do
I
know
if
I'm
using
basic
author
so
there's
a
couple
of
places?
I
want
to
point
you
to
so
one.
Is:
we've
been
sending
message
center
posts
to
all
the
tenants
who
use
basic
auth
every
month
since
about
october
last
year?
It
is
the
mother
of
all
male
mergers.
Think
of
it
like
that.
E
E
It's
not
precise
numbers,
it's
indicative,
because
if
you
think
about
something
like
exchange
web
services,
it's
used
by
applications,
it's
used
by
outlook
for
windows
for
mac,
it's
a
little
hard
to
be
precise.
Exactly
how
many
users
in
any
particular
time
are
using.
You
know
specific
applications
at
our
level
at
an
aggregate
level.
E
However,
if
you
want
the,
if
you
want
the
detail,
then
azure
ad
signing
reports
is
really
the
place.
A
customer
or
partner.
Whomever
can
go,
find
the
detail
so
message
center
posts
are
about.
I
know
there's
basic
auth
usage.
Azure
id
reports
are
about
who's,
the
user.
What's
the
nip
address?
What's
the
machine
name
and
so
on
and
so
forth?
That's
really
where
you
find
the
detail.
There's
a
filter
in
the
client
app
settings
in
the
azure
id
signing
reports.
E
You
want
everything
under
legacy,
but
if
you're
a
large
customer
there
is
a
link
as
well,
because
the
the
report
there
will
will
will
not
be
very
easy
to
download
if
you're
a
large
customer
with
a
lot
of
usage-
and
you
might
want
to
use
azure
id
workbooks
or
something
like
that,
instead
stream
it
to
log
analytics
now,
when
you
get
all
of
this
data,
when
a
customer
gets
all
of
this
data,
then
it's
like
work
out.
What
do
I
do
now?
Well,
the
first
thing
is:
get
the
data
exported
in
json
format.
E
If
you
are
downloading
not
csv,
because
json
format
will
give
you
all
the
user
agent
strings
and
user
agent
strings
while
not.
Obviously
a
hundred
percent
infallible
are
very
useful
to
help
customers
identify
what
the
usage
is
and
where
it's
coming
from.
If
I
were
to
write
a
bad
app,
I
probably
wouldn't
create
a
user
agent
string
of
my
evil
app
version
1.0.
I
would
probably
try
and
hide
it
so
user
agent
strings
are
not
infallible,
but
for
most
customers,
they're
incredibly
useful.
E
E
Well,
if
you're
a
large
customer,
you
probably
have
an
mdm,
but
if
you
have
an
mdm
solution,
you
need
to
use
it
to
change
the
profile
to
change
the
authentication
type
now
apple's
mdm
api,
for
example,
does
not
allow
you
to
modify
the
auth
type
of
an
existing
profile.
You
have
to
create
a
new
profile.
E
But
the
most
practical
solution
for
users
is
remove
the
account
from
the
device
and
add
it
back.
That
sounds
rather
rubbish.
I
know
the
native
male
app
on
an
iphone
has
supported
a
wall
for
two
years
or
more.
Why
is
it
still
using
basic
auth?
Because
there
are
a
lot?
Well,
it's
using
basic
auth,
because
the
user
had
their
first
iphone
more
than
two
years
ago.
They
configured
their
email.
It
was
using
basic
auth.
They
then
went
to
the
apple
store
or
wherever
and
got
themselves
a
new
iphone
shiny,
new
iphone.
E
The
first
thing
it
says
is:
do
you
want
me
to
transfer
your
data
and
settings
you're
like
well?
That
sounds
like
a
good
idea.
I
should
do
that
with
all
the
pictures
of
your
family
and
your
cats
and
everything
come
across
and
all
your
settings,
which
include
the
authentication
type
used
for
the
mail
app,
so
it
will
keep
using
basic,
even
though
it's
the
newest
iphone
so
remove
the
account.
Add
it
back.
E
Okay,
certificate
based
off
I'll
call.
This
out
is
not
basically
certificate
based
or
if
you're,
using
that
for
active
sync
will
show
up
under
legacy
off
in
the
azure
designer
reports,
but
it
is
not
going
to
be
effective
when
we
turn
off
basic
or
slightly
confusing
we're
trying
to
clarify
and
actually
have
a
call
today
to
try
and
get
some
of
this
clarified
in
in
our
documentation.
E
Okay,
jumping
forward
outlook
for
windows,
there's
a
variety
of
protocols
being
used
biggest
flag
at
the
top
here.
Is
this
oauth
2
client
profile
enabled
flag?
Is
a
per
tenant
flag
users
get
organization
config
set
organization
config?
If
that
flag
is
set
to
false
output
windows
cannot
do
modern
auth.
It
is
told
not
to
it's
only
out
for
windows.
That's
affected
by
this
particular
switch.
Make
sure
your
a
a
tenant
has
the
flag
set
to
true
out
for
windows
can
do
modern
auth.
E
Now,
when
you
look
through
user
agent
strings,
then
there's
that
the
user
agent
string
will
tell
you
what
version
of
outlook
is
in
play
by
whether
it
has
a
14,
15
or
16
in
it.
If
it's
a
14,
it's
out
of
2010,
and
yet
people
are
still
using
outlet.
2010,
okay
and
15
is
out
with
2013
needs.
A
registry.
Key,
though,
can
do
modern.
E
North
16
should
be
doing
modern
north,
and
so,
if
you
see
16
in
there,
somebody's
done
something,
that's
it
should
be
doing
modern
north
and
it's
not
either
the
flag
is
set
in
the
tenant
to
be
false
or
they've
gone
and
pushed
out
some
kind
of
policy
people
falling
asleep
to
my
voice.
I
don't
know
if
that's
a
good
thing
or
a
bad
thing,
all
right
I'll,
keep
plugging
on
regardless.
E
Sorry,
if
I'm
losing
your
audience
brian
investor
right
so
ews,
this
one's
a
bit
tricky
another
lots
of
developers,
there's
a
ton
of
apps
out
there
still
using
basic
auth.
The
user
agent
strings
are
mostly
helpful.
Python
requests
2.26.0
is
not
very
helpful.
Customers
are
discovering
applications
that
are
using
basic
auth.
They
need
help
from
they're
going
to
need
help
from
developers
partners
everybody
to
figure
out
what
they're
going
to
do
to
remediate.
E
The
app
ews
can
do
all
clearly
graph
would
be
a
preferential
way
to
go,
but
this
is
the
time
to
redevelop
your
app
from
ews
to
graph,
probably
a
little
late.
That
should
be
more
of
a
strategic
goal
rather
than
a
tactical
goal.
I've
called
out
a
couple
of
things
in
here
as
well.
If
you
see
user
agent
strings
from
surface
hubs
and
from
teams
rooms,
the
teams
rooms
devices
are
using
basic
auth.
E
There
are
updates
coming
from
the
teams
team,
but
you
can
go
in
the
teams,
admin
center
or
the
admin
console
and
change
the
device
to
use
mod
north
very
quickly
and
easily.
Customers
need
to
do
that
or
they
are
going
to
get
cut
off
pop
imap
and
powershell,
believe
it
or
not,
there's
still
quite
a
lot
there
going
on.
There
are
no
user
agent
strings
in
the
protocol,
so
we
have
no
idea
what
the
client
app
is
that's
being
used.
I
know
there's
a
lot
of
applications
that
are
using
them.
E
They
all
or
all
of
these
protocols
support
modern
flows,
client
credential
flow
for
and
imap
will
be
out
very
very
soon
for
non-interactive
flows,
but
for
client,
apps
and
in
any
kind
of
app
that
supports
an
interactive
flow
code
is
already
there.
People
are
going
to
need
help
so
make
sure
customers
look
in
the
message
center.
They
then
they
know
if
they
have
a
problem
or
not
use
the
azure
id
sign
reports
to
get
the
detail
figure
out
what
to
do
with
the
users
communicate
to
the
users.
E
E
E
A
Excellent,
thank
you
so
much
greg
a
very
useful
information
and
we
hope
that
everyone
does
pay
attention.
These
dates
are
coming
fast
and
we
would
like
people
to
definitely
make
sure
that
they're
prepared
and
ready
for
this
once
the
the
cutoff
date
hits
excellent.
At
this
point,
we'll
turn
over
to
andrew
to
talk
to
us
a
little
bit
about
the
graph.net
sdk
v5
android.
If
you'd
like
to
share
your
screen
and
the
floor,
is
yours.
C
So
hey
everyone,
my
name
is
andrew
and
I'm
from
the
graph
developer
experiences
team.
So
today
I
just
wanted
to
talk
a
bit
about
the
graph.net
v5
sdk
that
we
are
working
on
right
now
and
we're
just
hoping
to
address
some
of
the
few
changes
that
we're
making
and
enhancements
to
enrich
the
user
experiences.
C
So
the
first
thing
I
wanted
to
talk
about
really
is
like
the
change
of
the
developer
experience
and
at
the
top
of
the
slide,
I
can
see
what
you
would
currently
do
to
make
a
call
with
the
v4
and
the
bottom,
with
the
the
new
preview
version
of
v5,
and
you
notice
like
a
couple
of
things,
and
one
of
them
is
like
that.
There
is
no
longer
the
request
function
in
the
in
the
whole.
Fluent
api
method
called
to
make
the
the
user
sdk
a
bit
more
substantive
as
well
as
now.
C
So
the
next
thing
I
also
wanted
to
talk
about
was
the
barking
stone
and
really
the
bucking
store
is.
It
enables
like
dirty
tracking
of
the
changes
in
various
objects
and,
like
you
notice,
like
with
version
4,
the
sdk
like
in
a
scenario
where
you're
trying
to
like
disable
the
recurrence
of
an
event.
Let's
say
you
fetch
the
event
and
then
you
transfer
the
recurrence
property
to
now
and
then
send
it
back
what
you
notice.
C
That
would
really
won't
work,
because
the
serializer
won't
really
send
out
null
values,
but
now
with
v5,
we
have
this
barking
store
that
keeps
track
of
changes.
That's
happening
to
the
object
when
it
comes
back
and
therefore
you
should
just
be
able
to
set
the
property
to
now
and
send
it
back,
and
that
will
sort
out
your
issue.
And
since
now
we
are
also
keeping
track
of
the
object.
C
I
also
wanted
to
talk
about
is
now
the
use
of
parameter
objects
so
like
in
a
given
scenario
where
you
are
trying
to
maybe
call
the
send
mail
api
currently
in
version
four.
These
parameters
of
the
data
function
are
literally
function.
Parameters
of
the
ascend
main
function.
So
what
now?
What
we've
done
is
we've
moved
over
to
using
a
request
body
which
is
basically
like
a
nested,
is
an
object
that
nests
these
properties
inside
so
like.
C
Finally,
I
just
was
hoping
to
talk
about
like
a
couple
of
scenarios
that
weren't
really
supported
in
the
current
version
of
the
sdk
and
the
first
one
really
was
calling
like
the
dollar
count,
endpoints
or
the
account
segments
or
data.
So
this
is
a
scenario
like
whereby
you're
trying
to
like
get
the
number
of
users
in
your
tenant
or
something
so
you
just
want
to
get
that
as
an
integer
and
get
it
back
into
your
app
to
figure
out
what
you
want
to
do
next.
So
you
couldn't
really
do
this.
C
You
really
have
to
probably
build
the
url
yourself
and
make
your
own
native
http
request,
but
now,
with
the
use
of
kyoto
and
using
the
generated
sdk,
you
can
just
use
this
single
line
of
code
to
configure
request,
get
the
count
and
get
that
to
use
it.
Then.
The
next
scenario
is
the
support
for
the
auditor
cast
segment,
so
this
is
where
now
you
want
to
like
api
side
filtering,
especially
for
apis
that
give
like
a
collection
of
different
types
of
object.
C
So
let's
say
you
want
to
get
members
of
the
group
and
the
members
of
the
group
could
be
users
or
applications
or
any
other
type.
So
with
the
new
version
5
that
we're
working
on
in
preview,
you
can
just
add
the
extra
segment
like
to
get
like
members
that
are
users,
and
this
will
eliminate
the
need
for
you
to
do
like
client-side
filtering
and
add
all
that
logic.
That
would
make
life
a
bit
harder
for
you.
C
So
you
can
just
follow
the
link.
There
are
a
lot
of
other
changes
that
we
are
working
on,
so
the
link
will
lead
you
to
detailed
changes
of
things
that
are
going
on
the
new
version.
It's
in
preview,
we're
looking
for
feedback
from
everyone.
So
please
give
us
feedback
on
github
and
let
us
know
what
we
can
do
to
make
it
better.
With
the
current
version,
we
are
going
to
continue
supporting
it
with
metadata
updates
quickly,
as
we
continually
do,
that's
it
for
me
I'll
hand
it
over
back
to
brand.
A
Thank
you
so
much
andrew
great
to
hear
about
the
updates
coming
for
the.net
sdk
for
this.
With
this
there's
one
last
question,
I
think
in
the
chat
window,
if
you
want
to
address
that
one
andrew
otherwise
we'll
turn
things
over
to
seb,
to
give
us
a
little
overview
of
the
graph
postman
collection
except
the
floor.
Azures.
F
Awesome
thanks
brian
thanks
andrew
great
to
see
that
movement
on
the
dot
nine
under
that
five,
but
not
that
five
on
the
v5
version
over
that
sdk,
I'm
a
little
bit
tired,
I'm
sorry
everybody!
So
today
I
want
to
do
a
quick
introduction
to
our
postman
collection
for
micrograph,
but
this
will
be
a
series
of
of
different
of
different
sessions.
We
don't
know
exactly
yet
how
much
of
them,
but
at
least
two
or
three
sessions
around.
How
can
you
get
great
tooling,
to
play
with
postman
in
microsoft
graph?
F
The
reason
why
is
we
really
believe
that
there
is
a
strong
connection
between
postman
as
a
tool
in
microsoft
graph
as
an
api
that
can
work
together
in
this
session?
I
want
to
go
through
the
fundamentals
of
what
postman
is.
How
does
it
play
together
with
graph?
How
can
you
get
some
sort
of
data
through
postman
connecting
to
microsoft
graph,
but
the
next
couple
of
sessions,
we're
gonna,
go
and
really
do
some
advanced
scenario,
doing
chaining
of
different
requests.
We're
gonna
do
how
does
this
integrate
with
our
own
graphics
blur?
F
F
So,
first,
what
is
postman
if
you've
never
used
postman,
it's
absolutely
okay.
Postman
has
been
there
for
a
long
time
is,
is
usually
one
of
the
tool
that
is
basically
open
at
all
time,
for
anybody
that
are
heavily
using
apis
or
building
apis
postman
is
a
full
api
platform.
It
helps
you
test,
build
validate
work
as
a
team,
but
one
of
the
part
that
you
want
to
focus
on
today
is
really
around
using
an
api,
so
it
really
enables
you
to
use
apis
in
a
secured
way
in
a
very
convenient
way.
F
It
simplifies
each
step
of
the
api
and
it
enables
you
to
work
collaboratively
around
the
api.
So
it's
a
full
platform.
There
is
a
free
version
that
we're
going
to
use
today,
which
is
absolutely
sufficient
to
do
what
we
want
to
do
with
microsoft
graph.
But
if
you're
looking
into
more
the
enterprise
capabilities,
you
can
definitely
look
into
what
postman
can
offer
we're
going
to.
F
First
start
with
a
small
demo
around
the
postman
fundamentals,
and
here's
me
just
to
kind
of
get
you
used
to
the
ui
used
to
the
capabilities
that
postman
really
offers
and
from
there
we're
gonna
move
on
to
more
graph
related
topics.
So
let
me
start,
let
me
go
to
here
so
first,
this
is,
and
I'm
just
going
to
close
these
things.
So
it's
not
too
confusing
when
you
land
into
postman,
you
have
a
graph
explorer
like
experience,
or
maybe
we
can
say
that
the
graph
explorer
has
a
postman
like
experience.
F
It's
a
chicken
or
the
egg
situation.
Here,
I'm
gonna,
let
you
figure
out
which
one
came
first,
but
in
this
case
I
already
added
two
different
co.
What
we
call
collections
to
my
workspace,
the
first
one,
is
the
microsoft
graph.
We're
gonna
come
back
to
this
one
a
little
bit
later,
but
the
second
one
is
called
the
postman,
echo
think
about
the
echo
service
from
postman
as
a
way
to
test
the
capabilities
of
what
postman
really
offers.
F
And,
let's
start
with
the
first
thing,
I
think
that's
one
of
the
most
useful,
the
most
even
used
scenario,
which
is
around
getting
content
from
an
api,
doing
a
simple
get
to
an
api
and
get
the
content
here.
So,
for
example,
if
I
expand
the
postman
echo
that
I
have
here
so
when
you
create
a
new
postman
account,
you
automatically
get
the
postman
echo
in
there,
so
don't
delete
it.
It's
super
useful
to
go
back
to
the
basics
every
single
time.
F
So,
for
example,
if
I
do
a
request
method
here,
I
can
just
click
here
and
let's
look
at
what
we
have
here.
First,
we
have
the
resource
that
we're
looking
for.
In
that
case,
it's
a
postman,
echo
dot
com,
slash
get
with
a
couple
of
parameters
that
are
in
there
and
I
have
a
big
send
button
that
send
button
will
do
the
the
action.
So
it's
going
to
use
the
http
verb
that
we
have
here
we'll
send
that
to
this
endpoint
and
we
will
get
a
response
that
will
show
up
right
here.
F
So
what
is
great
with
this
is
now
we
have
the
ability
not
only
to
do
a
request,
but
also
to
ex
to
basically
expose
the
entire
response
back
to
you
when
you're
building
an
application
that
calls
into
an
api
having.
This
is
a
great
way
for
you
to
understand
what
you
have
available
so,
for
example,
when
you're
looking
into
an
odata
api,
when
you're
going
to
do
your
different,
select
or
different
filters,
or
even
different
top
and
limit
capabilities
or
even
count,
you
will
see
exactly
what
you
will
be
getting
back
from
it.
F
So
that's
a
great
way
to
understand
the
shape
of
the
data
and
understand
what
you
can
do
with
that
data.
So
when
you
expect
a
response
back
from
that
api,
you
know
exactly
how
the
data
is
shaped,
though
we're
not
just
doing
gets.
We
can
do
all
sorts
of
different
capabilities
like,
for
example,
I
can
do
just
a
post,
so
I
can
basically
send
raw
capabilities
here
to
this
one
here
and
when
I
hit
send
it
automatically
brings
it
back.
So
basically
that
api
is
really
an
echo
api
right.
F
F
Obviously
the
one
you
want
to
use
to
build
capabilities
in
your
app
or
you're,
going
to
it's
going
to
feel
a
little
bit
lonely
in
your
app.
That
being
said,
it
really
helps
you
to
understand
how
you
can
control
the
different
capabilities
of
postman,
because
when
we
get
into
graph
you're
going
to
see
that
there
are
a
lot
of
capabilities
that
we're
using
in
graph-
and
I
really
believe
that
going
back
to
the
basics
with
a
postman.
Echo
collection
is
a
great
step
for
you.
F
So
there
will
be
a
couple
of
things
you
can
do
with
here
and
I'll.
Let
you
explore
this.
I
I
don't
want
to
go
too
much
into
the
deeds
here,
but
I
think
what
is
important
is
always
use
that
collection
to
go
back
to
the
basics.
If
you
want
to
test
something,
if
you
want
to
understand
how
to
use
a
buddy,
a
json
object
to
send
in
your
to
your
api
whatsoever,
you
can
definitely
do
that
now.
Let's
talk
a
little
bit
about
graph.
F
So
when
you
use
the
link
that
you
see
here,
aka
dot
ms
slash
graph,
slash
postman
when
you
you
get
to
that
link,
you
will
be
able
to
follow
a
six
or
seven
step
process
to
get
your
environment
set
up
with
postman
connected
to
your
microsoft,
365
environment.
We
highly
recommend
that
you
start
with
the
microsoft
365
developer
program,
so
you
can
really
play
around
and
have
the
full
capabilities
can
go
on.
F
So
let
me
go
here
so
first
we're
going
to
use
this
guide
here
where
we
have
actually
an
8
step
guide
from
forking
the
marks
of
graph
postman
collection.
You
go
there,
you
will
be
able
to
create
a
fork
and
bring
the
the
updated
or
the
latest
version
of
the
graph
collection
inside
your
own
environment,
which
is
great
because
you're
going
to
get
notification
when
we
change
the
the
original
collection
you're
going
to
get
notifications
that
this
has
changed
so
you're
going
to
be
able
to
bring
the
changes
back
to
you,
it's
great.
Why?
F
Because,
if
we
add
new
endpoints
to
graph-
and
we
add
them
to
our
postman
collection,
now
you're
going
to
get
access
to
them.
The
second
thing
you
will
want
to
do
is
to
download
potentially
the
postman
agent,
especially
if
you're
using
the
web
browser
I'm
a
big
fan
of
web
browser.
I
prefer
web
browser
to
having
an
app
installed
on
my
machine,
so
I
I
am
using
the
postman
agent
online
machine
you'll
have
to
if
you're,
using
the
the
rich
client
of
postman,
which
is
exactly
the
same
experience
just
wrapped
inside
an
application.
F
The
third
step
you
will
want
to
do
is
to
create
an
azure
80
application.
Let
me
zoom
in
a
little
bit
an
azure
80
application,
and
why
do
you
want
to
do
that
well
to
be
able
to
control
the
permissions
that
you
will
have
access
to,
so
you
will
be
able
to
add
permissions
as
you
go
for
every
new
api,
so
you
will
know
exactly
what
are
the
sets
of
permissions
that
your
app
might
be
using?
F
That's
what
I
highly
recommend
any
developers
when
you're
using
an
application
and
you're
using
postman,
make
sure
that
postman
in
your
application
might
even
be
using
the
same
azure
ad
app.
So
that
way,
when
you
test
stuff
in
postman,
you
have
the
same
set
of
permissions
that
you
have
in
your
app.
So
that
way,
you
don't
get
data
that
you
would
not
get
actually
in
using
the
sdks
or
using
raw
http
calls
go
through
that
procedure.
F
F
Well,
postman
will
be
your
best
friend
so
you're
going
to
set
up
your
azure
80
application,
which
support
and
certificate
and
secrets
to
support
the
full
app
permission
cycle.
Then
afterwards,
you
will
configure
the
authentication
inside
postman
to
make
sure
that
you
can
get
tokens
either
delegated
or
have
permissions
on
the
endpoints.
F
But
what
I
want
to
do
today,
I
want
to
show
you
the
experience
once
you're
in
postman
of
these
things.
So,
first
of
all
let
me
go
to
my
workspace
here
and
let
me
close
these
two
tabs
that
I
have
open
earlier
that
we're
calling
into
the
postman
echo
service
and
let
me
expand
on
the
graph
here
so
first
you're
going
to
find
two
different
folders,
one
that
is
delegated
and
one
that
is
application
permissions.
F
So,
basically,
every
requests
that
live
in
delegated
will
all
be
using
a
single
token.
So
all
you
won't
have
to
re-authenticate
every
time
you
just
need
to
use
to
authenticate
with
your
delegated,
and
all
of
these
requests
that
are
here
will
automatically
get
access
to
the
delegated
token
same
thing,
with
the
application.
You're
gonna
be
able
to
do
the
exact
same
thing.
F
So,
let's
start
on
how
you
get
a
token
and
how
you
can
make
a
call
from
here.
So
first
you
want
to
go
to
your
delegated
tab
and
you
click
here
and
you're
going
to
find.
Oh
there
you
go,
you
have
a
bunch
of,
except
that
was
already
done.
Using
the
guide
that
I
showed
earlier,
you
will
be
able
to
go.
You
go
to
the
bottom,
you're
gonna
be
able
to
say
get
a
new
access
token.
Now,
I'm
gonna
select
my
account
and
now
it
just
completed.
F
So
it's
really
really
really
well
integrated
between
our
off
service
and
in
this
case
postman,
then
afterwards,
you're
going
to
click
on
use
a
token,
because
that's
the
token
you
want
to
use-
and
now
let's
say
you
want
to
go
to
the
users
and
you
want
to
get
my
profile.
So
now
you
see
https
graph.microsoft.comme,.
F
We
will
automatically,
if
that's
one
of
the
beauty
of
using
the
collection,
we
will
automatically
add
to
the
headers
the
right
access
token
and
make
sure
that
you're
always
authenticated.
So
that
way
you
won't
have
to
copy
paste
that
token,
over
and
over
and
over
again.
In
that
case,
I
have
this
one
here.
I
click
send
and
automatically
I
get
my
user
here.
I
can
also
go
here
and
change
it
hey
I
want
to.
I
want
to
hit
the
v1.
F
F
So
let's
do
the
same
thing
I'm
going
to
hit,
don't
save
and
let's
do
the
same
thing
with
application.
So
the
application
here
is
exactly
the
same
thing.
The
only
difference
that
we're
using
a
client
id
and
a
client
secret,
rather
than
a
delegated
token.
That
requires
me
to
log
in
so
now,
I'm
just
going
to
click
get
access
token.
It's
used
in
my
client
id
my
client
secret.
F
F
Last
thing
I
want
to
show
is:
how
did
I
get
all
of
this
thing
to
work?
Well,
in
my
app
that
I'm
using,
I
have
an
app
that
is
using
that
we're
using
an
actually
the
app
sorry
that
we're
using
to
authenticate
in
there.
We
already
have
a
list
of
api
permissions,
and
here
it's
really
up
to
you
to
decide
to
decide
what
are
the
scopes
that
you
want
to
support.
F
Well,
in
that
case,
I'm
going
to
have
to
go
through
blue
party,
but
like
we
would
receive
back
an
a
403,
a
forbidden,
then
how
do
we
get
a
new
token?
You
go
into
your
app.
You
add
your
new
permission.
You
do
a
grant
admin
for
that
permission,
then
you
can
go
back
to
getting
a
token
through
postman
and
re-submit
that
request
and
you
would
be
good
to
go.
A
A
So
big,
thank
you
to
all
of
our
presenters
today,
including
greg
andrew
and
seb,
great
information
shared.
We
really
appreciate
all
the
information
you
shared
demos
and
so
forth.
As
always,
our
recordings
will
be
available
within
the
next
24
hours
or
so
on.
The
m365
community
youtube
channel.
You
can
find
us
at
aka
dot.
Ms
slash
m365,
pmp
videos.
Please
do
subscribe
today,
so
you
get
all
the
latest
announcements
and
news
on
that
also
follow
along
with
us
on
twitter,
at
microsoft,
365
dev
as
well
as
m365
pnp.
A
Our
next
call
will
be
next
week
june,
21st
at
8am,
pacific
time
as
as
usual,
you
can
find
all
the
different
links
for
our
invites
at
aka
dot.
Ms
slash
m365
calls
and
one
other
additional
announcement
for
this
again.
We
will
be
on
break
on
the
months
of
july
and
august.
So
please
do
update
your
calendars
accordingly.