Skip to content

Collector Troubleshooting

  • 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.
  • Validate outbound access to:
    • graph.microsoft.com
    • login.microsoftonline.com
    • reportsncu.office.com (Microsoft Graph report download redirect)
    • your backend endpoint
  • Confirm proxy/firewall rules for HTTPS traffic.

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):

  1. 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
  2. Set advanced.ca_bundle_path in config.yaml pointing to your enterprise CA bundle in PEM format — see Advanced Options.

  • 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).