Plaza 365
Plaza 365

No results found for your search

RegisterLog in

4

Microsoft D365 Security Design Implementation Considerations

Visit article

#security

Dynamics 365 ERP - Development

Category

Feb 29, 2024

Published date

Text

Article Type

AI Summary

  • The article discusses the considerations for implementing a custom security model before or after an ERP implementation.
  • Designing and building a custom security model before an ERP implementation requires several months and conducting workshops with the business to determine access requirements.
  • Implementing security after an ERP implementation allows for more buy-in time from the business, IT, and compliance.
  • Designing custom security before an ERP implementation may help SMEs better understand the system and provide transparency among the responsibilities of other workstreams.
  • Designing custom security after an ERP implementation is more streamlined as the business processes and configurations are already defined.
  • The impact on the business differs depending on when the custom security model is implemented, resulting in additional change management and training efforts.
  • Incorporating security during the user acceptance testing phase of an ERP implementation is recommended to properly identify and troubleshoot bugs.
  • Customizing the security model to only the required access can save licensing fees and make the environment more secure.

Registered users can view the full text for FREE!

Sign In Now!

Cookies Consent

We use cookies to enhance your browsing experience, serve personalized ads or content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies.