Weave Code
Microsoft Teams Laravel Package
laravel-notification-channels/microsoft-teams
Send notifications to Microsoft Teams from your Laravel app. This channel plugs into Laravel's notification system so you can post rich MessageCard or Adaptive Card messages to Teams channels via incoming webhooks, all through a clean, familiar API.
A Laravel Notification Channel for Microsoft Teams
Frequently asked questions about Microsoft Teams
- How do I send a Laravel notification to Microsoft Teams?
- Install the package with Composer, configure a Microsoft Teams incoming webhook URL, add a toTeams() method to your notification class, and route the notification to the Teams channel. It plugs into Laravel's native notification system, so you can reuse your existing notification classes and routing patterns. No database migration or frontend work is required.
- Does this package support Laravel 13?
- Release 2.2.1 removes static from closures to restore Laravel 13 compatibility, so it is the baseline to target. The patch is described as a low-risk compatibility fix with no breaking changes, new features, deprecations, or payload changes. Verify that your lockfile resolves cleanly and confirm whether your target Laravel version is covered in the package's declared support matrix and CI.
- How do I install and configure laravel-notification-channels/microsoft-teams?
- Install it with Composer, configure the Teams webhook URL, add a toTeams() method to your notification, and route notifications to the channel. The setup is small for a standard Laravel/PHP stack and does not require migrations or frontend changes. Pin to 2.2.1, or use a ^2.2 constraint only if your team accepts patch-level drift, and verify the lockfile resolves cleanly.
- Does this package support queued notifications, retries, and failed-job handling?
- Because the channel extends Laravel's notification system, queued notifications are generally handled through Laravel's queue and failed-job mechanisms, but confirm channel-specific behavior for your version. The technical assessment lists queued notifications, retries, backoff, and failed-job handling as key questions rather than confirmed package features. Test queue workers, retry behavior, and failure paths in a non-critical Teams channel before relying on it for critical alerts.
- Which Microsoft Teams endpoint types does this package support: incoming webhook, Workflows, or Graph API?
- The package is described as posting messages to Teams channels via incoming webhooks. The assessment specifically flags verification of whether the current release targets legacy Office 365 Incoming Webhook, Power Automate/Teams Workflows, or Graph API. Do not assume all endpoint types are supported; confirm compatibility with your Teams tenant and connector policy before standardizing.
- Can I send MessageCard or Adaptive Card messages to Microsoft Teams with this channel?
- The package is described as posting rich MessageCard or Adaptive Card messages to Teams channels via incoming webhooks. Rendering depends on your Teams tenant, endpoint type, and connector policy, so validate the emitted card schema in a test channel. Confirm that your target endpoint accepts the card format you need before using it for operational alerts.
- Can I route Microsoft Teams notifications per notification or per tenant?
- The assessment lists per-notification versus per-tenant webhook routing as a key question, so treat routing flexibility as something to verify rather than assume. Basic setup configures a Teams webhook URL and routes notifications to that channel. If you need multi-tenant routing, test whether webhook selection can be set per notification or per tenant in your implementation.
- Is laravel-notification-channels/microsoft-teams safe for production use?
- It is MIT licensed and fits cleanly into Laravel notifications, but the assessment rates technical risk medium-high because the critical dependency is Microsoft's Teams connector lifecycle, not Laravel. Risks include webhook URL secrecy, Teams throttling, card-format compatibility, low ecosystem signals, and maintainer bus factor. Proceed with a security-reviewed proof of concept in a non-critical Teams channel and define a fallback path such as email, Slack, or PagerDuty.
- What are the alternatives to this package for Laravel Microsoft Teams notifications?
- Alternatives include calling a Teams webhook directly, using Microsoft Graph API, or routing through another notification channel such as email, Slack, or PagerDuty as a fallback. The package's value is that it plugs into Laravel's native notification system with a toTeams() method, avoiding custom webhook code. Evaluate endpoint lifecycle support and tenant policy compatibility before choosing a custom integration instead.
- Who maintains this package and is it actively maintained?
- It is maintained in the laravel-notification-channels ecosystem, and release 2.2.1 is a single-commit patch by Freek Van der Herten that restores Laravel 13 compatibility. That is a positive maintenance signal from an established Laravel ecosystem maintainer, but the assessment still flags low ecosystem signals and maintainer bus factor. Check recent commits and issue responsiveness before standardizing on it.
Weaver
How can I help you explore Laravel packages today?