Skip to content
Explore msspConnector profiles
MSSP/MDR · Technology

Connect each customer without a fork.
One connector. Separate profiles.

Deploy a connector once, then give each customer a Tenant Profile with its own endpoint and credentials. The Marketplace brings external data and actions into SOC workflows. Configure the connection, review its test result and enable the capabilities your licensed workflows need.

1,400+ connectors26,000+ connector actions40 connector categories
One connector, three customersIllustrative
Microsoft SentinelAll Tenants
ConfigureTenant Profiles
Tenant Profiles
NorthstarEndpoint: Northstar workspaceCredentials: own Vault profile
Harbor RetailEndpoint: Harbor Retail workspaceOwn credentials via proxy agent
JuniperEndpoint: Juniper workspaceCredentials: own Vault profile

Each customer keeps its own poll cursor and statistics alongside the connection profile.

Microsoft Sentinel
ConnectorSIEM
Installed
ConfigureEndpoint and credentials
Tenant ProfilesSeparate customer connections
IngestionConfigure supported polling

One connector definition serves the customer profiles.

Northstar
Profile
Primary
Endpoint
Northstar workspace
Credentials & configuration
Own credentials in the Vault
API Version
Automatic
Ingestion
Own poll cursor and statistics
Test Connection
Review the reported result

Harbor Retail uses its own proxy agent; Juniper has a separate connection profile.

Test Connection
NorthstarCredentials verified
Verified
Harbor RetailReached, not authenticated
Review
JuniperCredentials verified
Verified

A reachable endpoint does not by itself confirm authentication.

Next step
Review authentication before use
Test Connection
Northstar
Microsoft SentinelPrimary profile
Northstar
AutomatioConnector action in a licensed playbook
Agent StudioEnabled connector tool in a licensed agent
Credentials & configurationResolved from the customer profile

The calling workflow’s permissions and approval rules determine what can run.

Credentials, tenant access and the calling workflow's permissions and approval rules determine what can run.

Microsoft Sentinel is one connector in Marketplace. Customers use their own connection profiles.

Northstar, Harbor Retail and Juniper each have a separate endpoint and credentials in Tenant Profiles.

Review the reported result for each profile. Reaching an endpoint does not by itself confirm authentication.

A licensed playbook or agent uses the customer connection under its permissions and configured approval rules.

Illustrative customer workflow
Illustrative workflow combining separate product views. Names, people, code and values are sample data, not customer results.
01 - What it does

Keep the connector. Separate the connections.

A customer profile holds the connection details that differ between customers. Your team can reuse a connector without maintaining a fork for each customer environment.

One integration, customer-specific access.

Tenant Profiles give each customer its own encrypted credentials and endpoint for a Marketplace connector. A profile can use its own proxy agent or VPN, pin a vendor API version and maintain its own poll cursor and statistics. Configure and test each customer's connection before relying on its data. The catalog describes available connector actions; ingestion and execution still depend on the connector's capabilities, the services configured and the permissions of the workflow using it.

Onboarding another customer means configuring and testing its profile instead of forking the connector.

Microsoft Sentinel: profilesExample
Deployment
One connector
Customers
Northstar, Harbor Retail, Juniper
Credentials
Encrypted in the Vault, per profile
Endpoint
Separate per customer

Illustrative customers. Catalog entries are not counts of live connections.

Reuse the connector

Keep a shared connector definition with a separate profile for each customer.

Separate service credentials

Resolve the connection through the customer and profile settings.

02 - How it works in the product

Configure, test and then use the connection.

A catalog entry is the starting point. Set the customer connection and inspect the test result before depending on its ingestion or exposing actions to a workflow.

  1. 01
    Marketplace

    Choose the connector and review its supported capabilities.

  2. 02
    Tenant Profiles

    Set the customer endpoint and credentials, stored encrypted in the Vault.

  3. 03
    Test Connection

    Review the reported result; host reachability does not prove authentication.

  4. 04
    Ingestion

    Enable supported ingestion and field mappings, then configure permitted actions in the licensed workflow.

Developer Studio authoring in the Marketplace UI requires SecOps Platform and the relevant permissions.

03 - How it connects

Bring customer tools into the workflow.

Connector actions serve configured playbooks and agents. MCP Gateway can expose published capabilities to authenticated callers, with execution controlled by the gateway policy.

In the editions

The PortalIncluded

Marketplace shows Connectors, Webhooks and Ingestion.

Autonomous SOCIncluded

Use connectors with the licensed AI workflows.

SecOps PlatformIncluded

Developer Studio authoring also requires the relevant permissions.

04 - What it means for your service

Onboarding is a profile and a test, not a rebuild.

Reuse the connector definition, then validate the endpoint and credentials that belong to the customer. A tested profile gives the team a concrete connection to configure into its service.

Less connector duplication

Tenant Profiles replace a forked connector per customer.

A result to inspect

Test Connection reports what it verified so the operator can decide what remains.

Controls stay with execution

Permissions and approval rules still determine what a calling workflow can run.

Start with one customer

  1. 01
    Choose one customer tool

    Check its connector and supported ingestion capabilities.

  2. 02
    Create the customer profile

    Configure the endpoint and credentials, then inspect the test result.

  3. 03
    Try a permitted action

    Validate the action inside the licensed workflow you will use.

Explore Remote dedicated instances

Questions about Connector profiles.

1How is an integration deployed?

Choose the connector in Marketplace, configure the appropriate tenant or profile, and save its connection details and credentials. Review the reported connection-test result, then enable supported ingestion and field mappings. A reachable host does not always mean that credentials were verified; available tests and ingestion options depend on the connector.

2How are integration credentials stored?

Connector credentials are encrypted in Imperum’s server-side Vault. Tenant and profile settings determine which connection a workflow uses, so separate customers can configure separate credentials for the same tool. Viewing or changing stored secrets requires the relevant permissions; authorized administrators may manage credentials across their permitted tenant scope.

3Can different customers use different credentials for the same tool?

Yes. In multi-tenant environments, connector profiles hold tenant-specific endpoints and credentials. Named instance profiles also support separate deployments of the same connector within a tenant. Credentials are stored encrypted in the Vault; relevant permissions control access.

Have any other questions? Talk to our team

Bring a customer connection.
Build the workflow around it.

Review the supported connector, its customer profile and the actions your service needs.

Book a Demo

Film · 1:00

Imperum AI Fabric

One minute on the AI Fabric appliance: the agents, Agent Studio, routing, pools, Veil and token metering.