Agile is an approach, so can be adopted by all kinds of teams. To do this you need to favour responding to change, customer collaboration, interaction and the other values of agile.
Adopting the Scrum framework is a bit more involved, but is readily achievable within a data support team.
You can think of the reports the team generates as the product. The reports have value and so can be prioritised.
It would make sense to have a single Product Owner who is the judge of report value and who will own and maintain your product backlog. The people who make the requests act as the stakeholders rather than multiple Product Owners.
The advantage of this approach is that the Product Owner becomes a single voice of requirements in to the team. Their job is to listen carefully to the stakeholders (report owners) and to distil their requests down in to a series of user stories.
An example of a user story on your product backlog might be something like:
As a sales director I want to see the monthly sales figures broken down by district so that I can see which areas need help
This requirement is translated in to an update of the sales report.
Once you have several such user stories representing the requests from report owners then you have your product backlog.