---
schema_version: "1"
id: bd0a47c304f0499f1e2e8dd55b13b943453479589c51213907822a24e80b9b87
title: Anypoint Connectors Shared Responsibilities
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/connectors/introduction/connectors-shared-responsibilities.md
canonical_url: https://docs.mulesoft.com/connectors/introduction/connectors-shared-responsibilities
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 6f4a00798b22f4f7c86f14c569dd795ce5a84cd77714e383132714a853506bfa
description: MuleSoft Documentation Site
latest: true
---
---
product: Connectors
---

# Anypoint Connectors Shared Responsibilities

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The successful operation of Anypoint Connectors is a shared responsibility between MuleSoft and the
customer. It is critical to understand which areas customers are responsible for and which areas
MuleSoft is responsible for.

We have created this page as a helpful summary for you to better understand the different
responsibilities. However this page is provided for convenience only as all support obligations are
subject to your executed agreement with MuleSoft.

## Anypoint Connectors Categories

Anypoint Connectors fall into these categories:

- **Premium**  
  These connectors must be purchased as add-ons to an Anypoint Platform subscription and are
  available to licensed users only.

- **Select**  
  These connectors are included with a paid MuleSoft subscription.

  Select and Premium connectors can further be categorized as:

  - **Connectors or modules that enable connectivity to MuleSoft or Salesforce applications**  
    For example, Salesforce Marketing Cloud Connector or Anypoint MQ Connector.

  - **Connectors that enable the use of cross-platform protocols or open APIs**  
    For example, Database Connector, which is based on Oracle’s JDBC protocol.

  - **Connectors that enable connectivity to third-party or partner APIs**  
    For example, Azure Key Vault Connector or Stripe Connector.

- **MuleSoft Certified**  
  Connectors developed by MuleSoft’s partners and subsequently reviewed and certified by MuleSoft,
  for example, ESRI Connector. For these connectors, MuleSoft takes initial support calls and
  isolates the issue for resolution. MuleSoft disclaims any additional support obligation for
  MuleSoft Certified Connectors. For additional support of MuleSoft Certified Connectors, contact
  the MuleSoft partner who created the connector.

- **Community**  
  Connectors developed by the MuleSoft developer community. For example, Slack Connector.

## Shared Responsibilities

The following table clarifies the responsibilities that customers and MuleSoft share for Anypoint
Connectors:

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Type of Connector</th><th>MuleSoft Responsibilities</th><th>Customer Responsibilities</th></tr></thead><tbody><tr><td><div><div><p>Premium or Select: Connectors or modules that enable connectivity to MuleSoft or Salesforce applications.<br></p></div><div><p>For example:<br></p></div><div><ul><li><p>Salesforce Marketing Cloud Connector</p></li><li><p>Anypoint MQ Connector</p></li></ul></div></div></td><td><p>Support for the connector source code and the functionalities that the connector provides.</p></td><td><div><div><ul><li><p>Ensure that the connector versions and Mule runtime engine (Mule) versions are up to date with the latest version released by MuleSoft.</p></li><li><p>Grant roles and permissions for access to resources.</p></li><li><p>Check the shared libraries, plugin dependencies, configuration files, templates, scripts, proxies, and network configuration.</p></li><li><p>Check the third-party driver limitations, load balancing, parallel processing, and authentication protocols.</p></li><li><p>Check performance issues in destination servers and partner applications.</p></li></ul></div></div></td></tr><tr><td><div><div><p>Premium or Select Connectors: Connectors that enable the use of cross-platform protocols or open APIs.<br></p></div><div><p>For example:<br></p></div><div><ul><li><p>Database Connector</p></li><li><p>JMS Connector</p></li><li><p>SFTP Connector</p></li><li><p>X12 Connector</p></li><li><p>EDIFACT Connector</p></li><li><p>TRADACOMS EDI Connector</p></li></ul></div></div></td><td><div><div><ul><li><p>Support for the connector source code, its packaged libraries, and the functionalities the connector provides.<br></p></li><li><p>MuleSoft incorporates specific industry-standard message specifications into these connectors, but is not responsible for the partner system or domain technology configuration.</p></li></ul></div></div></td><td><div><div><ul><li><p>Ensure that the connector and Mule runtime engine (Mule) versions are updated with the latest version released by MuleSoft.</p></li><li><p>Grant roles and permissions for access to resources.</p></li><li><p>Check the shared libraries, plugin dependencies, configuration files, templates, scripts, proxies, and network configuration.</p></li><li><p>Check the third-party driver limitations, load balancing, parallel processing, and authentication protocols.</p></li><li><p>Check performance issues in destination servers and partner applications.</p></li><li><p>Check with the partner their system or domain configuration, and technology, for example database and JMS broker administration.</p></li></ul></div></div></td></tr><tr><td><div><div><p>Premium or Select Connectors: Connectors that enable connectivity to third-party or partner APIs.<br></p></div><div><p>For example:<br></p></div><div><ul><li><p>Stripe Connector</p></li><li><p>Azure Key Vault Connector</p></li></ul></div></div></td><td><div><div><ul><li><p>Support for the connector source code, connector packaged libraries, and the functionalities the connector provides.</p></li><li><p>MuleSoft is not responsible for specific third-party SDK libraries. MuleSoft uses APIs provided by the partner, but it is not responsible for these third-party provider configurations and does not provide assistance with issues related to the drivers or APIs that the connector uses in the background. For underlying third-party configuration or issues, contact the third-party provider directly.</p></li></ul></div></div></td><td><div><div><ul><li><p>Ensure that the connector version and Mule version are up to date with the latest version released by MuleSoft.</p></li><li><p>Implement the driver of your choice to configure third-party SDK libraries.</p></li><li><p>Review the third-party API specification documentation for configuration information.</p></li><li><p>Grant roles and permissions for access to resources.</p></li><li><p>Check the shared libraries, plugin dependencies, configuration files, templates, scripts, proxies, and network configuration.</p></li><li><p>Check the third-party driver limitations, load balancing, parallel processing, and authentication protocols.</p></li><li><p>Check the performance issues in destination servers and partner applications.</p></li><li><p>Check with the third-party or partner who provides security updates and apply modifications to the underlying endpoints. Third parties and partners can assist with using third-party APIs and drivers and with configuring SDK libraries.</p></li></ul></div></div></td></tr></tbody></table>

## See Also

- [Product Versioning and Back Support Policy](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf)