►
Description
Microsoft 365 platform community call delivered on November 30th. Three demos delivered during call, one was not captured in the session recording. Demos - Microsoft 365 Application Certification (not captured), Consume a multi-tenant API within Viva Connections Adaptive Card Extensions (ACEs), and Introduction to Microsoft Graph Go SDK. Start Viva Connections development today with free training Learning Path: Extend Microsoft Viva Connections. Join the Microsoft 365 Developer Program and get a free E5 developer tenant with instant availability. The host of this call was Sébastien Levert (Microsoft) | @sebastienlevert. Q&A takes place in chat throughout and live at end of call.
Learn more:
• See the full blog post for this call at: https://aka.ms/m365pnp/community/blog
• Download invite for this weekly Microsoft 365 Platform community call: https://aka.ms/m365-dev-call
• 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
A
We
have
people
in
conference
room
which
is
a
good
sign
of
recovery.
I'm
happy
to
see
you
guys
over
there.
Let's
see
how
it
goes
with
the
together
mode
later,
our
agenda
today
we're
gonna
have
tons
of
people
in
this
call,
and
I
can't
wait
to
hear
from
all
of
them.
First
we're
going
to
have
our
latest
updates
and
news
on
the
microsoft
365
platform,
where
we're
going
to
cover
some
of
the
news.
Some
of
the
latest
programs.
We
have
around
the
entire
platform
we
have
afterwards
we're
gonna.
A
Take
our
now
famous
group
picture
time
with
together
mode,
so
vesa
will
take
a
nice
screen
grab
of
us
waving
altogether.
If
you
want
to
join
and
afterwards
we're
going
to
go
through
the
demos,
three
demos
today
so
very
packed
agenda,
I
will
try
to
not
spend
too
much
time
on
the
updates.
So
we
can
have
all
these
demo
presenters
take
all
the
time
they
they
should.
A
Sdk
then
afterwards,
if
time
permits
we're
going
to
have
the
q
a
so,
let's
jump
on
to
some
of
the
news
that
we
have
for
this
week.
First,
a
couple
of
resources
that
we
believe
are
useful
for
all
of
us.
First,
our
microsoft
365
developer
videos
where
you
can
find
all
the
microsoft
driven
educational
presentation,
videos
on
our
youtube
channels.
We
also
have
the
same
thing
with
from
the
community
videos
parts
of
the
the
calls
we're
doing
either
on
the
the
pnp
call
on
the
platform.
A
Call
the
sharepoint
framework
and
viva
connections
call
all
of
them
in
a
single
repository
on
youtube.
So
really
really
cool
thing
to
do,
especially
at
lunchtime
like
bite,
size,
videos
have
a
look
at
them:
we're
open
source
at
heart.
We
have
tons
of
different
repos.
You
can
have
a
look
to
see
how
we're
contributing
how
we're
helping
the
community
all
of
our
repos
are
right
there.
A
We
also
have
different
sample
galleries,
where
you
can
find
examples
of
work
that
people
like
you
are
already
building
and
have
contributed
to
these
samples,
and
you
can
get
inspiration
from
these
sample
galleries
a
little
bit
more
on
that
later.
And
finally,
you
want
to
find
all
of
this
under
a
single
roof.
Well,
aka.ms
m365pmp!
A
That
program
super
useful,
especially
if
you're,
starting
with
microsoft,
365
development
learn.
We
want
to
learn
more
about
stuff
in
the
microsoft
365
ecosystem,
so
you
can
get
started
with
our
learn.
Our
different
learn
modules,
where
you
can
get
all
the
capabilities
of
the
m365
platform
with
training
modules.
So
you
can
go
on
the
link
that
is
on
the
screen
right
now,
and
now
we
even
have
the
latest
modules
with
the
viva
connections.
Training.
We're
gonna
even
hear
a
little
bit
about
that
module.
Today,
later
with
vessa
and
paulo.
A
Temples
not
only
we
have
different
sites
with
samples,
but
we
also
have
a
single
pane
of
glass
where
you
can
get
access
to
all
the
samples
that
have
been
created
by
the
community,
where
you
can
find
all
of
them
filter,
search,
find
by
author,
where
you
can
go
to
ak
dot.
Ms
m365
samples
and
the
simple
solution
gallery
will
give
you
access
to
everything
you
can
think
of
from
list
formatting
to
web
parts,
to
power
platform
to
team
samples,
anything
that
is
related
to
the
m365
platform.
You
can
find
it
there.
A
It's
awesome,
it's
super
useful
and
it's
really
quick
to
get
access
to
some
of
these
features.
I
haven't
seen
lately
capabilities
where
you
can
download
just
a
simple
sample
from
the
repos,
not
the
entire
repo.
So
thanks
you
go
for
adding
that.
To
that
platform,
even
more
sharing
is
caring
david.
Do
you
want
to
walk
us
through?
The
sharing
is
scary.
B
Absolutely
thank
you
seb.
Well,
for
those
that
are
new
to
the
community.
It's
important,
as
seb
had
mentioned,
to
know
that
we're
an
open
source
community
and
that
means
using
and
or
contributing
back
to
the
community,
but
we
know
there's
hurdles
along
the
way
things
like
interfacing,
with
github
or
understanding.
How
are
how
are
you
going
to
present
some
of
the
demos
that
you
would
like
to
present
the
things
that
you
are
contributing
back?
The
sharing
is
caring.
B
Initiative
is
a
program
that
is
here
to
provide
you
hands-on,
safe
space,
inclusive
guidance
on
utilizing
all
of
our
resources
and
contributing
back.
So
that
means
walking
you
through
your
first
pull
request.
If
you've
never
done
a
contribution,
giving
you
some
interface
to
how
you
can
set
up
your
spf
workstation
and
much
much
more,
you
can
see
a
whole
host
of
upcoming
sessions.
B
Following
this
call,
you
just
go
to
the
link
that
you
see
in
your
chat
and
find
that
session
you're
gonna
hit
join
more
and
it'll,
bring
you
directly
to
the
call
for
those
who
didn't
already
pre-register
right
after
the
call
I'll
include
a
link
as
well
after
the
call
again,
these
are
free,
safe
space
opportunities
for
you
to
collaborate
and
learn
together,
hands-on,
not
recorded,
so
you
can
bring
any
and
all
questions
invite
you
to
any
and
all
of
them.
Please
come
we'd
love
to
collaborate
with
you
forward.
A
Ama,
by
the
way,
some
of
the
resources
we
also
have
is
our
microsoft,
365,
dev
podcast,
hosted
by
jeremy,
fake
and
paul
safeline,
it's
great
to
see
lots
of
weekly
updates
around
the
microsoft
365
platform
by
either
microsoft
pm
shipping,
new
capabilities,
community
members,
teaching
on
how
they're,
using
or
learning
about
new
capabilities
and
even
just
random
news.
Definitely
the
m365
podcast
is
the
podcast
to
subscribe
to.
A
Another
podcast
webcast
amazing
resource
is
our
pnp
weekly,
where
you're
going
to
get
the
latest
news
and
announcements
for
microsoft
in
the
community,
where
we
have
a
format
of
interviewing
some
of
the
community
members
or
internal
microsoft.
Employees
where
you
can
learn
about
what
the
community
has
done
in
the
last
week,
so
pap
weekly
always
available
on
ak
dot.
Ms
pmp
weekly
and
you
can
also
listen
to
the
pap
weekly
on
pod
being
right.
There
so
join
the
fun
guys.
A
A
A
Also,
the
latest
microsoft
365
community
update,
is
available
where
we
highlight
the
latest
and
greatest
of
everything
around
the
community
contributors
organizations,
samples,
repos
and
all
of
that
feel
free
go
there.
I
think
it's
amazing
to
see
how
inclusive
and
diverse
this
community
is,
and
I
think
this
super
long
article
is
a
great
example
of
the
richness
and
the
depth
of
this
community.
So
have
a
look
learn
about
the
community
and
we're
super
happy
to
have
you
being
part
of
it
and
now
it's
our
optional
picture
time.
A
C
C
A
C
C
A
C
A
F
Everyone
greetings
wherever
you
are,
I'm
arpita,
I'm
a
program
manager
in
the
microsoft
azure
identity
organization
and
I
primarily
work
on
the
application
platform.
Security
and
focusing
on
a
lot
of
products
are
features
that
focus
on
the
authenticity
and
trustworthiness
and
of
the
apps
in
the
ecosystem.
F
So,
as
part
of
my
presentation
today,
I'm
going
to
talk
about
m365,
app
compliance
and
how
those
experiences
will
turn
in
the
azure
ready.
I
believe
I
have
around
15
to
20
minutes
so
I'll
quickly
run
through
this.
But
meanwhile,
if
you
have
any
questions,
please
feel
free
to
pause
me
and
ask
your
questions.
F
Let's
make
it
more
interactive.
My
goal
here
is
to
provide
an
overview
of
m362
app
compliance
program
and-
and
I
believe
most
here
would
be
aware
of
that
program-
so
I'll
not
spend
a
lot
of
time
on
that
and
then
again
some
some
introduction
and
value
of
publisher
verification-
probably
I
repeat
for
most
folks
here,
but
just
just
a
brush
up
and
then
microsoft,
365
application,
service,
certification,
experiences
within
azure
id.
F
So,
let's,
let's
dive
in
the
goals
of
m365
application
compliance
program
for
those
who
are
not
aware
of
that,
microsoft
has
introduced
the
m362
app
complex
program
very
recently,
like
one
or
two
one,
one,
one
and
a
half
years
ago.
It's
it's
nascent,
but
really
picking
up
the
steam
very
very
fast
and
in
our
effort
towards
building
a
very,
very
secure
and
and
trustworthy
apps
ecosystem,
we're
putting
all
the
weight
behind
to
to
make
sure
whatever
we
can
to
enable
developers,
as
well
as
the
entire
ecosystem
and
platform
experiences
to
come
together
and
build.
F
A
Thank
you
so
much
arpita.
This
is
an
an
amazing
program
that
I
think
all
of
you
on.
The
call
should
definitely
have
a
look
at
we've
seen.
Partners
and
customers
definitely
leveraging
it
and
we've
seen
adoption
going
like
skyrocket
with
these
programs.
So
thanks
for
sharing
super
interesting
now
we
will
be
transitioning
to
vesa
and
paulo
live
from
dusseldorf
around
consuming
a
multi-tenant
api
within
viva
connection,
aces.
C
C
So
pretty
recently,
we
did
a
a
reference
solution
related
on
consuming
a
multi-talented
apis
within
the
microsoft
viva
connection,
adaptive
card
extensions
and-
and
we
wanted
to
have
a
15-minute
story
related
on
what
is
available,
and
this
is
a
reference
solution,
a
kind
of
a
blueprint
which
is
demonstrating
how
to
make
these
things
happen.
But
let's
have
a
quick
look
on
a
few
slides
first
on
on.
Why
would
you
do
this?
So,
first
of
all,
just
a
recap.
Of
course,
the
microsoft
365
opportunity
is
huge
for
the
partner
ecosystem.
C
We
have
more
than
250
million
monthly
active
users
in
microsoft
teams,
and
we
have
more
than
200
million
monthly
active
users
in
sharepoint
online.
Of
course,
a
lot
of
the
people
are
overlapping
between
these
things,
because
sharepoint
is
powering
the
content
within
the
microsoft
teams,
but
related
on
viva
connection.
We
were
connection
is
exposed
in
the
teams,
but
it's
powered
by
sharepoint
behind
of
the
scenes
and
is
powered
by
the
sharepoint
framework.
C
Now,
in
this
particular
case,
we
basically
are
going
to
show
a
the
steps
and
requirements
of
building
a
isv
partner
offering
for
viva
connection.
So
what
we
actually
need
to
do
here
and
having
a
new
viva
card
exposed
in
the
viva
connection,
either
in
a
desktop
or
in
a
mobile,
so
you'll
see
the
mobile
experience
in
the
in
this
line.
C
So,
first
of
all,
viva
connection
experiences
are
being
built
with
using
sharepoint
framework
again
a
bit
of
an
interesting
terminology
to
call
it
still
a
sharepoint
framework,
but
will
will
hopefully
get
the
name
change
pretty
soon.
Marketing
is
in
charge
of
running
that
now
you
use
the
sharepoint
framework
to
create
those
reward
cards
and
application
customizations
and
web
parts,
and
we
actually
the
story
relates
in
all
of
them.
C
The
the
sample
sort
of
solution
focuses
on
cards,
but
in
the
same
way,
if
you
would
be
using
a
or
creating
a
partner
with
part
for
the
viva
connection
desktop,
and
it
would
be
hitting
a
molded
down
api,
you
would
actually
have
the
similar
requirements
now,
quite
typically,
a
partner
api
offering
is
based
on
some
sort
of
an
api
or
a
service
being
hosted
in
the
cloud.
So
the
the
cart
or
the
web
part
or
an
application.
C
So
deployment
of
this
one
we
have
actually
a
a
ready-to-use
sample
available,
actually
hosted
live
on
the
internet,
which
is
pretty
cool,
so
you
can
actually
step
through
the
steps
and
in
the
location,
we'll
share
the
location
and
guidance
and
all
of
that
and
we'll
show
some
assets
in
a
second.
But
we
need
to
have
an
api
which
needs
to
be
consented
in
a
customer
tenant.
C
So
the
customer
needs
to
be
aware
of
this
multitenant
api
so
that
they
can
start
using
it
and
then,
as
the
solution,
the
sharepoint
framework
solution
is
getting
installed.
The
solution.
Api
permissions
needs
to
be
approved
so
that
the
apis
can
be
called
in
that
particular
channel.
But
I
guess
the
easiest
way
to
understand.
One
of
the
bits
and
pieces
is
to
actually
show
the
solution.
So
let's
jump
on
that
one
and
paulo
is
going
to
take
lead
on
that.
D
Okay,
yes,
thank
you
visa.
So,
first
of
all,
let's
start
having
a
look
at
the
solution
in
action
so
that
we
can
play
with
it
and
we
can
understand
the
overall
goal
from
a
functional
point
of
view,
and
the
idea
is
to
provide
an
order
management
solution
with
a
ui
for
end
users
based
on
an
adaptive
card
extension
and
in
the
back
end
we
have
an
azure
function
which
will
provide
just
a
fake
list
of
orders
for
the
sake
of
simplicity
but
which
is,
as
visa
said,
already
hosted
on
azure
for
you.
D
So
you
can
play
with
this
solution
without
any
need
to
host
anything
on
your
site,
but
you
can
just
play
with
it
and
learn
from
it.
Of
course,
if
you
want,
you
will
also
find
in
the
source
code
of
the
solution,
the
azure
function,
so
that
you
can
take
inspiration
from
it.
So
now,
let
me
show
you
the
adaptive
card
extension
in
action.
This
is
my
adaptive
card
to
manage
the
orders.
D
I
can
show
you
that
in
the
settings
of
this
adapter
card,
we
configure
the
url
of
a
back-end
service,
which
would
be
the
one
we
are
going
to
use
in
order
to
show
the
functionalities,
and
if
I
will
go
to
the
preview
mode
of
my
workbench,
we
can
see
that
we
can
easily
click
on
this
button
to
see
a
list
of
orders,
a
fake
list
of
orders.
As
I
said,
because
this
is
just
for
the
sake
of
providing
an
example.
D
And
here
we
can
see
what
kind
of
experience
the
end
users
can
have
in
adaptive
card
extensions.
So,
for
example,
we
can
expand
an
item.
We
can
have
a
dynamic
ui.
I
can
say
that
as
a
person
in
charge
of
managing
the
orders,
I
can,
for
example,
say
that
this
order
is
now
under
processing
and
I
can
update
it.
So
imagine
this
kind
of
experience
from
a
mobile
device
where
the
user
in
storage,
for
example,
can
start
processing
an
order
received
by
the
system,
and
you
can
also
insert
a
new
order.
D
Okay,
new
order
and
you
can
use
another
card
to
insert
a
new
order
in
the
system.
Just
for
the
sake
of
making
an
example,
it
will
be
the
order,
number
11
or
11
2021
or
whatever
else,
and
this
will
be
my
customer
id
a
fake
one
for
sure,
and
the
order
will
be
inserted
today
with
a
specific
status
which
can
be
any
of
these
values.
When
I
will
click
on
insert
order,
we
will
see
that
right
now
we
have
10
orders
in
the
system,
but
by
clicking
on
insert
order.
D
D
Now,
how
did
we
build
this
solution?
We
have
the
adaptive
card
by
itself
and
we
can
really
briefly,
without
digging
into
the
code,
see
that
we
have
a
sharepoint
framework
solution
built
with
all
the
technology
landscape
that
we
already
know
if
we
are
sharpened
framework
developer.
This
is
just
an
extension
built
with
sharepoint
framework.
D
I
mean
just
the
class
built
with
typescript
and
all
the
beauty
and
the
capabilities
that
we
have
in
sharepoint
framework,
and
then
we
can
build
all
the
ui
elements
of
this
solution,
relying
on
the
adapter
card,
json
syntax,
which
is
one
of
the
killer,
features
in
my
opinion
of
the
adaptive
card
extensions,
because
in
order
to
define
the
ui,
you
simply
need
to
rely
on
a
well-known
and
broadly
adopted
technology
like
the
adaptive,
cart
json.
Here,
for
example,
you
can
briefly
see
the
json
we
are
using
to
render
the
list
of
orders.
D
This
is
the
front
end
of
our
solution
and
we
are
relying
in
the
back
end
on
a
major
function.
So
we
also
have
thanks
to
the
capabilities
that
we
have
in
sharpening
framework
the
possibility
to
use
a
backhand
api
secured
with
azure
active
directory,
and
that's
why,
in
our
solution,
we
have
in
azure
active
directory
an
application
registered
as
a
multi-tenant
app,
which
is
provided
to
any
tenant
willing
to
consume
our
solution.
D
How
can
you
use
it
well
in
order
to
have
this
application
available,
registered
or
known
in
your
target
tenant,
you
will
simply
need
to
go
through
a
constant
flow,
exactly
the
one
we
were
talking
about
in
the
previous
demo.
Actually,
so
the
user
is
willing
to
use
this
solution
in
their
tenant,
we'll
simply
to
go
through
a
registration
flow,
called
consent
flow
and
we'll
have
the
application
registered
in
their
tenant.
D
Then
we
provide
a
backend
infrastructure
based
on
an
azure
function,
hosted
on
azure,
which
will
provide
the
actual
backend
functionality
to
manage
the
list
of
orders
and
to
provide
all
the
create,
read,
update,
delete
and
query
functionalities
for
the
list
of
orders.
So
the
key
components
are
the
front
end
built
with
the
adaptive
card
extensions,
the
back
end
built
with
the
azure
functions
and
in
the
middle
we
have
azure
active
directory
to
secure
the
communication.
D
D
An
aav,
http
client
object
to
consume
a
specific
api
which
one
well
the
one
that
we
registered
as
an
obstacle
as
a
multi-tenant
application
in
our
azure
directory.
So
this
id
is
precisely
the
one
we
have
in
azure
ready
for
our
multi-tenant
application
right
here.
So
here
we
are
just
matching
that
application
unique
id
in
order
to
get
back
a
client
object
which
will
make
it
possible
for
us
to
easily
consume
the
backend
api
and
api.
I
said
it
is
a
azure
function
one.
D
So
if
we
look
at
the
function
sections,
we
can
see
that
we
have
some
okay.
We
need
to
refresh
this
guy,
or
I
can
even
switch
here
to
show
you
the
visual
studio
side
of
the
story.
We
have
functions
like
functions
to
get
the
list
of
orders
or
function,
to
get
a
specific
order
and,
generally
speaking,
all
the
create
read,
update
capabilities
well
on
the
sharpened.
D
Side
in
the
order
service
that
we
are
using,
we
simply
have
the
same
functionalities
in
typescript
on
the
client
side.
So
when
we
want
to
get
the
list
of
orders,
we
will
target
the
url
of
the
api,
followed
by
the
api,
slash
orders
endpoint
and
it
works
almost
like
when
we
use
the
microsoft
graph
from
sharepoint
framework.
But
now
we
are
using
a
custom
api
that
we
are
consuming
to
provide
additional
functionalities.
D
So
here
in
the
spfx
reference
scenarios
repository
on
github,
you
can
find
the
whole
source
code
of
the
solution.
Under
the
ac
pnp
contoso
orders
sample
solution,
and
in
there
you
will
find
the
source
code,
as
I
said,
both
of
the
spfx
adaptive
cap
extension
and
of
the
function
app
together
with
a
script
to
do
the
provisioning
in
your
own
tenant
and,
of
course,
a
set
of
documents
of
md
documents
that
you
can
refer
to.
D
In
order
to
do
the
minimal
path
to
awesome,
so
if
you
simply
want
to
play
with
it
well,
you
can
come
here.
You
can
execute
the
powershell
script,
providing
the
name
of
your
target
tenant
and
the
solution
will
be
registered
and
available
in
your
tenant,
meaning
that
you
will
have
the
constant
flow
applied
to
your
tenant,
and
you
will
find
the
sharepoint
framework
solution
automatically
installed
in
your
app
catalog
and
available
in
your
viva
connections.
D
C
Thank
you,
paula
and,
of
course,
not
working
on
the
final
location
of
all
of
these
assets
and
documentation,
and
all
that
so
most
likely
we'll
surface
this
sooner
or
later
in
the
docs.microsoft.com,
but
for
now
they're
in
github
and
in
this
location
and
we'll
put
that
one
in
the
video
notes
and
in
the
blog
posts
related
on
the
recording.
So
everybody
can
access
them
already.
But
thank
you
following
that.
One
thank.
D
A
G
Vince,
take
it
over
exactly
thank
you
for
having
us
today,
so
you
should
be
able
to
see
me
and
hear
me
as
well
yep
and,
as
you
said,
mesa
won't
be
able
to
join
us
because
they
don't
have
power
in
our
district
anymore.
For
now,
so
let's
get
started.
Welcome
everyone
and
thank
you
for
tuning
in
today,
I'm
vincent
a
developer
on
the
microsoft
graph
sdk
team.
G
I
should
have
been
joined
by
mesa
program
manager
on
our
team
as
well,
but
unfortunately
she's
having
power
issues
and
today
we're
here
to
talk
about
our
new
preview.
Microsoft
graph
go
sdk
and
we'll
see
how
it
works
and
what
value
it
provides
to
you.
If
you
don't
write
any
go
code,
don't
run
away
just
stay
here,
listen
in
and
see.
If
you
have
any
go
developer
friends,
so
you
can
tell
them
about
this
new
awesome
sdk.
G
We
don't
have
a
lot
of
slides,
so
I'll
go
through
this
quickly.
Why
would
you
use
this?
This
new
go
sdk
or
what
does
it
provide
for
you?
Well,
it
has
a
few
key
benefits
that
you
can
use
as
a
go
developer.
First
off
the
authentication.
It
is
based
off
azure
identity
and
brings
support
for
multiple
authentication
flows
like
the
authorization
code,
the
browser
interactive,
the
client
credentials
or
client
certificate
flow.
G
G
On
top
of
all
of
that,
we
also
have
a
middleware
pipeline
that
handles
crosscutting
concerns
like
well.
If
there
is
an
error,
should
we
retry?
Should
we
back
off
exponentially
if,
if
microsoft
graph
is
busy
and
all
those
kind
of
things,
so
that's
automatically
handled
for
you,
you
don't
need
to
implement
that
yourself
anymore.
We
also
have
a
redirect
handler
because
for
some
api
calls,
your
client
is
actually
being
redirected
to
another
service
like
sharepoint,
onedrive
and
so
on
and
so
forth.
G
Well,
we
do
have
a
handler
that's
available
from
day
one
and,
of
course,
we're
planning
to
add
more
handlers
as
we
move
through
the
preview
and
as
we
move
towards
ga
to
provide
a
better
experience
to
the
sdk
users
and
with
that
that's
pretty
much
all
the
slides
we
have
for
now.
So
let's
jump
in
the
demo.
G
So
here
I
already
run
my
go
application
and
I'm
using
the
device
code
flow.
So
what
I'm
going
to
do
is
I'm
going
to
run
through
the
application
and
then
I'm
going
to
show
you
the
code
here
we
go
so
I'm
going
to
go
off
to
microsoft.com
device.
Login
paste
in
the
code
select
my
account
click.
Ok,
that's
the
same
content
experience
that
arpita
was
telling
us
about
in
the
first
demo.
G
G
It
will
list
out
the
first
10
messages
and
it
will
also
send
an
email
and
we'll
get
back
to
that
from
the
code,
but
before
we
jump
into
the
code,
usually
when
you
want
to
get
started
with
a
new
sdk
or
with
a
new
technology,
well
you're,
looking
for
documentation,
another
great
thing
we
put
together
as
a
team
thanks
to
jason
and
other
team
members,
is
all
the
get
started
section
for
the
sdks
in
the
public.
Documentation
here
has
been
updated
to
include
all
the
go
instructions.
G
So
how
do
you
install
the
go
sdk
for
example,
or
how
do
you
create
a
go
client
with
the
authentication
setup
for
you,
for
example,
and
also
for
each
and
every
api
endpoint?
We
now
have
go
snippets
and
ghost
samples
available
for
you,
which
you
can
also
see
in
the
graphics
folder.
So
if
you
go
to
ak.mslg,
you
will
go
to
the
graphic
explorer
that
you've
probably
seen
many
times
at
this
point,
and
you
can
go
there
to
execute
different
requests.
G
I
can
against
microsoft
graph
and
if
you
run
the
query
and
then,
if
you
go
over
to
the
response,
tab
response,
section,
click
on
the
code,
snippet
tab
and
then
on
the
go
tab.
You
now
have
the
equivalent
code
for
that
specific
api
call
that
is
available.
So
if
I
change,
for
example,
to
go
to
slash,
miss
messages
to
get
the
messages
for
the
current
user
same
thing,
I'll
get
the
go
code
snippet.
That
is
the
reflection
of
that
specific
api
call.
G
So
now,
if
we
jump
into
the
code
of
my
application
to
show
you
how
it's
built,
the
first
thing,
of
course,
is
the
imports.
I
will
have
to
import
azure
identity
here,
as
well
as
the
microsoft
graph
sdk
and
a
few
sub
modules
under
the
microsoft
graph
sdk
to
get
things
like.
Whatever
messages,
how
do
you
send
an
email
and
all
those
different
things?
Then?
If
we
move
on
to
that
section
here,
I'm
actually
creating
a
client
all
the
way
through
here.
G
So
the
first
few
lines
here
are
actually
using
azure
identity
to
set
up
a
device
called
credential.
This
is
what
we've
just
seen
earlier,
where
the
application
will
say:
hey
go
to
that
url
paste,
that
code
go
through
the
authentication
of
the
content
and
then
come
back
to
the
applications
once
you're
done.
This
is
great
for
devices
or
application
services
that
do
not
have
a
great
user
input.
Experience
like
iot
devices
like
console
applications
like
I'm
just
showing
you
or
wearables
or
stuff
like
that.
Of
course.
G
The
next
step
here
is
to
create
a
new
identity,
authentication
provider.
So
this
is
where
we
pass
it.
The
credentials
which
we've
just
built
as
well
as
the
scopes
we're
going
to
be
using.
You
don't
have
to
do
that,
but
it's
always
better
here,
I'm
using
gradual
consent
where
I'll
say
for
this
specific
piece
of
code.
I
just
need
mail.read
and
mail.send,
so
this
is
what
I'm
going
to
be
requesting.
Of
course,
you
can
also
do
it.
G
The
other
way
around
where
you
register
all
your
scopes
on
your
application,
registration
and
don't
provide
anything
here
and
what's
going
to
happen,
is
that
you'll
have
the
content
go
through
all
the
scopes
that
are
registered
within
the
application
directly
instead,
once
I
have
that
I
can
build
my
request,
adapter
that
will
translate
my
fluent
api
request
into
actual
http
request
using
the
authentication
provider
we've
just
built
to
authenticate
the
request,
and
I
can
feed
that
into
my
graph
service
client
and
the
graph
service.
Client
itself
will
be
the
entry
point
for
the
fluent
api.
G
So
now,
if
we
move
to
actual
api
calls
once
we've
set
up
everything
here,
we
do
have
one
first
thing:
we're
doing
here,
we're
doing
client
dot
me
to
get
the
current
user
who's
authenticated,
dot
messages
to
get
their
messages,
dot,
get
to
list
all
the
messages
that
are
available.
But
if
we
look
above
a
little
bit,
I'm
also
providing
a
filter
here
to
say:
I
only
want
the
messages
that
start
with
major
update.
For
example,
I
don't
want
the
other
messages.
G
I
just
want
those
messages
that
start
with
that,
and
this
is
how
we
get
started
so
automatically
the
go.
Sdk
will
provide
you
types
for
the
query
parameters
and
also
the
ability
to
set
the
request,
headers
and
a
few
other
things,
and
you
can
use
that
when
you
execute
the
request
to
kind
of
narrow
down
your
request
to
get
the
exact
specific
things
that
you
you'd
like
to
get.
G
When
I
get
that
that
response,
what
I'm
doing
is
I'm
just
iterating
for
the
messages
to
display
the
receive
date
time
and
their
subject
as
I've
seen
as
I've
shown
in
the
application.
The
next
stop
and
the
next
thing
we're
doing
we're
actually
posting
a
new
message.
So
here
I'm
using
the
models
that
are
generated
by
are
available
through
the
go
sdk
and
I'm
creating
a
new
message.
I'm
setting
the
subject
and
then
within
the
message,
I'm
setting
the
body
of
a
message
with
some
kind
of
content.
G
We
support
enumerations,
we
support
the
different
values
here
and
then
on
the
message.
I'm
also
setting
the
recipients
here
where
we
are
setting
the
new
email
address
for
the
recipient,
which
we're
putting
into
a
collection
for
the
message,
and
once
we've
done
all
of
that
we
put
the
body
again
in
the
request
options
like
we've
done
earlier
before
the
filter
query.
G
Instead
of
here
we're
setting
the
the
body
instead
and
using
the
fluent
api,
I'm
doing
client
dot
me
dot,
send
mail
to
send
to
send
a
new
email,
dot
post
with
options
which
do
contain
my
body
and
that's
it.
Then
we
return
the
application
and
and
and
we're
done
so
if
we
go
over
the
browser
here
and
if
we
look
at
the
inbox,
you'll
see
that
I've
received
a
non-delivery
reply.
This
is
because
the
email
I'm
sending
the
email
address,
I'm
sending
the
email
to
does
not
exist,
but
this
is
fine.
G
The
api
call
worked.
I
was
able
to
send
an
email.
The
service
actually
got
the
email
sent
it
to
the
distance
server,
which
said
hey.
I
don't
have
that
email
address
and
reply
to
us,
but
basically
the
whole
loop
is
completed
here
and
with
that
I
know
we
have
a
couple
of
minutes
left
so
I'll,
go
back
to
the
slides
really
quickly
to
talk
about
a
few
things
and
give
you
a
few
useful
links.
G
So
if
you
want
to
get
started,
you
should
go
over
to
our
public
documentation,
of
course,
because
you'll
find
how
to
get
started
and
all
the
snippets,
but
you
can
also
go
to
our
github
repositories,
so
github.com,
slash
microsoft,
graph,
slash
ms
graph
dash
sdk
dash
go
or
ms
graph
beta
sdk
for
the
beta
sdk
again,
those
can
be
used
together
in
an
application.
If
you
need
to,
we
also
have
a
blog
post.
G
That
goes
through
most
of
the
demonstration
that
I've
put
together
here
and
explain
all
the
other
benefits
of
the
go
sdk
we
haven't
talked
about
today.
This
is
available
at
aka
dot.
Ms
slash
preview
dash
go
v1
and,
of
course,
if
you
have
questions
well,
you
can
always
reach
out
on
the
repositories
for
vigo
sdk,
but
you
can
also
go
to
microsoft.
Q,
a
at
aka
dot.
Ms
slash
ask
graph
sdk
all
attached
and
with
that.
G
A
Well,
we
are
almost
at
time,
wanted
to
remind
you
or
get
you
up
to
speed
with
some
of
our
developer
community
calls
that
we
have
where
we
have
tons
of
different
calls
happening
either
monthly
weekly
bi-weekly
lots
of
links,
lots
of
things.
The
one
thing
you
need
to
remember
is
the
aka.ms-m365
pmp,
where
you're
going
to
be
able
to
get
access
to
all
of
these
calls
in
a
way
better
format
here,
so
you
can
add
them
to
your
calendar
and
join
when
it
suits
you.
A
A
All
our
community
calls
are
also
available
in
the
m365
pnp
aka.mslink,
so
feel
free
to
join
in
and
feel
free
to
go
see
there
we're
at
the
end
of
our
of
our
session.
Today,
thanks
everybody
thanks
the
community
for
being
so
active,
so
inclusive,
and
also
so
great
with
us.
It's
great
to
see
people
started
to
to
bond
together
in
these
conferences
so
great
to
see
our
life
getting
a
little
bit
back
to
normal
everybody.
Thank
you
so
much
and
see
you
all
next
week,
bye-bye.