Connecting data sources and integrations

This article explains how data sources are connected in Kaseya MDR, where those connections are initiated in the user interface, and how incoming telemetry is associated with organizations for analysis.

In Kaseya MDR, data sources can be connected using two different UI entry points:

  • A Settings‑initiated flow, used to create integrations from an administrative or partner context

  • An organization‑initiated flow, used to add applications within the context of a specific organization

Both workflows ultimately associate telemetry with an organization so it can be analyzed in Kaseya MDR.

Key concepts

Integrations (partner‑level management)

An integration defines how Kaseya MDR connects to a data source and receives telemetry. Integrations typically represent partner‑managed tools, such as MSP RMM platforms, PSA systems, or shared security services.

Integrations are created and managed centrally from Settings > Integrations. Creating an integration here establishes how the data source connects, what credentials or authorization are used, and which organization incoming telemetry is routed to.

Integrations created at the Settings level may be reused when connecting multiple environments, depending on the integration.

Applications (organization‑level association)

An application represents a data source as it is associated with a specific organization.

Applications are visible from Organizations > Edit organization > Applications tab.

Applications may represent:

  • Customer‑owned SaaS services (for example, Microsoft or Google Workspace)

  • Organization‑specific security tools

  • Partner‑managed tools that are connected in the context of a single organization

Adding an application associates telemetry from that source with the selected organization.

Organizations (data ownership and analysis boundary)

An organization defines the boundary in which telemetry is stored and analyzed in Kaseya MDR.

Incoming telemetry must be associated with an organization in order to appear in alerts, investigations, and analysis. Connection workflows differ in how the association is initiated, but the organization ultimately determines visibility.

Workflow 1: Connecting an integration from Settings (partner‑level)

This workflow is used when initiating a connection from the administrative Settings area and is commonly used for partner‑managed integrations.

UI path

  1. From the side navigation menu, click Settings.

  2. Select Integrations.

  3. Click + New Integration

  4. Select an organization to route incoming data.

  5. Choose the integration type.

  6. Provide the required credentials or authorization.

  7. Click Next to continue setup.

Organization selection during setup

During setup, you are prompted to map the integration to an organization. This mapping determines where incoming telemetry is routed for analysis.

The Add Integration screen also indicates constraints and behaviors such as:

  • Each organization supporting only one connection per application type

  • Multiple instances of the same application requiring separate connections

  • How mapped and unmapped data is handled for the selected organization

Organization mapping behavior

When connecting an integration from Settings:

  • All mapped telemetry is routed to the selected organization

  • Any unmapped telemetry is typically stored under the selected organization by default.

  • Each organization can have one connection per application type

To connect multiple instances of the same tool (for example, two separate RMM environments), each instance must be connected separately and mapped to its own organization.

Integration warnings and constraints

During setup, warning messages may appear indicating that:

  • A connection already exists for a given application

  • Adding the same integration instance to multiple organizations may result in duplicate events or alerts

These warnings are integration‑specific and enforced by the setup interface.

Workflow 2: Adding an application from within an organization

Kaseya MDR also supports initiating connections from within an organization.

Use this workflow when:

  • The connection is customer‑specific

  • The customer must complete authorization or consent

  • The data source is scoped to a single organization

UI path

  1. From the side navigation menu, click Organizations.

  2. Click Edit organization.

  3. Open the Applications tab.

  4. Click + New Application.

  5. Select the application and complete the connection.

Applications are grouped into categories (for example, MSP Tools, Customer Apps, Endpoint Security) to reflect ownership and scope.

Credential and delegation options

When adding an application from within an organization, the interface may present options indicating who completes the authorization step, such as:

  • Using partner or administrator credentials

  • Allowing the customer to complete authorization

These options affect who performs the authorization, not how telemetry is processed once the connection is established.

How connection scope affects visibility

Where a connection is created affects where it appears in the interface:

  • Integrations created from Settings appear at the platform level.

  • Applications added from within an organization appear under that organization’s Applications tab.

Both workflows result in valid telemetry ingestion once the data source is connected and associated with an organization.

What happens after a data source is connected

After a data source is connected and associated with an organization:

  • Telemetry from that source becomes available for analysis in Kaseya MDR within the context of the associated organization.

  • Existing configuration, alerts, and investigation behavior apply based on the data and rules already configured in Kaseya MDR.

Key takeaway

  • Settings > Integrations is used to create integrations from an administrative or partner context.

  • Organizations > Edit Organization > Applications is used to connect data sources within a specific organization.

  • During setup, integrations are mapped to an organization so telemetry can be routed for analysis.

  • The two workflows reflect different starting contexts, not different data outcomes.

Related articles

  • Integrations and data sources: Explains the categories of supported data sources in Kaseya MDR and how different integration types contribute telemetry for analysis

  • Application Configurations: Explains how behavior, processing, and handling of ingested data can be adjusted after a data source is connected, including configuration settings that affect analysis and investigations

  • Detection and correlation: Describes how detections, indicators of compromise (IOCs), and response rules operate on ingested telemetry after data sources are connected and associated with an organization