Microsoft Teams is deprecating the old Office365 connection mechanism to post messages to team channels. This change affects all Flare users who rely on Flare notifications sent to Microsoft Teams.
To get these notifications working again. A new endpoint must be retrieved to which the notifications should be sent.
Since Microsoft stopped supporting the creation of webhooks using Office365 connections, all new Microsoft Teams connections within Flare will automatically use the new system.
We'll keep sending notifications to the old webhook URLs until the end of September 2024. After September, Microsoft will stop accepting these payloads, so update your webhook URL as quickly as possible!
Let's take a look at how to receive the new webhook URL!
Getting a Microsoft Teams notifications webhook URL
In Microsoft Teams, add or open the Workflows app (this is an application built by Microsoft to allow automation in Teams):

Next, create a "New Flow"

Microsoft Teams provides a few templates for typical flows, we 're going to create one from scratch:

Now a trigger for the flow should be selected; search for "webhook" and select "When a Teams webhook request is received":

Make sure that "Anyone" (and thus Flare) can post to this Webhook:

Add a new step and, search for "post" and select "Post card in chat or channel":

Configure the step with the following options:
- Post as: Flow bot
- Post in: Channel
- Team: Select the team you want to post to
- Channel: Select the channel you want to post to

For the Adaptive card entry, click on "Add dynamic content" and select the "Expression" tab:

Type in: triggerBody() and hit enter:

Hit the save button:

Then select the webhook URL from the "When a Teams webhook request is received" step:

Use this URL in the Flare dialog to receive Flare notifications in Microsoft Teams:

Continue reading
Create richer issues from your errors
When Flare creates an issue on GitHub, GitLab or Linear, you can now pick the assignee and labels right away.
Ruben
One core, many clients: the new Flare JavaScript client architecture
We recently reshaped the Flare JavaScript client from a single browser library and a few thin framework specific packages into a small family of packages built on a shared, platform-agnostic core. This post explains why we did it, what the core package exposes, how the browser and Node SDKs are built on top of it, why the React, Vue, and Svelte packages sit one level higher, and how anyone can use the same core to write a Flare JS client for a platform we do not ship ourselves.
Dries
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates