►
From YouTube: Dataverse Environment Permissions for Power Platform
Description
📺 In this 15 minute maker-focused video, Michael shares how to leverage Dataverse environment permissions (aka Dataverse Teams) in order to bulk manage user permissions in Power Platform environments. Dataverse group teams are a way to add security roles to a group, in order to customise permission level. Comprehensive walkthrough to concept and Power Platform Admin Center.
This demo is taken from the Power Platform Monthly Community call 20th of July 2023. Join the next call! Download recurrent invite from https://aka.ms/community/calls
✨ Presenter
Michael Roth (Avanade) | @michaelroth42
📖 Supporting materials
• Documentation - Microsoft Power Platform security and governance documentation | https://learn.microsoft.com/power-platform/admin/security
• Documentation - Configure user security in an environment | https://learn.microsoft.com/power-platform/admin/database-security
• Documentation - Associate a business unit with an Azure AD security group | https://learn.microsoft.com/power-platform/admin/wp-security-cds#associate-a-business-unit-with-an-azure-ad-security-group
• Documentation - Security in Microsoft Dataverse | https://learn.microsoft.com/power-platform/admin/wp-security
• Documentation - Security concepts in Microsoft Dataverse | https://learn.microsoft.com/power-platform/admin/wp-security-cds
💡 Learn more about the Microsoft 365 & Power Platform community
• Microsoft 365 & Power Platform Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 & Power Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 & Power Platform - http://aka.ms/community/home
Sharing is caring! You are awesome! 🧡
A
A
So
this
is
a
quick
one,
I'm
Michael
for
everybody
who
doesn't
know
me
a
quick
introduction,
I'm,
a
business
applications,
MVP
I
work
as
a
manager
of
experience,
Tech
and
I
know
that
nobody
knows
what
that
means.
I
love
this
confusing
title:
I
work
as
a
whole
platform
consultant
solution,
architect
and
I
can
focus
on
the
most
fun
topics
in
the
Power
Platform
governance
and
administration.
A
Yeah
I
am
a
speaker
and
a
blogger
if
I'm
not
horribly
overworked,
which
I
am
right
now
at
the
moment,
as
you
can
see
on
the
left
side,
I've
been
busy
in
the
community
last
year.
This
is
all
2022
and
I
really
have
to
change
that
and
yeah
I'm
almost
afraid
to
say
that
I
work
part-time
as
a
graphic
designer,
but
I
saw
Hugo's
awesome
power
page
earlier,
so
maybe
I
should
step
back
and
let
it
do
let
him
take
over
all
right
now.
I'm
clicking
and
nothing's
happening
so
yeah.
A
Okay,
here
we
go
David
said
database
environment,
permissions
for
Power
Platform,
that's
a
mouthful
staring
a
little
bit
of
azure
and
a
little
bit
of
database,
and
this
is
actually
one
of
my
favorite
features
in
the
last
couple
of
weeks.
Actually
I'm
going
to
blog
about
it.
If
I
have
time
so,
but
I
thought
when
they
would
ask
I
might
show
you
as
well,
and
data
was
environment.
Permissions
is
a
very
long
word
and
a
very
long
term.
A
It's
basically
known
as
database
teams,
not
data
Wars
for
teams,
but
data
Works
teams,
there's
a
little
bit
confusing
naming
actually
and
yeah.
Sorry
for
the
for
the
theme
and
the
Apollos
I
was
a
little
bit
inspired
by
the
80s.
When
I
made
this
presentation
but
yeah
now
you
have
to
go
through
it.
Okay,
database
teams,
I
have
a
little
story
for
you
meet
ltsu
ltsu
security
is
a
security
company.
A
So
what
they
have,
they
have
a
special
sales
team.
That's
called
the
security
sales
team
and
they
do
have
their
own
environment.
They
realized,
and
they
know
that
if
they
want
to
provide
the
best
service
for
their
customers,
they
do
have
to
utilize
the
Power
Platform
and
they
know
their
governance.
So
they
come
up
with
an
environment
adjust
for
their
sales
team.
In
this
environment
they
use
basically
canvas
apps
model,
driven
apps
flows
and
power.
Virtual
agents
they're
not
really
a
fan
of
power.
A
Obviously,
as
you
can
see-
and
they
have
their
customer
data
in
there
and
they
are
pretty
huge
and
it's
a
successful
company,
as
you
can
see
from
some
of
their
customer
Brands,
they
got
azamon
and
the
the
brand
down
there.
That's
one
of
my
favorites
ghost
boards,
so
they
have
huge
customers
right,
and
so
that
is
the
initial
idea
of
the
year
of
customer
data.
You
don't
want
to
have
everybody
in
your
company
have
access
to
this
data
so
they
put
it
in
their
own
environment,
locked
it
up
with
a
security
group.
A
So
just
people
in
security
sales
business
units
are
able
to
access
those
data
which
is
smart,
which
is
nice
all
right.
They
have
a
huge
team,
as
you
can
see
from
these
huge
Brands.
They
have
a
lot
of
data
and
these
are
huge
customers
and
you.
This
is
not
a
job
for
just
a
few
people.
They
need
a
huge,
huge
team
to
work
with
all
this
data
and
what
you
usually
do.
A
If
you
want
to
handle
lots
of
data
in
a
very
appropriate
day,
you
use
a
power
app,
for
example,
customer
success
app
to
just
handle
all
this
data
according
to
your
needs,
so
that
doesn't
get
confusing.
So
that's
what
happened
to
ltsu.
They
have
their
security
sales
environment.
They
have
so
many
customers
with
so
many
data.
So
they
come
up
with
this
customer
success.
App
and
they're
using
that,
and
since
the
team
is
quite
a
lot,
there
are
lots
of
team
members
actually
up
here.
A
Oh
yeah,
they
are
not
just
working
for
all
the
customers,
they
have
key
account
managers
and
people
who
work
just
with
certain
customers.
As
you
can
see
here,
some
of
them
are
just
working
for
this
orange
brand,
some
of
this
white
off-white
brand
and
some
for
this
for
this
blue
company,
whatever
that
may
be-
and
the
point
is
as
soon
as
you
as
you
start-
to
use
it
as
a
Power
Platform
within
those
data
was
environments,
you
will
need
certain
roles
within
this
environment.
A
You
I
think
you're
pretty
much
all
aware
of
those
and
in
this
environment
we
need
some
system
admins,
some
makers
and
some
users,
because
not
everybody
needs
to
get
added
rights
on
every
on
this
data,
but
some
are
just
users,
so
this
is
kind
of
a
thing
that
I
would
usually
usually
start
with.
I
go
to
the
admin
Center
I
go
for
my
users
in
the
environment
and
I
would
assign
the
security
row
according
to
their
needs.
But,
as
you
can
see,
this
team
is
kind
of
huge
and
big
and
it
gets
even
bigger.
A
A
I
can
do
that
manually.
But
when
the
team
grows,
as
you
can
see,
it
does
grow,
then
it
gets
like
a
lot
and
luckily
we
do
have
dataverse
teams.
So
now
it's
still
more
people
coming.
The
company
is
growing,
which
is
great
still
growing.
Okay,
at
a
certain
point,
you
won't
assign
security
roles
manually
anymore,
so
that
now
it's
time
for
database
teams,
the
demo,
woohoo,
okay
and
now
I
need
to
switch
over
great
got
all
my
emails
open
here.
This
sounds
good.
Okay,
you
can
still
see
my
screen
right.
A
Yeah
that
looks
good
okay
I'm
here
in
my
Power
Platform
admin,
Center
and
I
have
this
security
sales.
This
is
my
environment
that
it's
it's
all
about
and
let
me
show
you
real
quick,
yes,
I
do
have
a
security
group
here:
sex
security
sales,
security
group.
So
everyone
who
is
part
of
the
security
group
can
access
this
data.
A
I
want
to
show
you
real,
quick,
how
it
looks
in
Azure,
because
I've
created
a
few
more
groups.
Actually,
let's
see
ad
groups
here
are
my
groups,
let's
see
down
here,
make
a
little
bit
bigger
here's.
My
security
group
that
handles
the
environment
and
I
created
three
more
groups,
because
sometimes
I
need
to
reach
multiple
people.
I
want
at
once.
So
I
have
my
security
sites,
admin,
Security
Group.
My
security
says:
make
a
security
group
and
the
user
Security
Group.
A
Basically,
they
are
according
to
the
rules
and
rules
that
I
need
in
my
environment.
So
what
I
do
usually
if
I
go
to
settings
and
let's
check
my
users-
I-
have
a
few
of
them
here
so
Andreas.
If
I
would
like
to
see
to
get
him
the
the
correct
security
role,
this
is
usually
what
you
start:
you'd
select
the
security
Rule
and
assign
it
to
him,
and
that's
the
point,
but
I
do
have
many
users
now
and
I
need
to
assign
the
security
rules
to
multiple
people.
A
So
it
doesn't
work
in
the
user
settings
it
might
work
in
the
security
rules
set
settings.
If
I
there
was
my
first
idea
actually
when
I
just
click
a
user
role,
let's
say
basic
user
and
then
I
click
on
members
that
sounds
like
I
could
add
multiple
members
at
once,
but
I
can
only
add
people
here
so
once
again,
I
can
search
for
mail,
an
email
address
or
a
team
name,
and
this
little
indicator
is
quite
of
important.
Actually
I
thought
at
first
I
could
assign
a
group
here.
A
Security
say
it's
admin,
for
example,
and
if
I
try
that
security
sales,
nope
no
user
or
teams
found
because
this
is
really
important,
it
says
teams
and
not
groups.
So
I
was
trying
to
add
a
group
and
that
where
I
started
there
was
a
point
where
I
started
to
work,
because
I'm
really
lazy,
let's
go
all
the
way
back.
This
is
on
the
front
page.
A
Luckily,
I
have
my
teams
here
and
if
I
click
on
that
I
click
on
the
teams,
I
have
just
the
basic
team
that
is
created
when
you
create
the
environment.
If
you
create
a
new
team
and
then
what
I
do
usually
I
create
a
team
for
each
of
my
groups
that
I
have
here
and
I
will
start
with
the
admins
and
just
show
you
this
one
example:
I
will
just
copy
the
name
as
I
mentioned,
I'm
really
lazy,
so
I
will
create
a
new
team
and
I
call
it
sex
sales.
A
A
A
A
A
Now
we
have
that
team
and
so
on.
The
point
is,
and
you
can't
really
see
or
show
that
okay,
if
I
manage
the
security
room
now
I
can
just
see
the
security
rule
here.
The
the
point
is
everyone
who
is
a
member
of
this
team
also
now
inherits
the
security
role
that
I
gave
to
this
team,
which
is
the
environment
maker
role,
which
was
a
little
bit
stupid,
because
this
is
the
admin
team.
A
Here
we
go
now:
everybody
who's
part
of
their
team
will
get
the
security
role
and
the
thing
that
I
really
like
about
it.
What
I
usually
do
with
every
customer
I
have
and
I
hardly
see
that
out
there
in
the
world,
with
my
customers,
I
use
those
teams
and
hook
them
up
with
security
groups
from
azure,
because
that
way
I
can
assign
security
roles
and
manage
the
security
level,
not
on
a
on
a
user
basis,
but
on
a
group
basis,
and
this
one
is
really
cool.
A
I
can
even
go
a
little
bit
further
if
I
came
up
with
with
those
groups
and
I
have
a
group
for
all
my
different
people
and
my
roles.
Let's
see
that
was
the
admin
role
with
the
maker
and
the
user
role
as
well.
This
one
is
just
for
the
environment,
the
security
group
to
secure
that
environment.
So
everyone
is
part
of
that
group,
everyone
in
the
security
sales
department
and
then,
according
to
their
role,
they
get
one
of
those
groups.
What
happens
when
I
use
those
groups
as
well?
A
Is
that
when
I
have
a
app
or
flow
that
I
want
to
share,
I
can
share
with
it
with
the
whole
group.
So
then
it's
easy
to
see
and
set
with
sharing
the
app
to
set
the
set
the
access
right
straight,
because
this
is
basically
done.
If
I
have
to
have
my
app
here
yep
that
says
it
gives
its
customer
success
app
if
I
want
to
share
it
and
I
just
want
to
share
it.
A
With
my
admin
team,
for
example,
I
will
see
those
males
and
I
know
that
the
security
rules
are
set
up
up
front,
so
this
makes
it
really
easy
to
the
app
set
who
is
allowed
to
see
which
data
and
who
can
do
what
in
this
environment
and
the
cool
thing
is?
Oh,
no,
that
wasn't
what
I
wanted
to
do
so,
and
the
cool
thing
is
basically
like
on
SharePoint.
You
will
manage
the
whole
thing
on
a
group
level
and
not
on
a
on
a
user
level.
A
So
if
I
would
sum
it
up,
the
benefits
are-
and
this
is
the
point-
is
actually
the
database
environment
permissions
for
Power,
Platform
or
data
was
teams.
I
can
hardly
see
they're
out
there
in
the
Wildwoods,
which
is
a
shame,
because
you
have
a
very
granular
level
of
access
and
security
within
your
environments
and
even
within
those
environments,
you
can
see
who
is
allowed
to
use
which
data
or
who's
only
to
see
with
which
data
the
approach
is
based
on
groups.
A
So
you
don't
need
to
manage
individual
users
that
that
makes
it
makes
it
super
easy
to
scale
it
up
or
down.
I
was
demonstrating
that
earlier
when
the
team
is
growing,
then
it's
really
really
easy
to
add
people
to
this
database
team
and
the
cool
part
which
I
really
like
is
when
the
Azure
ID
connector.
You
have
this
action,
add
user
to
group,
and
then
you
can
add
your
users
to
those
ID
groups
and
that
basically
means
that
you
assign
security
roles
with
power
automatic.
A
So
would
somebody
please
think
about
the
security
rules,
so
you
know
not
only
adding
your
user
to
the
groups
but
in
the
end
to
the
security
role,
because
the
security
rule
is
linked
to
the
group
with
the
team.
This
makes
it
pretty
easy
and
pretty
cool
it
can
build
really
cool
onboarding
processes
with
that
that
are
fully
automated,
which
I
really
like,
and
sharing
apps
and
flows.
Remember
of
the
group
is
really
easy,
and
that
is
basically
data
versus
teams.