A successful Microsoft Graph request does not prove that Entra ID sign-ins reached the Wazuh indexer. Collection, manager-side processing, forwarding, indexer processing, and dashboard search are separate stages. A Wazuh QA report found event processing disabled in a tested beta package, but the available evidence does not establish a supported one-processor fix or the affected release range. Treat that finding as a diagnostic lead, not a universal change to make blindly.
First, identify which Graph integration you configured
Wazuh has two distinct configurations that can be relevant to Microsoft Graph data. The ms-graph module is configured with resources and relationships. The Azure logs integration has a Graph request configuration that documents the auditLogs/signIns path for sign-in logs. Do not assume a setting or endpoint from one configuration applies to the other.
As an Amazon Associate I earn from qualifying purchases.
| Configuration | How it is expressed | Sign-in detail to check |
|---|---|---|
Wazuh ms-graph module |
An <ms-graph> configuration with resource and relationship entries. |
Confirm that the configured resource/relationship combination retrieves the data you expect. Its reference documents configurable resources and relationships, not the Azure logs request syntax. |
| Azure logs Graph route | An <wodle name="azure-logs"><graph> block with a Graph request. |
The Azure logs reference lists auditLogs/signIns as a valid query path. Confirm the request, credentials, tenant settings, and time window. |
These are documented collection approaches, not a complete feature comparison. The documentation does not establish that either route is categorically better for every deployment.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsCheck collection settings and polling time
If you use ms-graph
Review the module’s enabled state, api_auth tenant, client, and secret values, the selected resource and relationship, API version, interval, time_delay, and run_on_start. Wazuh documents a default interval of one day and says the first poll waits for the configured interval unless run_on_start is enabled. That delay can look like a collection failure immediately after setup. The reference recommends v1.0 for production.
#1 Best Overall
- Compact and Efficient Design: The FortiGate 40F is designed for small to mid-sized businesses and enterprise branch offices, featuring a compact, fanless desktop form factor that ensures quiet operation and minimizes space usage.
- Robust Connectivity Options: Equipped with 5 GE RJ45 ports, including 1 WAN port and 4 internal ports, this model provides essential connectivity and flexibility for various network configurations in a small-scale environment.
- High-Performance Security: Offers up to 1 Gbps IPS throughput and 600 Mbps threat protection throughput, using Fortinet’s purpose-built security processor technology to deliver industry-leading performance and protection for SSL encrypted traffic.
- Advanced Threat Protection: Integrated with Fortinet’s AI-powered FortiGuard Labs, the FortiGate 40F offers comprehensive cybersecurity, identifying and mitigating both known and unknown threats to maintain robust security across your network.
- Simplified Management and Deployment: Features a user-friendly management console that provides comprehensive network automation and visibility, coupled with Zero Touch Integration with Fortinet’s Security Fabric for easy deployment.
These checks establish whether collection is configured and when a poll should happen; they do not establish that a retrieved record passed through the manager or indexer.
If you use Azure logs
Check that the Graph request includes auditLogs/signIns, that tenant and credential settings are valid, and that time_offset covers the period you are searching. The Azure logs reference describes this offset as selecting events in a recent time window, so a narrow or mismatched window can yield no records even when the request itself is valid.
Trace the event through each stage
Find the last stage where you can observe the sign-in record. Wazuh documents Filebeat as shipping manager output and describes the indexer connector separately; a successful API response is therefore not proof of successful indexing. Use host logs and actual event output to distinguish these outcomes:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #2
- HARDWARE PLUS SECURITY SERVICES: FortiGate-60F Firewall Appliance bundled with 1 year of FortiCare Premium and FortiGuard Unified Threat Protection.
- UNIFIED THREAT PROTECTION (UTP): Secures against advanced online threats with comprehensive web filtering and anti-botnet technologies.
- OPTIMIZED FOR MEDIUM-SIZED BUSINESSES: Tailored for businesses needing robust security without the infrastructure of larger enterprises.
- RELIABLE CUSTOMER SUPPORT: FortiCare Premium ensures high-quality support and service continuity.
- EFFECTIVE PROTECTION: Employs advanced filtering technologies to safeguard against sophisticated threats.
- No Graph results: Inspect the relevant integration’s query path, credentials, resource/relationship, schedule, and time window.
- A response arrives, but no manager-side event appears: Verify that the module is processing the response and producing output. A non-empty API response alone does not demonstrate that Wazuh emitted an alert or archive record.
- The event appears in manager output, but not in the index: Check the applicable shipping path, including Filebeat or the indexer connector, then inspect indexer engine status and logs.
- The indexer reports a rejection: Read the error and inspect the event shape and index mapping. A rejected record is different from one that silently never reaches indexer processing.
- The record is indexed but not visible in the dashboard: Check the dashboard’s search, time range, and selected data view against the indexed record.
This is a practical diagnostic sequence based on Wazuh’s documented forwarding components and the reported symptoms, not a single official runbook.
What the disabled-processor report does—and does not—show
A Wazuh QA report for a beta environment found this value in /usr/share/wazuh-indexer/engine/run_engine.sh:
WAZUH_SERVER_ENABLE_EVENT_PROCESSING="false"The report says the startup log in wazuh-engine.log included: “Indexer Connector DISABLED – events will not be indexed”. It attributes failed Office 365 integration test events to this disabled event-processing path and links the finding to indexer issue #1768. This makes the engine state worth checking when collection and manager output are already verified.
Rank #3
- 【Up to 1100 Mbps VPN Speed 】 Hardware-accelerated WireGuard and OpenVPN-DCO deliver up to 1100 Mbps VPN throughput, over 3× faster than Brume 2 for smooth remote access and file transfers.
- 【Three 2.5G Ports & Multi-WAN】Tri-port 2.5GbE design with flexible WAN LAN configuration supports multi-gigabit wired setups, dual-ISP Multi-WAN and failover to keep home and SOHO networks online.
- 【Stealth VPN Obfuscation】VPN obfuscation disguises VPN traffic as regular HTTPS, helping you evade blocking, bypass restrictive networks and maintain stable, private connections.
- 【DPI protection】Deep Packet Inspection with visual dashboards blocks adult/gambling/malicious sites, while SQM and QoS prioritize gaming, calls, and video when bandwidth is tight
- 【OpenWrt & USB 3.0 Expansion】OpenWrt with 1GB DDR4 and 8GB eMMC lets you install plugins and build VPN, ad-blocking or NAS, while USB 3.0 Type‑C connects high-speed storage or 4G/5G dongles
It does not prove that changing the value to true is the supported fix for every Wazuh installation, nor does it establish which released versions are affected or fixed. The report concerns a tested beta package; it is not a general confirmation of the root cause for missing Entra ID sign-ins. Before changing a package script or service setting, verify the behavior and supported configuration for the exact installed package and consult the status of Wazuh indexer issue #1768 and the relevant release guidance. If the engine is disabled, preserve the package’s original state and logs while determining the supported remediation.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchTell a silent processing problem from a mapping rejection
A separate Wazuh issue describes index rejection because ms-graph.status was mapped as keyword while the event could contain an array or object form. A mapper parsing error is observable evidence that a record reached indexing and was rejected because of its shape or mapping. It is not the same symptom as the QA report’s disabled event-processing path. When an error names a field or mapping type, compare the rejected event with the index template rather than treating it as proof that Graph collection failed.
Use similar reports carefully
A user issue titled “HTTPS request confirmed via tcpdump, but no events reach the index” reports a non-empty response and no indexed records for security/alerts_v2 and security/incidents. The reporter says resetting the checkpoint and changing only_future_events did not resolve that case. Those relationships are not Entra ID sign-ins, so the report is useful as an example of a downstream gap—not evidence that the same cause or workaround applies to auditLogs/signIns.
Quick Recap
Practical decision checklist
- Identify whether the manager uses
ms-graphor Azure logs Graph configuration. - Confirm the correct sign-in query/resource, authentication, and relevant polling or time-window settings.
- Establish whether the event exists in the Graph response, manager output, and shipping path.
- If it reaches the indexer, distinguish disabled event processing from a field-mapping rejection by checking engine logs and index errors.
- Do not make a one-variable processor change solely on the basis of the beta QA report; verify the installed version’s supported fix and release status.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
