docs: document Workflows-based webhook setup replacing retired O365 connectors#123
Merged
Merged
Conversation
ahanoff
force-pushed
the
docs/update-webhook-setup-instructions
branch
7 times, most recently
from
5630eff to
e62c50a
Compare
…n to 2.1.0 Microsoft has retired the legacy Office 365 connectors / incoming webhooks in Microsoft Teams. The old URLs silently accept POSTs with 2xx but no longer deliver, so the action looks healthy while nothing arrives in the channel. Replace the inline step-by-step instructions with a one-liner that links to the canonical Microsoft Learn walkthrough (Create webhooks using Workflows). The MS docs are the source of truth here and we should not duplicate them; our copy was already drifting (template name changed, sample URL pattern may change again). Add a top-level GitHub admonition (> [!WARNING]) flagging the retirement so users with an existing MS_TEAMS_WEBHOOK_URI secret understand why their notifications silently stopped. Admonitions do not render when nested inside list items, so it sits above the numbered list. Refresh the sample workflow to actions/checkout@v7 (matches the version this repo's CI uses), add a placeholder comment showing where build/test/deploy steps go, and drop the version pin from the Known Issues note so it stops going stale. Bump version to 2.1.0 (minor): the Workflows-webhook requirement is a user-facing change in setup, not just a docs edit.
ahanoff
force-pushed
the
docs/update-webhook-setup-instructions
branch
from
e62c50a to
08bf090
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the README setup instructions to reflect that Microsoft has retired the legacy Office 365 connectors / incoming webhooks in Teams, and aligns the steps with the current Microsoft Learn walkthrough (updated Oct 2025).
Background
Microsoft has retired the legacy Office 365 connectors / incoming webhooks. The old-style URLs (
https://*.webhook.office.com/...orhttps://outlook.office.com/webhook/...) silently accept POSTs with a 2xx response but no longer deliver messages to the channel. From the action's side everything looks healthy (workflow job succeeds, response isok), but nothing arrives in Teams.What changes
Replaces the previous one-liner step 1 with concrete instructions for creating a Workflows-based incoming webhook via the Teams Workflows app. The steps now mirror the canonical Microsoft Learn article (Create an Incoming Webhook, last updated 2025-10-01):
https://prod-XX.<region>.logic.azure.com:443/workflows/.../triggers/manual/paths/invoke?...URLMS_TEAMS_WEBHOOK_URIsecretAlso adds:
> [!WARNING]GitHub admonition (replacing the previous> ⚠️emoji blockquote) describing the retirement of legacy connector URLs, so users with an existingMS_TEAMS_WEBHOOK_URIsecret understand why their notifications silently stopped.Note
The template name changed: previous versions of the MS docs called it "Post to a channel when a webhook request is received"; the current name (as of Oct 2025) is "Send webhook alerts to a channel". The README now uses the current name.
Scope
Docs-only change. No source or built artifact touched. Independent of #121 (test/code) and #122 (CI bump, already merged).