Built inside Microsoft 365
Native. Not integrated.
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.
In one sentence
AlignX is built on Microsoft Power Platform and runs inside the customer's own Microsoft 365 tenant, on Dataverse, so the tenant's identity, security, compliance and data residency apply to it automatically.
Runs on your Microsoft platform
The Microsoft foundation
Native, not integrated.
AlignX is built on the Microsoft platform, not bolted beside it. Because it is Microsoft-native, it inherits the identity, compliance and residency controls you already run, which removes the procurement friction and integration risk that stall enterprise decisions.
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 tableDataverse auditing records who changed what and when. The History tab reads it back on the record.
Lives in Dataverse auditingCompliance and protection
Purview retention and audit controls extend to AlignX, and Defender and Sentinel watch it like the rest of your estate. Compliance is part of how the platform runs rather than a bolt-on.
PurviewSensitivity labels, retention and DLP policies extend to the Dataverse tables that hold the model.
Lives in Microsoft PurviewData residencyYour environment’s region is the model’s region. Australian residency is a configuration, not a request.
Lives in Power Platform admin center
Defender and SentinelSign-in and activity signals land in the same monitoring you use for the rest of the tenant.
Lives in Microsoft Defender and Sentinel
IRAP and ISM alignmentDesigned for the controls government and higher education already assess Power Platform against.
Lives in your existing Microsoft 365 assessmentData and automation
Data lives in Dataverse, in your regions, and connectors and workflows run on Power Automate, configurable without bespoke integration development.
Dataverse131 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 AutomateReporting 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 SharePointIn practice
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
- Dataverse auditing on from day one
Compliant by design
- Purview retention and audit controls extend to AlignX
- Sensitivity labels and DLP apply to the model’s tables
- Designed for IRAP and ISM alignment
- 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
- Deleting the solution leaves your data in your tenant
Questions
What security teams ask.
Is AlignX a SaaS product hosted by you?
No. It is a Power Platform solution installed into your own Microsoft 365 tenant. There is no AlignX-hosted copy of your data.
Which region is the data in?
Whichever region your Dataverse environment is in. For Australian government and higher education that is Australia, set once at the environment level.
Do we need new licences?
AlignX runs on Power Platform licensing you may already hold. We confirm what applies to your tenant before you commit.
Can our security team review it?
Yes. The solution, its tables and its plug-ins are inspectable in your environment, and Dataverse auditing records every change from day one.
Does it work with Teams?
Yes. Approvals and records open in Teams, and the model links to the SharePoint sites and channels your work already lives in.
See it running in your environment.
A twenty-minute walk through the tenant, with your security lead in the room if you like.