Teams Calls data source for All, Missed, Incoming, Outgoing, Voicemail
The requirement is for all users Team, Calls, with filters History for
Type of call = All, Missed, Incoming, Outgoing, Voicemail.
the caller name, number, date & time, call duration.
For Voicemail, donot need the actual voice message. again require the caller name, number, date & time, call duration.
data source to be loaded and available in powerbi report. data source to be greater than 30days.
For example Executives and Managers are requesting to see Teams Calls yearly data, and by month, by week
I have looked at the following and
The Microsoft Power Bi report template, Teams Auto Attendant & Call Queue Historical Reports V3.2.0
https://learn.microsoft.com/en-us/microsoftteams/aa-cq-cqd-historical-reports
does not provide this data.
Microsoft Graph API - a function does not exist to obtain Call data and the required properties. Chats, or missed Chats are available, Calls not available.
The requirements are
in Teams, Calls all data displayed here and for all users in the tenant to be available for reporting. see screenshot
Data to be available and search by user. Ideally the Team/Department
Data to be available for reporting. Timelines year, month, week, day
Purpose
Teams Voice & AutoAttendant calls are setup.
Executives would like reports on the Call journey and impacts to Service Delivery
Executives would like to see:
calls answered and dealt by receptionists.
receptionists transfer calls to user/department.
calls transferred to the user (department) and the Type of call. eg Missed Call, Incoming, Outgoing, Voicemail.
If calls go to Voicemail, the date & time. For example, are people in meetings at this time.
If calls are transferred to user/department and call is then transferred again/ multiple times. The result is the client has to repeat/explain again their query. For example, is this a training issue for receptionists to correctly triage the call and call to be transferred to the right department the 1st time.
Call number & duration of call. The call journey from call start to call end
Recent ideas
Allow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara10 minutes agoNew MemberNew3Views0likes0CommentsSupport Synonyms in Fabric Warehouse
Microsoft SQL Server has a very powerful feature by the way of "synonyms." It allows users and DBAs to do all sorts of powerful magic such as rewiring objects under the hood (e.g. run the code agains...matthias-bi3 hours agoRegular VisitorNew1.3KViews18likes2CommentsExpose Refresh Warnings and Informational Messages via Notifications and API
When a Power BI semantic model refresh completes successfully, the status shows Completed, even when the refresh details contain warnings or informational messages that require attention. Please pro...Jashwanth_K5 hours agoMicrosoft EmployeeNew21Views6likes0CommentsInvoke Pipeline Task - Workspace Identity Authentication
Currently, the Fabric Data Factory Invoke Pipeline task uses the user's credentials who saved the pipeline to then authenticate to the Azure Data Factory to execute the ADF pipeline. When that user'...dzebrowitz10 hours agoAdvocate IPlanned1.8KViews61likes5CommentsFabric Pipeline should run as workspace identity
Currently, Microsoft Fabric pipelines run under the identity of the last user who modified them, which can cause disruptions when tenant administrators make changes to security policies, such as enab...pellitteris10 hours agoAdvocate IINew1.4KViews27likes3Comments