To learn how to install and use the GitHub integration in Teams please refer to our docs

The data residency version of the Microsoft Teams app can be installed from AppSource here.

We are announcing GA for GHES integration with Microsoft Teams with GHES 3.8.

With this integration, you will now be able to subscribe to your repositories in your GHES instance and get live updates about your Issues, PRs, Commits and Deployments in your MS teams channels and personal app. And you can also take actions like commenting, open/close issues and approve your deployments directly from chat.

Starting with GHES 3.8, we are shipping a dedicated ChatOps service bundled along with your GHES server. And you can choose to integrate with Microsoft Teams. With our integration for GHES, you will have

1. A fully secure and scalable experience: All your subscriptions info and any other metadata stays within your GHES setup. So, you don't have to worry about data flowing to any external service.

2. Connectivity between GHES and Azure Bot: Our GHES integration is not just a notification service. It will also enable you to perform actions directly from chat. So, the only prerequisite you need is to ensure your GHES instance is accessible from Azure Bot that is deployed when MS Teams integration is set up on GHES.

The existing GitHub app you see in the app store can only be used for GHEC (hosted GitHub) integration. To integrate your GHES instance with MS Teams, you need to configure a private GHES app. Here are the steps to integrate with GHES.

1. Navigate to "your-ghes-url:8443" and go to section “Chat Integrations”

2. Select the checkbox Enable GitHub Chat Integration
3. Select MS teams tab
4. Register application on Azure portal by going to the link mentioned.
5. Enter your application registration name and for account type select “Multi-tenant” and click “Register

6. Take note of application ID and tenant ID

7. Click on “Certificates & secret” and generate a new client secret.
8. Take note of application ID, tenant ID and client secret and navigate back GHES instance settings
9. Click on Deploy to Azure button

10. Select the subscription and resource group for Azure bot to be deployed. Enter the GHES hostname, the app ID and tenant ID previously generated and click Review + create.

    • If your GitHub Enterprise instance is reachable on the public internet make sure that the Append '_msteams' to path option is checked.
    • If your GitHub Enterprise instance is not reachable on the public internet and requires a proxy make sure that the Append '_msteams' to path option is unchecked. Also, enter the URL that will forward the traffic to the instance in GHES Instance Host Name.

11. Once the bot is provisioned. Return to the settings page and enter the app ID, tenant ID and client secret. If the GHES endpoint is not reachable on public internet and the traffic is going to be forwarded enter that URL in Public Endpoint URL. Click on Save client settings.

12. Once the settings are saved download the manifest from the generate manifest button. Click on green Save settings to persist the settings on the instance. Once settings are applied (could take 5-15 mins depending on the configuration).

13. Upload the manifest to MS teams app. Steps here

And now you have a dedicated GHES integration with Microsoft teams. All the features that are available in our hosted GitHub integration (GHEC) will be available in GHES integration.

If you need support or help please fill out GitHub's Support form and your request will be routed to the right team at GitHub.