FabOps Product Attestation

Currently implemented

Microsoft Fabric service and API integration

FabOps uses qualified Microsoft Fabric services and APIs for the released product scope. Permissions and telemetry paths are confirmed during technical qualification.

Architecture dependent

Identity and access

Microsoft Entra configuration, roles, conditional-access behaviour and customer approval requirements depend on the selected architecture and tenant policy.

Architecture dependent

Data boundary and residency

The applicable data boundary, processing location and residency position are documented for the customer configuration. No universal tenant-only assertion is made.

Customer-configurable

Lineage and sensitivity-label coverage

Coverage depends on enabled Microsoft capabilities, permissions, item types and customer configuration. Full lineage and enforced-label coverage are not universally attested.

Not included as a universal claim

Private connectivity

Private connectivity requirements are assessed during solution design. Availability must be evidenced for the proposed deployment before commitment.

Contract specific

Availability, support and incident response

Service levels, support windows, escalation targets and remedies are defined only in the applicable executed agreement.

Evidence on request

Business continuity and disaster recovery

Current continuity, backup, recovery and testing evidence is supplied through due diligence. No universal RPO, RTO, geo-redundancy or automated-failover promise is published here.

Evidence on request

Accessibility and regulatory compliance

Accessibility and data-protection positions are assessed against the current released product, customer role and contract. FabOps does not publish an unqualified compliance guarantee.

Not included

Planned capabilities

Roadmap items are not represented as released functionality and do not form part of this attestation.