Article content
In briefShow moreShow lessPower BI made automatic mobile layout generally available and expanded data questions in read mode.
- Power BI made automatic mobile layout generally available and expanded data questions in read mode.
- Copilot Pages, Analyst and the Project Manager agent created more ways to share and develop work.
- Report teams should test comprehension and decision quality on mobile, not merely whether visuals fit.
Analysis reached a smaller screen
The 22 April Power BI update made automatic mobile-layout creation generally available. It also expanded ad hoc Copilot calculations to read mode and continued TMDL and Direct Lake work. Automatic placement could save design effort, but could not decide which measures a leader needed first or whether a complex chart was understandable on a phone.
The collaboration surface expanded
The next day’s Microsoft 365 Copilot update highlighted expanded Pages, Analyst, Researcher and a Project Manager agent in Planner. Information could move between conversation, analysis and follow-up with fewer manual steps. The risk was multiple machine-generated summaries carrying different wording and status. Teams needed one visible source for approved measures and decisions.
Early research showed a mixed picture
A field study published on 15 April examined early impacts of Microsoft 365 Copilot in real work. Results indicated time savings for some tasks alongside variation in use and effect. This supported task-specific experiments: report summaries, meeting preparation and status drafts should be evaluated separately, including quality and rework as well as minutes saved.
Mobile use changed the decision setting
A phone report was often read between meetings or at a customer site. Context, deviation and recommended action then mattered more than full detail. A mobile layout should show reporting period, definition and refresh time with a clear route to evidence. Copilot summaries needed generated-content labeling and should not conceal uncertainty or missing data.
Control before scaling
The design test should also examine accessibility and language. Automatic mobile layout could change reading order, shorten labels and move detail behind touch interactions. Participants should therefore test screen readers, large text and both Norwegian and English interfaces where relevant. Questions should ask what the measure meant, which deviation required action and where evidence could be found. If users reached the correct answer only after opening the desktop report, the mobile view served as an alert rather than standalone decision evidence.
Test with real decisions
Choose three recurring decisions and build a controlled mobile view for them. Let half the participants use the current report and the rest use the mobile view with Copilot support. Measure correct understanding, time, clarification needs and alignment between decision and evidence. Capture edits made to the summary because they reveal where the model, language or instruction needs improvement.
Sources
Microsoft Power BI: Power BI April 2025 Feature Summary, 2025-04-22
Microsoft 365 Copilot: What’s New in Microsoft 365 Copilot | April 2025, 2025-04-23
Dillon et al. (arXiv): Early Impacts of M365 Copilot, 2025-04-15
Asana: Anatomy of Work Global Index 2023, 2023-03-08
Join the discussion
Which experience from your own organisation is most relevant to this story? Share what you learned.








