Book_07 — Access Control: Groups, Roles, and Dynamic Membership

Designing the Entra Groups Behind SQL Server Access — Role-Mapped Groups, Attribute-Driven Membership, Scoped Delegation, and Just-in-Time Privilege

What replaces the AD security group as the unit of SQL Server authorization. Explains how Entra group membership reaches SQL Server logins and database roles, why each group should map to exactly one role, how dynamic membership rules keyed on HR-sourced user attributes keep access current without DBA tickets, and the governance that makes that safe — attribute source of truth, rule testing and processing limits, administrative-unit delegation, PIM for Groups, access reviews, break-glass, and monitoring. Conditional Access becomes the outer perimeter once every login is Entra-backed.
Note

The migration moves SQL Server’s groups from Active Directory to Microsoft Entra ID, but it keeps group-based authorization. What changes is who maintains the groups and how. A group that maps to a single database role can keep itself current from HR-sourced attributes, which removes the helpdesk ticket. That only works if the attributes are trustworthy, the rules are tested, delegation is scoped, and privileged access is just-in-time. This book covers that design and the governance it needs.

Outside the engine, the HR system of record feeds user attributes in Entra ID and Entra security groups; inside the engine, a type X group login maps to a user-defined database role and its permissions, unchanged from before.

The directory half of SQL Server access moves to Entra ID; the engine half barely changes.
TipDownload this book

Book_07-bundle.docx — every chapter of this book concatenated into one Word document. Regenerated on every site deploy.

Chapters

Place in the dependency chain: Step 5 — Introduce Entra principals (groups and authorization).

Authoritative references

Checked 19 October 2026.

Back to top