►
From YouTube: Latest on eDiscovery Premium APIs on Microsoft Graph
Description
Since July’s rollout, there are new Microsoft Graph “eDiscovery” APIs supporting automating common Security, Compliance, Identity, and Management (SCIM) workflows under the Microsoft Purview brand. In this 14-minute developer focused demo – Brian Jackett and Cameron Parker focus on eDiscovery Premium (eDP) APIs targeted for inclusion in v1 release, Look at use cases, and specifically at a demo of legal case creation in Postman. The APIs also help on integrating third party applications into eDiscovery (Premium). A review of licensing/monetization, demo environments, trials and supporting resources. This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on September 6, 2022.
Demo Presenters
• Brian Jackett (Microsoft) | @BrianTJackett
• Cameron Parker (Microsoft)
Supporting materials
• Documentation – ediscoveryCase resource type | aka.ms/ediscographapi
• Documentation – Create searches | https://docs.microsoft.com/graph/api/security-ediscoverycase-post-searches
• Documentation – Create ediscoveryCase | https://docs.microsoft.com/graph/api/security-casesroot-post-ediscoverycases
• Article – eDiscovery API for Microsoft Graph is now generally available | https://devblogs.microsoft.com/microsoft365dev/ediscovery-api-for-microsoft-graph-is-now-generally-available/
• Documentation – Effective permissions | https://docs.microsoft.com/graph/auth/auth-concepts?context=graph%2Fapi%2F1.0&view=graph-rest-1.0#effective-permissions
• Documentation – Use the Microsoft Graph eDiscovery API | aka.ms/eDiscovery/API
• Sandbox – Join the Microsoft 365 Developer Program today! | aka.ms/M365DevProgram
• Documentation – Postman Collection | aka.ms/eDiscovery/Postman
• Documentation - Assign eDiscovery permissions in the compliance portal | https://docs.microsoft.com/microsoft-365/compliance/assign-ediscovery-permissions?view=o365-worldwide
Learn more
• 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 - http://aka.ms/m365/community
A
Good
morning,
good
afternoon,
everybody,
so
today,
myself
and
cameron,
one
of
my
teammates
will
be
talking
a
little
bit
about
some
new
apis
that
released
on
microsoft
graph.
These
are
specifically
for
the
e-discovery
apis.
So
we'll
talk
a
little
bit
about
how
you
can
automate
this
for
some
use
cases,
and
then
camera
actually
walk
us
through
some
demos
to
be
able
to
see
some
stuff
actually
in
action.
A
So
we'll
give
a
quick
little
overview
again
on
the
apis
themselves,
we'll
go
into
some
use
cases.
Some
demos
talk
a
quick
little
bit
about
some
of
the
license
implications
for
this
also
how
you
can
actually
go
and
get
a
demo
or
a
trial
environment.
For
this
a
great
thing.
Oh,
these
gifts
are
awesome.
Thank
you
for
sharing
those
in
the
chat
and
then
we'll.
A
If
we
have
any
time
at
the
end,
we'll
have
a
little
bit
of
q
a
time
now,
there's
a
couple
of
new
apis
that
have
released
or
are
in
the
process
of
releasing
for
what
we
call
security,
compliance,
identity
and
management
skim.
So
for
this
the
main
ones
that
we've
been
focusing
on
today
are
right.
In
the
middle,
this
is
our
e-discovery
premium
apis.
A
If
you're
interested
in
seeing
which
all
ones
are
included.
With
this
v1
release,
you
can
go
to
aka.ms
e-disco
graph
api.
There
are
a
handful
of
these
that
were
in
beta
previously
that
did
not
make
their
way
to
v1.
This
includes
the
export
files
holds
hold
policies
and
also
the
purge
data
action
that
was
out
there.
These
are
ones
that
are
still
in
beta,
we're
working
on
getting
them
over
to
v1,
but
for
time
via
node.
A
Now,
in
terms
of
the
actual,
what
can
I
do
with
these
apis?
The
idea
here
is
that,
for
a
long
time
now,
we've
had
the
security
and
compliance
center
inside
of
m365.
This
actually
has
gone
through
a
rebranding.
You'll
now
see
it
referred
to
as
microsoft
purview.
It's
kind
of
our
combination
together
of
what
was
azure
per
view,
along
with
a
lot
of
the
security
and
appliance
pieces,
they're
now,
actually
under
one
brand
called
microsoft
purview
and
as
part
of
this,
we
still
have
the
compliance
portal.
A
How
can
I
go
and
find
all
that
content,
maybe
again
for
a
yearly
audit,
or
maybe
I'm
doing
some
kind
of
legal
case,
and
you
go
actually
go
and
find
that
content
to
date,
you've
had
to
go
through
the
ui
to
actually
go
and
find
all
that
content
be
able
to
export
it,
be
able
to
put
together
into
cases
into
review
sets
and
to
a
lot
of
other
kind
of
things
like
that?
The
idea
here,
though,
is
with
these
apis.
Now
we
can
actually
automate
a
lot
of
that
process.
A
So
if
you
are
in
the
process
of
trying
to
do
something
in
terms
of
a
repeated
process
where
hey
I'm
doing
this,
you
know
10
times
a
day
or
maybe
more.
I
want
to
kind
of
automate
that
process
or
maybe
you're
looking
for
a
way
to
integrate
with
third-party
software
a
great
way
to
be
able
to
actually
pull
that
content
in
people
to
work
with
it
and
other
solutions.
A
A
Basically,
there's
some
different
post
commands
on
here.
We
can
actually
go
and
you'll
notice
that
also
we're
also
under
the
security
root
node.
This
is
a
change
from
previous.
In
the
past,
it
was
under
slash
compliance
as
part
of
this.
You
know
rebranding
the
org
under
the
microsoft
preview
label.
We're
now
going
to
be
under
the
slash
security
for
this
so
find
all
those
under
that
slash
security.
We
can
see
things
like
doing
management
of
the
cases
so
again
slash
cases,
slash
discovery
cases
you
can
specify
the
on
different
payloads.
A
You
need
for
this
also
for
creating
custodians,
similar
kind
of
path
for
this
you'll
just
pass
in.
What's
that
discovery
case
id
and
then
also
where
the
custodians
they're
going
to
be
tied
to
this,
that's
basically
the
mailboxes
or
maybe
even
some
of
the
sites
they're
going
to
be
subject
to
that
search
that
you're
doing-
and
you
can
even
do
things
like
apply-
holds
to
those
custodians
so
once
you've
set
them
inside
of
the
case.
A
Now
you
can
actually
go
and
say:
hey
retain
this
content,
so
I
can
actually
go
and
do
my
again
due
process.
I
can
do
any
kind
of
a
review
that
I
need
with
this
if
you'd
like
finding
the
different
documentation
for
this
great
link
down
at
the
bottom
out
into
our
documentation,
for
this
we'll
make
sure
to
put
that
out
into
the
chat
as
well.
So
you
have
that
for
your
purposes.
A
Another
example
out
here
for
things
like
that:
workflow
automation,
if
you're
going
to
actually
go
and
create
the
searches
you
can
specify.
What
is
that
content
search?
What
are
the
keywords,
the
kind
of
things
you're
passing
them
for
you
can
look
at
the
statistics
for
this.
How
many
mailboxes
were
held?
What's
the
size
of
them,
number
of
sources
found
a
lot
of
other
kind
of
content
like
that,
so
great
ways
to
actually
go
and
access.
A
This
do
the
automation,
processes
and
actually
see
what's
available
to
you
now
enough
for
me
talking,
I'm
actually
going
to
turn
things
over
to
my
teammate
cameron.
It's
going
to
walk
us
through
a
little
bit
of
some
demos
showing
these
things
actually
live
so
cameron.
If
you
want
to
share
out
your
screen
and
the
floor,
will
be
yours
all
right,
thanks
brian.
B
So
I've
got
a
postman
collection
here
that
we
can
share
out,
and
so
what
we're
going
to
be
going
through
today
is
the
essentially
demo
scenario
for
case
creation,
which
is
just
one
of
the
use
cases
that
you
could
automate
with
the
ediscovery
apis
here
and
so
with
this
collection,
I've
got
my
environment
variables
already
populated
with
my
tenant,
id
client,
id
client,
secret,
etc.
So
in
this
case
we're
using
delegated
permissions.
B
So
following
that
authorization
code
off
flow
here,
to
get
our
token,
so
I'm
going
to
go
ahead
and
get
my
token
now.
You'll
notice
that
in
this
scenario
it
just
went
ahead
and
it
gave
me
my
token-
that's
because
I
had
previously
consented
to
this
permission,
which
is
this
ediscovery.readwrite.all,
so
just
something
to
be
aware
of,
if
you're
going
through
this
for
the
first
time,
so
moving
into
the
case
creation,
we
first
got
here
our
list
e
discovery
cases.
So
if
you've
got
any,
you
know
pre-existing
cases.
B
You
can
of
course
use
this
api
to
enumerate
those,
but
to
kind
of
get
into
the
actual
creation
portion.
We've
got
this
post
call
here
to
the
ediscovery
cases:
endpoint.
I've
got
a
few
of
my
variables
populated
here
with
the
display
name,
description
and
an
external
id
that
you
can
use
if
you're
trying
to
tie
that
this
e-discovery
case
to
like
some
external
ticketing
system
right
and
so
just
to
kind
of
show
you
where
that's
coming
from
right.
I've
got
my
variables
here.
B
Some
of
these
will
come
pre-populated
with
the
collection,
but
of
course
I've
got
a
few
of
my
own,
that's
specific
to
to
my
my
test
environment
here.
So
with
that
we'll
go
ahead
and
we'll
send
this
request
to
get
our
case
created.
So
if
everything
is
all
in
well
we'll
get
back
a
response,
and
you
can
see
here
that
our
case
has
now
been
created
for
us.
We
can
then
take
that
a
step
further
and
see
that
this
is
now
populated.
B
Now
you
may
be
wondering
where
this
came
from
and
so
in
this
collection
under
this
test
tab
here
what
happens?
Is
we
take
that
in
that,
essentially
that
id
that
gets
returned
from
the
case
creation
and
then
feed
that
into
that
ediscovery
case
id
variable,
and
so
that
can
then
be
used
to
feed
into
this?
B
So
we'll
rerun
this
query
and
see
that
when
we
look
at
the
external
id
we'll
see
that
it
was
now
updated
to
the
value
that
we
passed
in
this
patch
call
for
that
update.
Following
that,
we
want
to
make
sure
that
we
add
those
custodians,
so
we're
going
to
go
ahead
and
add
a
custodian
here.
That
again,
is
is
populated
from
from
one
of
my
my
variables
and
I'm
going
to
go
ahead
and
send
that
to
get
the
custodian
created,
which
is
just
essentially
adding
that
custodian
to
the
case.
B
Let
that
complete
all
right
and
so
now
one
thing
to
note
here:
you
can
see
that
the
whole
status
is
not
applied,
so
we'll
be
applying
a
hold
here
shortly.
But
before
we
do
that
right,
we
can
go
ahead
and
again
there's
a
call
to
list
the
custodians.
So
you
know
for
now.
Of
course
we
just
have
this
one.
B
A
Excellent
appreciate
you
walking
through
us
that,
with
the
different
samples
on
there
cameron
and
we'll
go
back
to
my
pleasure
now
we
did
a
couple
of
questions
pop
up
in
the
chat
window
and
we'll
address
them
actually
on
here
on
this
slide
regarding
the
licensing.
Slash
monetization
for
these
apis
do
note
that,
in
order
to
actually
use
these
apis,
this
is
again
part
of
e-discovery
premium.
It
does
require
the
applicable
license.
You
can
see
them
on
here
on
the
screen
they're
also
in
the
blog
post.
A
There's
a
link
down
at
the
bottom
on
this,
so
you'll
need
to
have
at
least
an
e5
license
or
the
similar
type
of
compliance
or
security
appliance.
There's
also
an
e-discovery
and
audit
license
that
are
out
there.
Now,
that
is
licensing
required
just
to
call
the
apis
in
general.
There's
also
one
specific
endpoint
on
here
called
add
to
review
set.
A
If
you
have
e5
licenses
again,
which
required
above
that
will
give
you
what
we
call
seated
capacity,
the
idea
being
that
hey
I'll
give
you
for
each
license
a
certain
amount
of
storage,
I
think
believe,
is
one
gigabyte
per
license
per
month,
and
that
will
be
pooled
basically
against
your
tenants
that
you
actually
call
against.
So
as
long
as
you
have
sufficient
e5
licenses,
you
may
not
actually
see
any
kind
of
costs
tied
to
this.
A
If
you're
doing
a
very
large
excuse
me
very
large
amount
of
queries
in
the
system
or
using
up
a
lot
of
that
storage,
there
may
be
some
over
charges
that
will
be
tied
to
that,
but
take
a
look
at
the
blog
posts.
We
can
see
more
on
this.
The
charges
are
not
in
effect
today,
but
they
will
come
online,
probably
in
the
calendar
23
time
frame.
A
One
quick
mesh
done
here
on
permissions:
these
are
only
supporting
delegated
permissions.
Today
we
are
working
on
application,
permissions
and
note
that,
because
it
requires
delegated,
you
will
have
to
have
the
appropriate
role
assigned
in
purview.
Usually
things
like
e-discovery
manager
use
coverage,
administrator
or
similar
for
these
things.