Microsoft Dynamics 365 Customer Insights

Microsoft Dynamics 365 Customer Insights helps deliver personalized customer experiences by unifying customer data with operational and IoT data in real time. This integration tracks changes via the Dynamics 365 Customer Insights UI; creation, update, and deletion events of API calls; and monitoring the execution events of workflow.

Log types

For Microsoft Dynamics 365 Customer Insights, you can collect the following types of logs:

• Audit events. API events to track the configuration changes on the service.
• Operational events
  • Workflow events. The execution events of a workflow.
  • API events. Events to track all API calls from the customer's instance to Dynamics 365 Customer Insights.

API events and workflow events have a common structure, but with a few differences. For more information, see API event schema or Workflow event schema.

Setup

Azure service sends monitoring data to Azure Monitor, which can then stream data to Eventhub. Sumo Logic supports:

• Logs collection from Azure Monitor using our Azure Event Hubs source.

When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: Azure/Dynamic365/Logs

Prerequisites

Follow the prerequisites before configuring the collection setup. We will be using Event hub as a destination resource, and more details about its limitations and permissions are described here.

Configure logs collection

In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.

1. Create an Event Hubs namespace as described in step 2 of the prerequisites section. Here, you do not have to create an Event Hub Instance in step 3 since Microsoft Dynamics 365 Customer Insights automatically creates the below two Event Hubs:
   • insight-logs-audit. It contains audit events.
   • insight-logs-operational. It contains operational events.
2. Create a Shared Access Policy for the entire namespace with the Listen claim or you can use the existing default RootManageSharedAccessKey policy. Copy the Primary key associated with this policy. For more details, refer to steps 4 and 5 of the Vendor configuration section.
3. Create two Azure Event Hubs Sources using the instructions described here. You can add both of them to the same Hosted Collector. Provide insight-logs-audit and insight-logs-operational as Event Hubs Instance Name in the two Azure Event Hubs Sources, respectively.
4. To create the Diagnostic settings in the Azure portal, refer to the Azure documentation.
   1. Choose Event Hub as the Resource type.
   2. Select the Event Hub's Subscription name, Resource group name, and Resource name for the destination resource.

Troubleshooting

Azure Event Hubs Source

Common error types are described here.

You can try restarting the source for ThirdPartyConfig errors.