# \#microsoft-365

**URL:** https://community.autommate.com/tag/microsoft-365/52.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…

---

## [Stop orphaned M365 groups from stalling access tickets](https://community.autommate.com/t/stop-orphaned-m365-groups-from-stalling-access-tickets/141)

<div class="topic-metadata">

**Author:** [@Caglayan](https://community.autommate.com/u/Caglayan)\
**Replies:** 0\
**Last updated:** [March 25, 2026, 12:27am UTC](https://community.autommate.com/t/stop-orphaned-m365-groups-from-stalling-access-tickets/141 "2026-03-25T00:27:59Z")

</div>

Stop “orphaned” M365 groups from stalling access tickets Orphaned (or effectively orphaned) Microsoft 365 / Exchange groups are a quiet service-desk killer: A user requests “add/remove members” for a distribution list …

---

## [Stop “fulfilled” M365 license tickets that don’t grant access](https://community.autommate.com/t/stop-fulfilled-m365-license-tickets-that-don-t-grant-access/139)

<div class="topic-metadata">

**Author:** [@erdem.sakin](https://community.autommate.com/u/erdem.sakin)\
**Replies:** 0\
**Last updated:** [March 24, 2026, 12:28pm UTC](https://community.autommate.com/t/stop-fulfilled-m365-license-tickets-that-don-t-grant-access/139 "2026-03-24T12:28:01Z")

</div>

Problem: “License granted” tickets that don’t actually grant access A very common service desk failure mode: A user requests Microsoft 365 / Teams Phone / Project / Visio access via ITSM. The ticket gets approved and m…

---

## [Govern shared mailbox access requests with deterministic execution](https://community.autommate.com/t/govern-shared-mailbox-access-requests-with-deterministic-execution/117)

<div class="topic-metadata">

**Author:** [@sarp.acikelli](https://community.autommate.com/u/sarp.acikelli)\
**Replies:** 0\
**Last updated:** [March 19, 2026, 12:27am UTC](https://community.autommate.com/t/govern-shared-mailbox-access-requests-with-deterministic-execution/117 "2026-03-19T00:27:59Z")

</div>

Break the “ticket → action” gap for shared mailbox access (with approvals + audit) Shared mailbox access is one of those recurring service desk requests that looks simple, but turns into a messy chain of: a ticket in t…

---

## [Stop SMTP Basic Auth Breakage With Approved, Audited Automation](https://community.autommate.com/t/stop-smtp-basic-auth-breakage-with-approved-audited-automation/97)

<div class="topic-metadata">

**Author:** [@sarp.acikelli](https://community.autommate.com/u/sarp.acikelli)\
**Replies:** 0\
**Last updated:** [March 3, 2026, 2:03pm UTC](https://community.autommate.com/t/stop-smtp-basic-auth-breakage-with-approved-audited-automation/97 "2026-03-03T14:03:31Z")

</div>

The problem (happening right now) Microsoft 365 / Exchange Online is in the middle of retiring Basic auth for SMTP AUTH client submission, which breaks a lot of “quiet” automations (ticket notifications, approval emails,…