Integrations

Works with the tools you already run.

19 integrations across PSA, RMM, documentation, Microsoft, identity and developer tools, each with what ConfigCheckup sends, what it reads and the plan it comes with.

PSA

Tickets for what needs doing, closed when it is done.

  • HaloPSA

    ConfigCheckup sends
    • A ticket for each failing check at or above the severity you choose, closed with a note when it passes
    • Tickets for security alerts and drift, as you choose
    • Tickets for admin changes that succeed, as you choose (with Automate)
    • Scheduled tenant reports, each as a ticket with the report’s link
    • Time logged on the ticket for admin changes, if you choose (with Automate)
    ConfigCheckup reads
    • Your companies, to map each tenant to one
    • Each open ticket’s status, after every assessment
    • Ticket updates as they happen, and new leaver tickets, which draft an offboarding for someone to check (webhook, beta)

    On every plan

    Set up HaloPSA 

  • ConnectWise Manage

    ConfigCheckup sends
    • A ticket for each failing check at or above the severity you choose, closed with a note when it passes
    • Tickets for security alerts and drift, as you choose
    • Tickets for admin changes that succeed, as you choose (with Automate)
    • Scheduled tenant reports, each as a ticket with the report’s link
    • Time entries for admin changes, if you choose (with Automate)
    ConfigCheckup reads
    • Your companies, to map each tenant to one
    • Each open ticket’s status, after every assessment
  • Autotask

    ConfigCheckup sends
    • A ticket for each failing check at or above the severity you choose, closed with a note when it passes
    • Tickets for security alerts and drift, as you choose
    • Tickets for admin changes that succeed, as you choose (with Automate)
    • Scheduled tenant reports, each as a ticket with the report’s link
    • Time entries for admin changes, once you set the resource and role IDs (with Automate)
    ConfigCheckup reads
    • Your companies, to map each tenant to one
    • Each open ticket’s status, after every assessment
  • NinjaOne

    ConfigCheckup sends
    • A ticket for each failing check at or above the severity you choose, closed with a note when it passes
    • Tickets for security alerts and drift, as you choose
    • Tickets for admin changes that succeed, as you choose (with Automate)
    • Scheduled tenant reports, each as a ticket with the report’s link
    • Time logged on the ticket for admin changes, if you choose (with Automate)
    ConfigCheckup reads
    • Your companies, to map each tenant to one
    • Each open ticket’s status, after every assessment
  • Kaseya BMS

    Beta
    ConfigCheckup sends
    • A ticket for each failing check at or above the severity you choose, closed with a note when it passes
    • Tickets for security alerts and drift, as you choose
    • Tickets for admin changes that succeed, as you choose (with Automate)
    • Scheduled tenant reports, each as a ticket with the report’s link
    ConfigCheckup reads
    • Your companies, to map each tenant to one
    • Each open ticket’s status, after every assessment

    On every plan

    Beta: tested against API documentation, not a live account.

    Set up Kaseya BMS 

RMM

Devices and alerts, read only, matched with what Microsoft 365 knows.

  • Datto RMM

    Beta
    ConfigCheckup sends

    Nothing: it only reads.

    ConfigCheckup reads
    • Devices and open alerts for the site each tenant is mapped to
    • Compared with Intune and Entra: devices with an agent but not enrolled, and enrolled devices with no agent

    On every plan

    Beta: tested against API documentation, not a live account.

    Set up an RMM 

  • N-able N-central

    Beta
    ConfigCheckup sends

    Nothing: it only reads.

    ConfigCheckup reads
    • Devices and open alerts for the customer each tenant is mapped to
    • Compared with Intune and Entra: devices with an agent but not enrolled, and enrolled devices with no agent

    On every plan

    Beta: tested against API documentation, not a live account.

    Set up an RMM 

  • NinjaOne

    Beta
    ConfigCheckup sends

    Nothing: it only reads.

    ConfigCheckup reads
    • Devices and open alerts for the organisation each tenant is mapped to
    • Compared with Intune and Entra: devices with an agent but not enrolled, and enrolled devices with no agent

    On every plan

    Beta: tested against API documentation, not a live account.

    Set up an RMM 

Documentation

An as-built page for each tenant, updated every day.

  • IT Glue

    Beta
    ConfigCheckup sends
    • A “ConfigCheckup as-built” flexible asset for each mapped organisation, updated every day: the score, open critical and high findings, Conditional Access policies, the GDAP relationship, licences and devices
    ConfigCheckup reads
    • Your organisations, to map each tenant to one

    On every plan

    Beta: tested against API documentation, not a live account.

    Set up IT Glue 

  • Hudu

    Beta
    ConfigCheckup sends
    • A “ConfigCheckup as-built” article for each mapped company, updated every day: the score, open critical and high findings, Conditional Access policies, the GDAP relationship, licences and devices
    ConfigCheckup reads
    • Your companies, to map each tenant to one
    • Stored credentials as details only, never the passwords, when the key has password access

    On every plan

    Beta: tested against API documentation, not a live account.

    Set up Hudu 

Microsoft

The tenants themselves, your partner account, and the Microsoft tools your team already uses.

  • Microsoft 365

    Through Microsoft Graph, with admin consent

    ConfigCheckup sends
    • Only the changes a person approves, and only once automation is turned on for the tenant (with Automate)
    ConfigCheckup reads
    • Each tenant’s settings, sign-ins and audit log, devices and licences, for the checks, alerts and reports
  • Partner Center

    Your CSP and GDAP customers

    ConfigCheckup sends
    • Seat changes, each as an approved change (with Automate)
    ConfigCheckup reads
    • Your customers, to connect their tenants in bulk through GDAP
    • Each tenant’s CSP subscriptions, beside the licences in use
  • Microsoft Sentinel

    Beta
    ConfigCheckup sends
    • The audit log as it happens and, if you choose, alerts and the checks that start or stop failing
    ConfigCheckup reads

    Nothing.

    With Automate

    Beta: tested against API documentation, not a live account.

    Stream to Sentinel 

  • Power Automate

    A custom connector, also for Power Apps and Logic Apps

    ConfigCheckup sends
    • What an API key can read, as actions in your flows (on every plan)
    ConfigCheckup reads
    • Assessments to queue and changes to draft for approval (with Automate)

Identity

Your team signs in with the identity provider you already run.

  • Single sign-on

    Okta, Google Workspace, Auth0, JumpCloud, Microsoft Entra ID or another OpenID Connect provider

    ConfigCheckup sends

    Nothing: it only reads.

    ConfigCheckup reads
    • Sign-ins from the email domains you have proved are yours
    • Group membership, to give each person their role
  • SCIM 2.0 provisioning

    From the same identity provider

    ConfigCheckup sends

    Nothing: it only reads.

    ConfigCheckup reads
    • Members added, changed and suspended, and the groups that give them roles

Developer

For your own dashboards, scripts and log collectors.

  • REST API

    OpenAPI 3.1

    ConfigCheckup sends
    • Tenants, assessments, findings, reports, changes, baselines, alerts, licences, devices and the audit log (on every plan)
    ConfigCheckup reads
    • Assessments to queue and changes to draft for a person to approve (with Automate)

    On every plan

    API reference 

  • Webhooks

    ConfigCheckup sends
    • Signed events, 17 kinds to choose from, such as an assessment finishing, a tenant drifting or a change being approved
    ConfigCheckup reads

    Nothing.

    With Automate

    Add a webhook 

  • SIEM: HTTPS endpoint

    Beta

    Splunk HEC, a Logstash http input, a syslog-over-HTTPS listener or similar

    ConfigCheckup sends
    • The audit log as it happens and, if you choose, alerts and the checks that start or stop failing, as JSON
    ConfigCheckup reads

    Nothing.

    With Automate

    Beta: sends JSON as most log collectors take it. Tell us if yours needs something else.

    Stream to your SIEM 

What a listing means

Each listing is an integration ConfigCheckup built itself, against the tool’s published API or an open standard. It is not a partnership with the vendor, and not an endorsement by them. Product names belong to their owners.

Beta marks an integration not yet proven in everyday use, most of them built from the vendor’s API documentation rather than tried against a live account; each says why in its own words.

ConfigCheckup

Connect your first tenant, then your PSA.

14 days of daily monitoring and alerts, every finding with its fix guide, and reports on up to 3 tenants, from your first connected tenant. No card. Then choose the plan that fits.