The idea of monitoring Dynamics 365 or Model Driven Applications is not a new concept. Understanding where services are failing, users are interacting with the platform, where form and business processes could be tuned for performance are key drivers for most if not all businesses, from small companies to enterprises. Luckily, the Power Platform provides many tools to help audit and monitor business and operational events.

This article will cover locating and downloading environment analytics using the Common Data Service for Analytics. Questions regarding capacity and all up usage can be answered here. For operational events the Release Wave 1 2020 for Power Apps will be explored for feature announcement to allow for both manual and automated gathering and alerting.


Organization Insights / CDS for Analytics


A Common Data Service specific feature is the former Organization Insights or now called the Common Data Service for Analytics or CDS-A. Its key to point out here that Organization Insights will no longer be supported in future releases per this document. Some of the key analytics compiled include active user usage and operations performed, customizations used, storage consumed and failed workflows and API calls.

CDS for Analytics in the Power Platform Admin Center


Analytics for the Common Data Service can be observed within the Power Platform Admin Center. To navigate to these analytics, simply expand the Analytics area of the Power Platform Admin Center and choose "Common Data Service".

Who can access this data?


Its key here to point out that access to this data is limited based on user access to the CDS environment in combination with their Office 365 role. As shown in this article there consist of various admin roles within Office 365 that will scope to specific reports. Environment Admin will scope to environments the admin has access to while other admin roles will expose every environment.

The Common Data Service for Analytics accessibility is somewhat different than the other analytics features and I want to point out what I've seen. One common ask I get is how to allow analysts the ability to view this data without obtaining too much abilities that an Environment Admin would have. I've seen that giving the Power Platform Admin role in Office 365 will set Environment Admin in each of the Dynamics 365 environments within the tenant. Removing this role from the user in the environments will restrict them from performing activities within the environment. However they will be able to perform administration activities such as backups or DELETE environments.

Navigating the Portal


With the appropriate permissions, an admin will land on the Home dashboard for Common Data Service for Analytics. Below is an overview of each of the dashboards available currently.

As described in the article, each of these metrics is updated every 24 hours. I have seen this data presented within the same working day, so while the documentation details this you may see metrics sooner.

The Dashboards


The Home dashboard includes the ability to filter to specific environments and time range to help focus on finding out more about a particular question. Active Users, API Calls and Pass Rate are shown as well as top Plug-Ins by Failure.

The Active Users dashboard is helpful to see which users are most active during what timeframe and what operations are being performed by the most active users. Total operations (Create, Retrieve and RetrieveMultiple, Update and Delete) per day and total page requests are shown with line charts.

The Usage report is extremely helpful for insight into user environment access based on the filter set. This report can help answer questions such as Who was logged in a given time window and when users are most active in the environment.

The Mode of Access dashboard can help admins better understand user client usage (OS, device, browser type) and active users by business units and security roles.

The charts in the Mode of Access report can help answer questions about recently introduced browsers or devices users are using to interact with the platform. If we see a rise in errors we begin to examine if client usage plays a part. The Active users by security role chart can help identify roles during a time frame. If the particular organization has multiple apps with access controlled by security roles, this chart could prove helpful.

The Entity Usage dashboard displays the most active entities by operation, split by out of the box (OOB) and custom entities.

The most used custom entities chart helps visualize if a recent update made by my organization or from a vendor is being used. In the above image I can see the "adx" entities are being used which leads me to believe a Power Apps Portal is configured.

In the below image I can see that bot content has recently been created and updated with tells me a user has provisioned a Microsoft Virtual Agent and is authoring content.

The System Jobs dashboard is useful to admins for help understanding throughput numbers and pass rates. The active and top workflow reports show the top 10 most executed and failing workflows for the overall specified time, while the throughput metrics are broken down per hours.

The System jobs execution and backlog chart I find extremely useful and recommend reviewing this regularly. The below gif shows how to filter down to a hourly window and the difference between the time shown on the chart and my filter.

Shown below is another dashboard I find very useful, the Plug-Ins Dashboard. Within this dashboard, data points for success or pass rate, number of executions, most active plug-ins and top plug-ins by failure can be found.

The Average plug-in execution time chart will visualize the averages based on our filtered time frame. Filtering can help reduce the scope so the average can be calculated from a more narrow number of plug-ins. Once an offending plug-in has been determined, analysts can use additional tools offered by the Power Platform to further drill down to specific executions.

The Mailbox Usage dashboard enables admins to visualize mailbox configurations and active email mailboxes and profiles. Utilizing data from Server-side Synchronization, admins can review incoming and outgoing configurations, which mailboxes are enabled and how many are using the service.

The Common Data Service API is heavily used in the Power Apps platform and the final dashboard, the API Calls Statistics dashboard contains rich data points. This dashboard will help admins see the API success rate, most used API calls, all up API calls and top failing API calls.

At the bottom of this dashboard is the Total API calls chart. This chart is useful to investigate when the platform may be experiencing significant demand and which calls are being used. From there, we can identify where improvements could be made with techniques such as batching or caching to reduce the number of calls made.

Filtering the data returned


The Common Data Service for Analytics will show environments an admin has access to review data for. During acceptance or end to end testing, admins may want to focus on a specific environment and time range. To do this, click the "Change filters" button for any dashboard.

The filter can be as broad as an entire month or can be as specific as any hour within a given day. I find that starting with the broad filter allows me a better understanding of overall usage. From there, I can begin to drill down into specific time frames for further analysis.

Export data for Analysis


Data from the Common Data Service for Analytics dashboards can be exported to an Microsoft Excel spreadsheet for further review and storage by clicking the "Download" button. As the image below shows, data points can be collected that may not necessarily be visualized in the Power Platform Admin Center.

The data included in the downloaded spreadsheet will present more data than shown in the dashboard reports. For instance the API Used spreadsheet shows operations for each entity down to a single call.

These spreadsheets can be used as a source for Microsoft Power BI reports or even uploaded to Azure Application Insights, Azure Log Analytics for Azure Blob Storage for extended capabilities.

NOTE: An important report that can be downloaded is the Non-conformant usage by users with Team Member license. Please review this report to ensure your organization is aligned with the Release Wave 1 2020 announcement.

Common Data Service for Analytics PowerShell cmdlets


Starting in July 2020 the PowerShell cmdlets for Power Apps will be generally available allowing for automation of tasks typically performed in the Power Platform Admin Center. These commands allow admins the ability to perform management tasks on environments and environment permissions. Admins can govern CDS and underlying technologies such as custom connectors, Power Automate Flows, CDS databases, Canvas Apps, etc.

According to the Release Wave 1 2020 article, new cmdlets will be available allowing for managing capacity, user permissions and lifecycle operations for an environment.

Service Health within the Power Platform Admin Center


Service Health for the Common Data Service can be found within the Office 365 Admin Portal by navigating to Current health as well as advisories are shown. Messages for important updates such as planned maintenance can also be found here. Both the service health and messaging allow for email delivery. Currently this is limited to two so consider ways to broadcast this via distribution lists, Office Groups, or Microsoft Team channels!

Next Steps


As the Common Data Service for Analytics feature evolves, I expect administrators will be given increased visibility and tooling to assist with the governance of CDS environments. Until then continue exploring the dashboard and export capabilities to assist with unification of CDS environment activity. As touched on briefly, there are mechanisms available now to help build custom reporting and alerting which will be elaborated on in another article.

If you are interested in learning more about specialized guidance and training for monitoring or other areas of the Power Platform, which includes a monitoring workshop, please contact your Technical Account Manager or Microsoft representative for further details.

Your feedback is extremely valuable so please leave a comment below and I'll be happy to help where I can! Also, if you find any inconsistencies, omissions or have suggestions, please go here to submit a new issue.



Monitoring the Power Platform: Introduction and Index