> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/connector-repositories/reporting-tool/microsoft-dynamics-365-reports.md).

# Microsoft Dynamics 365 Reports

This article outlines the integration with the Microsoft Dynamics 365 Reports connector, enabling metadata management through report crawling and lineage building (automatic and manual). The connector extracts metadata for report groups, reports, and system forms.

The connector connects to Microsoft Dynamics 365 Reports using REST APIs and authenticates through a Microsoft Entra ID application using the Host Name, Client ID, Client Secret, and Tenant ID. The registered application must have the required permissions to access Microsoft Dynamics 365 Reports metadata, enabling validation, metadata crawling, and lineage extraction.

<img src="/files/qr04cS0MiQYDMzNhdMFM" alt="" height="321" width="624">

## Overview

### Connector Details

<table data-header-hidden><thead><tr><th width="321"></th><th></th></tr></thead><tbody><tr><td>Connector Category</td><td>Reporting Tool</td></tr><tr><td>OvalEdge Release Supported</td><td>Release7.2.x and later</td></tr><tr><td><p>Connectivity</p><p>[How the connection is established with Microsoft Dynamics 365 Reports]</p></td><td>REST APIs</td></tr><tr><td>Verified Microsoft Dynamics 365 Reports Version</td><td>v9.2</td></tr></tbody></table>

{% hint style="info" %}
The Microsoft Dynamics 365 Reports connector validates with the listed “Verified Microsoft Dynamics 365 Reports Version” and supports other compatible Microsoft Dynamics 365 Reports versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Profiling                                    |      NA      |
| Query Sheet                                  |      NA      |
| Data Preview                                 |       ❌      |
| Auto Lineage                                 |       ✅      |
| Manual Lineage                               |       ✅      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality                                 |       ❌      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ✅      |

{% hint style="info" %}
'NA' indicates that the respective feature is 'Not Applicable.'
{% endhint %}

### Metadata Mapping

The following objects are crawled from Microsoft Dynamics 365 Reports and mapped to the corresponding UI assets.

<table><thead><tr><th>Source Object</th><th>Source Attribute</th><th width="144">OvalEdge Attribute</th><th width="154.666748046875">OvalEdge Category</th><th>OvalEdge Type</th></tr></thead><tbody><tr><td>Domain</td><td>Default Domain</td><td>Report Group</td><td>Report</td><td>Report Group</td></tr><tr><td>Report</td><td>name</td><td>Report</td><td>Report</td><td>Report Name</td></tr><tr><td>Report</td><td>Type</td><td>Report Type</td><td>Report</td><td>Dynamics365Report</td></tr><tr><td>Report</td><td>description</td><td>Source Description</td><td>Report</td><td>Source Description</td></tr><tr><td>System Form</td><td>name</td><td>Report</td><td>Report</td><td>System Form Name</td></tr><tr><td>System Form</td><td>Type</td><td>Report Type</td><td>Report</td><td>Dynamics365SystemForm</td></tr><tr><td>System Form</td><td>description</td><td>Source Description</td><td>Report</td><td>Source Description</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

#### **Service Account User Permissions**

{% hint style="warning" %}
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
**👨‍💻 Who can provide these permissions?** The Microsoft Dynamics 365 Reports administrator grants these permissions, since users may not have sufficient access to assign them.
{% endhint %}

| Operations           | Objects      | Permissions                            |
| -------------------- | ------------ | -------------------------------------- |
| Connector Validation | -            | OAuth token success only               |
| Crawling             | Report       | Read on reports, systemforms, entities |
| Crawling             | System Form  | Read on reports, systemforms, entities |
| Crawling             | Semantic map | Read on reports, systemforms, entities |

### Connection Configuration Steps

{% hint style="warning" %}
Users must have the Connector Creator role to configure a new connection.<br>
{% endhint %}

1. Log into **OvalEdge**, go to **Administration** > **Connectors**, click **+ (New Connector)**, search for **Microsoft Dynamics 365 Reports**, and enter the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="223">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "Microsoft Dynamics 365 Reports" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add-On</td><td><p>Select the Auto Lineage Add-On checkbox to build data lineage automatically.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Microsoft Dynamics 365 Reports connection              </p><p>(Example: "Microsoft Dynamics 365 Reports_Prod").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</p></td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>Host Name*</td><td>Enter the Microsoft Dynamics 365 reports URL, for example, https://orgname.crm.dynamics.com. Ensure the URL is accessible from the connector environment.</td></tr><tr><td>Client Id*</td><td>Enter the Application (Client) ID of the Microsoft Entra application registered with permissions to access Microsoft Dynamics 365.</td></tr><tr><td>Client Secret*</td><td>Enter the client secret associated with the registered Microsoft Entra application. Ensure the secret is active and has not expired.</td></tr><tr><td>Tenant Id*</td><td>Enter the Directory (Tenant) ID of the Microsoft Entra tenant where the application is registered. This value is used to authenticate the connector with Microsoft Entra ID.</td></tr><tr><td>Connection String*</td><td><p>Configure the connection string for the Oracle database:</p><ul><li>Automatic mode: The system generates a connection string based on the provided credentials.</li><li>Manual mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to the database name.</p></td></tr><tr><td>Proxy Enabled*</td><td>Select Yes to enable proxy settings or No to connect directly without a proxy.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="219.6666259765625"></th><th></th></tr></thead><tbody><tr><td><strong>Default Governance Roles</strong></td><td></td></tr><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr><tr><td><strong>Admin Roles</strong></td><td></td></tr><tr><td>Admin Roles*</td><td>Select one or more users from the drop-down list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr><tr><td><strong>No of Archive Objects</strong></td><td></td></tr><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p><strong>Example</strong>: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr><tr><td><strong>Bridge</strong></td><td></td></tr><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl

{% hint style="warning" %}
To perform crawl operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more Report Groups/Reports for crawling.&#x20;

1. Navigate to the **Connectors** page and click **Crawl/Profile**.
2. Select the report groups/Reports to crawl.
3. Click **Run** to collect metadata from the connected source and load it into the Data Catalog.
4. After a successful crawl, the information appears in the Data Catalog > Report / Report Column tab.

The **Schedule** checkbox allows automated crawling for a selected timeframe, from a minute to a year.

1. Click the **Schedule** checkbox to enable the Select Period drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the crawl operation at the scheduled time.

#### Other Operations

The Connectors page provides a centralized view of all configured **connectors** and their health status.

**Managing connectors includes:**

* **Connectors Health**: Displays the current status of each connector, with a green icon for active connections and a red icon for inactive connections, helping monitor connectivity to data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including Reports, Report Columns, and Report Group.

**Nine Dots Menu Options:**

To view, edit, validate, build lineage, configure, or delete connectors, click on the Nine Dots menu.

* **Edit Connector:** Update and revalidate the data source.
* **Validate Connector**: Check the integrity of the connection.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Access Instructions:** Add notes on how data can be accessed.
  * **Business Glossary Settings**: Manage term associations at the connector level.
  * **Lineage**: Select server dialects for parsing and setting connector priority for table lineage.
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector**: Remove a connector with confirmation.

For more details on connector settings, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/reporting-tool/microsoft-dynamics-365-reports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.