401 Response about o365beat HOT 5 CLOSED

Happy to help troubleshoot. If you send your debug log, I can narrow down the specific part of the process that's failing: you can email me at [email protected] (to avoid having to redact too much from your logs) and I'll update this issue with whatever we find.

from o365beat.

Mark - we found a bug in v1.2 last week that might explain your recent 400 error(s). You may have more luck with the latest, v1.3.0. If that doesn't fix your issue, please email me directly at [email protected] (the github issue isn't keeping your email attachments) and we can sort through the details, and I'll come back to the github issue with a "cleaned up" solution for anyone else running into the problem. Thanks!

from o365beat.

After reviewing your logs, it looks like it's the same bug with subscriptions that was fixed in v1.3.0: the beat wasn't properly auto-subscribing you to the "feeds" for each content type. Using the latest version should fix this issue. Sorry for the inconvenience, and thank you for the feedback!

from o365beat.

After more research, we noticed another issue: auditing wasn't turned on for the Office 365 tenancy, and that's required for any of this to work. Enabling audit logs is straightforward, but takes a while to kick in (multiple hours).

We'll update the documentation to reflect this requirement, and update the beat's next version to detect if this isn't enabled and give a more helpful error message (captured this in #5)

from o365beat.

from o365beat.