AlignX runs inside your Microsoft environment, under your identity, your compliance controls and your data residency rules. No parallel platform to govern. No new silo to maintain.
What that gets you
Your tenant. Your controls. Your data.
Secure in your tenant
- Governed by Entra ID and your role-based access control
- No separate identity store, no new attack surface
- The solution, its tables and plug-ins are inspectable in your environment
- Every AlignX table ships with auditing switched on
Compliant by design
- Purview retention and audit controls extend to AlignX
- Every decision, control and piece of evidence stands up to audit
Data residency
- Australian regions for government and enterprise
- Residency is a configuration you control
- No AlignX-hosted copy of your data
Where each control lives
Every one of these is a console you already open.
Nothing here is an AlignX setting screen. Each control is the Microsoft one your team already operates, applied to the model.
Identity and access
AlignX operates inside your Microsoft tenant. Access is governed by Entra ID and role-based access control, so there is no separate identity store to manage and no new attack surface beside your estate.
Entra ID sign-inConditional access, MFA and device policy apply to AlignX as they do to everything else in the tenant.
Lives in Microsoft Entra admin center
Security rolesDataverse security roles and business units scope every table, row and field. Nothing is visible by default.
Lives in Power Platform admin center
Teams and delegationApproval authority is a record in the model, delegated with a start and end date, and audited.
Lives in AlignX, on the committee record
Audit on every tableEvery AlignX table ships with auditing on. Switching on auditing for the environment is the first install step. The History tab reads it back on the record.
Lives in Dataverse auditing
Compliance and protection
Purview retention and audit controls extend to AlignX. Compliance is part of how the platform runs rather than a bolt-on.
- Data residency
Your environment's region is the model's region. Australian residency is a configuration, not a request.
Lives in Power Platform admin center
Data and automation
Data lives in Dataverse, in your regions, and connectors and workflows run on Power Automate, configurable without bespoke integration development.
- Dataverse
Nearly 300 tables with real relationships. Yours to query, back up, export and extend with your own columns.
Lives in Your Dataverse environment 
Power AutomateConnectors to Jira, ServiceNow and the rest run as flows in your tenant, configurable without code.
Lives in Power Automate
Reporting and collaboration
Power BI reports across the whole living model, and governance workflows run in Teams and SharePoint, so adoption is faster and the learning curve is lower.
Power BIReport across the whole model from the semantic layer you already govern.
Lives in Power BI
SharePointEvidence and documents stay in SharePoint. The record links to them; it does not copy them.
Lives in SharePoint
What security teams ask
No. It is a Power Platform solution installed into your own Microsoft 365 tenant. There is no AlignX-hosted copy of your data.
See it running in your environment.
Twenty minutes, your tenant’s controls, one connected model.