Auto attendant and Call queue historical reports - Version 3.2

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.