• Advertising & Marketing Agencies

Security Concepts & Methodologies in Microsoft Dynamics 365 for Finance and Operations

In this blog, we would explore the security concepts and methodologies available in Microsoft Dynamics 365 for Finance and Operations and how we could assign them to different roles.

Security Concepts

Job Function
Assigned to user

Accounting Manager
Accounts payable clerk
Accounts receivable Clerk

Dynamics AX 2012 Security role accountant
(Microsoft Dynamics AX 2012 View)
To avoid losing personal sysadmin rights during security testing, it is best to use test accounts.


Business Process
Group of related privileges

Configure electronic fiscal document
Enable bank management process
Inquire into fixed assets
Approve travel requisitions and expenses
Maintain project ledger postings

Dynamics AX 2012 security privileges

(Microsoft Dynamics AX 2012 View)


Access Required for Job/Business process
Permission to object

Approve bank account reconciliation
Create bank prenotes

Dynamics 365 for Finance and Operations Security Configuration

Microsoft Dynamics 365 for Finance and Operations View

Roles, Duties, and Privleges work together much like an essay outline to provide a user with the necessary access to the system. A user might be assigned 2 roles (A&B), each of which containing a bundle of duties, with each duty containing a bundle of privleges.

Example User Security Setup:

  1. Role A
    1. Duty A
      1. Privlege A
      2. Privlege B
      3. Privlege C
    1. Duty B
      1. Privlege C
      2. Privlege D
      3. Privlege E
  1. Role B
    1. Duty C
      1. Privlege A
      2. Privlege F
      3. Privlege G

Security Methodologies

Standard AX Roles:

Stick to the standard AX roles and assign them to users as necessary until they have the necessary access.


  • Little to No Customizations
  • Minimal Time
  • Use of Lifecycle Services


  • Little Flexibility
  • Need to determine how to handle customizations
  • Segregation of Duties concenrs

By Process:

Map out the processes done by each type of system user and create roles for those processes.


  • Give people access they need proven by outlined processes
  • Flexibility
  • Ease of Segregation of duties
  • Use of Lifecycle Services


  • Time Consuming
  • Requires that processes have been outlined
  • General Access bay be missed if processes are missed

By Menu Item:

Go through each menu item in AX and determine which users should have access to it.


  • Easy to analyze access required with end users
  • Security is largely based on Menu Items


  • Most time consuming
  • No synergy with other implementation processes

Related Articles

About the Author

Josh Knox

Josh Knox

Josh Knox is a Functional Consultant for sa.global, where he helps provide strategic consulting services around the design and deployment of the client’s Dynamics ERP system. Josh identifies client requirements, assists with system setups and configurations, writes development specifications, provides training, and performs other project activities. He has significant experience helping professional services companies with their Dynamics 365 implementations, particularly in the areas of data migration, workflow design, business intelligence, and projects360 – sa.global’s custom enhancements to the Projects module.

  • This email address is being protected from spambots. You need JavaScript enabled to view it.
Contact Us

Select Country

Select Your Local Website

Other Websites

sa.global does not share your personal data with any third parties.
I'm ok with sa.global storing my personal information as per their privacy policy