# GitHub issue to Teams

> Post every new GitHub issue to a Microsoft Teams channel.

Recipe in the SAPUGO Marketplace. Free to install. Page: https://sapugo.com/marketplace/github-issue-to-teams

- Type: Workflow (Recipes)
- Publisher: SAPUGO
- Version: 1.0.0
- Updated: 2026-11-14
- Price: free on every plan
- Install: https://sapugo.app/blueprint/github-issue-to-teams

## Overview

Posts to a Microsoft Teams channel for every new GitHub issue, with the repository, number, title and link.

## Highlights

- Needs GitHub and Microsoft 365
- Choose the team and channel at install
- Repository, title and link in the post

## What it adds to a workspace

- Workflow (1): GitHub issue to Teams
- Business rule (1): GitHub issue to Teams

## Setup

- Install first: [GitHub](https://sapugo.com/marketplace/github)
- Install first: [Microsoft 365](https://sapugo.com/marketplace/microsoft-365)
- Setting: Team id
- Setting: Channel id

## Questions

### What does the GitHub issue to Teams recipe do?

Posts to a Microsoft Teams channel for every new GitHub issue, with the repository, number, title and link.

### Is the GitHub issue to Teams recipe free?

Yes. GitHub issue to Teams is free to install on every SAPUGO plan, including the Free plan. You only need a SAPUGO workspace.

### What does it add to my workspace?

It adds 1 workflow and 1 business rule to your SAPUGO workspace. Everything it adds is yours to rename, change or remove.

### What do I need to set it up?

It needs GitHub and Microsoft 365 installed first. During setup SAPUGO asks for: Team id and Channel id. Keys and secrets are entered in your own workspace. They are never part of the blueprint.

### Can I change it after installing?

Yes. A blueprint is a starting point, not a locked app. You can rename, extend or remove anything it adds, and install a newer version when one is published.

### Where is my data stored?

In your own SAPUGO workspace, in an isolated database hosted in the EU.

## Changelog

First release.