Permissions are the design, not a detail
Microsoft Graph will happily grant an application access to every mailbox and every site in the tenant, and that is the configuration most integrations ship with because it is the one that works first. It is also the one that fails a security review. We scope access with application access policies so an automation can read the shared inbox it was built for and nothing else, register it as its own identity in Entra, and separate development credentials from production so a test run cannot touch live records. Admin consent is usually required, which means an IT stakeholder belongs in the project from the first week.
Throttling, labels and retention
Graph throttles under load, and it does so per-resource in ways that are hard to predict from a small test. Any workflow that processes a backlog needs retry with backoff and a way to resume rather than restart. Sensitivity labels and retention policies add a second constraint that is easy to miss: a labelled document may not be processable by an external service at all, and automated actions still fall under the tenant's retention rules. Both are cheaper to design around than to discover during a compliance review after launch.
Recover an Outlook-to-approval workflow safely
For a shared inbox approval flow, normalize each message or file event to the tenant, mailbox or site, stable item ID, change marker and received time before processing. Check the item's current state and the user's access before creating an approval task; use the tenant and item IDs as an idempotency key so event redelivery cannot create duplicate tasks. If a sensitivity label or retention rule blocks processing, stop and route the item to its owner rather than copying it elsewhere. Backfills should checkpoint completed items, respect service throttling with bounded backoff and resume from the last confirmed point. Keep approval outcome separate from message or document state, alert the named M365 owner on unresolved failures, and include app disablement, permission removal and credential rotation in the handover runbook.
How to measure the pilot
A pilot is accepted against the current process, not an industry promise. Agree the sample, baseline and owner before launch, then review the same measures after the workflow has handled real cases.