An undo button for messages moved to the wrong folder

One wrong drag, and messages were hard to find

When a user dragged a batch of messages into the wrong folder, Outlook offered no simple way back. Working out what moved, when, and where it came from meant searching by hand, often by the support team.

Detect, record, confirm, restore

1. 1

   Discovery and approvals

   Confirmed the process, the target mailboxes, admin consent, retention and success criteria.

2. 2

   Detect moves

   Set up Microsoft Graph subscriptions that detect folder moves in Exchange Online mailboxes in near real time.

3. 3

   Record each move

   Built an Azure Function that records each move (who, when, from where and to where) in a short-term store kept for 72 hours.

4. 4

   One-click undo

   Added a Teams Adaptive Card and an Outlook actionable message with Undo, Ignore and View Details buttons.

5. 5

   Ask the agent

   Built a Copilot Studio agent that understands requests like "Undo the last message move" and asks for confirmation first.

6. 6

   One secured restore path

   Routed every restore through one secured service with role-based access and audit logging that respects legal holds and Purview retention.

7. 7

   Pilot and handover

   Piloted and hardened it, testing throttling, retries and unsafe requests, then delivered documentation and training.

Users undo their own mistakes, safely

Orbis users can now reverse an accidental folder move themselves, from a card in Teams or Outlook or by asking the Copilot agent. Every restore is confirmed first and logged for audit, and the support team no longer has to trace moved messages by hand.

• Folder moves detected in near real time
• Undo from Teams, Outlook or the Copilot agent
• Every restore confirmed first and logged
• Restores respect legal holds and retention

• Microsoft Graph
• Azure Functions
• Copilot Studio
• Teams Adaptive Cards
• Exchange Online