Release date: November 3, 2026
Service build: 26.11.0.613
Configuration Client build: 26.11.0.696
User Interface build: 26.11.0.1020
Upgrade assessment
Recommendation: Recommended update
Why update now: This release adds Microsoft 365 application OAuth for mail and manual hostname mappings. It also preserves the first Event Log event after a subscription resumes, verifies TLS and DTLS destinations, recovers pending file rotation at startup, and corrects SETP forwarding and configuration handling.
If you defer: Existing processing continues, but Microsoft 365 application OAuth, hostname mappings, and the Event Log, file, forwarding, and configuration corrections in this release remain absent.
Who benefits most: Administrators who send mail through Microsoft 365, monitor the Event Log, map hostnames, or forward over TLS, DTLS, or SETP.
Upgrade and verification: Update EventReporter using the normal supported upgrade path. Confirm that the installed service version is 26.11.0.613. Test the changed functions that are relevant to your deployment.
Important changes
Mail action
- Change: The Mail action can send mail through Microsoft 365 using application-based OAuth authentication. SMTP LOGIN credentials are protected in diagnostic output and authentication failure reports, and encrypted mail verifies the destination.
- Operational impact: Mail can use Microsoft 365 application authentication, and diagnostic output no longer exposes SMTP LOGIN credentials.
- Applies to: EventReporter installations that send mail.
- Verification: Configure Microsoft 365 application OAuth, send a test mail, and confirm the message arrives. Confirm an authentication failure report does not include the SMTP LOGIN password.
Hostname and IP mappings
- Change: General settings can define hostname and IP address mappings in the Configuration Client and in the User Interface.
- Operational impact: Events can use a configured hostname or IP address mapping instead of the resolved value alone.
- Applies to: EventReporter installations that resolve hostnames.
- Verification: Add a hostname and IP address mapping, then confirm a processed event uses the mapped value.
TLS and DTLS forwarding
- Change: TLS and DTLS forwarding verify destination certificates and identities. Stalled TLS forwarding no longer blocks shutdown indefinitely.
- Operational impact: A destination with an unexpected certificate or identity is not treated as verified, and a stalled TLS send does not keep the service from shutting down.
- Applies to: EventReporter installations that forward over TLS or DTLS.
- Verification: Exercise one TLS or DTLS forwarding destination you use. Confirm the service shuts down after a TLS send that does not complete promptly.
File output and rotation
- Change: The File action writes queued data more efficiently. File rotation starts recovery before new events are processed, so pending rotated files can be recovered after service startup.
- Operational impact: Queued file writes complete more efficiently, and a pending rotation can be recovered when the service starts.
- Applies to: EventReporter installations that use the File action or file rotation.
- Verification: Confirm queued file writes complete. Restart the service with a pending rotated file and confirm recovery starts before new events are processed.
Event Log and SETP forwarding
- Change: The Event Log Monitor preserves the first event after a subscription resumes. SETP forwarding handles invalid responses safely.
- Operational impact: The first Event Log event after a subscription resumes is preserved, and an invalid SETP response does not leave forwarding in an unsafe state.
- Applies to: EventReporter installations that monitor the Event Log or forward with SETP.
- Verification: Resume an Event Log subscription and confirm the first event is present. In a test environment, confirm forwarding continues after an invalid SETP response.
Remote configuration, licensing, and diagnostics
- Change: Remote configuration rejects invalid HTTPS certificates and insecure redirects. With registry configuration, the service looks for the default license file in the location used by the Configuration Client. When a listening socket cannot be opened, diagnostics include possible owners.
- Operational impact: Insecure remote configuration downloads are rejected, the default license file is looked up where the Configuration Client stores it, and a failed listening socket identifies possible owners.
- Applies to: EventReporter installations that download remote configuration, use registry licensing, or open listening sockets.
- Verification: Confirm an invalid HTTPS certificate or an insecure redirect is rejected when downloading configuration. With registry configuration, confirm the service finds the default license file in the Configuration Client location. Confirm a failed listening socket reports possible owners.
Configuration Client
- General settings can define hostname and IP address mappings.
- The Syslog action can set the TLS send progress timeout.
- The Mail action can use Microsoft 365 application OAuth, and a test mail can check the settings.
- A partial configuration is not saved after loading fails, and existing settings are preserved when a selective import fails.
User Interface
- General settings can define hostname and IP address mappings.
- The Syslog action can set the TLS send progress timeout.
- The Mail action can use Microsoft 365 application OAuth, and a test mail can check the settings.
- A partial configuration is not saved after loading fails, and existing settings are preserved when a selective import fails.
- The dashboard displays content in the selected language.
- SMTP LOGIN username validation accepts a valid username.
Partner deployment notes
Availability: Use the canonical EventReporter download and this Technical Release Notes page as the release reference; do not use temporary build links as the long-term reference.
Localization: The User Interface translation workflow is being prepared. Translation strings and contribution guidance will be published in the Adiscon community repository when available.
Partner verification: Confirm the installed service, Configuration Client, and User Interface builds. Where relevant, send a Microsoft 365 test mail, resume an Event Log subscription, and save a configuration change.