Prerequisites for the Nodinite Dynamics 365 Monitoring Agent

Get started with confidence! This page outlines everything you need to successfully install and run the Nodinite Dynamics 365 Monitoring Agent.

Architecture overview: The Nodinite agent connects securely to your Dynamics 365 instance via the Microsoft API.

For best performance and security, install the agent close to your Nodinite Core Services. This guide covers a typical local network setup (usually on the Nodinite application server).

Verified	Topic
	Software Requirements
	What Dynamics 365 instance Rights does the Dynamics 365 Monitoring agent require?
	What Windows User Rights does the Dynamics 365 Monitoring agent require?
	What Firewall settings are required for the Dynamics 365 Monitoring agent?
	What SQL user rights does the Dynamics 365 Monitoring agent require?

Software requirements

The Nodinite Dynamics 365 Monitoring Agent is a Windows Service, typically installed on the Nodinite application server.

Product
Windows Server	Windows 2025 Windows 2022 Windows 2019 Windows 2016 Windows 2012 R2 Windows 2012
.NET Framework	.NET Framework 4.8 or later New 6.0 We recommend .NET Framework 4.8.1 or later

Versions 6.0 and later require .NET Framework 4.8 or later.
Versions 5.4 and up require .NET Framework 4.6.2 or later.
Versions before 5.4 require .NET Framework 4.5.2 or later.

Supported Versions

Cloud technologies evolve quickly, and Microsoft deprecates older APIs and SDKs regularly. Nodinite always supports the APIs and SDKs currently supported by Microsoft. Update Nodinite and the Dynamics 365 Monitoring Agent as needed to stay current.

Subscribe to our Release Notes to stay informed.

What Dynamics 365 instance Rights does the Dynamics 365 Monitoring agent require?

See the list of SDK/API calls.

To use the Audit feature, enable user audits in your Dynamics 365 instance.

• Enable Audit user – Audit data and user activity
  
  Make sure to enable the audit user option.

What Windows User Rights does the Dynamics 365 Monitoring agent require?

Install the agent as a Windows Service (usually on the Nodinite application server; virtual machines are supported).

• Use a local named account or domain account (preferred).
• Ensure the account has access and run-time rights.
  • Follow the 'How to set logon as a Windows service right' user guide for details.

What Firewall settings are required for the Dynamics 365 Monitoring agent?

The Nodinite Dynamics 365 Monitoring Agent requires both inbound and outbound communication:

1. Between the Monitoring Service and the Dynamics 365 Monitoring Agent
2. Between the Dynamics 365 Monitoring Agent and Dynamics 365 API (using the SDK)
3. Between the Dynamics 365 Monitoring Agent and the Monitoring Database

Network overview: Communication paths for the Dynamics 365 Monitoring Agent.

1. Between the Monitoring Service and the Dynamics 365 Monitoring agent

Allow the following ports on the Windows server where the agent is installed:

Port	Name	Inbound	Outbound	TCP	UDP	Comment
53	DNS					The Agent needs to know where your other servers/services are (can sometimes be solved with local hosts file entries)

For local network installations (if installed on the same machine, no external traffic):

Local network

Port	Name	Inbound	Outbound	TCP	UDP	Comment
8000	RPC					Communication is initiated by the Monitoring Service

2. Between the Dynamics 365 Monitoring agent and Dynamics 365 instance

Port	Name	Inbound	Outbound	TCP	UDP	Comment
443	HTTPS					Secure outbound traffic with the Dynamic 365 APIs using the SDK

3. Between the Dynamics 365 Monitoring agent and SQL Server instance with monitoring database

The Monitoring agent requires outbound ports to be opened. Since Nodinite is highly configurable, the actual ports in use may differ from these examples.

Port	Name	Inbound	Outbound	TCP	UDP	Comment
53	DNS					The Agent needs to know where your other servers/services are (can sometimes be solved with user-defined entries in the hosts file), see 'Microsoft' user guide
88	Kerberos					See 'Microsoft Kerberos' user guide
135	DTC/RPC					This port is shared between many Windows Services
1433/...	SQL Server instance ports (multiple)					Depends on policies and settings. See How to configure RPC dynamic port allocation to work with firewalls

What SQL user rights does the Dynamics 365 Monitoring agent require?

The service account running the Dynamics 365 Monitoring Agent must have the following rights:

Nodinite Dynamics 365 Monitoring database

To improve performance, all operations initiated from the Web Client/Web API use a SQL-based Monitoring Database.

• db_owner (required to apply DACPAC updates)

---

List of API Calls

API Call	Privilege	Purpose
RetrieveOrganizationsRequest	System User account	Registered users and logon history
RetrieveVersionRequest
RetrieveDeploymentLicenseTypeRequest	prvReadLicense
DeviceRegistrationRequest
RetrieveLicenseInfoRequest	prvReadLicense
QueryExpression - Audit.EntityLogicalName, Columns: objectid, createdon, operation, action, userid		Audit
QueryExpression - Workflow.EntityLogicalName, Columns: createdon, name, description, statecode, category, workflowid, activeworkflowid		Workflow
QueryExpression - Solution.EntityLogicalName, Columns: solutionid, uniquename		Solution
QueryExpression - SdkMessageProcessingStep.EntityLogicalName, Columns: createdon, name, description, statecode, introducedversion, mode		Processing step

---

Frequently asked questions

Find more solutions and answers to common problems for the Nodinite Dynamics 365 Monitoring Agent in the Troubleshooting user guide.

Next Step

Install Dynamics 365 Monitoring Agent

Related Topics

Add or manage a Monitoring Agent Configuration
Monitoring
Administration