Moving an AI intake-triage task off a retiring platform
An intake-triage automation had to move off its platform because Microsoft was retiring it on June 30, 2026, not because anyone asked for a redesign. Before writing a single build step, the work went to confirm exactly what the replacement could and couldn't do, and that check caught a real platform limitation that would have broken the build if it had gone unnoticed.
Category
Automation continuity through a platform migration.
What I was trying to accomplish
Recreate an existing intake-triage automation on tools the firm would keep, before Microsoft retired the Copilot Cowork preview it was originally built on.
The data challenges
Confirming upfront exactly what the new tool's own connector could and couldn't do (read and search only, no scheduling or writing), then catching a real platform limitation, a standard action couldn't set categories on a shared mailbox, before it became a false assumption baked into the build.
The result
A paste-ready build guide using a mail-triggered automation flow instead of the original hourly timer, that only reads and tags mail, never sends, replies, moves, or deletes. The work then continued with my operations assistant, with my guidance, as a person-started process rather than an unattended one.
Technical details
Tools: Claude Cowork, Microsoft Power Automate with AI Builder (design), Microsoft Graph (design)
New-client inquiries from the firm's website landed in a shared inbox, and reception had to read each one to decide which practice group should get it. The firm had written a detailed categorization prompt and run it as an hourly scheduled task in Microsoft's Copilot Cowork preview. That preview was ending on June 30, 2026, so the goal was to recreate the same task on tools the firm would keep.
In one Claude Cowork session I worked through the options. Claude first confirmed what its own Microsoft 365 connection could and could not do, so the recurring job had to live in Microsoft's automation platform. It proposed a Power Automate flow with an AI Builder prompt step, triggered when mail arrives rather than on a timer. Before writing the build steps, Claude checked the one action it was unsure of and found a real limitation: the standard action cannot set categories on a shared mailbox, so the design uses a Graph API request instead.
The output was a paste-ready build guide with the classification prompt adapted for AI Builder, revised once when the category names actually created in Outlook did not match the plan. The project then continued with my operations assistant, who took it forward in Claude, with guidance from me, as a person-started session that drafts hand-off emails for review rather than as an unattended flow.
Pull up a chair.
Let's talk through where things stand, and where they could go.