Microsoft Dynamics 365 Customer Engagement (on-premises) reporting requirements
Microsoft Dynamics 365 Reporting Extensions are data processing extensions that are installed on the SQL Server Reporting Services server. The Microsoft Dynamics 365 Reporting Extensions accept authentication information from Dynamics 365 Server and pass it to the SQL Server Reporting Services server.
Dynamics 365 Customer Engagement (on-premises) Reporting Extensions includes two data processing extensions: Fetch data processing extension and SQL data processing extension. By default, these extensions are installed during Dynamics 365 Customer Engagement (on-premises) Reporting Extensions Setup:
The Fetch data processing extension is required to create, run, and schedule Fetch-based reports.
The SQL data processing extension is required to create, run, and schedule the default (out-of-the-box) or SQL-based custom reports in Dynamics 365 Customer Engagement (on-premises).
You don’t need Microsoft Dynamics 365 Reporting Extensions to run Dynamics 365 Customer Engagement (on-premises). However, if you want to create, use, or schedule reports in Dynamics 365 Customer Engagement (on-premises), you need to install Microsoft Dynamics 365 Reporting Extensions. Additionally, you need to install these extensions if you want to create or import an organization, like when you migrate from an earlier version of Dynamics 365 Customer Engagement (on-premises) using Deployment Manager.
SQL Server Reporting Services
SQL Server Reporting Services is required for reporting features in Dynamics 365 Customer Engagement (on-premises).
For Dynamics 365 Customer Engagement (on-premises) reporting, you can use the following SQL Server editions running on a supported version of Windows Server:
- Microsoft SQL Server 2022 Enterprise1
- Microsoft SQL Server 2022 Standard1
- Microsoft SQL Server 2022 Developer (for nonproduction use only)1
- Microsoft SQL Server 2019 Enterprise
- Microsoft SQL Server 2019 Standard
- Microsoft SQL Server 2019 Developer (for non-production use only)
- Microsoft SQL Server 2017 Enterprise
- Microsoft SQL Server 2017 Standard
- Microsoft SQL Server 2017 Developer (for non-production use only)
- Microsoft SQL Server 2016 Enterprise, with Service Pack 2 or Service Pack 3
- Microsoft SQL Server 2016 Standard, with Service Pack 2 or Service Pack 3
- Microsoft SQL Server 2016 Developer, with Service Pack 2 or Service Pack 3 (for non-production use only)
1Requires Service Update 1.25 for Microsoft Dynamics Customer Engagement v9 (on-premises)
Important
- SQL Server Compact or SQL Server Express editions are not supported for use with Dynamics 365 Server.
- Using a SQL Server Reporting Services server running in SharePoint mode isn't supported with Dynamics 365 Customer Engagement (on-premises). For more information about SQL Server Reporting Services SharePoint mode, see Reporting Services Report Server (SharePoint Mode).
Dynamics 365 Reporting Extensions requirements
The Microsoft Dynamics 365 Reporting Extensions component has the following requirements:
You must complete Microsoft Dynamics 365 Server Setup before you run Dynamics 365 Customer Engagement (on-premises) Reporting Extensions Setup.
You can install and run Microsoft Dynamics 365 Reporting Extensions on only one instance of SQL Server Reporting Services on a computer.
The identity account running the instance of SQL Server Reporting Services where the Microsoft Dynamics 365 Reporting Extensions are running can’t be the local system or a virtual account. This is required for Dynamics 365 Customer Engagement (on-premises) reporting to work because the identity account must be added to the
PrivReportingGroup
Active Directory security group that is used by Dynamics 365 Customer Engagement (on-premises).Separate deployments of Dynamics 365 Customer Engagement (on-premises) cannot share one SQL Server Reporting Services server. However, a single deployment of Dynamics 365 Customer Engagement (on-premises) that has multiple organizations can use the same SQL Server Reporting Services server.
You must run the Dynamics 365 Customer Engagement (on-premises) Reporting Extensions Setup on a computer that has a supported version and edition of SQL Server Reporting Services installed. More information: SQL Server Reporting Services
For smaller data sets and fewer users, you can use a single-server deployment or a multi-server deployment. With larger data sets or more users, performance decreases quickly when running complex reports. Use a multi-server deployment with one computer that is running SQL Server for Dynamics 365 Customer Engagement (on-premises), and another server for SQL Server Reporting Services.
Report Authoring Extension requirements
Dynamics 365 Customer Engagement (on-premises) Report Authoring Extension is required to author Fetch-based reports used with Dynamics 365 Customer Engagement (on-premises) by using SQL Server Data Tools. You must install the Dynamics 365 Customer Engagement (on-premises) Report Authoring Extension on a PC that has the following software.
Supported operating systems
One of the following Windows versions:
- Windows 11
- Windows 10
Additional software requirements
Visual Studio. These versions are supported:
- Visual Studio 2019.
- Visual Studio 2017.
- Visual Studio 2015.
SQL Server Data Tools (SSDT). SSDT is available with Visual Studio. More information:
Microsoft Reporting Services Projects extension. Used to create report server projects. The extension is included with Visual Studio 2015. For later versions, see Report Services Projects extension.
Dynamics 365 Customer Engagement (on-premises) Reporting Extensions Setup includes two data processing extensions: Fetch data processing extension and SQL data processing extension. By default, these extensions are installed during Dynamics 365 Customer Engagement (on-premises) Reporting Extensions Setup:
The Fetch data processing extension is required to create, run, and schedule Fetch-based reports.
The SQL data processing extension is required to create, run, and schedule the default (out-of-the-box) or SQL-based custom reports in Dynamics 365 Customer Engagement (on-premises).
You don’t need Microsoft Dynamics 365 Reporting Extensions to run Dynamics 365 Customer Engagement (on-premises). However, if you want to create, use, or schedule reports in Dynamics 365 Customer Engagement (on-premises), you need to install Microsoft Dynamics 365 Reporting Extensions. Additionally, you need to install these extensions if you want to create or import an organization, like when you migrate from an earlier version of Dynamics 365 Customer Engagement (on-premises) using Deployment Manager.
SQL Server Reporting Services
SQL Server Reporting Services is required for reporting features in Dynamics 365 Customer Engagement (on-premises).
For Dynamics 365 Customer Engagement (on-premises) reporting, you can use the following SQL Server editions running on a supported version of Windows Server:
- Microsoft SQL Server 2017 Enterprise1
- Microsoft SQL Server 2017 Standard1
- Microsoft SQL Server 2017 Developer (for non-production use only)1
- Microsoft SQL Server 2016 Enterprise, with Service Pack 2 or Service Pack 3
- Microsoft SQL Server 2016 Standard, with Service Pack 2 or Service Pack 3
- Microsoft SQL Server 2016 Developer, with Service Pack 2 or Service Pack 3 (for non-production use only)
Important
- 1Requires Microsoft Dynamics 365 Server, v9.0 (on-premises) Update 0.3.
- SQL Server Compact or SQL Server Express editions are not supported for use with Dynamics 365 Server.
- Using a SQL Server Reporting Services server running in SharePoint mode is not supported with Dynamics 365 Customer Engagement (on-premises). For more information about SQL Server Reporting Services SharePoint mode, see Reporting Services Report Server (SharePoint Mode).
Dynamics 365 Reporting Extensions requirements
The Microsoft Dynamics 365 Reporting Extensions component has the following requirements:
You must complete Microsoft Dynamics 365 Server Setup before you run Dynamics 365 Customer Engagement (on-premises) Reporting Extensions Setup.
You can install and run Microsoft Dynamics 365 Reporting Extensions on only one instance of SQL Server Reporting Services on a computer.
The identity account running the instance of SQL Server Reporting Services where the Microsoft Dynamics 365 Reporting Extensions are running can’t be the local system or a virtual account. This is required for Dynamics 365 Customer Engagement (on-premises) reporting to work because the identity account must be added to the
PrivReportingGroup
Active Directory security group that is used by Dynamics 365 Customer Engagement (on-premises).Separate deployments of Dynamics 365 Customer Engagement (on-premises) cannot share one SQL Server Reporting Services server. However, a single deployment of Dynamics 365 Customer Engagement (on-premises) that has multiple organizations can use the same SQL Server Reporting Services server.
You must run the Dynamics 365 Customer Engagement (on-premises) Reporting Extensions Setup on a computer that has a supported version and edition of SQL Server Reporting Services installed. More information: SQL Server Reporting Services
For smaller data sets and fewer users, you can use a single-server deployment or a multi-server deployment. With larger data sets or more users, performance decreases quickly when running complex reports. Use a multi-server deployment with one computer that is running SQL Server for Dynamics 365 Customer Engagement (on-premises), and another server for SQL Server Reporting Services.
Report Authoring Extension requirements
Dynamics 365 Customer Engagement (on-premises) Report Authoring Extension is required to author Fetch-based reports used with Dynamics 365 Customer Engagement (on-premises) by using SQL Server Data Tools. You must install the Dynamics 365 Customer Engagement (on-premises) Report Authoring Extension on a PC that has the following software.
Supported operating systems
One of the following Windows versions:
- Windows 11
- Windows 10
Additional software requirements
Visual Studio. These versions are supported:
- Visual Studio 2019.
- Visual Studio 2017.
- Visual Studio 2015.
SQL Server Data Tools (SSDT). SSDT is available with Visual Studio. More information:
Microsoft Reporting Services Projects extension. Used to create report server projects. The extension is included with Visual Studio 2015. For later versions, see Report Services Projects extension.
See also
Install Dynamics 365 Report Authoring Extension
Microsoft Dynamics 365 Customer Engagement (on-premises) system requirements and required technologies