# \#sharepoint

**URL:** https://community.autommate.com/tag/sharepoint/95.md

[Latest](https://community.autommate.com/latest.md) · [Categories](https://community.autommate.com/categories.md) · [Tags](https://community.autommate.com/tags.md)

---

## [Fix SharePoint orphaned permissions via governed ITSM runbooks](https://community.autommate.com/t/fix-sharepoint-orphaned-permissions-via-governed-itsm-runbooks/166)

<div class="topic-metadata">

**Author:** [@sarp.acikelli](https://community.autommate.com/u/sarp.acikelli)\
**Replies:** 0\
**Last updated:** [March 31, 2026, 12:35pm UTC](https://community.autommate.com/t/fix-sharepoint-orphaned-permissions-via-governed-itsm-runbooks/166 "2026-03-31T12:35:11Z")

</div>

A weird pattern we hit in ops: a P1 incident gets opened because a VIP can’t access a critical SaaS app… but the real issue is that their Entra ID account is fine — it’s the SharePoint / M365 permission layer still refer…
