The pilot proves little if the same responder sees different knowledge across connected systems.
Fast incident retrieval depends on Slack context while access must remain tied to Microsoft 365 permissions.
Who you’d be doing this for
“I had three people asking for the rollback steps while the search result came back empty.”
Ragnhild Makinen · Incident Response Manager
Leads responders who need current runbooks during active production incidents.
What is at stake
Authorized responders cannot reliably find Microsoft 365 runbooks after seeing them in Slack. You must weigh a fast pilot correction against evidence that permissions still hold for every test identity.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast pilot proof vs. unchanged SSO
- responder speed vs. permission enforcement
- source visibility vs. searchable retrieval
- local correction vs. reusable validation
Why Glean
Microsoft 365 and Slack are decision-making platforms that must produce permission-aware retrieval inside the same enterprise index.
Written with these in mind
Not your kind of problem? 29 more at Glean, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.