Installing the Nodinite Azure agent
Start monitoring your Azure EAI services proactively and securely with the Nodinite Azure Monitoring Agent. This guide leads you through each installation step so you can quickly realize the benefits of Nodinite.
- ✅ Deploy the Azure Monitoring Agent quickly using a user-friendly installer
- ✅ Empower your team to monitor Azure resources without direct portal access
- ✅ Secure your environment with least-privilege access and compliance
- ✅ Access robust troubleshooting and support resources
Once installed, the Azure Monitoring Agent supports monitoring of Web Jobs, Azure Storage, API Management, Certificates, Event Hub, Event Grid, and Data Factory resources, in addition to other Azure services.
Info
This guide shows you how to install the Nodinite Azure Monitoring Agent. Check the Prerequisites first; that page is the one home for software, Azure access, Windows rights, and firewall ports.
Understanding the installation
The agent is the bridge between your Azure subscriptions and Nodinite. After installation, the Monitoring Service talks to the agent to evaluate the state of your Azure Resources, so that your users can see them in Monitor Views and act on them with Remote Actions. How you install it depends on your Nodinite version:
IIS web site"] end subgraph V6["fa:fa-box Nodinite v6, legacy"] MSI["fa:fa-box MSI installer"] -->|"Installs"| WS["fa:fa-gears Agent
Windows Service"] end IIS --> MAC["fa:fa-monitor-waveform Monitoring Agent Configuration"] WS --> MAC style P fill:#2678BD,color:#fff style PS fill:#2678BD,color:#fff style IIS fill:#93d16d style MSI fill:#FFD525 style WS fill:#FFD525
Diagram: The recommended v7 path (blue and green) installs the agent as an IIS web site from a Portal-generated script. The legacy v6 path (yellow) uses an MSI installer and a Windows Service. Both end with a Monitoring Agent Configuration.
Key components
| Component | Role |
|---|---|
| Portal | Holds your environments and generates the PowerShell installation scripts (v7) |
| Agent | Runs as an IIS web site (v7) or a Windows Service (v6) under a service account; see Windows User Rights |
| App Registration | Lets the agent call Azure; see Azure User rights |
| Monitoring Agent Configuration | Tells the Monitoring Service where the agent is, so you can use Remote Configuration and Remote Actions |
v7 vs v6 installation
| Aspect | Nodinite v7 (Portal) | Nodinite v6 (MSI) |
|---|---|---|
| Status | ✅ Recommended | ⚠️ Legacy, deprecated |
| Installer | PowerShell script generated by the Portal | MSI file, run manually |
| Agent host | IIS web site with its own port | Windows Service |
| Many agents and environments | ✅ Yes, with consistent settings | ❌ No, one server at a time |
| Guide | Install Nodinite v7 | Steps below |
Before you begin
Confirm that you meet all prerequisites.
Important
You must have local administrator rights to install the agent (IIS web site or Windows Service).
Nodinite version 7
Preferred Method: Portal-Based Scripted Installation
In Nodinite v7, agent installation is automated through the Portal-based scripted installation. This modern approach:
- ✅ Automates agent installation and configuration via PowerShell scripts
- ✅ Configures multiple agents simultaneously with consistent settings
- ✅ Eliminates manual MSI installations and reduces human error
- ✅ Centrally manages all environments from the Portal
Follow the Install Nodinite v7 guide to install agents using the Portal-based approach. The Portal generates PowerShell scripts that install and configure agents automatically across your infrastructure; you set the agent's IIS web site, port, and service identity in the Agents step. When the agent runs, configure it.
Nodinite version 6 (MSI-Based Installation - Legacy)
Use this MSI installation workflow only for legacy v6 environments.
Warning
The MSI-based installation method for Nodinite v6 is deprecated and will be retired. Please upgrade to Nodinite v7 for the modern Portal-based scripted installation experience.
Step 1: Start the installer
Double-click the MSI file to launch the installation of the Nodinite Azure Monitoring Agent.
The MSI installer for the Nodinite Azure Monitoring Agent.
Step 2: Welcome screen
When the MSI file runs, the Welcome screen appears:
Welcome screen for the Nodinite Azure Monitoring Agent installer.
Click Next to continue or Cancel to exit the installer.
Step 3: Accept End User License Agreement
Accept the terms in the License Agreement to continue. Make sure you have the formal rights to install and modify the target environment before you proceed.
End User License Agreement screen. Acceptance is required to proceed.
Step 4: Custom setup
Select the components to install and choose the destination path.
Custom setup options for the Nodinite Azure Monitoring Agent.
Note
Use the default settings for best results.
Click Next to continue or Cancel to exit the installer.
Step 5: Service Account Information
Enter the credentials for the Account that runs the Nodinite Azure Monitoring Agent Windows Service; see Windows User Rights.
Enter credentials:
- Domain: Enter the domain name. For local accounts, use the server name or a dot (.) as Domain.
- User: Enter the account name.
- Password: Enter the account password.
Example of entering domain service account credentials.
Insufficient Privileges
If the account information doesn't meet the Prerequisites, an error message appears.
Error message for insufficient privileges during installation.
Usually, this error means the account can't run as a service or isn't a local Administrator. Follow the How to set Logon as a Service right guide and click retry. If the issue persists, click cancel and restart. Always enter valid credentials!
Tip
Check the local event log (System and Application) for errors.
Step 6: Ready to install
When you complete all preparations, click Next to continue or Cancel to exit.
Ready to install dialog for the Nodinite Azure Monitoring Agent.
Step 7: Completed setup
The final step displays either a success or a premature exit.
Successful installation
Successful installation confirmation.
Failed installation
A failed installation results in a premature exit.
Click Finish to exit the installer.
Step 8: Add Agent as a new Monitoring Agent Configuration
After a successful setup, a README.txt file opens with the connection details you need to configure the agent as one of your Monitoring Agents. The agent regenerates this file on each successful start.
To add the Azure Monitoring Agent as a Monitoring Agent, follow the detailed instructions in the shared article below, then continue with the Configuration:
Support
Contact our Support team if you need help resolving installation issues.
Note
You may find additional troubleshooting information in the Windows Event Logs.
Frequently asked questions
Find solutions to common problems and the Nodinite Azure Monitoring Agent FAQ in the Troubleshooting user guide.