Auto attendant and Call queue historical reports - Version 3.2

[SeanMoody]

So from my understanding of how this report works, it uses OAuth2 authentication which is based off of my credentials.

My credentials have been given access to Different AutoAttendant and Calling Queues.

If I open it up in the desktop then it shows me the proper information.

If I put it on the power bi service then I also have to use my credentials in the Semantic Model Refresh.  This will show me the data for the teams access I've been provided as well.

However, is there not a way to have this report pass through the users credential so that everyone sees there own teams assignments and not the assignment of the credentials used to refresh the data?

Or is the intent of the report that you have one account that is assigned everything and the user then filters the report based on the Call Queue and Auto Attendent pull down lists.

Thanks for your assistance.

Sean

[v-pnaroju-msft]

Thankyou, @Ritaf1983, for your response.

Hi SeanMoody,

We appreciate your inquiry submitted through the Microsoft Fabric Community Forum.

Based on my understanding, the Auto Attendant and Call Queue Historical Reports utilize OAuth2-based authentication with a pre-authorized account (usually an administrator or service principal) to retrieve data via Microsoft Graph and CQD APIs. In the Power BI Service, the dataset refresh always uses this single account; the viewer’s credentials are not passed through. This behavior is by design and is not currently supported. Therefore, all users see data based on the refresh account’s access privileges, not according to their individual Teams assignments.

Please follow the workaround steps outlined below, which may help resolve the issue:

1. To ensure that each user only views data for their respective Auto Attendants and Call Queues, you can implement Row-Level Security (RLS) in Power BI:
   1. Create a user-to-queue mapping table (for example, email → assigned queue names).
   2. Define RLS rules using the USERNAME() or USERPRINCIPALNAME() functions in Power BI.
   3. This will filter the data based on the identity of the logged-in user, irrespective of the refresh account credentials.

Additionally, kindly refer to the following links for more information:
Auto attendant and Call queue historical reports - Microsoft Teams | Microsoft Learn
Plan for Auto attendant and Call queue authorized users - Microsoft Teams | Microsoft Learn

If you find our response helpful, please mark it as the accepted solution and provide kudos. This will assist other community members who may have similar queries. Should you have any further questions, please feel free to contact the Microsoft Fabric Community.

Thank you.

[SeanMoody]

Thanks for the explaination.

So if I create a user-to-queue mapping table (for example, email → assigned queue names) then I have 2 additional questions:

1) How do I tie this mapping table into the many tables within this report so it filters the multiple reports ?

2) Am I correct in assuming that this table will need to be kept up to date with every change that is made on the teams queue administrative side?

Thanks

Sean

[Ritaf1983]

Hi @SeanMoody 

In Power BI, the process of refreshing the data and the way users access or view the data are handled separately.

Data refresh is managed through the on-premises data gateway (if needed) and is configured with organizational-level credentials. The refresh runs automatically on a schedule, or manually when triggered, and always uses the credentials defined in the dataset settings – not the credentials of the user viewing the report.

Access to data within the report is controlled using Power BI's internal Row-Level Security (RLS). With RLS, each user sees only the data they're authorized to view, based on the security rules you've defined.

So even though one account is used for data refresh, each user can still see only their relevant information if RLS is implemented correctly

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly