Gill Walker – CRM Success Catalyst, Speaker, Educator, D365 Project Manager, Microsoft Dynamics 365 Functional Consultant, Solution Architect, Advisor, Trainer, MCT, MVP, DTM

 

For real ROI from your CRM
call us now on

+61 2 82 1234 80

Gill Walker description of the Moving Parts in Dynamics 365 / Microsoft Power Platform security using a set of interlinked gear wheels

The Moving Parts of Dynamics 365 Security

Security in Microsoft Dynamics 365 isn’t a single mechanism — it’s an ecosystem. It blends licensing, security roles, team structure, environment controls, identity management, and app governance into one coherent framework. Each part has a distinct purpose; together they protect data integrity, enforce compliance, and support safe collaboration across the Power Platform.  Having said that, mot of the technical aspects are easy to understand - the real key to get it right is the governance.

Licences: The Foundation

Licences determine entitlement — what each user type is allowed to do.

  • Sales Enterprise/Professional, Customer Service, Project Ops: full create-read-update-delete rights across business entities.
  • Team Member: low-cost, read-mostly access with limited update ability.
  • Power Apps per App/User: custom-app entitlements outside the core CRM modules.

Licences define the ceiling; security roles define the floor. Even with a broad licence, a user can still be restricted by role.

Security Roles: The Enforcement Layer

Security roles turn licensing rights into practical access control.  Each role specifies privileges (Create, Read, Write, Delete, Append, Share, Assign) and depth (User → Business Unit → Parent:Child → Organisation).

Roles are additive — multiple roles combine.

Default “Basic User” ensures platform access; app-specific roles (e.g., Salesperson, Customer Service Rep) refine it.

Custom roles can tighten privileges but must never extend them beyond the user’s licence.

Business Units and Teams: The Context Engine

Business Units create hierarchical data boundaries.
Teams group users across those boundaries, enabling shared record ownership and collaborative work without transferring records.

Owner Teams can own records directly.

Access Teams provide temporary or dynamic sharing (e.g., for an opportunity pursuit).
This structure allows flexible, auditable collaboration without compromising security segregation.

Multi-Factor Authentication (MFA) and Conditional Access

Identity sits above everything else. Dynamics 365 inherits identity and access management from Microsoft Entra ID (formerly Azure AD).

MFA ensures credentials alone aren’t enough.

Conditional Access policies control how and where users connect (e.g., compliant device, corporate IP, location).
Together, they convert authentication from a binary gate into a context-aware decision engine.

Apps, App Modules and Managed Environments

Modern Dynamics 365 runs on the Power Platform, so Apps define user experience and security scope.

App modules limit what tables, dashboards, and processes each role can access.

Team Member licences are enforced at the app level — users must use Team Member Apps, not Sales Hub.

Managed Environments introduce administrative boundaries, DLP policies, and analytics for governance at scale.

Data and Column-Level Security

Beyond table access, Column-Level Security Profiles restrict sensitive fields (salary, tax ID, etc.) to approved users.  

Row-level (record-based) access flows from ownership and sharing; column-level control overlays additional precision — critical for privacy compliance and data minimisation.

Auditing, Telemetry and Compliance

Microsoft’s telemetry monitors entity access, API usage, and licence alignment (“functional equivalence” detection).
Admins can enable auditing for record history and changes, while activity logs feed compliance reports.
Together, they form the evidence trail regulators expect — and the early-warning system leaders need.

Governance: The Glue

True security isn’t configuration — it’s governance.

You should regularly - at least quarterly - review:

  1. Role-to-licence mapping 
  2. DLP policies and connector approvals
  3. Environment boundaries and owner assignments
  4. Conditional Access and MFA policies

Governance turns security from a checklist into a living management discipline that supports agility and compliance equally.

In Summary

LayerPurpose
Licences Define entitlement ceilings
Roles Enforce granular privileges
Business Units / Teams Structure collaboration
MFA / Conditional Access Protect identity and session integrity
Apps / Managed Environments Contain access and govern data flows
Field-Level Security / Auditing Protect sensitive data and maintain accountability
Governance Keeps all parts aligned and current

Power Platform Security is dynamic.

When executives and architects treat it as part of business governance — not IT plumbing — they gain control, confidence, and compliance in one integrated model.

👉 Opsis helps organisations build governance-first Power Platform and Dynamics 365 strategies that keep environments secure, compliant, and ready to scale.

Gill Walker's showreel QR code


Opsis is an expert Microsoft Dynamics 365, Microsoft Power Platform and CRM strategy consulting company. Our focus is your CRM success, with Microsoft Dynamics 365 / Microsoft Power Platform or any CRM technology - not licence sales or billable hours. As Principal CRM Success Catalyst, Gill oversees all business operations, strategic planning and execution, yet she still believes in offering personal attention to each and every client, so as to understand their needs and offer tailored solutions.  We are based in Sydney, with clients in Sydney, Canberra, Melbourne, Brisbane and across Australia.  Gill is the creator of SuccessRM - your blueprint for CRM success.  We offer:

  • Strategy for your successful CRM
  • Microsoft Dynamics 365 and Power Platform
    • scoping
    • implementation
    • technical support
    • training
    • consulting, advice and guidance
    • assistance with your centre of excellence
  • Mentoring for CIOs and other decision makers tasked with implementing CRM.