►
From YouTube: Managing permissions in modern SharePoint
Description
A summary has been posted to our Ask Sympraxis blog that details all the links and resources from this episode. https://symp.info/AS_20230906
Timeline
0:00 Introduction
1:20 Introduction to Microsoft 365 Groups
8:40 Work Process/Content Management
11:05 Communication Sites
15:06 Team Sites
19:19 Team Site: Site Permissions vs Group Membership
22:47 Permissions Better Practices
26:13 Microsoft 365 Group Bugaboos
29:43 Dynamic Groups
31:02 Resources
If you would like to get involved check out our Ask Sympraxis page (https://symp.info/AskSympraxis) where you can get the iCal invitation to our recurring meeting, links to the resources from the video, and a link to the form to submit a question that might be the focus of one of our future episodes! Also, follow us on social media to get updates about the upcoming topics. Twitter: @SympraxisC
If you have any questions or comments about this episode, please feel free to post them below.
~ Music Credit: Ken Bagley
D
Let
us
get
started,
it
is
September
6th
asked
some
Praxis
and
we
have
a
full
contingent
of
the
Sim
practice
team
here
today.
Today's
topic
is
managing
Provisions
in
modern
SharePoint,
and
this
is
a
pretty
good
topic
because
things
have
changed
with
SharePoint.
So
we're
going
to
talk
about
the
introduction
of
Microsoft
365
groups,
which
happened
a
very
long
time
ago,
but
I
think
there's
still
a
lot
of
confusion
about
that.
D
So
that
makes
this
a
fairly
good
topic:
we're
going
to
talk
about
content
Management
in
the
in
the
construct
of
permissions,
permissions
overview
between
communication
sites
and
team
sites
and
there's
that's
where
the
the
goodness
really
happens.
I
think
permission
better
practices
and
then
some
things
that
we
consider
bugs
that
others
that
others
in
the
Microsoft
Homeworld
might
think
are
actually
features
and
then
a
little
talk,
Of
Dynamic
groups,
so
that'll
so
that'll
be
good,
all
right
Todd.
A
So
when
we
were
talking
about
this
slide
yesterday
in
our
prep
session
I
I
mentioned
several
years
ago,
I
was
talking
to
the
product
manager,
for
this
and
I
was
like
you
know
what
are
these
at
that
time
they
were
oenko
365
groups
I'm
like
what
are
these.
What
these
groups
thing
and
he's
like
come
on,
this
stuff
is
easy
and
I'm
like,
and
we
were
at
an
event
we
were
at.
You
know,
igniter
ticket
or
something
he's
like
I've
got
the
75-minute
session
later
today.
A
A
You
know
you
when
you,
you
get
your
your
SharePoint
site
and
it
creates
this
group
and
you
get
SharePoint
like
you're
expecting,
but
then
off.
In
the
background,
these
little
robots
run
off
into
Microsoft
365
and
they
create
you
a
distribution
list,
an
exchange.
They
might
creature
a
team
in
teams,
they
create
you
a
plan
and
planner.
But
that's
that's
what
this
group
is?
A
It's
just
like
your
your
group
in
ad,
except
you
get
all
these
things
with
it
or
if
I'm,
if
I'm
talking
to
end
users,
I,
say
Microsoft,
365
groups
are
just
like
a
distribution
listed
exchange.
You
create
the
distribution
list,
you
add
some
people
to
it
that
gets
created
in
the
cloud
and
then,
when
that
happens,
a
bunch
of
little
robots
run
off
into
Microsoft
365
and
they
create
a
SharePoint
site
and
a
teams
team
and
a
planner
plan
and
that's
kind
of
the
way
to
look
at
it.
A
A
The
idea,
the
reason
that
Microsoft
foisted
this
upon
us
was
because,
as
things
were
in
the
cloud
services
started
to
overlap
a
little
bit
and
it
didn't
make
sense,
for
instance,
for
teams
to
find
a
way
to
store
files
when
right
down
the
hall.
There's
the
SharePoint
team
who's
got
this
great
product
that
stores
files.
So
you
know
they
take
the
chocolate
and
the
peanut
butter.
You
mix
your
teams
with
your
SharePoint,
so
you
can
be
in
teams
and
share
files.
A
But
then
you
got
to
make
sure
the
permissions
are
the
same
and
that's
kind
of
the
problem
that
groups
is
trying
to
solve,
so
SharePoint
doesn't
have
to
have
mail
because
exchange
has
it.
It
doesn't
have
to
have
a
real-time
chat
because
teams
has
it
so
on
so
forth,
so
groups
that
gives
us
this
one
pane
sort
of
to
manage
the
group
for
all
this
One-Stop
management.
A
For
all
these
things,
and
if
you
make
the
permission
change
at
the
group
level
or
at
the
app
level,
it
goes
to
all
the
other
ones
and
another
great
advantage
of
it
is
compliance
and
governance.
So
now
you
know
that
if
you
set
some
sort
of
permission
or
something
in
exchange
for
the
distribution
list,
that
permission
is
also
in
teams
that
permission
is
also
in
SharePoint.
All
of
that
kind
of
stuff
Greg
is
trying
to
steal
some
Thunder
I'm
going
to
talk
about
that
in
a
minute.
A
Greg
don't
be
looking
ahead,
follow
along
so
what's
in
it
for
us,
as
practitioners
in
M365,
well,
I'll
begrudgingly
admit
that
it's
a
little
easier
to
manage
those
permissions.
Because,
again
you
can't
just
change
the
permission
at
the
group
level
and
then
that
person
has
access
to
the
SharePoint
site,
the
teams
team,
all
that
kind
of
stuff.
It
also
makes
it
easier
for
your
users
to
move
into
using
other
services,
because
you
don't
have
to
worry
about
making
sure
they
have
the
right
permissions
and
everything's
kind
of
bolted
together.
A
When
somebody
uploads
a
file
in
teams,
they
don't
realize
that
it's
in
SharePoint
and
then
they
show
into
SharePoint
like
hey
I,
recognize
all
this
stuff,
so
it
does.
It
does
help
with
that
they
are
created
automatically.
You
don't
have
to
think
about
it.
As
a
matter
of
fact,
you
have
to
go
out
of
your
way
to
not
get
a
group
when
you
create
a
team.
C
A
Got
it
right
so
so
you
have
to
sometimes
teamify
a
group
depending
on
how
you
create,
if
you
create
it
in
teams.
Obviously
you
get
the
group
of
teams
if
you
create
it
in
SharePoint
or
somewhere
else,
you
have
to
teamify
it
later.
If
you've
ever
created
a
SharePoint
site,
that's
group
connected
and
you
get
that
little
thing
in
the
corner
that
says:
hey
have
you
heard
about
real-time
collaboration?
That's
what
you're
doing
if
you
click
that
you're
teamifying
your
group
and
to
answer
Greg's
question
earlier.
A
If
you
delete
any
part
of
the
group,
you
delete
everything
in
the
group.
So
if
you
create
the
team
that
was
created
when
the
group
was
created,
it
deletes
the
team
just
like
gask,
but
it
also
deletes
the
group
which
deletes
the
SharePoint
site,
which
deletes
the
distribution
list
and
all
that
kind
of
stuff.
Now
there
are
warnings
everywhere
about
that,
but
when
groups
first
came
out,
that
was
not
the
case
and
so
I
learned
the
very
hard
way.
A
Two
things
one
day,
I
learned
that
when
you
delete
one
part
of
a
group,
in
this
case
the
planner
plan,
it
deletes
the
whole
group,
the
SharePoint
site
and
all
that
and
I
also
learned
that
it
pulls
out
of
the
recycle
bin
in
like
30
some
days,
and
if
your
users
don't
notice
until
like
40
days,
then
it's
just
all
gone.
So
that
was
hard.
Lessons
learned
all
the
way
around.
D
That
day,
but
you
absolutely
know
that
to
be
true,
but
it
is
weird
that
now
and
I
know
this
from
doing
some
testing
for
some
deployment
stuff
recently
that
if
you
delete
a
team
site,
SharePoint
team
site
that
has
a
Microsoft
360
group,
private
group,
it
does
have
a
checkbox,
it
says:
do
you
want
to
delete
the
group
too
and
I'm
like?
Why
are
you
giving
me
that
checkbox
you're
just
gonna
delete
it
anyway?
So
I,
don't
know
what
that
checkbox
does,
but
just
FYI.
D
A
Yeah
and
I
think
I,
don't
have
it
on
this
site,
but
but
one
of
the
limitations
for
a
SharePoint
folks
is
groups
have
two
levels
of
permissions,
mostly
owner,
which
means
you
can
do
anything
at
the
management
level.
Add
people
all
that
kind
of
stuff
and
then
a
member
which
means
you
have
all
full
control
of
the
content.
You
can
add,
delete,
create
and
all
that
kind
of
stuff.
For.
A
D
C
Right
so
so,
Todd
talked
about
groups,
we're
going
to
talk
about
permissions
on
different
type
types,
but
I
wanted
to
sort
of
frame
it
a
little
bit
here
so
like.
Why
do
we
care
one
of
the
things
that
we
believe
pretty
strongly
at
some
Praxis
I
believe
I,
know,
Emily
and
I
see
totally
eye
to
eye
on
this.
Is
that
you?
You
do
your
work
in
in
one
place
and
you
and
you
provide
your
work
to
be
public
to
be
consumed
in
another
many
many
times.
C
So
this
is
a
slide
that
actually
comes
from
the
micro
maturity
model
from
Microsoft
365
in
the
management
of
content
competency,
where
we
talk
about
how
these
different
apps
and
services
sort
of
work
together
to
support
the
kinds
of
work
it
takes
to
build
content
productively.
So,
typically
you
build
your
content
in
either
in
in
teams
or
in
the
in
your
SharePoint
or
OneDrive
sites.
It's
all
sort
of
the
same
place.
You
know
the
content
ends
up
in
the
same
place
you
iterate
on
that
content
in
your
sort
of
Team
environment.
C
You
know
SharePoint
team
site
or
or
a
team,
and
you
make
sure
that
you've
got
something
that
you
believe
should
see
the
light
of
day,
and
then
you
share
that
with
people
in
your
organizations
through
an
internet,
typically
in
a
communication
site,
that's
where
people
consume
it,
they
give
you
feedback.
You
go
back
to
the
drawing
board.
C
You
do
come
up
with
version
two,
so
that's
sort
of
the
model
of
content
management
and
create
creation
and
management
that
that
we
think
about,
and
so
when
we
talk
about
the
different
ways
to
set
up
permissions,
it's
to
serve
that
process,
because
really
you
know
SharePoint
and
teams,
and
all
of
the
all
of
the
places
where
we
tend
to
implement
these.
These
permissions
are
about
creating
and
managing
content
and
collaborating
around
it.
D
C
D
D
C
Aren't
any
yeah
there
isn't
a
Microsoft
365
group
behind
a
communication
site,
because
the
idea
is
that
you
manage
the
permissions
very
very
tightly
for
communication
sites.
You
tend
to
only
have
a
couple
of
owners.
You
may
have
site
members,
but
it's
not
a
place
where
people
collaborate,
it's
not
a
place
where
we're
like
working
on
multiple
versions
of
of
a
document
and
sort
of
kicking
around
ideas
and
iterating
and
collaborating
and
chatting
and
all
that
sort
of
stuff.
It's
a
place
where
we
sort
of
I
I.
C
C
Cream
tofu
part
the
the
ice
cream
shop.
Nobody
needs
to
know
what
happens
in
the
back
room.
You
you
get
to
see
the
the
front
room
and
see
you
know
the
the
end
product
and
that's
really
what
communication
sites
are
intended
for.
So
that's
that's,
probably
the
the
primary
reason
why
there
isn't
a
Microsoft
365
group.
It's
not
a
place
where
we
do
that
stuff.
So
well
so
I'll.
A
A
Just
it
doesn't
make
any
sense,
and
so
because
of
that
you
got
the
least
common
denominator
of
permissions,
which
removes
read
only
but
like
Mark
was
saying
when
you
have
a
com
site,
it's
supposed
to
be
read
only
for
most
people
and
so
I
think
that's
the
real
limitation.
They
couldn't
put
a
group
behind
it
because
there's
no
way
to
do
that
and
have
it
be
read
only.
C
Multiple
reasons
I
think
so
when,
when
you're,
when
you're
working
with
the
communication
site,
you
typically
have
it.
You
know
two
to
three
site
owners:
I,
wouldn't
recommend
that
you
have
more
than
that
because
it
just
becomes
messy.
I
was
working
with
a
communication
site
earlier
today
where
they
had
15
owners.
That's
that's
dangerous,
because
then
you
don't
know
who's
doing
what
and
you
know
how
do
you
make
decisions
without
having
some
sort
of
gating
Factor?
C
It's
not
a
place
where
you
put
your
whole
team
because,
depending
on
your
culture,
you
do
want
to
have
some
sort
of
gating
gating
idea
about
what
goes
on
to
those
communication
sites
and
then
and
then
site
visitors.
As
Todd
said,
you
know,
Microsoft
365
groups
don't
have
a
visitor
bucket,
they
don't
have
a
read-only
bucket,
but
with
communication
sites,
once
we've
launched
them
once
they're
available
to
the
organization,
and
we
usually
use
them
in
the
context
of
of
an
intranet,
then
we
give
everyone
except
external
users.
Read
permission.
C
That's
a
great
pseudo
group,
it's
just
free,
you
don't
don't
have
to
manage
it.
It's
always
everybody
who's
licensed
in
the
tenant.
There
are
exceptions
to
everything
it
depends.
There
are
organizations
we've
worked
with
where
they
might
have
a
you
know
all
ex-employees
instead
of
everyone
except
external
users,
because
they
actually
want
to
manage
that
and
they've
got
other
people
that
they
give
accounts
to
who
are
Outsiders
and
things
like
that,
but,
generally
speaking
on
average,
this
is
a
good
way
to
set
up
your
permissions
for
a
communication
site
and.
D
B
C
A
B
C
All
right
so
team
sites,
when
I,
say
team
sites
I'm
also
including
teams
sort
of
because
they're
they
can
be
bolted
together.
They
they
can
be
symbiotic.
They
tend
to
work
together.
Not
every
team
site
has
a
Microsoft
team
attached
to
it,
but
usually
you
tend
to
attach
it
because
that's
where
you
have
those
conversations
so
team
sites
or
Microsoft
teams
or
Microsoft
365
group
backed
so
that's,
that's
the
big
difference
between
team
sites
and
communication
sites.
You
can
see
in
that
image
on
the
right
we've
got.
C
C
That's
that
in
this
case,
with
a
team
site,
you
have
that
group
you're
managing
the
membership
of
that
group.
The
site
visitors
role
here
in
SharePoint
is
actually
just
a
SharePoint
permission
Todd.
So
in
this
case
we've
actually
given
everybody
except
external
users,
read
on
this
team
site,
which
is
a
very
unusual
thing
to
do.
I,
probably
shouldn't
have
left
that
on
that
permission,
but
we
have
a
very
small
tenant
and
there
we
know
we
know
everybody
in
there.
C
So
as
with
communication
sites,
you
want
to
have
two
to
three
site
owners,
so
people
who
have
that
role,
because
that
that
is
a
role
that
manages
site,
structure
and
permissions.
So
you
don't
want
just
everybody
managing
permissions
for
your
team
site
again,
depending
on
your
culture.
Everything
depends
site.
Members
typically
are
the
rest
of
your
work
group,
so
that
can
be
a
much
larger
group.
You
know
it
depends
on
how
large
the
team
is
working
on
a
common
goal,
but
really
that's
what
team
sites
are
about?
C
It's
about
bringing
people
together
to
collaborate
to
reach
some
sort
of
finished
product,
some
sort
of
process,
and
it's
either
a
a
limited
time
thing
like
we're
going
to
have
a
team
site
where
we're
going
to
plan
our
summer
party
or
it's
a
long-term
thing.
We're
gonna
have
a
team
site
where
HR
does
their
work
site.
Visitors
are
rarely
used,
they're,
not
part
of
that
Microsoft
365
group.
C
You
know
they
may
ask
for
full
permissions,
but
if
you
give
them
read
permissions,
then
you
know
that
they're
able
to
see
everything
that
they
need
to
see,
but
they
don't
necessarily
make
any
changes.
So
again,
these
are
sort
of
average
typical
ways
to
think
about.
These
two
permission
sets
for
the
two
different
kinds
of
sites.
D
So
there's
a
chat
around
are
the
perms
shown
in
this.
It's
like
screenshot
the
default
when
you
create
a
team's
connected
site
when
they're,
provisioned
and
I'm
gonna
move
to
the
next
slide,
because
it's
from
you
know
cyber
missions
versus
group
permissions,
which
I
think
is
the
most
confusing
part
of
all
this.
But
I
believe
it
is.
Isn't
that
correct
that
when
you
provision
a
team
site,
a
team
connected
team
site,
you
get
the
group
names
owners
in
full
control
and
you
get
the
group
name
members
in
limited
control
by
default.
C
Yeah,
private
and
private
and
public
teams
or
team
sites
have
different
Behavior.
So
if
you
create
a
public
team
site,
it
will
actually
add
everyone
except
external
users,
to
the
edit
or
to
the
site.
Members.
If
you
do
a
private
team
site,
then
it
will
not
so
I
mean
if
you
think
about
it.
Public
and
private
makes
sense.
There
are
some
teams,
you
just
want
to
let
every
you
know
the
summer
party
one.
Let's
say:
let's
let
anyone
who
wants
to
come
in
and
work
with
us
on
this.
Do
it.
C
So
when
in
in
a
team
site,
you
have
two
options
when
you
go
to
when
you
click
that
add
members
drop
down,
which
is
a
pretty
bad
piece
of
UI,
because
when
you
click
add
members,
you
have
two
options,
one
of
which
is
not
to
add
members.
So
you
can
add
members
to
the
to
the
group
and
they
can
have
a
role
of
either
owner
or
member,
so
they're.
Also
using
the
word
member
in
a
strange
way
or
you
can
just
share
the
site,
so
what's
the
difference?
C
Well,
when
you
add
add
the
add
somebody
to
as
a
member
to
the
group,
they
may
get
permissions
on
a
whole
bunch
of
other
stuff,
because
that
Microsoft
365
group,
as
Todd
said,
is
like
a
permission.
It's
like
a
security
group,
so
we
may
give
the
IT
team
access
to
the
badging
application
and
all
kinds
of
other
things.
If
we
add
somebody
to
that
group,
then
all
of
a
sudden
they
have
the
permissions
that
that
being
a
member
of
that
group
inherits.
C
If
you
share
the
site
only
it
basically
gives
them
a
key
to
the
to
the
door,
that's
at
the
front
of
the
site
and
they
can
come
in
and
and
do
stuff
in
the
site,
but
that
doesn't
make
them
a
member
of
the
group.
It's
a
it's
a
lesser
permission
level.
If
you
think
about
the
context
of
what
a
Microsoft
365
group
can
do
across
the
apps
and
services
in
Microsoft,
365.
D
If
you
can
stick
to
that
you're
going
to
reduce
confusion
about
what
is
going
on
in
something
and
only
break
these
sort
of
that
sort
of
implied
governance
rule
when
there's
a
really
good
reason
to
do
it,
because
it
is
so
much
more
confusing
right
like
if
you
have
something
that
is
to
be
create
content.
That
is
to
be
created
by
a
few
and
consumed
by
many
stick
to
a
communication
site.
D
C
I,
don't
think
I,
don't
think
I
made
the
point
and
I
want
to
make
sure
I
make
the
point
that
if
you
keep
your
permissions
at
the
site
level,
your
life
will
be
the
easiest
right.
If
you
start
to
poke
a
lot
of
holes
in
the
permissions-
and
you
start
to
say
well,
let's
create
a
library
for
this
and
a
folder
that
other
people
have
access
to,
and
let
me
give
special
permissions
to
these
three
documents
that
are
spread
across
a
bunch
of
folders.
C
It
becomes
a
nightmare,
there's
a
reason
that
you
have
to
use
third-party
tools
to
understand
permissions,
they're,
complicated
and
as
soon
as
you,
you
sort
of
stray
from
using
the
per
the
site
permissions
into
more
more
specific
permissions.
You
have
an
administrative
headache
and
therefore
we
have
this
slide.
C
C
It
can
be.
You
know
a
few
more.
It
shouldn't
be
less
because
there
are
always
times
when
somebody's,
not
around.
I
also
mentioned
the
difference
between
public
and
private
team
sites
and
I.
Think
that's
a
very
important
distinction
to
know
when
you,
when
you
create
a
team
site,
and
you
have
to
understand
its
use
case
before
you
make
that
decision.
D
Marcel
made
a
comment
in
the
in
the
in
the
chat
about
that.
Some
people
really
dislike
feeling
interacting
with
SharePoint
in
a
browser,
and
so
they
want
to
stay
in
teams
and
that's
why
they're?
Looking
for
that
read-only
permission
in
teams,
groups
I
would
argue.
That's
the
entire
point
of
Viva
connections
and
based
on
like
Viva
connections
sessions
that
we've
done
previously.
There's
lots
of
ways
to
add
more
sites
at
that.
You
know,
pinned
left
rail,
so
I,
wouldn't
I
would
argue
that.
That's
maybe
your!
D
You
should
go
down
the
Viva
connections,
route
and
surface
your
communication
sites
to
give
people
a
way
into
the
intranet
in
teams
keeping
them
in
context,
because
I
totally
understand
why
they'd
want
to
stay
in
context.
Emily
to
quote
slash.
You
know
nielsenorman
here,
whatever
that
role
thingy
is,
but
I
would
want
to
keep
them
in
teams
I
totally
get
that,
but
then
use
the
Viva
connections
tool
and
that's
why
we
have
that
and
that's
why
it's
so
powerful.
C
If
they're
interacting
with
a
SharePoint,
if,
if
they're
interacting
with
SharePoint
document
libraries,
the
interface
that
teams
has
is,
is
actually
pretty
much,
the
same,
I
mean
it's,
it's
not
that
different,
so
it
sort
of
becomes
a
little
bit
of
a
religious
War,
I
think.
But
you
know,
if
you're
consuming
content.
Viva
connections
is
more
about
consumption.
Right.
B
C
D
So
we've
got
some
group
Bugaboo,
so
this
is
something
that
we've
all
experienced
at
different
ways.
All
our
roles
have
experienced
this
in
different
ways,
so
the
owners
of
the
group
are
often
not
treated
as
part
of
the
group,
and
that
is
something
that
I
run
into
I
forget
and
run
into
quite
often
so
like
audience,
targeting
can't
be
used
for
owners.
D
So
if
you
are
an
owner-
and
you
have
audience
targeting
that
you're-
not
part
of
the
group
limit
to
10
groups
in
navigation,
so
that's
an
for
that
audience.
Targeting
piece
navigation,
keep
in
mind
that
navigation
is
limited
to
just
10
groups.
So
if
you
have
an
incredibly
complicated
grouping
structure
or
whatever
and
you're
thinking
that
you're
going
to
use
that
to
audience
Target
navigation-
that's
going
to
be
that's,
maybe
not
going
to
work
for
you
and
then
the
sites
web
part.
So
Mark
found
this
the
other
day.
D
Apparently
the
site's
web
part
will
not
show
you
sites
where
you
are
an
owner
which
is
just
like.
So
that's
when
you
come
to
us
and
we'll
build
you
a
different
sites.
Web
part
that
actually
works
and
then
managing
external
users
in
Microsoft
365
groups.
So
this
was
definitely
one
that
confused
me
for
sure
is
that
you
have
to
go
to
the
Outlook
web
app
to
when
entering
through
SharePoint,
and
it's
just
so
weird
I.
Don't
understand
why
we
have
to
do
that.
A
Yeah
and
a
note
on
that
is
that's
that
whole
idea
that
you've
got
multiple
panes,
so
you
don't
have
to
do
it
in
Outlook.
You
can
do
it
in
other
places,
but
that's
just
where
SharePoint
takes
you,
because,
whichever
app
gives
you
access
to
the
group
has
different
settings
of
group
settings,
it's
it's.
D
D
So
Microsoft
365
groups,
you
have
a
500
000
group
limit
in
the
number
of
groups
for
per
tenant,
and
so
an
admin
can
be
the
owner
of
every
single
one
of
those
groups.
So
that's
that
essentially
then
saying
admins
have
no
limit,
but
the
limit
is
the
tenant
limit.
Each
user
can
create
up
to
250
groups.
So
if
you
as
a
user,
do
not
have
the
admin
role,
you
can
create
up
to
250
groups,
so
I.E
be
the
owner
of
250
groups.
D
Each
user
can
be
a
member
or
owner
of
up
to
7
000
groups.
So
that's
like
a
end
game
like
so.
Maybe
you've
hit
your
250
owner
membership,
but
if
you're,
a
member
of
more
than
600
and
109
I
can't
do
that
math.
Why
did
I
start
down
that
road?
That's
horrible,
whatever
the
math?
Is
you
can't
do
that?
Seven
thousand
minus
250.
I.
D
A
Groups
are
normally
static,
Todd
gets
in
Derek
gets
in,
Mark
gets
in,
Julie
doesn't
get
in
that
kind
of
stuff,
but
you
also
have
the
option
of
creating
a
dynamic
group
so
that
you
can
base
group
membership
on
something
like
location
and
then
as
people
move
offices
Azure
handles
all
that
in
the
background
I
got
a
blog
post
at
the
bottom.
We
talked
earlier
about
the
everyone
except
external
I've,
created
a
dynamic
group
for
customers.
Before
that
says
everybody
except
people
whose
user
ID
is
null
because
that
means
they're,
not
a
user.
A
E
I
did
so
I
will
say
that
a
common
one
we
see
is
managers,
so
there's
the
need
for
manager,
resources,
for
example,
and
then,
of
course,
whenever
we
have
region,
you
don't
want
to
be
spamming.
Everyone
about
cookies
in
Cincinnati,
when
there's
no
cookies
in
Boston,
so
making
sure
that
we
just
tell
people
highlights
that
are
relevant
to
them
is
very
helpful
too.
D
Yep
yep
absolutely
good
use
case,
so
here's
some
resources
for
you.
Maybe
you
skipped
ahead,
maybe
you
clicked
on
them
already.
If
you
go
to
our
website
later
and
or
the
YouTube
recording
later,
all
the
links
are
going
to
be
there
for
you,
so
that
will
be
helpful
and
then,
last
but
not
least,
September
20th
is
our
next
episode
and
we're
gonna
dive
into
Community
Resources.
D
So
things
like
the
PMP
and
other
community
resources
that
we
have,
but
we're
going
to
take
the
lens
of
being
an
intranet
owner
and
how
you
might
think
about
those
Community
Resources
from
that
perspective,
Mark
and
Todd
are
going
to
be
at
Seth
in
Stockholm
Sweden
coming
right
up
in
the
next
week.
Collab
days,
New
England
is
the
a
big
some
Praxis
collaborate
collaboration
event.
Whatever,
however,
I
mean
to
say
that
and
I
don't
know,
registration
is
open.
D
October,
21st,
Burlington
Mass,
please
come
in
person.
It
is
an
in-person
only
event.
It
is
going
to
be
awesome.
This
year
we
have
a
ton
of
sponsors.
We
have
all
sorts
of
great
speakers
we're
going
to
do
it
up
right
this
year,
so
definitely
come
and
join
us
for
that
live
also
see
Derek
and
I
in
Chicago,
at
365
educon
at
the
end
of,
and
so
we'll
see
you
all
next
time,
September
20th
for
Aspen
Praxis,
thanks
for
joining
us
today,.