<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=523033&amp;fmt=gif">

Moving Dyn 365 for Finance & Operations Security Between Environments

The Security Designer tool from Fastpath offers the ability to easily set up your security in a compliant way from a segregation of duties and licensing perspective. Once this process is completed and tested in a development instance, the next question is how to move this security to your other environments... this blog explains how to do just that.

How Security Changes Migrate Between Environments

Sometimes customers want to try and take the security models used to deploy security in a development environment and re-deploy them to other instances. Doing this though would break the ALM (application lifecycle management) story that Microsoft has developed for D365FO. We instead recommend that you treat security as code and have it follow the same promotion process that you would any custom code.

So instead of doing what is demonstrated in the graphic below, where you use Fastpath Security Designer to move security to each D365FO instance:

Fastpath Security Designer for D365FO

We recommend doing this, where you publish security changes to DEV and then use your normal code promotion process to move the security changes to other instances:

Alex-2.12.20-BFastpath Security Designer for D365FO - better way

The goal with this is that no security changes should directly be made in production just like how code changes are not done in production.

Security Migration Options

1.  Migration as part of code – if all of your security changes are done via the AOT you can move your security as part of your deployable package between environments.

2.  Migration using user interface changes – if you made changes to security in the user interface, these changes are not a part of code and need to be migrated manually this can be done via the Import/Export functionality within the Security Configuration area of D365FO.
Fastpath Security Designer for D365FO - migrating data
3. Migration using the Security Migration solution within Security Designer – if you use Fastpath Security Designer or the D365FO user interface to make your security changes, you can take the XML document generated during the export of security via the Import/Export security functionality described above and use the Security Migration tool within Fastpath to customize which changes to export, modify security labels, and what format to export the results.

Fastpath Assure Security Designer for D365FO - Security Migration

More information on this solution can be found here: https://support.fastpathassure.com/hc/en-us/articles/360041124533-D365-Finance-and-Operations-Security-Migration 

Looking for even more tips and tricks for Microsoft Dynamics 365 for Finance & Operations Security? Check out all of our D365FO blogs here.