Contenido generado con IA
Transcrito
The Dataverse Security Model Explained for Architects
31 de oct. de 2026 ·
1h 22m 59s
Descarga y escucha en cualquier lugar
Descarga tus episodios favoritos y disfrútalos, ¡dondequiera que estés! Regístrate o inicia sesión ahora para acceder a la escucha sin conexión.
The Dataverse Security Model Explained for Architects
Descripción
Most Dataverse security problems start when access is granted one ticket at a time instead of by structure. This episode walks architects through business units, security roles, teams, ownership, column...
mostra más
Most Dataverse security problems start when access is granted one ticket at a time instead of by structure. This episode walks architects through business units, security roles, teams, ownership, column and hierarchy security, and sharing, and shows how to design a model that survives reorgs, audits and Copilot.
In this episode
Key takeaways
Worth quoting
“A Dataverse security model only scales when it's designed around ownership and hierarchy, not around individual access requests.” – Mirko Peters (00:12)
“So treat organization depth the way you treat a master key. A small number of people need it admins, integration accounts, maybe a data steward or two.” – Mirko Peters (24:28)
Explore more on M365.FM
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
This episode includes AI-generated content.
mostra menos
In this episode
- 00:00 – The question Dataverse security actually answers
- 03:11 – The four layers and the environment boundary
- 08:34 – Business units and why trees break at scale
- 18:15 – Security roles, privileges and access depth
- 25:10 – Record ownership and teams
- 37:15 – Column-level security and hierarchy security
- 51:45 – Sharing, its cost and how access is evaluated
- 64:01 – Role and team design, anti-patterns and governance
Key takeaways
- Dataverse security decides which rows a user can reach by combining identity, privilege, scope and record ownership, and access is always additive.
- Business units should model real data boundaries such as legal, regulatory or contractual walls, not the org chart, and teams should own long-lived data.
- Sharing, organization depth and one-off roles are shortcuts that erode the model, so roles, teams and profiles belong in solutions with reviews and auditing.
Worth quoting
“A Dataverse security model only scales when it's designed around ownership and hierarchy, not around individual access requests.” – Mirko Peters (00:12)
“So treat organization depth the way you treat a master key. A small number of people need it admins, integration accounts, maybe a data steward or two.” – Mirko Peters (24:28)
Explore more on M365.FM
- Episode page: the full episode with chapters, key quotes and a short FAQ
- Dataverse – the platform whose row-level security model of units, roles, teams and ownership is dissected
- Microsoft Entra – security groups gate who can enter an environment, and Entra group teams drive team membership
- Governance – solutions, reviews, access recertification and documentation that keep roles and teams from drifting
- Related episode: Dataverse - Simply Explained
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
This episode includes AI-generated content.
Información
| Autor | Mirko Peters M365, Azure & AI |
| Organización | m365 FM |
| Página web | www.m365.fm |
| Etiquetas |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Comentarios