A company is implementing Dynamics 365 Finance. The company will complete an acquisition in the upcoming year. The acquisition will be implemented as a second legal entity in Dynamics 365. Some existing key users will move to the new legal entity. Which Microsoft best practice security structure for business units should you implement?

Each business unit in Dynamics 365 Finance represents a separate division or legal entity. By implementing a separate business unit for the new legal entity formed by the acquisition, you ensure that the data, transactions, and security roles are isolated and distinct from the existing legal entity.

2. Security Management:

Dynamics 365 allows you to assign security roles at the business unit level. By setting up a separate business unit, you can define security roles specific to the users who will work in the new legal entity. This ensures that users only have access to the data and functionality relevant to their roles within the new entity.

3. Organizational Structure:

Maintaining separate business units aligns with the organizational structure of having distinct legal entities. This structure supports clearer management of operations, reporting, and compliance requirements for each entity independently.

Therefore, to best manage the acquisition scenario described while adhering to Microsoft's best practices for security and organizational structure in Dynamics 365 Finance, you should implement a separate business unit for the new legal entity formed by the acquisition.

Explanation:

Answer :

Implement a Separate Business Unit for the New Legal Entity

Here's why this structure is recommended:

1. Isolation of Data:

2. Security Management:

3. Organizational Structure:

hope this answer helps you

Other Questions