Outlook Email to GitHub Issue

Overview

Watches a shared Outlook mailbox for tagged bug-report emails. When a new email arrives whose subject contains the configured bug prefix (default [BUG]), the flow creates a GitHub issue in the target repo using the email subject as the title and the email body as the issue description, then replies to the original sender with a link back to the issue for tracking.

Use Case

Convert unstructured bug reports from customers, stakeholders, or internal teams that land in a shared support inbox into structured, trackable issues in GitHub — without a human triaging every message. The sender gets an immediate confirmation reply so they know the report was captured.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Clone solution into target environment

Import the solution into the destination environment (Dev/Test/Prod) before configuring connections or values.

Set the four environment variables per deployment

Update flowlibs_SharedMailboxAddress, flowlibs_GitHubRepoOwner, flowlibs_GitHubRepoName, and flowlibs_BugSubjectPrefix to point at the right mailbox, repo, and subject prefix for that deployment.

Re-authorize Outlook and GitHub connection references

Bind the shared_office365 and shared_github connection references to accounts with the required permissions in the target tenant (Send As / Send On Behalf for the shared mailbox; write access to Issues in the target repo).

Add multi-repo routing

For additional routing (e.g. different prefixes going to different repos), duplicate the Condition and add sibling branches, each bound to its own set of env vars.

Swap GitHub for Azure DevOps

To file into Azure DevOps instead of GitHub, replace the Create GitHub Issue From Email action with the Azure DevOps Create a work item action and update the reply body URL template to point at the DevOps work item.

Turn the flow on

The solution ships with the flow in a Stopped state — enable it only after connections and env var values are confirmed for the target environment.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@contains(toLower(triggerOutputs()?['body/subject']), toLower(variables('varBugPrefix')))

@{trim(replace(toLower(triggerOutputs()?['body/subject']), toLower(variables('varBugPrefix')), ''))}

@{concat('**Reported by:** ', triggerOutputs()?['body/from'], '<br>**Received:** ', triggerOutputs()?['body/receivedDateTime'], '<br><br>', triggerOutputs()?['body/body/content'])}

outputs('Create_GitHub_Issue_From_Email')?['body/html_url']