Connection is not authority.
A connection can supply evidence without granting action authority. Enterprise Hub resolves the principal, registered operation, account, target, and verification path separately.
CONNECTORS
Enterprise AI connectors for evidence and governed action.
Enterprise Hub includes Microsoft 365, Google Workspace, and Jira integration paths, with bounded Microsoft Dataverse / Power Platform support. Customers authorize supported sources; the Enterprise Hub team scopes deployment and onboarding. Connection, evidence availability, and action authority are checked separately.
Capability matrix
Connector capabilities remain independently governed.
Evidence access, events, actions, provider binding, and read-back are enabled separately for each connector and deployment.
| Connector group | Evidence | Events | Governed actions | Read-back | Status |
|---|---|---|---|---|---|
| Microsoft 365 | Supported where configured | Scoped by source | Operation-specific | Supported where bound | Deployment-specific |
| Google Workspace | Supported where configured | Scoped by source | Operation-specific | Supported where bound | Deployment-specific |
| Jira | Supported where configured | Scoped by source | Operation-specific | Supported where bound | Deployment-specific |
| Microsoft Dataverse / Power Platform | Scoped record evidence | Bounded freshness replay | Operation-specific | Bounded verification | Limited scope |
Swipe or scroll horizontally to inspect all capability columns.
Dataverse support currently covers bounded record-level evidence and workflow context. Broader permission hierarchies, change feeds, and write operations require separate validation. This is not a claim of support for every Power Platform app or flow.
Where supported, provider acceptance is followed by read-back before completion is recorded.
The supported connectors are already part of Enterprise Hub. Our team scopes deployment and onboarding around your approved sources, permissions, and review workflow.