How to Update Webhook URLs for Microsoft Teams due to Webhook Connector Retirement

Microsoft is changing how Teams webhooks are implemented, so any pre-existing webhooks will stop working after the retirement date of January 31, 2025 unless they are updated to the new URL structure.

First published date

1/10/2025 10:58 PM

Last published date

2/6/2026 9:18 PM

Overview

Microsoft is updating its Webhook-based connectors within the O365 Connectors service in Teams to a new URL structure. If you use SolarWinds products to send messages to Teams via webhooks or a Teams integration, you’ll need to update your configurations before January 31, 2025 to ensure they continue to work. 

The SolarWinds Platform, SolarWinds Observability SaaS, DPA, Loggly, Pingdom, and SQL Sentry are affected by this change.

 

Resolution

Known issues and recommendations

Workflows cannot send messages to a Private Channel

Workflows cannot send messages to a Private Channel. If you are currently using Webhooks in a Private Channel (indicated by a lock icon next to the Channel name), you will need to perform the following:

  1. Create a Private Team with the same people as the Private Channel.
  2. Create a Public Channel inside the Private Team.
  3. Create the Workflow and integrate it as mentioned above.

Generation one SaaS customers: consider migrating to SolarWinds Observability SaaS

Microsoft's recent changes to Teams webhooks may impact users of AppOptics, Loggly, Papertrail, and Pingdom who were using Microsoft Teams webhooks (if supported) for notifications. For AppOptics, Papertrail, and Pingdom, updating the connector-based webhook URL may temporarily extend functionality until Microsoft phases out support (follow the same instructions as for DPA, found here). Loggly has already updated to support the new workflow-based webhooks that have broader support from Microsoft (follow instructions here).

However, to ensure continued compatibility and access to improved alerts, SolarWinds strongly recommends all generation one SaaS (AppOptics, Loggly, Papertrail, and Pingdom) customers migrate to SolarWinds Observability SaaS. SolarWinds Observability SaaS offers streamlined Teams webhook integration for all users, along with enhanced alerting capabilities and ongoing support for future updates.

 

Workflow and webhook reliability

Teams webhooks and Power Automate flows are not “set and forget” integrations. Even after you update to the new webhook URL format, there are several Microsoft‑controlled behaviors that can cause notifications to silently stop unless they are monitored and maintained.

To ensure uninterrupted event delivery, customers should monitor Microsoft service communications and review their flows regularly.

 

Potential causes of missed or disabled webhook notifications

  • Webhook trigger URLs can change over time
    Microsoft may update Power Automate webhook trigger URLs or Teams infrastructure as part of platform changes or migrations. When this happens, existing URLs can stop working if they are not updated in your SolarWinds alert or notification configuration.

    • Recommended action: Monitor Microsoft communications (for example, Message Center, admin emails, and Power Automate change notices) and update any configured webhook endpoints in SolarWinds when Microsoft instructs you to rotate or replace a URL.
  • Flows can be automatically disabled due to inactivity
    Event‑driven flows that trigger only when something rare happens (for example, a critical alert condition) can go more than 90 days without any runs. Power Automate may treat these flows as inactive and automatically disable them, even though they are still business‑critical.
    • Impact: The SolarWinds product will continue sending events, but nothing in Power Automate will be listening, so no Teams messages are posted.
    • Recommended actions: Consider adding a low‑impact recurrence (“keep‑alive”) trigger or scheduled test run (for example, every 60–80 days) so the flow stays active even if no real alerts occur.
    • Alternatively, run the flow manually with a test payload on a regular schedule if adding a recurrence is not possible.
    • Work with your Power Platform administrators to exempt critical flows from cleanup policies or mark them as business‑critical where possible.
  • Teams/Power Automate connections may require re‑authentication
    Teams actions in a flow (such as posting a message to a channel or sending an Adaptive Card) depend on a user‑based connection. These connections can require periodic re‑authentication when passwords change, MFA or conditional access policies are updated, or the owning user account is disabled or leaves the company.
    • Impact: Flows may continue to run, but the Teams step fails and no message is delivered, sometimes with the only notification being an email to the original flow owner.
    • Recommended actions: Use a monitored service account (or centrally managed account) as the connection owner for critical Teams flows.
    • Regularly review Power Automate for any connections that show “needs attention” and re‑authenticate as required.
    • Avoid having critical integrations depend solely on an individual user’s personal account and inbox.

Operational best practices

For business‑critical alerts, we recommend the following operational practices in addition to the configuration steps in this article:

  • Use service accounts for workflow ownership
    Assign critical Teams flows to a service account or shared mailbox that is actively monitored, so disablement and re‑authentication emails are not missed when individuals are on vacation or leave the organization.

  • Separate test, “keep‑alive,” and production channels
    Use dedicated channels for:

    • Day‑to‑day production alerts
    • Test or development flows
    • Keep‑alive or scheduled test messages
      This helps you confirm that flows are still functioning without adding noise to your primary alert channel.

  • Test integrations regularly
    Periodically send a test alert from the SolarWinds product through to Teams to confirm that:

    • The webhook URL is still valid
    • The Power Automate flow is enabled
    • The Teams connection is authenticated and has access to the target team/channel

  • Treat webhook URLs as secrets
    Webhook and workflow URLs can be used by anyone who has them to post messages into your Teams channels. Store them securely (for example, in a password vault) and avoid sharing them in screenshots, documentation, or public forums.

 

Update your Teams alert notifications for SolarWinds Platform, SolarWinds Observability SaaS, and Loggly

If you have set up to use either a webhook or a Teams notification to send alerts to Teams, you need to update their webhook in Teams, then update the alert settings to use the new URL. This is the case both for native Teams integrations and for alerts that send messages to webhooks generically. If you send notifications to Teams, perform the following 2 steps. 

  1. Create a new Teams webhook with Workflows for Microsoft Teams.
  2. Follow the links for instructions for the products listed below to update the webhook URL in the alert/notification settings of the SolarWinds application.
    Note: SolarWinds Platform users may also need to update your custom JSON (also referred to as a Payload) configuration in your alert notification settings to support the Adaptive Card format, as the message card format will no longer be supported in Workflows. For more information, see how to convert connector message card format to Adaptive Card and Microsoft Retiring Office365 Connectors.

Update your Teams alert notifications for DPA and SQL Sentry

DPA and SQL Sentry currently only support connector-based Teams webhooks, though some connector-based webhook URLs may be too long to be supported in SQL Sentry. In the meantime, connector-based URLs used in either DPA or SQL Sentry need to be updated using the steps below.

  1. Update the Teams webhook using Microsoft instructions at Manage Microsoft 365 connectors and custom connectors.
  2. Update the webhook URL in the application:

 

If Teams notifications stop unexpectedly

If you stop receiving Teams messages from SolarWinds but alerts are still occurring in the product, we recommend checking the following in Microsoft Power Automate and Teams:

  1. Confirm the Power Automate flow is still enabled and has recent successful runs.
  2. Verify that the connection used for Teams actions does not show “needs attention” and re‑authenticate if required.
  3. Ensure the webhook or workflow URL configured in SolarWinds exactly matches the current URL shown in the Power Automate trigger.
  4. Check with your Microsoft 365 / Power Platform administrators for any recent policy changes, connector retirements, or governance rules that might have disabled or blocked the flow or connector.

 

Note: Connector-based Teams webhooks will stop working entirely at the end of 2025, even if they are updated using the steps above. Before the end of the year, DPA users will need to upgrade to a version of DPA that has been updated to provide support for Workflow-based webhooks. After upgrading, you must create a new Workflow-based webhook URL for use in the application.

Please note that THWACK is a community space where users may post any content as a suggestion or recommendations to you for your internal use. The information set forth herein may come from third-party websites or customers. SolarWinds is not liable for any downtime or any issue that may occur if you perform the following suggestions on the link provided. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.