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.
Overview
Connector Details
Connector Category
Reporting Tool
OvalEdge Release Supported
Release7.2.x and later
Connectivity
[How the connection is established with Microsoft Dynamics 365 Reports]
REST APIs
Verified Microsoft Dynamics 365 Reports Version
v9.2
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.
Connector Features
Crawling
✅
Profiling
NA
Query Sheet
NA
Data Preview
❌
Auto Lineage
✅
Manual Lineage
✅
Secure Authentication via Credential Manager
✅
Data Quality
❌
DAM (Data Access Management)
❌
Bridge
✅
'NA' indicates that the respective feature is 'Not Applicable.'
Metadata Mapping
The following objects are crawled from Microsoft Dynamics 365 Reports and mapped to the corresponding UI assets.
Domain
Default Domain
Report Group
Report
Report Group
Report
name
Report
Report
Report Name
Report
Type
Report Type
Report
Dynamics365Report
Report
description
Source Description
Report
Source Description
System Form
name
Report
Report
System Form Name
System Form
Type
Report Type
Report
Dynamics365SystemForm
System Form
description
Source Description
Report
Source Description
Set up a Connection
Prerequisites
The prerequisites to establish a connection:
Service Account User Permissions
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.
👨💻 Who can provide these permissions? The Microsoft Dynamics 365 Reports administrator grants these permissions, since users may not have sufficient access to assign them.
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
Users must have the Connector Creator role to configure a new connection.
Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for Microsoft Dynamics 365 Reports, and enter the required parameters.
Fields marked with an asterisk (*) are mandatory for establishing a connection.
Connector Type
By default, "Microsoft Dynamics 365 Reports" is displayed as the selected connector type.
Credential Manager*
Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.
Supported Credential Managers:
OE Credential Manager
AWS Secrets Manager
HashiCorp
Azure Key Vault
For more details, click here.
License Add-On
Select the Auto Lineage Add-On checkbox to build data lineage automatically.
For more details, click here.
Connector Name*
Enter a unique name for the Microsoft Dynamics 365 Reports connection
(Example: "Microsoft Dynamics 365 Reports_Prod").
Connector Environment
Select the environment (Example: PROD, STG) configured for the connector.
For more details, click here.
Connector Description
Enter the description related to the connector.
Host Name*
Enter the Microsoft Dynamics 365 reports URL, for example, https://orgname.crm.dynamics.com. Ensure the URL is accessible from the connector environment.
Client Id*
Enter the Application (Client) ID of the Microsoft Entra application registered with permissions to access Microsoft Dynamics 365.
Client Secret*
Enter the client secret associated with the registered Microsoft Entra application. Ensure the secret is active and has not expired.
Tenant Id*
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.
Connection String*
Configure the connection string for the Oracle database:
Automatic mode: The system generates a connection string based on the provided credentials.
Manual mode: Enter a valid connection string manually.
Replace placeholders with actual database details.
{sid} refers to the database name.
Proxy Enabled*
Select Yes to enable proxy settings or No to connect directly without a proxy.
Default Governance Roles
Default Governance Roles*
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.
Admin Roles
Admin Roles*
Select one or more users from the drop-down list for Integration Admin and Security & Governance Admin. All users configured in OvalEdge Security are available for selection.
No of Archive Objects
No Of Archive Objects*
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.
Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.
Bridge
Select Bridge*
If applicable, select the bridge from the drop-down list.
The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.
After entering all connection details, the following actions can be performed:
Click Validate to verify the connection.
Click Save to store the connection for future use.
Click Save & Configure to apply additional settings before saving.
The saved connection will appear on the Connectors home page.
Manage Connector Operations
Crawl
To perform crawl operations, users must be assigned the Integration Admin role.
The Crawl/Profile button allows users to select one or more Report Groups/Reports for crawling.
Navigate to the Connectors page and click Crawl/Profile.
Select the report groups/Reports to crawl.
Click Run to collect metadata from the connected source and load it into the Data Catalog.
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.
Click the Schedule checkbox to enable the Select Period drop-down.
Select a time period for the operation from the drop-down menu.
Click Schedule to initiate metadata collection from the connected source.
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.
Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA
Was this helpful?