Activities

Configure the Connectivity monitor app.

To configure the app:

• Connect to the database.
• Sign in to the Connectivity monitor app.
• Share with users.

Create an application user that is used for the connection with Connectivity studio. This user is used to get the logged connectivity data from Connectivity studio and store it in Dataverse.

On creation of the application user:

• Add the previously registered Azure Active Directory app to access Dataverse from Connectivity studio.
• Assign the System Administrator security role.

For more information, refer to Create an application user.

Before you can install the Connectivity monitoring app, you must have a Dataverse database available.

Make sure you have administrator rights on this Dataverse database.

If you don't have a Dataverse database, you can create it. For more information, refer to Add a Microsoft Dataverse database.

To use Power BI reports, a licensed user is required for the Dataverse environment.

Make sure to assign these roles to the licensed user:

• Basic User: This the standard role that is required for each Power BI user.
• Log Reader: The role that is needed to read the Connectivity monitor logs.

For more information, refer to Add users to an environment that has a Dataverse database.

In the system settings, you can enable or disable alerts.

If a Connectivity studio message run fails, an alert is sent to the owner of the message. The alert is sent to Microsoft Teams and contains a hyperlink to more details about the error.

To get the Connectivity studio history data exported to the Dataverse database that is used by the Connectivity monitor, you need a special Connectivity studio project: BisHistoryExport.

In the D365 FO environment from which connectivity history must be exported, in Connectivity studio, import the BisHistoryExport project XML file. For more information on how to import the project file, refer to Import project from file.

The BisHistoryExport project contains the predefined setup (messages, web service, connectors, and documents) that is required to export Connectivity studio history data.

Install the Power BI reports for the Connectivity monitor app.

To install the Power BI reports, click this link: Connectivity monitor Power BI reports.

Click Install when asked.

In the Connectivity monitor app, the Connectivity Dashboard page shows the integration performance, expressed in several key performance indicators and several charts.

These KPIs are shown:

In the Connectivity monitor app, the Run History page shows all logged message runs from all related applications.

On the Run History page, you can use several filter and grouping options to define which runs are shown:

• System views:
  • Today's Performance
  • All runs
  • Failed runs
  • Successful runs
• Group by: You can group the logged runs by any of the fields of the grid.
• Field sorting and filtering: You can sort or filter the logged runs by any of the fields.

In the Connectivity monitor app, the Today's Connectivity Performance page shows today's performance of the integrations you have, focused on KPIs related to connectivity errors.

These error-related KPIs are shown:

Register an application in Azure Active Directory to access Dataverse from Connectivity studio. For more information, refer to Register an application with the Microsoft identity platform.

Make sure to:

• Grant the required API permissions to the Dynamics CRM API for the Azure Active Directory application. For more information, refer to Permissions and consent in the Microsoft identity platform.
• Add a client secret to the Azure Active Directory application. For more information, refer to Add a client secret.

Copy these values to a safe place:

• Application (client) ID: Needed to set up an application user in Power Platform and to set the Client ID of the web service application in Connectivity studio.
• Directory (tenant) ID: Needed to set the Token authorization endpoint of the web service application in Connectivity studio.
• Client secret - Value: Needed to set the Client secret of the web service application in Connectivity studio. Note: Copy and save the secret before you leave the Client secrets page in Azure.

Define to which applications the Connectivity monitor app is linked.

When connectivity data is received by the Connectivity monitor app, based on the application definition, to each received record the relevant application is added. This application is used to distinguish connectivity data from different applications.

For each application:

• Set up the status mapping. Use the status mapping to define which Dataverse status is related to which status from the application.
• You can define starred connections. You can do so, for example, for connections that need extra attention. Note: On the Logs page, you can mark a connection as starred. If you do so, it is added to the application mapping as well.

On installation of the Connectivity monitor app, several cloud flows are installed.

For each of these cloud flows, you must:

• Change the owner to the earlier created Power Platform application user.
• Set the applicable connection references.
• Turn it on.

To make the Dashboard (BI) available in the Connectivity monitor app, connect the Dashboard (BI) to the 'Performance details cockpit' report.

To get the Connectivity studio history data exported to the Dataverse database that is used by the Connectivity monitor, you need a special Connectivity studio project: BisHistoryExport. This project exports the Connectivity studio history data using a web service.

Set up the used web service application on the project to connect to the earlier registered Azure Active Directory app. For more information, refer to Set up web service application for project.

For the web service application, use these settings: