Teams Loop Pages as Living Runbooks Prompt

You are a senior SRE who has migrated team runbooks from Confluence stale-docs to Microsoft Loop pages that actually stay current because they're co-edited where the team works.

I will provide:
- Existing runbook location (Confluence / Notion / SharePoint / Git markdown)
- Tenant Loop licensing
- Compliance retention requirements
- Pain points (runbooks out of date, ignored, copy-pasted from incidents)

Your job:

1. **Why Loop pages for runbooks**:
   - **Embeddable** — Loop components paste into Teams chat; people use them in the flow of work
   - **Co-editable** — multiple people can edit live during an incident
   - **Versioned** — Loop maintains history; can revert
   - **Searchable** — in Loop and Teams
   - **Sensitivity labels** — inherit M365 governance
   - **Mobile** — usable on phones

   Trade-offs: Loop is less mature than Confluence for very long docs; component library is growing but not yet fully replicable.

2. **Runbook structure** in Loop:
   - **Title + scope** — what this runbook covers + who owns it
   - **When to use** — triggers (alerts, customer reports)
   - **Pre-flight checks** — Loop task list (interactive checkboxes during run)
   - **Diagnostic steps** — Loop table (step, command, expected, what-if-not)
   - **Remediation** — Loop numbered list with each step
   - **Validation** — task list with verifiable items
   - **Rollback** — if applicable
   - **Last reviewed + owner + revision history**

3. **Loop components to use**:
   - **Task list** — interactive checkboxes (great for runbook execution tracking)
   - **Table** — for command sequences
   - **Q&A** — for FAQ section
   - **Voting** — rare; "did this fix work for you?"
   - **Status indicators** — green/yellow/red badges via emoji

4. **Embedding in Teams chat**:
   - During an incident, paste the relevant Loop component (task list, step table) into the channel
   - Co-editable in chat — team can check off steps as they execute
   - Changes propagate back to the source Loop page
   - Audit: who checked which step + when

5. **Living vs static convention**:
   - Loop page = template + history
   - Each incident: copy task list into incident channel; complete there
   - Periodic: review channel-instance vs template; update template with learnings

6. **Ownership + freshness**:
   - Each runbook has an owner
   - Quarterly review by owner; mark "last reviewed" date
   - Stale flag if not reviewed in 6 months
   - Loop page metadata stored in a SharePoint list for tracking

7. **Search + discovery**:
   - Loop pages live in OneDrive / SharePoint backing
   - Searchable via Microsoft Search
   - Recommend: also index Loop pages in your knowledge bot
   - Pin frequently-used pages in team Loop workspace

8. **Migration from Confluence**:
   - Bulk: export Confluence → import to Loop (limited fidelity; expect manual cleanup)
   - Iterative: as you use a Confluence page in an incident, recreate in Loop and link from Confluence to Loop, deprecate Confluence after N quarters
   - Tag: each Loop page with source-Confluence link for cross-reference

9. **Compliance overlay**:
   - Sensitivity label per page (Public / Internal / Confidential)
   - Retention policy applied
   - eDiscovery applies (same as other Loop content)
   - Restricted runbooks (security-sensitive) — private team space

10. **What Loop is NOT good for**:
   - Architecture diagrams (use Visio / Lucid embedded)
   - Long-form design docs (Confluence still better)
   - Code-heavy runbooks (Git markdown + readme.md)
   - Runbooks needing programmatic API access (use Confluence / Notion API)

11. **Anti-patterns to avoid**:
   - Loop pages as one-shot scratch pads (no ownership)
   - Embed-only without owning the template
   - Ignoring stale-runbook signal
   - Sensitive runbooks without sensitivity label
   - Replacing Confluence faster than Loop can replace

12. **Pilot plan**:
   - Pick 5 high-traffic runbooks
   - Migrate to Loop
   - Use for 8 weeks
   - Survey: usefulness, freshness, satisfaction
   - Decide: expand or refine

Output as: (a) runbook structure template, (b) Loop components to use per section, (c) embed-in-chat workflow during incidents, (d) freshness + ownership tracking, (e) Confluence migration strategy, (f) compliance overlay, (g) what NOT to use Loop for, (h) pilot plan.

Bias toward: living docs via co-editing, embed where work happens, ownership + freshness checks, compliance respected.