Skip to main content

Notifications

Announcements

New Dynamics 365 Community Call! (ERP Edition)
Next Dynamics 365 Community Call (CRM Edition)
News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM forum / Single vs multiple pro...
Microsoft Dynamics CRM forum
Suggested answer

Single vs multiple production instances architectural considerations

(0) ShareShare
ReportReport
Posted on by Peragin 135

Hi there,

Currently we are reviewing our D365 architecture where it predominantly provides B2C service support, i.e. D365 CE. We now want to look at providing a B2B contact management facility for the organization. We are trying to decide whether we should create a separate instance or use the existing instance. Our main concerns are that the security model would get very involved if we try to use a single instance as access to contacts on the B2B side is far more segmented and sensitive. However, multiple instances mean integration and master data management. I would be very grateful of any experience and advice on the pros and cons etc.

Thanks in advance,

J

Categories:
Administration and Setup
  • FF-24051435-0 Profile Picture
    FF-24051435-0 2 on at
    Single vs multiple production instances architectural considerations
    Hi Mukesh Naik,
    The post is 4 years old and I would be interessted in the decision you took and also the expereinces you had with.
    We are currently asking us the same question in a very similar situation B2C & B2B Dynamics solution on top of a CDS.
     
  • Suggested answer
    Adrian Begovich Profile Picture
    Adrian Begovich 20,979 Super User on at
    RE: Single vs multiple production instances architectural considerations

    Hi Mukesh Naik,

    If you do a multi-environment deployment in a single tenant then data is not shared across environments. You will need to build an integration to sync these environments with the on-premise CMS. However, it sounds like the users preforming B2B and B2C sales actions will need to access the same data. If they need to access the same data then it is best that they are in the same environment.

    It is worth investigating whether or not you can achieve the desired outcome with a single production instance deployment. This way you can avoid adding additional complexity and unnecessary duplication of data.

  • MukeshNaik Profile Picture
    MukeshNaik 10 on at
    RE: Single vs multiple production instances architectural considerations

    Thanks Adrian, is ther any other optimized way to achive the same?

  • Suggested answer
    Adrian Begovich Profile Picture
    Adrian Begovich 20,979 Super User on at
    RE: Single vs multiple production instances architectural considerations

    Hi Mukesh Naik,

    That approach will work if the implementation is good.

  • MukeshNaik Profile Picture
    MukeshNaik 10 on at
    RE: Single vs multiple production instances architectural considerations

    Hi There, 

    We are in a similar situation for our Implementations, Could you please suggest any architectural guidance.

    Our plan is to use MultiInstance (for B2B and B2C sales) and use Separate CDS instance for Master data Synchronization (read Only) to the respective instances, CDM/CDS shall be synched with On Prem CMS.

    Request guidance for this approach

  • Suggested answer
    Adrian Begovich Profile Picture
    Adrian Begovich 20,979 Super User on at
    RE: Single vs multiple production instances architectural considerations

    Hi Peragin,

    This article explains common use cases for multi-instance deployment. For most companies, adding and using multiple instances in your subscription provides the right mix of functionality and ease of management. Enterprises with separate geographic locations might consider using multiple tenants to separate licenses.

    A single production instance deployment may be sufficient when the typical use cases for multi-instance and multi-tenant deployment are not required. For this approach it is best to segregate data using business units. Multiple instances are needed when segregation is required of plugins, workflows, or admin resources that cannot be easily isolated by using business units.

Helpful resources

News and Announcements

New Dynamics 365 Community Call! (ERP Edition)
Next Dynamics 365 Community Call (CRM Edition)

Quick Links

Dynamics 365 Community Update

Welcome to the inaugural Community Platform Update. As part of our commitment to…

Dynamics 365 Community Newsletter - August 2024

Catch up on the latest D365 Community news

Community Spotlight of the Month

Kudos to Waed Ayyad!

more Community News

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 289,995 Super User

#2
Martin Dráb Profile Picture

Martin Dráb 227,174 Super User

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans