Forum Discussion
Sentinel Playbook Issue
- Dec 31, 2019
leoszalkowski I discovered today that our subscription was impacted by a Log Analytics disruption yesterday between 00:28 and 04:04 UTC. That is around the time the playbooks have stopped working, and are still being impacted.
leoszalkowski I discovered today that our subscription was impacted by a Log Analytics disruption yesterday between 00:28 and 04:04 UTC. That is around the time the playbooks have stopped working, and are still being impacted.
The issue was narrowed down to the playbook running in one of the tenants my company is managing. The playbook is getting a 404: not found error when it's run.
Not sure if some permissions were changed in the tenant or if it could be a separate issue.
- Rod_TrentDec 31, 2019
Microsoft
So, just one tenant has the issue? Where was the original Playbook created? Does this tenant reside in a different datacenter/region?
Does the Playbook work if run manually?
- leoszalkowskiDec 31, 2019Brass Contributor
So it's a strange issue.
The playbook is located in our tenant. Our region is different than our customers' region.
It was running perfectly fine for the past two weeks, up until yesterday morning for the one customer's tenant.
The playbook runs manually if I run it from inside of the incident details page.
It does not run, however, if I go to the specific playbook overview and run the trigger.
- Rod_TrentDec 31, 2019
Microsoft