NetEvolve.HealthPublishers.MicrosoftTeams 1.13.10

Prefix Reserved
dotnet add package NetEvolve.HealthPublishers.MicrosoftTeams --version 1.13.10
                    
NuGet\Install-Package NetEvolve.HealthPublishers.MicrosoftTeams -Version 1.13.10
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="NetEvolve.HealthPublishers.MicrosoftTeams" Version="1.13.10" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="NetEvolve.HealthPublishers.MicrosoftTeams" Version="1.13.10" />
                    
Directory.Packages.props
<PackageReference Include="NetEvolve.HealthPublishers.MicrosoftTeams" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add NetEvolve.HealthPublishers.MicrosoftTeams --version 1.13.10
                    
#r "nuget: NetEvolve.HealthPublishers.MicrosoftTeams, 1.13.10"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package NetEvolve.HealthPublishers.MicrosoftTeams@1.13.10
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=NetEvolve.HealthPublishers.MicrosoftTeams&version=1.13.10
                    
Install as a Cake Addin
#tool nuget:?package=NetEvolve.HealthPublishers.MicrosoftTeams&version=1.13.10
                    
Install as a Cake Tool

NetEvolve.HealthPublishers.MicrosoftTeams

NuGet Version NuGet Downloads License

An IHealthCheckPublisher implementation that pushes HealthReport results to a Microsoft Teams channel, using an incoming webhook or a Power Automate workflow connector, posting an Adaptive Card directly over HTTP.

Features

  • Posts a single Adaptive Card per publish, summarizing the overall report status, elapsed time, and a per-check breakdown
  • Maps HealthStatus to an Adaptive Card text color (Healthygood, Degradedwarning, Unhealthyattention)
  • Tags every card with the machine name and a required, free-form SystemIdentifier to tell instances apart
  • Configuration- or builder-based setup, consistent with the NetEvolve.HealthChecks.* conventions
  • Named registrations to publish to multiple Microsoft Teams channels side by side
  • No Microsoft Teams/Bot Framework client dependency - just HttpClient via IHttpClientFactory
  • Debounces notifications instead of posting on every publish: a worsening status is posted immediately, while an improving status must stay sustained for a configurable delay before a "recovery" card is posted

Installation

NuGet Package Manager

Install-Package NetEvolve.HealthPublishers.MicrosoftTeams

.NET CLI

dotnet add package NetEvolve.HealthPublishers.MicrosoftTeams

PackageReference

<PackageReference Include="NetEvolve.HealthPublishers.MicrosoftTeams" Version="x.x.x" />

Quick Start

using NetEvolve.HealthPublishers.MicrosoftTeams;

var builder = services.AddHealthChecks();

builder.AddMicrosoftTeamsPublisher(options =>
{
    options.WebhookUrl = new Uri("https://example.webhook.office.com/webhookb2/...");
    options.SystemIdentifier = "checkout-service";
});

Usage

Basic Example

Register under the default name ("Default"), configured via code:

var builder = services.AddHealthChecks();

builder.AddMicrosoftTeamsPublisher(options =>
{
    options.WebhookUrl = new Uri("https://example.webhook.office.com/webhookb2/..."); // Required
    options.SystemIdentifier = "checkout-service"; // Required, tags the card alongside the machine name
});

Notification Behavior

The publisher keeps track of the HealthStatus it last actually posted about (per registered instance) and does not post a card for every PublishAsync call:

  • Same status as last notified: no card is posted.
  • Worsening status (e.g. HealthyDegraded, DegradedUnhealthy, or HealthyUnhealthy): a card is posted immediately, regardless of RecoveryConfirmationDelay.
  • Improving status (e.g. DegradedHealthy, UnhealthyDegraded, or UnhealthyHealthy): the improvement must be sustained for at least RecoveryConfirmationDelay before a "recovery" card is posted. If the status regresses back to the last-notified status before the delay elapses, no card is posted and the delay resets; a later improvement starts a new delay from scratch. If the status regresses to something worse than the last-notified status instead, that is treated as a new worsening event and is posted immediately.

Advanced Example

Register multiple named Microsoft Teams targets, each pushing the same health reports to a different channel:

var builder = services.AddHealthChecks();

builder.AddMicrosoftTeamsPublisher("Ops", options =>
{
    options.WebhookUrl = new Uri("https://example.webhook.office.com/webhookb2/ops...");
    options.SystemIdentifier = "checkout-service";
});
builder.AddMicrosoftTeamsPublisher("OnCall", options =>
{
    options.WebhookUrl = new Uri("https://example.webhook.office.com/webhookb2/oncall...");
    options.SystemIdentifier = "checkout-service";
});

Configuration

Code-based

builder.AddMicrosoftTeamsPublisher(options =>
{
    options.WebhookUrl = new Uri("https://example.webhook.office.com/webhookb2/..."); // Required
    options.SystemIdentifier = "checkout-service"; // Required
    options.RecoveryConfirmationDelay = TimeSpan.FromMinutes(10); // Optional, defaults to 5 minutes, minimum 5 minutes
});

appsettings.json-based

builder.AddMicrosoftTeamsPublisher(); // reads the "Default" section below
{
  "HealthPublishers": {
    "MicrosoftTeams": {
      "Default": {
        "WebhookUrl": "https://example.webhook.office.com/webhookb2/...",
        "SystemIdentifier": "checkout-service",
        "RecoveryConfirmationDelay": "00:10:00"
      }
    }
  }
}

When using an explicit name, the section key must match: builder.AddMicrosoftTeamsPublisher("Ops") reads HealthPublishers:MicrosoftTeams:Ops.

Requirements

  • .NET 8.0 or higher
  • A Microsoft Teams incoming webhook, or a Power Automate workflow configured to receive Adaptive Cards

Documentation

For complete documentation, please visit the official documentation.

Contributing

Contributions are welcome! Please read the Contributing Guidelines before submitting a pull request.

Support

License

This project is licensed under the MIT License - see the LICENSE file for details.


Made with ❤️ by the NetEvolve Team Visit us at https://www.daily-devops.net for more information about our services and solutions.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.13.10 26 8/23/2026