> ## Documentation Index > Fetch the complete documentation index at: https://docs.germainux.com/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft Teams notification > GermainUX can send real-time notifications to Microsoft Teams when monitored conditions, issues, or events require attention. Components [`Engine`](https://docs.germainux.com/main/germain-ux-engine) Availability 2026.1 or later > **[What Can Trigger a Teams Notification](#what-can-trigger-a-teams-notification)** > > Conditions that send alerts > **[From Notification to Investigation](#from-notification-to-investigation)** > > Using alerts to start investigations > **[Example: Notify Teams of a New Error](#example-notify-teams-of-a-new-error)** > > New error alert workflow > **[Security](#security)** > > Protecting Teams credentials Teams notifications can be triggered by GermainUX monitoring, analytics, SLAs, Rules, or Automation, helping the appropriate team respond without continuously watching dashboards. Typical use cases include: * Application or technology errors * SLA violations * User Experience frictions * Conversion issues * Adoption issues * Productivity issues > **Show all 11** > > * AI-detected findings > * User feedback > * Service or integration failures > * Infrastructure conditions > * Custom business conditions A typical workflow is: Detect Analyze Notify in Microsoft Teams Investigate Act Validate ## What Can Trigger a Teams Notification A Microsoft Teams notification can be associated with conditions monitored or analyzed by GermainUX. Examples include: ### Errors & Technology Notify a team when: * A new application error is detected * Error volume exceeds an expected threshold * A service becomes unavailable * Response time exceeds an SLA * A transaction fails * Infrastructure utilization reaches a configured threshold Example: New Error Analyze Impact Send Teams Notification Investigate ### User Experience Notify a team when GermainUX detects significant user friction, such as: * User-facing errors * Rage Clicks * Dead Clicks * Error Clicks * Slow interactions * Failed actions * Abandonment * Negative user feedback Example: Experience Friction Determine Users Affected Send Teams Notification Review Session Replay ### Conversion Teams notifications can alert eCommerce or digital teams when GermainUX detects conditions affecting conversion. For example: Conversion Decline Detect Conversion Friction Analyze Affected Visitors Send Teams Notification Investigate ### Adoption & Productivity Notify application owners when monitored conditions indicate potential adoption or productivity issues. For example: Workflow Duration Increases Identify Affected Employees Send Teams Notification Analyze Workflow ### AI Findings AI-generated analysis can also be incorporated into a Teams notification. For example: Issue Detected AI Analysis AI Recommendation Send Teams Notification This can provide the receiving team with more context than a notification containing only the original event or threshold violation. ## Notification Content A Microsoft Teams notification can provide the information required to understand and investigate the condition. Depending on the trigger and configuration, this may include: * Alert or issue * Application or service * KPI * Current value * Expected threshold * Severity > **Show all 13** > > * Time detected > * Number of users or sessions affected > * Error information > * Friction > * AI analysis > * AI recommendation > * Other contextual information Where applicable, the notification can direct the recipient back to GermainUX for deeper investigation. ## From Notification to Investigation A Teams notification is often the starting point for an investigation rather than the end of the workflow. For example: **Teams Notification** \ → Open GermainUX \ → Review KPI \ → Identify Affected Population \ → Review Related KPIs \ → Analyze Individual Instances \ → Review Session Replay or Trace \ → Determine Likely Root Cause This connects the notification to the monitoring and analytical evidence available in GermainUX. ## Configure Microsoft Teams Notifications Microsoft Teams must first be configured to accept notifications from GermainUX. The Teams endpoint and required authentication or connection information depend on the Microsoft Teams configuration used by your organization. Once the Teams integration is available, configure the GermainUX Rule, SLA, Watch, or Automation that determines: **1. What condition should trigger the notification** **2. Which Microsoft Teams destination should receive it** **3. What information should be included** **4. When the notification should be sent** The Germain Team can help configure Microsoft Teams notifications for your specific monitoring and automation requirements. [Contact GermainUX Support](https://docs.germainux.com/main/support.md). ## Example: Notify Teams of a New Error A common automation is to notify the appropriate team when GermainUX detects a new application error. The workflow can be configured as: **New Error Detected** \ → Analyze Error \ → Determine Frequency and Impact \ → Identify Affected Users and Sessions \ → Send Microsoft Teams Notification \ → Create or Update Ticket \ → Continue Monitoring The Teams notification can therefore provide the team with the context required to prioritize the issue instead of simply reporting that an error occurred. ## Example: Notify Teams of an SLA Violation GermainUX can notify a Teams channel when a monitored KPI violates an SLA. For example: **Application Response Time Exceeds SLA** \ → SLA Violation Detected \ → Determine Application and Population Affected \ → Send Teams Notification \ → Investigate in GermainUX \ → Validate Recovery ## Security Microsoft Teams connection information and credentials should be protected according to your organization's security policies. Only authorized GermainUX users should be permitted to configure or modify notification destinations and the Rules or Automation that trigger notifications. Avoid including sensitive information in Teams notifications unless the destination and recipients are authorized to receive it. ## Additional Resources * [AI](https://docs.germainux.com/main/ai-driven-insights.md) Insights & Recommendations * [Monitoring](https://docs.germainux.com/main/monitoring-management.md) * Rules for [automated analysis](https://docs.germainux.com/main/rules-advanced-automated-analytics.md) or [action execution](https://docs.germainux.com/main/rules.md) * [SLAs](https://docs.germainux.com/main/slas.md) management and violations dashboard * Alerts * [Analytics](https://docs.germainux.com/main/analytics.md) Features * [Automation](https://docs.germainux.com/main/automation.md) Features * [Dashboard](https://docs.germainux.com/main/dashboard-and-report.md) & [Reports](https://docs.germainux.com/main/reporting-automatic.md) * [Management](https://docs.germainux.com/main/management.md) Features. ## Get Help > **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)** > > The Germain Team can help you set this up. > **Can't find what you need?** > > Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing. The content of this document is proprietary to GERMAIN SOFTWARE. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.