The practical change is more consequential than another entitlement appearing in a Microsoft 365 account. Power BI Pro gives staff the paid per-user rights needed to publish reports to shared workspaces, share dashboards and reports with other licensed colleagues, and collaborate on material held outside a Premium capacity. Microsoft’s own Power BI documentation draws the line clearly: a free Power BI licence can create personal content, but it cannot normally publish to app workspaces or share content with others.
Loughborough says the A5 upgrade also brings enhanced security and compliance features, but its announcement does not identify which A5 capabilities it will configure, when they will be enabled, or whether policies will change alongside the licence assignment. Staff should therefore treat the confirmed immediate change as Power BI Pro access; the broader security and compliance benefit is real at the licence level but depends on the university’s implementation choices.
Power BI Pro changes who can publish institutional reports
For staff who have already built reports in Power BI Desktop or used the Power BI service under a free entitlement, the migration removes a common barrier: being able to create a report but being blocked when trying to publish it to a team workspace or distribute it to colleagues.
Microsoft describes Power BI Pro as a per-user licence for creating, reading, sharing and collaborating on Power BI content. In a standard shared-capacity workspace, a Pro licence is generally required for people who publish, edit or collaborate. A Power BI Pro user can create a workspace, upload a report from Power BI Desktop, update a dashboard, set up subscriptions, and share content with other Pro-licensed users, subject to the organisation’s permissions and tenant policies.
That means the new entitlement is most useful to staff working in operational reporting, departmental analytics, research administration, finance, student-support services, estates, HR, project delivery, and any area currently passing static spreadsheets or PDF exports between colleagues because interactive reports are difficult to distribute.
The licence does not automatically give every staff member access to every report, underlying dataset, workspace or Microsoft Fabric feature. Power BI permissions remain separate from licensing. A user still needs to be added to a workspace, granted access to an app or report, and given the appropriate role before they can view or edit content. A Pro licence solves the licensing requirement; it does not bypass data-access controls.
It also does not turn Power BI Pro into Power BI Premium Per User. Microsoft’s licensing documentation distinguishes Pro from Premium Per User, which includes additional premium capabilities and requires other participants in a Premium Per User workspace to hold the same higher-tier licence. Staff encountering a Premium Per User prompt after the migration should not assume the A5 assignment is incomplete.
Student and doctoral researcher accounts remain outside the rollout
The most important boundary in Loughborough’s notice is its exclusion: the licence migration does not apply to student or Doctoral Researcher accounts. The university has stated that staff currently assigned Microsoft 365 A3 will be upgraded automatically, but it has not announced a corresponding Power BI Pro entitlement for those two account categories.
That creates an immediate collaboration consideration for projects involving both staff and students. A staff member will be able to publish and share Pro content, but a student’s ability to consume or collaborate on it depends on where the report is hosted, what licence the student already holds, and how the workspace is configured.
In standard shared-capacity workspaces, recipients normally need Power BI Pro or Premium Per User licences to view shared content. Microsoft makes an exception for content hosted in qualifying Premium or Fabric capacity: users with free licences can consume content when it has been shared with them and the workspace meets the required capacity threshold. The capacity, rather than the staff member’s new A5 licence, is what makes that broader audience possible.
For Loughborough teams, the result is straightforward: do not design a staff-produced Power BI service report on the assumption that student collaborators will automatically be able to open it after 18 August. Check the intended audience before publishing, particularly for taught-course dashboards, departmental reporting that includes student representatives, and research projects where doctoral researchers are participants rather than employees.
The university’s announcement does not say whether it will create a separate process for student or doctoral researcher Power BI access, whether any existing exceptions will continue, or whether it operates Premium or Fabric capacity for reports intended for users without Pro licences. Those omissions matter more than the headline entitlement in mixed-audience projects.
A5 includes more than analytics, but the university has not detailed the configuration
Microsoft includes Power BI Pro in Microsoft 365 A5 for Education and also sells it separately or as an add-on for lower education plans. Loughborough is therefore using the broader A3-to-A5 move to extend Power BI capability rather than running a separate Power BI Pro assignment exercise for each member of staff.
A5 also carries higher-tier security, identity, information-protection and compliance entitlements than A3. But a licence catalogue is not the same thing as a live control. Features such as advanced security investigation, stronger identity protections, data-loss prevention, retention policies, sensitivity labelling and compliance workflows can require administrator configuration, policy design, user communication and, in some cases, staged deployment.
Loughborough’s notice says those enhanced capabilities will help protect staff and students, but it does not name the products or controls being introduced. It also does not say whether the A5 upgrade changes existing data-retention rules, OneDrive limits, SharePoint sharing policies, Teams controls, or Microsoft Defender protections. Staff should not infer a new mandatory workflow until IT Services publishes one.
The storage-reduction guidance included in the announcement is a meaningful signal, however. Giving a much larger group the right to create and distribute reports can increase the number of workspaces, exported files, copied datasets, Teams attachments and SharePoint-hosted source documents. The university is explicitly asking staff to review Microsoft 365 content and keep data only where there is a legitimate business need.
That should be read as an operating requirement, rather than a suggestion to tidy up when convenient. Power BI reports often contain data extracts, refresh connections, exported spreadsheets and supporting documentation across multiple Microsoft 365 locations. Deleting a report without understanding its underlying semantic model, refresh schedule or linked source files can break an established process; retaining everything indefinitely creates a different compliance and storage problem.
Publishing access raises the value of data governance
The new licensing model expands who can make an interactive report available to a group. It does not expand what staff are permitted to disclose within those reports.
Before publishing a report, staff should establish who owns the underlying data, whether the intended audience is correct, whether the report includes personal, confidential or commercially sensitive information, and whether row-level access controls are needed. A report that looks harmless in a private workspace can reveal more than intended when shared across a department, particularly where filters, drill-through pages, downloadable data or linked semantic models expose underlying records.
Power BI workspace roles also deserve attention. A Viewer can read content; Contributor, Member and Admin roles can carry progressively greater editing and management rights. Microsoft notes that the collaboration and publishing functions associated with those roles require paid licensing in the usual shared-workspace model, but the role still determines what a Pro-licensed employee can do once admitted.
The sensible approach for a new departmental workspace is to assign the smallest group of people who need build or publishing rights, use Viewer access for report consumers where appropriate, and review membership when projects end or staff change roles. Licensing a whole staff population does not mean a whole staff population should receive Contributor or Member permissions in every workspace.
Staff should also avoid treating Power BI Pro as a licence to upload unvetted local files into a shared reporting environment. The service is designed to connect, model, refresh and redistribute data. Once a report is shared, a small spreadsheet can become a recurring organisational data product, with access, retention, accuracy and ownership obligations that outlast the original request.
What staff should do between 18 and 31 August
Loughborough says no action is required for the licence migration itself. Staff assigned A3 should receive the A5 entitlement automatically during the 18–31 August window, and the university advises affected users who encounter a problem to sign out of Microsoft 365 and sign in again.
After the change, users can check their active subscription in their Microsoft 365 account details. The university says the relevant label should change from “Microsoft 365 A3 for faculty” to “Microsoft 365 A5 for faculty.” That verifies the suite entitlement, though Power BI access can still depend on the service being enabled for the account and on the user signing in to the correct university tenant.
For teams planning a Power BI rollout, the more useful first step is to audit the audience and workspace before building anything new. Establish whether all report authors and recipients are staff, whether students or doctoral researchers need access, whether the report will sit in shared or Premium capacity, and which group is responsible for maintaining the data. Those decisions determine whether Power BI Pro will solve the actual publishing problem or merely reveal an unresolved permissions and capacity issue.
By the end of August, staff A3 accounts should have become A5 accounts automatically. The immediate result is that Loughborough employees who previously lacked a paid Power BI entitlement can publish and collaborate within the institution’s Power BI environment; the remaining constraint will be whether each workspace, recipient group and dataset has been set up for the audience it is meant to serve.