12 Tips of D365 F&O - Testing With Security

December 4, 2023

🎶In the first tip of D365 F&O, D365 with Brittany shared with me--always test with proper security!🎶

Why is Testing With Security Important?

There is nothing worse than turning a customization over to a user only to be plagued by security issues and missing menu items. Before suggesting users should test, be sure to complete 2 rounds of testing - one with system admin to fully assess the functionality and a second with the proper security assigned. 


Functionality Testing

Testing customizations and new functionality should start with a full testing cycle with the System Administrator role before creating and testing with the proper security that users will be assigned.  This cycle of testing should be completed by the IT/Project/Consulting team prior to any user testing. 

Why test with System Admin access first?

Advanced Functionality Testing:

Troubleshooting and Debugging:

 In my experience, ensuring the functionality works as intended before adding in the additional layer of security will help to ensure the solution is complete and that any issues with the solution regardless of security are worked out. Only once the functionality is working with System Admin should it be turned over to users for testing with proper security.

Security Testing

Once the functionality has been full vetted without limited security, customizations should be tested with the same access a user would have in a live environment. 

Why should I test with limited security?

Accurate Representation of User Experience:

Identification of Permission-Related Issues:

Validation of Security Configuration:

Risk Mitigation:


Have questions about testing with security? Send me a message and I will be in touch!


Don't forget to subscribe to my newsletter to get exclusive content and stay up to date with all my latest posts.Â