Feedback:
When authoring DAX in Power BI Desktop, the Copilot dialog box is anchored at the bottom of the DAX editor and overlaps the IntelliSense dropdown. This obscures function suggestions and makes it difficult or impossible to see and select them without inserting multiple blank lines into the code.
Suggestion:
Allow the Copilot dialog to be repositioned (e.g., docked as a side pane) or made movable/resizable so users can place it where it does not interfere with IntelliSense or code authoring workflows.
1 Comment
- roywils1New MemberI would go further and this and suggest that there needs to be Default Behaviour or optional arguments to suppress the copilot pane The Copilot button and capability are valuable and should remain available. What’s missing is admin and user control over the default behaviour of the Copilot pane. Today, the pane appears by default in report view and does not respect organisational or user preference, which is disruptive in many report consumption scenarios. Requested capability: Provide admin and user‑level settings (tenant, capacity, or user) to suppress the Copilot pane from opening by default. Ideally, persist the user’s choice (open vs closed) across sessions This is a governance and experience control issue, not an anti‑AI request. Organisations need the ability to balance powerful authoring features with clean, focused report consumption experiences.
Recent ideas
Allow External OneLake Data Shares to Be Accepted into Multiple Fabric Item Types
Fabric External Data Sharing provides an excellent zero-copy mechanism for sharing OneLake data across tenants. However, the receiving tenant currently has to accept the share into a Lakehouse. I w...Mourak10 hours agoNew MemberNew5Views0likes0CommentsAllow OneLake Shortcut Authentication Mode to Be Changed In Place
OneLake shortcuts support passthrough and delegated authentication, but changing the authentication model currently requires deleting and recreating the shortcut. I would like shortcut authenticatio...Mourak10 hours agoNew MemberNew7Views0likes0CommentsTenant-Wide OneLake Shortcut Lineage and Impact Analysis
This is grounded in a documented limitation: shortcut lineage is currently workspace-scoped, and Microsoft specifically says lineage for shortcuts to warehouses and semantic models isn't currently av...Mourak10 hours agoNew MemberNew12Views0likes1CommentAdd an End-to-End Production Reference Architecture for Microsoft Fabric Real-Time Intelligence
I would like to see a complete end-to-end Microsoft Fabric Real-Time Intelligence reference architecture that demonstrates how the individual RTI capabilities work together in a production-oriented s...Mourak10 hours agoNew MemberNew5Views0likes0CommentsImprove 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, destinat...Mourak10 hours agoNew MemberNew3Views0likes0Comments