Microsoft disabled Office 365 Connectors in Teams between May 18 and May 22, 2026. Scripts, monitoring tools and CI pipelines that still post to a connector webhook URL no longer reach their channel. Here is how to find each sender, move it to a Workflows webhook, or pick a bot or Microsoft Graph instead.
| Date | What Microsoft announced |
|---|---|
| July 3, 2024 | Retirement announced; the deadline later moved to the end of 2025, March 31, 2026 and April 30, 2026. |
| November 30, 2025 | Workflows URLs containing logic.azure.com stop working in environments on the Logic Apps architecture; the flow's trigger card shows the new one. |
| February 5, 2026 | Workflows webhooks accept MessageCards and can post to shared channels. |
| April 14, 2026 | Final schedule; private channels supported through the Power Automate portal. |
| May 18–22, 2026 | Connectors disabled in stages; after that they no longer function. |
webhook.office.com and webhookb2 (a Microsoft Q&A moderator refers to the old endpoints as *.webhook.office.com/webhookb2/...) and for MessageCard JSON: "@type": "MessageCard", potentialAction.1, and that throttling shows up in the body (Microsoft Teams endpoint returned HTTP error 429), not as a 429 status. Replace both checks.*.webhook.office.com, and alert channels that went silent between May 18 and May 22, 2026, point to the rest.Get-AdminFlowWithMigratingTriggerUrl -EnvironmentName <name> (module Microsoft.PowerApps.Administration.PowerShell). Since June 2, 2026, HTTP and Teams webhook trigger URLs can also include a scale-unit segment (for example, /direct/cu/20/workflows/... instead of /direct/workflows/...); Microsoft recommends the new URL for better performance and says the old one keeps working.sig= key of HTTP trigger URLs). Allow for URLs over 255 characters, and in the commercial cloud open *.api.powerplatform.com and *.logic.azure.com on outbound firewalls.The trigger accepts Anyone, Any user in my tenant or Specific users in my tenant. For token claims, the Teams connector reference points to Power Automate's docs for its HTTP request trigger, which call Anyone a legacy setting. The two tenant options need a bearer token whose aud is exactly https://service.flow.microsoft.com/ (public cloud, trailing slash included), plus iss and tid, and oid for specific users, which can include a service principal's object ID. With Anyone, send no Authorization header, or requests fail.
The trigger takes Adaptive Card attachments or a single MessageCard, so a MessageCard without buttons may need only the new URL. To convert:
TextBlock elements; facts (name, value) become a FactSet (title, value); OpenUri becomes Action.OpenUrl."markdown": false).themeColor, and Microsoft's MessageCard reference calls it a brand color, not a status signal. For a visual cue, give a Container a style such as attention; the schema calls this a style hint, so check how Teams shows it.Action.Submit.Before, a MessageCard (its button won't render on Workflows):
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"themeColor": "D70000",
"summary": "Disk space low on SRV01",
"sections": [{
"activityTitle": "Disk space low on SRV01",
"facts": [ { "name": "Drive", "value": "D:" }, { "name": "Free", "value": "4%" } ],
"markdown": true
}],
"potentialAction": [{
"@type": "OpenUri",
"name": "Open dashboard",
"targets": [ { "os": "default", "uri": "https://monitor.example.com/srv01" } ]
}]
}
After, as an Adaptive Card:
{
"type": "message",
"attachments": [{
"contentType": "application/vnd.microsoft.card.adaptive",
"contentUrl": null,
"content": {
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.2",
"msteams": { "width": "Full" },
"body": [
{ "type": "TextBlock", "text": "Disk space low on SRV01", "weight": "Bolder", "size": "Medium", "wrap": true },
{ "type": "FactSet", "facts": [ { "title": "Drive", "value": "D:" }, { "title": "Free", "value": "4%" } ] }
],
"actions": [
{ "type": "Action.OpenUrl", "title": "Open dashboard", "url": "https://monitor.example.com/srv01" }
]
}
}]
}
Microsoft recommends exponential backoff on HTTP 429. If a request succeeds but no card appears, check the flow's run history in Power Automate.
using System.Text;
// The Workflows URL is a secret: keep it in configuration, not in source code.
var webhookUrl = Environment.GetEnvironmentVariable("TEAMS_WORKFLOW_URL")
?? throw new InvalidOperationException("TEAMS_WORKFLOW_URL is not set");
var cardJson = await File.ReadAllTextAsync("card.json"); // the Adaptive Card message above
using var http = new HttpClient();
for (var attempt = 1; ; attempt++)
{
using var content = new StringContent(cardJson, Encoding.UTF8, "application/json");
using var response = await http.PostAsync(webhookUrl, content);
if (response.IsSuccessStatusCode) break; // request succeeded
if ((int)response.StatusCode == 429 && attempt < 5) // throttled: back off and retry
{
await Task.Delay(response.Headers.RetryAfter?.Delta ?? TimeSpan.FromSeconds(Math.Pow(2, attempt)));
continue;
}
response.EnsureSuccessStatusCode(); // throws with the status code
}
In PowerShell 7, Invoke-RestMethod retries only if you set -MaximumRetryCount. It then retries on a 304 or any 400–599 status; on a 429 with a Retry-After header, it waits that long instead of -RetryIntervalSec. Windows PowerShell 5.1 has neither parameter. Set -Depth: ConvertTo-Json stops at two levels by default.
$card = @{
type = 'message'
attachments = @(@{
contentType = 'application/vnd.microsoft.card.adaptive'
contentUrl = $null
content = @{
'$schema' = 'http://adaptivecards.io/schemas/adaptive-card.json'
type = 'AdaptiveCard'
version = '1.2'
body = @(
@{ type = 'TextBlock'; text = "Backup failed on $([Environment]::MachineName)"; weight = 'Bolder'; wrap = $true }
@{ type = 'FactSet'; facts = @(@{ title = 'Time'; value = (Get-Date -Format u) }) }
)
}
})
}
Invoke-RestMethod -Method Post -Uri $env:TEAMS_WORKFLOW_URL `
-ContentType 'application/json; charset=utf-8' `
-Body ($card | ConvertTo-Json -Depth 10) `
-MaximumRetryCount 4 -RetryIntervalSec 5
In CI, add --fail: by default curl doesn't treat HTTP errors as failures.
curl --fail --silent --show-error --retry 4 \
-H "Content-Type: application/json; charset=utf-8" \
--data-binary @card.json "$TEAMS_WORKFLOW_URL"
| Limit | Value |
|---|---|
| Message size | About 28 KB; larger posts fail with Request Entity too large. |
| Burst rate | Over four requests a second gets the client throttled. |
| Flow bot posts | 25 non-GET calls per connection per 300 seconds. |
| Trigger calls | 4,500 per 5 minutes on the Low profile (Microsoft 365 licenses), 45,000 on higher ones. |
| Daily actions | About 10,000 Power Platform requests a day on Low; each action counts. |
| Idle or failing flows | No trigger for 90 days: may be turned off after 30 days' notice (premium-licensed owners and Process-licensed flows are exempt), a risk for rare alerts. Failing for 14 days straight: turned off. |
| Identity | The Flow bot or a user; no custom name or icon. No Flow bot in GCC, GCC High or DoD. |
POST /teams/{team-id}/channels/{channel-id}/messages with delegated ChannelMessage.Send (ChatMessage.Send for chats). Application permissions are supported only for migration (message import), so an unattended job would have to post with a user's delegated token. Using Teams as a log file violates Microsoft's terms.