Improve CI/CD consistency for Microsoft Fabric Real-Time Intelligence Eventstreams
Microsoft Fabric Real-Time Intelligence has made strong progress with Git integration and deployment pipelines, but lifecycle management can still be inconsistent across Eventstream sources, destinations, connections, and deployment scenarios.
I would like to see more consistent CI/CD support across Real-Time Intelligence artifacts, including automated environment-specific connection rebinding, easier promotion from development to test and production, deployment validation before activation, and clearer diagnostics when an RTI artifact cannot be promoted successfully.
For enterprise implementations, it would also be valuable to reduce the amount of manual reconfiguration required after deployment.
Improving these capabilities would make Real-Time Intelligence solutions easier to operationalize, govern, automate, and teach as production-ready architectures rather than solutions that require manual configuration between environments.
Recent ideas
Prevent Overwriting Subscription Parameters When Adding Report Parameters
Summary: Currently, when a paginated report is republished with a new parameter, making any subscription changes (e.g., adding or editing one) overwrites all existing subscriptions' parameter values...andrew41 hour agoNew MemberNew825Views8likes2CommentsAllow Mirror Database to use Variable Library, not just Deployment Rules
Currently, the source connection for Mirrored DBs is managed through Deployment Rules in data pipelines. There is no way to use Variable Libraries with Mirrored DB, like you can do in CopyJob or Dat...hedeencharles2 hours agoAdvocate INew428Views11likes1CommentAzure Maps Power BI - Support Dynamic Geometry Data from Dataset Columns
Problem The Azure Maps Reference Layer currently relies on file uploads or URL-based geometry sources (GeoJSON, KML, etc.). In our enterprise use case, geometry data is private, changes daily, and m...jurner4 hours agoNew MemberNew24Views1like0Comments