When working with the TIBCO Scribe Insight Publisher for Microsoft Dynamics 365, the best practice is to connect only one publisher to the Dynamics 365 organization. If you connect multiple publishers from the same Insight server or publishers from multiple Insight servers, unexpected behavior can occur. 

When a publisher connects to a CRM organization it creates the Scribe changehistory plugin and assembly. When you add an entity to the publisher and an action to monitor, such as insert, update, or delete, the publisher will add this corresponding step to the plugin in CRM. Only one Scribe changehistory plugin can exist in a CRM organization. Any additional publishers configured on the same Insight server or on multiple Insight servers will use the same Scribe changehistory plugin and assembly and will overwrite the plugin. There are a few symptoms and behavior that can be seen with multiple publishers connecting to the same CRM organization. 

Symptoms and Behavior

• When changes are made in one publisher, it will modify the Scribe changehistory plugin in CRM to reflect these changes. As a result, settings that were in place by another CRM publisher will be overwritten. You may see entities and actions that are being monitored change in the CRM plugin assembly of the CRM organization. 
• If multiple Insight servers are using a publisher for the same CRM organization, you may see strange message queue behavior. Potentially messages meant for one Insight server could be seen on another Insight server.

TIBCO recommends connecting only one Publisher per CRM organization to prevent issues from occurring.

TIBCO recommends that you only ever have one publisher connecting to a Dynamics 365 CRM organization.  

If you need to capture changes from one Dynamics 365 CRM organization as a data source from multiple Insight servers, these methods are available and will not cause a conflict. 

• Query Publishers - When using queue based integrations.
• Time Integration Processes - Runs a DTS on a defined schedule. Can use a CRM source query to pull records. 
• Query Integration Processes -  Runs a DTS based on the results of a source query in the DTS.