The Security Development Tool is a feature developed initially for AX 2012 that helps to more easily create and maintain security artifacts such as roles, duties, and privileges. Technically this is still a beta tool offered by Microsoft through Life Cycle Services which provides the following features:

  1. Displays entry point permissions for a given role, duty, or privilege
  2. Provides the ability to record business process flows and identify the entry points that are used
  3. Allows for testing a newly created or modified security role, duty, or privilege without having to use a test user account


It is an extremely helpful tool that Security Administrators of AX can use during the development of user security. In D365FO though, the Security Development Tool doesn’t exist as a separate application but instead its features are implemented directly in the application itself.

Here’s a breakdown of where the features of the Security Development Tool now live in D365FO:

  • Full hierarchy view of role, duty, privilege, entry point security assignments
    • On the System Administration -> Security Configuration page if you select a role and choose View Permissions
    • You will then be presented with a report that shows an overview of the role, duty, privilege, and entry point assignment 
    • You can also follow this process to get the same information at a duty and privilege level
  • Breakdown of the roles, duties, and privileges that have access a particular page/form in D365FO
    • On a particular record or form go to Options -> In the Page Options section -> Select Security Diagnostics
    • A Security Diagnostics window will open and show the roles, duties, and privileges that have access to this page/form
  • Record a task/process
    • To start recording a process go to gear in the menu bar and click on Task Recorder
    • Give the recording a name and description
    • Navigate the steps required to complete the task, each step will be recorded in the right hand pane
    • When you are done, click the Stop button in the top menu bar and you will be presented with options to save the task steps in a number of ways

To help with the process of figuring out which menu items are used during the task, I have created a tool to help parse out a Developer’s Recording, it is available on my GitHub and a screenshot is below.


D365FO has now added an easy way to parse the task recordings to get the menu item data from it. In the system administration module, under the Security heading you will find an entry for ‘Security diagnostics for task recordings’.

One thing to note though is that this tool will not recognize menu item outputs or menu item actions used during a task recording.

If you click on that you will be presented with a couple options, with the Open from this PC option you can upload previously downloaded task recording XML files, you can also open any saved task recording from LCS.

Once the file is processed, you will be presented with a screen with very similar output from the utility I wrote. It will show you the label name, AOT name, and type of each menu item found in the task recording. One really cool feature, is that you can select a user from the User ID drop down and the system will tell you whether that user currently has the necessary permissions. In the example below, you can see that this user is missing the necessary permissions to perform this process.


YouTube Tutorial on Simulating the Security Development Tool in Dynamics 365 for Operations (5:35)

Security Development Tool user interface (AX 2012)

Task Recorder in Microsoft Dynamics 365 Enterprise