web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Splitting Instance

(0) ShareShare
ReportReport
Posted on by 6,125

Hi Experts

Due to enough users and different operations load, a Microsoft expert suggests that we go with a split instance approach in my current project. As we have a really big community here, and I need to understand from all of my community mates what kind of challenges we can face while moving from signal instances to multiple instances.

Some of the following challenges I knew.

  • Code state management.
  • Batch management.
  • Licensing Cost (if some users want to work on both instances?)
  • Deployment management.
  • More maintenance/support resources(In person) are required.

Important

We have completed enough performance improvement in almost all areas.

I have the same question (0)
  • Suggested answer
    nmaenpaa Profile Picture
    101,162 Moderator on at

    Hi Sheikh Sohail,

    this would mean that you have two separate LCS Implementation projects and two sets of systems (at least Prod and one Sandbox tier 2 where you validate the deployable packages).

    I would start by going through this article: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/implement-multiple-projects-aad-tenant

    But also discuss with the Microsoft expert who suggested this to you.

  • Sheikh Sohail Profile Picture
    6,125 on at

    Thanks nmaenpaa

    Thank you for sharing the blog, and Yes, we will have two separate LCS implementations(Prod) in the same Azure Tenant. As we are already in discussion with Microsoft and the same time I would need some valuable feedback from the community if they had experienced multiple instances.

  • Wajahat Mirza Profile Picture
    254 on at

    We are using two separate LCS implementation projects in one tenant and both projects are having different business operations, they are different projects.

    We have separate DEVOps projects and code deployments and bought separate licenses for each of them.

  • Sheikh Sohail Profile Picture
    6,125 on at

    Hi Wajahat

    Thank you very much for your reply.

    Would it be possible for you to share a little more detail here, about the advantages and disadvantages of this approach (except the ones mentioned on MS docs)?

    what was the reason, why you moved to the multiple instances approach?

    After the implementation, have you achieved your objective?

    What was the improvement after the implementation of the multiple instances approaches?

    What kind of issues you are suffering now?

    what are the disadvantages?

    Do we have data sync between additional instances and the primary instance?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 449 Super User 2025 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 422 Most Valuable Professional

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans