Skip to content

docs: document Workflows-based webhook setup replacing retired O365 connectors #123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ahanoff merged 1 commit into from
Jun 19, 2026
Merged

docs: document Workflows-based webhook setup replacing retired O365 connectors #123

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,12 @@

### Usage

1. Add `MS_TEAMS_WEBHOOK_URI` on your repository's configs on Settings > Secrets. It is the [webhook URI](https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook) of the dedicated Microsoft Teams channel for notification.
> [!WARNING]
> Microsoft has [retired the legacy Office 365 connectors / incoming webhooks](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/). URLs that look like `https://*.webhook.office.com/...` or `https://outlook.office.com/webhook/...` are no longer delivered. A Workflows-based webhook (below) is required.

2) Add a new `step` on your workflow code as last step of workflow job:
1. Create a **Workflows-based incoming webhook** in Microsoft Teams and add it as the `MS_TEAMS_WEBHOOK_URI` secret in your repository's **Settings → Secrets and variables → Actions**. See [Create webhooks using Workflows](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=dotnet#create-webhooks-using-workflows) in the Microsoft Learn docs for instructions.

2. Add a new `step` on your workflow code as last step of workflow job:

```yaml
name: MS Teams Github Actions integration
Expand All @@ -16,7 +19,8 @@ jobs:
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v7
# ... your build / test / deploy steps go here ...
- uses: opsless/ms-teams-github-actions@main
if: always() # to let this step always run even if previous step failed
with:
Expand All @@ -26,7 +30,7 @@ jobs:

### Known Issues

- Always set this step with `if: always()` when there are steps between `actions/checkout@v2` and this step.
- Always set this step with `if: always()` when there are steps between `actions/checkout` and this step.

### Roadmap

Expand Down
4 changes: 2 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@opsless/ms-teams-github-actions",
"version": "2.0.1",
"version": "2.1.0",
"private": true,
"description": "MS Teams Github Actions integration",
"main": "lib/main.js",
Expand Down