►
From YouTube: Introduction to Microsoft Graph with Jeremy Brown
Description
Microsoft has stated the AzureAD and MSOL modules are being deprecated! We need to move to the Microsoft.Graph module if we want our scripts to keep working. Come join us to see how to get started with the Microsoft.Graph module. We're going to look at how to explore the Graph module, use it interactively, setup an app registration for automation, create some users and groups, and pull back some information about those objects.
Join Jeremy Brown for a look at the new Microsoft.Graph module and some of the features available!
Speaker Bio:
Jeremy https://github.com/bananajama is a long-time Microsoft professional with over 20 years experience in systems administration. has spent most of his career in education working for NC state public and private schools as well as the NC Judicial Branch. He is a PowerShell evangelist in every organization he's been in; providing mentorship and experience in moving rote work to automation.
About RTPSUG:
We're a group of PowerShell pros from all walks of life who love to share ideas with fellow community members. Our meetings are open to anyone who would like to talk about and learn more about how to PowerShell!
B
Say:
hey
how's,
it
going
everybody,
so
I
am
jeremy
brown.
I've
been
nit
for
a
little
over
20
years.
I've
posted
some
of
my
contact
info
here,
so
my
github
repo,
which
has
just
public
stuff
that
I
play
around
with
with
it's,
not
the
there's,
not
a
ton
in
there
most
of
what
I
write
can't
be
published
publicly
and
then
my
twitter
handle.
B
I
just
switched
jobs
so
previously
I
was
working
with
azure
ad
and
microsoft
online
office,
365
stuff,
almost
completely.
That
was
a
big
portion
of
my
job,
so
I
had
automated
a
whole
lot
of
what
the
my
previous
organization
did
inside
that
environment,
and
I
noticed
that
I
would
speak
and
talk
to
people
about
the
fact
that
I
you
know,
I
needed
time
to
continue
to
take
all
this
code
and
start
updating
it
to
use
graph.
B
We
can
go
here
and
look
at
it,
so
this
is
from
june
of
2020
the
write-up
about
the
fact
that
they're
going
to
kill
off
the
azure
80
graph
api
and
that
affects
azure
ad
and
microsoft
online,
and
the
big
part
of
that
is
this
piece
down
here,
which
I
actually
have
an
entire
slide
for.
Just
that
paragraph
coming
up,
but
azure
ad
stops
working
in
less
than
six
months
and
people
don't
know
that.
B
What
they're
saying
is
right
now
june
30th
2022,
when
you
go
to
connect
azure,
80
you're,
going
to
get
nothing
back
and
that's
going
to
hurt
a
lot
of
people
personally.
I
think
that
no
one's
prepared
for
this,
and
as
soon
as
they
do
that
they're
going
to
end
up
pushing
that
deadline
to
a
later
date,
and
that's
when
everybody
will
start
to
learn
about
this.
B
B
B
A
B
So
the
graph
explorer
looks
like
this
by
default.
It'll
sign
you
in
with
a
sample
user
account
and
there's
not
much
that
you
can
do
against
this
account
other
than
query
against
yourself.
If
you
have
an
account
in
a
azure
id
tenant,
then
feel
free
to
sign
in
with
your
account,
and
that
will
give
you
a
greater
breadth
of
things
to
play
with.
B
B
This
is
kind
of
like
a
postman
for
graph
right.
So
up
top,
we
can
build
the
query,
run
the
query
and
then
on
the
bottom,
we'll
get
the
response
from
whatever
the
query
is
that
we
ran
and
the
and
whatever
you
know
the
data
that
would
have
come
back
from
that,
or
at
least
a
portion
of
it
if
it's
a
large
set
of
data,
so
up
at
the
top
after
you
have
your
query,
you
can
come
in
and
specify
any
sort
of
extra
data
that
might
belong
in
the
header.
B
B
B
Doesn't
really
give
you
a
lot
of
feedback
back
and
the
errors
aren't
the
best
errors
and
so
figuring
out
how
I
want
to
build
my
filters
and
whether
or
not
I'm
even
looking
at
the
correct
endpoints
those
types
of
things
I'll
usually
come
in
and
kind
of
play
in
the
graph
explorer.
First,
on
those
end
points
and
kind
of
get
idea
of
what
the
data
that
I'm
working
with
is
before
I
move
to
the
dot
graph
module
and
then
once
I'm
there,
I
I
have
a
better
idea
of
how
I'm
going
to
write
that
code.
B
So
that's
the
graph
explorer
we're
going
to
play
a
little
bit
more
with
that
in
a
minute.
So
for
what
we
want
to
talk
about
tonight,
the
question
is:
is
how
do
we
use
microsoft.graph
so
step?
One
is
install
the
module
so
install
module,
name
microsoft.graph
and
then
from
there
you're
going
to
choose
the
api
version
you
want.
If
we
take
a
look
back
at
the
graph
explorer
you'll
see
where
it
says
version,
one
there's
also
a
beta
option.
B
The
endpoints
for
these
two
are
mostly
the
same
there's
a
few
things
that
are
different
in
two
different
ways.
One.
The
beta,
of
course,
has
a
few
extra
api
endpoints
that
the
version
one
currently
does
not
have
because
they're
not
released
for
production
yet
and
then
the
other
one
is
is
sometimes
in
the
beta.
B
We
would
select
mg
profile,
specify
the
dash
name
parameter
and
then
give
it
the
name
of
whichever
endpoint,
so
by
default.
It'll
come
in
as
a
v.10,
and
if
you
want
to
switch
to
beta,
then
you
would
run
this
command
right
here
and
that
would
switch
you
to
the
beta
endpoint
and
then
once
you've
selected,
which
endpoint
you're
going
or
which
version
you're
going
to
call.
B
The
scopes
can
be
reread
on
the
fly.
So
if
you're
not
sure
what
you're
about
to
do,
I
start
small
and
then
work
your
way
out.
So
you
know,
if
all
if,
if
I'm
exploring,
I
would
only
ever
use
a
read
scope.
I
wouldn't
use
the
read,
write
scope.
Just
because
I
know
if
I
use
the
read
scope,
I
don't
ever
have
to
worry
about
changing
data
with
something
that
I'm
not
quite
sure
about
how
to
use.
Yet.
B
Whereas
if
I
choose
the
greater
set
of
permissions
from
the
read
write
scope,
then
I
run
the
risk
of
doing
something
I
didn't
intend
to
do.
While
I'm
exploring
right
so
start
small
use
the
reed
scopes
and
then,
when
you're,
ready
to
to
branch
out
and
go
bigger
than
that,
you
can
do
that
interactively
by
reissuing.
This
connectmg
graph
with
a
force
refresh,
switch
and
it'll,
give
you
those
new
permissions
on
the
fly.
B
A
B
So
this
is
the
way
it
comes
in
so
you'll
go
to
install
the
microsoft.graph
module
and
the
manifest
will
pull
in
the
rest
of
the
module
right.
So
you'll
see
it
works
like
the
az
module
does,
so
everything
will
be
broken
out
into
smaller
name
spaces
across
each
piece
of
this,
so
the
microsoft
graph
itself
doesn't
really
hold
any
commands.
B
Everything
is
held
inside
something
a
step
lower.
So
if
we
were
interested
in
interacting
with
users,
we
would
look
inside
the
microsoft.graph.users
we're
dealing
with
groups,
there's
a
microsoft.graph.groups
right
if
we're
going
to
deal
with
bookings
for
the
booking
service
or
if
we
want
to
deal
with
setting
up
like
audit
data
for
the
identities
stuff
like
that
those
were
part
of
the
identity
sign-ins.
B
B
B
And
that's
would
give
us
the
parameter
sets
and
then
the
information,
some
basic
information
about
what
each
of
the
parameters
work
off
of
right.
So
most
of
the
time,
if
I'm
doing
something
like
this,
I
pass
in
show
window
and
that
will
open
it
up
into
its
own
little
window.
We
saw
this
earlier
today,
so
I
think
phil
was
doing
this
and
if
I'm
on
a
machine
that
doesn't
have
internet
access,
I
find
this
works
pretty
well
right.
B
If
I
do
have
something
with
this
internet
access,
then
I
prefer
to
just
head
to
the
docs
themselves
and
read
it
from
here
and
the
same
content.
That's
in
show
window
will
exist
on
this
website
as
well.
Sometimes
you'll
get
a
little
a
little
bit
more
feature-rich
data,
for
example.
Some
of
these
features.
However,
I
find
that
most
of
the
commandlets
in
the
microsoft.graph
module
have
very
little
information
in
them.
It
is
exactly
what
would
be
in
show
window
right.
B
A
B
So
in
this
instance,
here
we
can
go
and
let's
go
take
a
look
at
listing
users,
for
instance,
so
get
mguser
ties
to
the
same
thing
as
the
list
users
inside
here,
and
I
can
see
that
because
they're
both
retrieving
a
list
of
users
objects,
and
this
is
where
you
would
actually
learn
the
permissions
that
you
need
so
in
my
instance.
So
I
need
to.
I
need
one
of
these
particular
permissions
in
order
to
be
able
to
list
the
users
using
gitmg
user.
B
If
I
don't
pass
in
user,
read
basic
all
user
read
all
you
know
one
of
these
as
a
scope,
then,
when
I
execute
get
mg
user,
it's
going
to
give
me
a
permissions
denied
and
we
can
watch
that
happen
right
now.
Actually,
so
let
me
close
clear
that
out
so,
like
I
said,
install
the
module.
Clearly,
I've
already
done
that.
So
if
I
do
a
get
mg
profile.
B
A
B
B
Well,
that's
fine!
I
can
make
this
error
happen
in
a
minute,
because
I'm
doing
a
get
and
I'm
already
signed
in
as
this
particular
user
who
has
permissions,
it's
actually
doing
what
I
want
it
to
do.
But
if
we
go
to
do
a
creation,
it
should
fail,
and
so
we'll
see
that
in
a
second
I
can
make
that
fail.
B
But
if
we
want
to
change
our
permissions
run,
connect
graph
again
pass
scopes
and
then
pass
the
scope
that
you
want
and
then
pass
force
refresh,
and
this
will
reconnect
you
with
those
new
permissions
against
whatever
the
new
scope
you've
connected
as
so.
At
this
point
I
would
have
expected
this
to
work
now,
but
it
worked.
B
How
do
we
set
it
up
so
that
we
can
use
automation-
and
this
is
probably
something
that's
a
little
better
and
easier
than
it
would
have
been
in
previous,
like
microsoft,
on
the
ms
online
module,
didn't
have
anything
for
this.
When
I
ran
code
against
the
microsoft
online
module,
I
would
always
still
have
to
sign
in
as
a
normal
user,
and
then
I
would
just
have
you
know
this
exception
of
a
user
in
my
environment
in
order
to
be
able
to
automate
my
code
against
it.
B
So
that's
kind
of
what
we're
looking
to
do
here,
so
we're
going
to
use
application
and
registration
in
azure
id
to
be
able
to
establish
automation.
That's
going
to
alleviate
the
need
for
passwords
or
user
accounts
in
azure
active
directory
to
connect
to
and
benefits
us
in
ways
like
not
having
a
requirement
for
mfa.
Things
like
that
in
order
to
make
the
app
registration
you
may
or
may
not
have
the
permissions
to
do
that.
B
B
That
a
good
answer
sounds
good
to
me
all
right
and
then
the
last
thing
is
is:
when
you
set
your
app
registration
up,
there's
two
ways
to
authenticate:
you
can
use
a
certificate
or
a
secret.
So
if
you're
using
a
secret,
you
can
store
that
in
azure,
key
vault
or
something
like
that
and
then
access
it.
That
way,
personally,
I
prefer
to
use
certificates
most
of
the
certificates
that
I
make
for
this
are
self-signed
certificates,
because
I
don't
really
see
the
need
of
setting
up
a
crl
for
all
of
that.
B
B
So
that's
how
I
prefer
to
do
mine,
but
you
can
do
them.
However,
you
want
either
way
they're
both
pretty
straight
forward,
and
we
can
take
a
look
at
how
each
of
those
will
look.
So
let's
go
ahead
and
build
a
application
registration,
and
so
what
I'm
going
to
do
is
I'm
going
to
go
ahead
and
log
in
here
into
azure
id
and
my
personal
tenant
and
then
over
under
app
registrations
is
where
we
can
build.
B
B
An
application
registration
is
a
a
broad
thing.
It
can
do
many
things
so
for
what
we're
using
it.
For
it's
very
simple,
however,
if
we
wanted,
if
we
were
writing
something
with
an
oauth
workflow
or
something
like
that
through
it,
there's
a
lot
more
about
how
we
would
enter
how
the
user
would
interact
with
this.
B
As
far
as
you
know,
pulling
an
access
token
and
then
getting
redirected
back
to
some
other
application
stuff
like
that,
and
so
all
of
this
that
you
see
down
in
here
is
starting
to
work
us
through
more
bigger
grander
things
than
we
really
need
to
concern
ourselves
with.
All
we
want
is
a
way
to
identify.
B
This
thing
in
azure
that
will
give
me
back
an
access
token,
so
that
I
can
interact
with
graph
on
it
right
and
then
that's
what
think
of
this,
like
a
service
account
right?
That's
really
what
it
is.
So
this
is
a
thing.
That's
going
to
give
that
you
know
this.
Is
the
service
account
user
that
you
would
have
made
in
an
on-premises
ad
where
you
would
go
in
and
say
this
user
is
a
member
of
these
groups,
so
we
can
go
and
do
these
things,
nothing
else
right.
B
So
that's
what
we're
going
to
do
here
where
the
application
registration
is
just
that
service
account,
so
I'm
going
to
name
the
service
account
and
then
hit
register.
We
don't
have
to
worry
about
anything
else
and
then,
once
it's
built,
the
things
that
I
care
about
are
the
certificates
and
secrets
and
the
api
permissions.
The
rest
of
this
really
isn't
going
to
do
much
for
me,
since
I'm
not
doing
anything
bigger
than
authenticating
the
graph
module,
so
certificates
and
secrets
is
where
we
would
add
those
like
I
said
so,
we
could
come
in.
B
B
So
that
way
we
have
a.
I
think
this
is
the
way
that
would
give
us
more
options
for
anybody.
That's
going
to
watch
later,
and
so
I
wanted
to
try
to
give
options
right.
So
the
secrets
one's
pretty
straightforward,
you
put
in
the
secret
here.
You
cap,
you,
put
carry
it
put
it
somewhere,
that
you
can
read
it
later
and
then
read
that
into
your
code.
From
that
point,
however,
you
want
so
let's
talk
about
how
we're
going
to
make
a
secret
real,
quick
or
a
certificate
real
quick.
B
So
this
is
how
I
choose
to
make
mine
there's
a
lots
of
options
for
a
new
self-signed
certificate,
and
you
can
get
really
crazy
with
the
cheese
whiz.
If
you
want
to
go
with
your
own
particular
blend
of
you
know,
encryption
standards
or
cryptography
standards
or
key
strengths
or
whatever
you
want
to
do.
B
B
B
So
there
we
go
so
here
we
can
see
that
I've
passed
in
these
parameters
into
new
self-signed
certificate,
using
a
splat
stored
that
value
in
this
cert
variable,
and
then
we
output
that
cert
variable
just
so.
We
can
take
a
look
here
at
the
certificate
that
it
created
and
so
in
memory
now
I
have
a
self-signed
private
certificate
and
then
what
I
do
is
after
I
have
that
certificate.
B
You
know
with
a
pfx,
and
so
here
we're
just
going
to
specify
the
location
we
want
to
save
that
pfx
and
then
you'll
need
to
encrypt
the
private
key
with
something
right,
and
so
here
we're
going
to
use
this
password,
which
is
a
secure
password
to
encrypt
that
private
key.
And
so,
if
we
run
that
over
here
on
the
left,
we'll
see
the
sign
pfx
certificate
now
has
been
created,
and
so
from
this
point
forward,
whenever
I
need
to
go,
do
something
I
can
just
read
this
self-signed
certificate.pfxn.
B
B
And
then
once
we
do
that
we
can
just
go
ahead
and
delete
this,
because
we
don't
care
about
it
now
and
so
now,
if
we
take
a
look
you'll
see,
we've
got
two
files
right,
so
the
self
sign
cert.sir
is
my
public
certificate,
we'll
be
able
to
open
that
one
like
we
would
anything
else
that
we're
used
to
being
able
to
open
and
see
because
it
doesn't
carry
the
private
key
with
it.
This
is
our
public
cert,
and
so
we
can
see
it's
not
trusted.
It's
issued
two
and
it's
issued
by
the
same
name.
B
Go
so
now
what
we've
done
is
we've
specified.
This
application
here
is
going
to
be
the
application
that
the
microsoft.graph
module
is
going
to
authenticate
with,
and
it's
going
to
pass
in
the
private
cert
that
goes
along
with
this
public
cert
and
so
think
of
that
as
the
application
typing
in
its
password.
B
So
since
it
has
the
private
cert
and
the
application
registration
at
the
public,
then
we
know
that
these
two
things
are
the
same
or
came
from
the
same,
and
so
that's
going
to
allow
me
to
authenticate
to
the
application
and
then
for
whatever
permissions
we
assign
this
application
is
what
any
script
will
be
able
to
do
with
it
right,
and
so
we
don't
really
need
these.
So.
B
B
B
Admin
consent
which
is
required
in
order
for
these
to
work,
because
the
application
would
only
be
able
to
interact
on
itself
unless
a
global
admin
comes
in
and
says
otherwise,
and
so,
when
we're
granting
admin
consent
for
this,
we're
saying
that
this
application
can
go
out
and
connect
to
other
users
as
well,
essentially,
is
what
we're
doing
so.
We're
going
to
go
ahead
and
grant
consent.
B
B
So,
in
order
to
do
that,
we're
going
to
come
back
over
to
connect
graph
and
we're
going
to
see
that
there's
a
couple
different
parameters-
one
of
them
is
client
id.
One
of
them
is
certificate
and
one
of
them
is
tenant
id
and
those
are
the
things
that
we
care
about
right
now
right.
So
if
we
go
and
we
take
a
look
back
at
what
we
created
under
overview,
we
can
see
that
there
is
a
client
id.
So
this
is
the
username
of
our
service
account,
and
this
is
the
domain
of
our
service.
B
B
What
we
would
have
done
in
active
directory
versus
what
we're
going
to
do
in
azure
id,
so
let
me
go
ahead
and
disconnect
graph
and
clear
the
screen,
and
then
we
need
to
reconnect
back
up
right.
So
we're
going
to
do
it
interactively
first
right
now
so
step
one
is.
I
need
to
grab
my
certificate
again.
B
We're
going
to
go
in
and
we're
going
to
grab
our
certificate
and
we're
going
to
do
that
by
specifying
the
location
that
the
certificate's
in
and
then
the
secret
password.
So
we
can
decrypt
the
private
key
and
then
store
that
value
into
our
certificate
from
there
we're
going
to
want
to
establish
a
new
splat
that
holds
the
client
id
the
tenant
id.
B
A
A
Okay,
you
really
shouldn't
be
just
two
years
anymore,
because
max
won't
support
it
yeah
three
hundred
367
days
or
something
like
that
is
recommended.
Okay,
and
is
there
a
way
to
find
out?
Is
there
something
in
azure
to
let
you
know
when
those
certificates
are
are
expiring,
but
you
have
to
keep
track
of
them
yourself.
B
A
B
B
B
B
A
B
A
A
B
A
Yeah
so
effectively
there's
a
lot
of
ways
to
accomplish
it.
There's
two
examples
of
using
power.
Automate
then
there's
you
know
azure
monitor,
but
it's
going
to
have
to
roll
your
own
in
to
the
only
variables
that
you
want
to
go.
So
how
far
do
you
want
to
go
out?
Who
do
you
want
to
automate?
You
know
who
do
you
want
to
alert
that
kind
of
stuff,
yeah,
okay,
good?
And
lastly,
I
noticed
that
you
gave
the
when
you
do
the
app
registration
you're,
giving
it
access
to
the
entire
tenant.
B
A
B
A
B
Yeah,
because
when
you're
syncing
it
into
azure
id
you're,
still
syncing
everything
into
the
same
user's
bucket.
Yes,
there
may
be
a
way.
I
I
just
don't
know
it
okay,
but
I'm
not
aware
of
a
way
to
limit
by,
like
you
know,
upn
or
something
like
that,
so
that
every
it
only
has
write
access
on
a
subset
of
the
users
that
are
synced
to
badger
id.
A
B
B
B
Boom
and
so
now
I'm
not
connected
I'm
actually
connected
as
this
posh
rtp
sub
automation,
application,
and
so,
if
my
azure
id
requires
things
like
mfa
or
if
my
user
account
isn't
an
account
that
needs
elevated
permissions
and
I
want
work
to
happen
or
if
I'm
trying
to
you
know
separate
the
work
that
I'm
doing
off
of
my
cron
server
away
from
an
actual
user
account.
You
know
we've
achieved
that
goal
right.
B
So
let's
go
and
do
something
with
that.
So
I've
got
this
code
here
that
I
made
up
and
it's
just
playing
around
with
identities
a
little
bit.
So
I'm
going
to
build
a
upn,
I'm
going
to
take
the
name
clean
it
up.
If
it's
hyphenated
do
some
stuff
like
that,
and
then
down
here
is
where
the
the
real
code
is.
So
I'm
going
to
go,
grab
20
random
users
and
then
for
those
20
random
users.
B
B
B
I
captured
the
state
that
flory
lives
in
the
city
that
flory
lives
in
so
the
department
that
flory
works
in
the
company
and
then
I'm
giving
everybody
a
job
title
of
temp.
So
we
can
filter
on
that
and
delete
them
later
and
so
now
I
I
want
to
be
able
to
put
all
of
these
users
and
groups
that
go
along
with
their
departments
right.
B
A
B
I
often
make
one
expensive
call
at
the
very
beginning
versus
repeated
small
calls
and
I
think
in
the
grand
scheme
of
things
it's
cheaper
right,
so
I
could
either
connect
to
azure
id
every
time.
I
need
to
loop
through
the
next
user
to
pull
information
about
that
user
and
then,
after
that,
go
and
do
the
next
step.
B
B
So,
most
of
the
time,
what
I'll
do
is
I'll
just
go
grab
the
complete
user
data
set
well
the
complete
users
set,
but
I
will
only
pull
the
subset
of
the
data
that
I
need.
So
this
will
give
me
not
a
whole
lot
of
storage,
but
everything
that
I
need
in
memory
right
from
the
start.
So
in
this
instance
for
all
of
my
users.
If
we
go
ahead
and
just
run
like
this
command,
for
instance,.
B
B
B
Members
inside
this
one,
the
one
user,
and
so
we've
worked
our
way
through
now,
creating
users,
creating
groups,
adding
users
to
groups
and
then
all
that's
left
is
to
go
clean
up
and
do
some
removal
stuff,
and
so
this
is
kind
of
my
like.
I
said
my
goal,
for
this
was
to
kind
of
give
some
some
starting
points
for
how
do
you
make
users
with
graph?
So
that
would
be
this
area
here.
B
How
do
we
add
users
to
groups
that
would
be
this
command
here
and
then
removing
is
going
to
be
really
simple
right,
just
go,
find
stuff
and
remove
them
so
and
then
some
of
the
other
things
that
are
worth
looking
at
is
when
you're
looking
in
the
graph
module
for
something
so
get
mg
user.
Actually
it's
right
here,
I'm
just
going
to
use
this
one.
So
there
is
a
filter
option
that
support
that
is
supported
for
most
of
your
get
endpoints
in
the
microsoft.graph
module.
B
So
that's
just
filtering:
I
have
to
go
look
for
there's
a
more
general
odata
usage
set.
That
would
be
worthwhile,
so
this
is
just
for
filter,
but
everything
inside
of
here
this
is
what
we
can
use
against
the
filter.
So
when
you're
passing
in
a
filter,
all
of
this
is
available
to
you,
and
you
know
things
like
starts
with
and
ends
with
weren't
things
that
you
could
have
ever
used.
You
know
in
the
active
directory
module,
but
they
are
available
to
you
here.
B
So
if
you
wanted
to
only
pull
users
to
do
work
against
of
a
certain
kind
of
upn,
you
know
if
you
had
multiple
names,
and
you
know
I
have
telespin
toys.
I
have
you,
know
primary
toys.
I
have
everything
for
coffee
at
all
right
of
the
at
sign,
and
I
only
wanted
those
things
that
were
telespin
toys.
You
could
use
the
ends
with
in
order
to
pull
back
just
those
users
right-
and
these
are
the
things
too,
where
coming
over
and
playing
in
the
graph
explorer
for
them
is
helpful.
A
A
B
B
So
here
we
see
fedora,
graber
and
florie.
Ellicott
are
returned
back,
and
so
I
find
it
easier
for
me
personally
to
work
inside
graph
explorer
when
I
need
to
come
up
with
this
kind
of
work
and
then
once
I
have
what
I
want
working
correctly,
then
I'll
come
over
and
add
that
in
to
my
filter
appropriately
under
here
right,
so
that's
kind
of
how
I
I
personally
work
between
the
graph
module
and
graph
explorer.
A
B
A
B
B
Right
so
we
just
ran
this
command.
This
is
how
you
add
a
user
to
a
group.
So
but
there's
nothing
in
here.
That
tells
me
anything
about
what
what
permissions.
I
need
to
add
that
user
to
a
group
or
anything
like
that
right,
but
it
will
tell
me
what
I
can
pass
in
what
can
be
passed
in
the
body
right
and
then,
if
there's
anything
for
what
I
can
and
can't
do
across
the
graph
data.
It
won't
tell
me
any
of
that
here,
but
if
I
come
over
into
here
and
we
go
to
groups.
A
B
A
A
A
A
B
Yeah
so
then
the
last
thing,
then,
would
be:
let's
go
ahead
and
purge
the
users
back
or
the
groups
out
and
again
here,
I'm
just
getting
all
of
the
groups
and
then
looping
through
them
and
deleting
them
all
and
then
the
same
for
the
users
except
I
don't
want
to
delete
all
the
users.
I
just
want
to
all
delete
all
the
ones.