Integrations

What it connects to.

AlignX does not replace your work, service, risk or analytics platforms. It sits above them as the shared decision context, draws their objects into one model, and sends lineage back. Microsoft services need no connector at all.

Microsoft-native

Six that need no connector.

AlignX runs inside your tenant, so these are not integrations. They are the same services, reading and writing the same model.

  • Entra ID

    Sign-in, groups and conditional access, as they already apply.

  • Teams

    Approvals and records open where the conversation is.

  • SharePoint

    Evidence and documents stay put; the record links to them.

  • Power BI

    Report across all 131 tables from the semantic layer.

  • Power Automate

    The engine every connector below runs on.

  • Dataverse

    The model itself. Query, export and extend it as your own.

Connectors

Connected to the systems you already run.

Connectors run on Power Automate in your tenant, configurable without bespoke integration development. Each maps their objects to ours, both ways.

Work management

AlignX draws execution context from your work management tools and returns decision traceability, so every investment is connected to the intent that justified it.

  • Jira

    Epics, issues and sprints against initiatives and milestones.

  • Planview

    Portfolio and resource plans against the plan of record.

  • Asana

    Projects and tasks against requirements and benefits.

  • Monday.com

    Boards and items against initiatives.

Work management

EpicStory / IssueSprintTimesheet

AlignX

InitiativeRequirementMilestoneBenefit

InProgress, effort, dates

OutStrategic intent, decision lineage, benefit linkage

CMDB and ITSM

Bidirectional data flow between AlignX and your CMDB and ITSM platforms. Architectural components are connected to the requirements that drove them, the investments that funded them and the governance decisions that authorised them.

  • ServiceNow CMDB

    CIs, services and changes against the application estate.

  • Jira Service Management

    Incidents and changes against components and risks.

CMDB / ITSM

Configuration itemServiceIncidentChange request

AlignX

ApplicationIT componentArchitecture decisionRisk

InCI inventory, service map, change records

OutArchitectural context, ownership, lifecycle stage

Risk and compliance

Risk conditions and compliance obligations connect to the strategic and architectural decisions that create or mitigate them. Where Purview provides information governance, dedicated GRC platforms extend the picture.

  • OneTrust

    Risks, controls and findings against the decision record.

  • ServiceNow GRC

    Policies, controls and issues against obligations.

  • Archer

    Register entries against risks and controls.

GRC platform

Risk register entryControlPolicyIssue / finding

AlignX

RiskControlObligationDecision

InRisk ratings, control tests, findings

OutDecision linkage, capability and investment context

Analytics

Power BI is the native reporting layer. Where the estate runs more than one platform, measures and datasets connect to the metrics and objectives they inform.

  • Tableau

    Dashboards and measures against metrics.

  • Snowflake

    Tables and semantic models against data objects.

  • Databricks

    Datasets against data objects and metrics.

Analytics platform

Dataset / tableMeasureDashboardSemantic model

AlignX

MetricObjectiveData objectReport

InActuals, measures, refresh state

OutDecision context, model semantics, ownership

Connect the systems you already run.

Bring the tool you most want connected. We will show the exchange against your own objects.