IT OPS

Route shared-mailbox requests through a Teams approval before provisioning

Receives a shared-mailbox request via webhook, posts an approval card to the IT channel in Teams, and only provisions the Outlook mailbox after a manager approves.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMailbox request received via webhookHTTP webhook
  • ActionPost approval card to IT channel in TeamsMicrosoft Teams
  • LogicBranch on approve vs reject decision
  • ActionProvision shared mailbox in Exchange OnlineShell
  • ActionGrant owners FullAccess in OutlookOutlook
  • OutputConfirm mailbox live and tag requester in TeamsMicrosoft Teams

What it does

Adds a lightweight approval gate in Microsoft Teams between a department's mailbox request and the actual Outlook provisioning, so unapproved or duplicate mailboxes never get created.

When to use it

Use this when shared-mailbox creation must stay controlled but you still want it self-service. A department lead submits a request form; IT approves with one click in Teams instead of working a ticket queue.

How it works

  1. 1An intake form posts the request (alias, display name, owners) to the workflow webhook.
  2. 2A Teams action posts an actionable approval card into the IT Operations channel showing the requested mailbox details.
  3. 3A logic step branches on the approver's response: rejected requests post a polite decline back to Teams and stop.
  4. 4On approval, a shell step provisions the shared mailbox in Exchange Online and sets the requested owners.
  5. 5An Outlook step applies FullAccess to the owners and confirms the mailbox is reachable.
  6. 6A final Teams message confirms the mailbox is live and tags the original requester.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect Microsoft TeamsChannels, chats, files.
  3. 3
    Connect ShellRun sandboxed commands inside the workspace.
  4. 4
    Connect OutlookMail, calendar, contacts.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.