Fabric Graph should support controlled schema evolution as enterprise business models change over time.
Graph models are rarely static. Organizations need to add new node types, properties, relationships, keys, and source mappings as new business requirements emerge. These changes should be manageable without forcing teams to recreate the graph model and reconnect downstream dependencies.
Fabric Graph should support compatible schema changes directly on an existing graph model while preserving the graph identity, security configuration, queries, lineage, and downstream references.
Requested capabilities include:
Add or modify node properties
Add new node and relationship types
Add or update source mappings
Safely modify keys and relationship definitions
Schema version history
Compare and diff between graph schema versions
Breaking-change detection
Dependency and impact analysis before deployment
Migration preview
Rollback to a previous schema version
CI/CD support for promoting graph schema changes across development, test, and production environments
For potentially breaking changes, Fabric should identify the affected queries, Digital Twin models, Fabric IQ ontologies, dashboards, Data Agents, and other downstream consumers before the change is applied.
For example, an organization may initially model Asset, Site, and Work Order entities and later introduce Manufacturer, Sensor, Maintenance Contract, and additional relationships. These changes should be evolutionary rather than requiring a graph redesign or recreation.
Enterprise graph models will continuously evolve. Fabric should provide a governed schema-evolution experience that allows organizations to extend those models safely while protecting existing applications and dependencies.
