Collector Troubleshooting
Authentication Issues
Section titled “Authentication Issues”- Verify tenant ID, client ID, and secret/certificate in your config.
- Confirm admin consent is granted for required Microsoft Graph permissions.
- Check system time drift on the collector host.
Connectivity Issues
Section titled “Connectivity Issues”- Validate outbound access to:
graph.microsoft.comlogin.microsoftonline.comreportsncu.office.com(Microsoft Graph report download redirect)- your backend endpoint
- Confirm proxy/firewall rules for HTTPS traffic.
TLS Certificate Errors
Section titled “TLS Certificate Errors”If the collector logs show a TLS certificate verification failed error mentioning reportsncu.office.com, this is not a licensing problem. That domain is a Microsoft redirect used for Graph API report downloads.
Cause: The collector host’s CA trust store does not include the certificate authority of the server or TLS-inspecting proxy.
Fix options (choose one):
-
Update the OS CA trust store on the collector host:
- Linux:
sudo update-ca-certificates - Windows: import the CA certificate into the system certificate store
- Linux:
-
Set
advanced.ca_bundle_pathinconfig.yamlpointing to your enterprise CA bundle in PEM format — see Advanced Options.
Data Not Visible in Backend
Section titled “Data Not Visible in Backend”- Confirm at least one output is enabled in configuration.
- Review collector logs for export errors.
- Validate backend-side credentials (Dynatrace token or Splunk HEC token).
Next Steps
Section titled “Next Steps”- Re-run from Installation with one output enabled first.
- Cross-check config with Configuration.