Mirror GitHub bug issues into Microsoft Planner

Build a code-based workflow that mirrors GitHub bug issues into Microsoft Planner so PMs and non-engineering stakeholders can track bugs without living in GitHub.

Trigger: a webhook subscribed to a GitHub repository's issues events. Only fire on the opened and labeled actions, and only when the issue carries the bug label (the label name should be a configurable input so I can change it later).

When the webhook fires, do the following in order:

1. Deduplicate. Look at the issue body from the webhook payload. If it already contains a Planner task URL (substring check for tasks.office.com or planner.microsoft.com), stop and exit successfully. This keeps the workflow idempotent when the bug label is removed and reapplied.

2. Read the latest issue. Call GitHub's Get an Issue operation with the repo owner, repo name, and issue number from the webhook payload, so we work from the current title, body, assignees, and labels rather than stale payload data.

3. Find the triage bucket. Call Microsoft Planner's List Buckets in Plan operation against the engineering plan ID I provide as input, then pick the bucket whose name matches my configured bucket name (default 'Triage', case-insensitive). If no bucket matches, fail with a clear error so I know to fix the configuration.

4. Create the Planner task. Call Microsoft Planner's Create Task with this mapping: planId is my engineering plan ID; bucketId is the bucket from step 3; title is the GitHub issue title (truncate to Planner's title limit if needed); assignments contains one plannerAssignment entry per GitHub assignee whose verified email matches a Microsoft user in my tenant. Put the GitHub issue body into the task description and add the GitHub issue HTML URL as an external reference titled 'GitHub Issue' so it shows up under Planner's links section. If a GitHub assignee can't be matched to a Microsoft user, list them by handle in the description so the task owner can reassign manually.

5. Cross-link back to GitHub. Call GitHub's Create an Issue Comment on the original issue with a short message like 'Tracked in Planner: <task URL>' that includes the Planner task ID and a direct link to the new task. This is the piece that makes the integration actually useful day to day, so don't skip it.

Inputs I want to be able to configure without editing code: GitHub repo owner and name, the bug label name, the Microsoft 365 group ID and plan ID, and the destination bucket name. Integrations: github and microsoft-planner.