{
  "doc": {
    "id": "cloud/integrations/microsoft-teams",
    "title": "Integrate Microsoft Teams with Cypress Cloud",
    "description": "Setup Microsoft Teams notifications for your Cypress Cloud organization and projects.",
    "section": "cloud",
    "source_path": "/llm/markdown/cloud/integrations/microsoft-teams.md",
    "version": "3b85801b725bd02bf0cb58cedaf42944712cdc72",
    "updated_at": "2026-07-12T03:11:07.806Z",
    "headings": [
      {
        "id": "cloud/integrations/microsoft-teams#microsoft-teams-integration",
        "text": "Microsoft Teams Integration",
        "level": 1
      },
      {
        "id": "cloud/integrations/microsoft-teams#enable-the-microsoft-teams-integration",
        "text": "Enable the Microsoft Teams integration",
        "level": 2
      },
      {
        "id": "cloud/integrations/microsoft-teams#per-organization-configuration-all-projects",
        "text": "Per-organization configuration (all projects)",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#remove-a-webhook",
        "text": "Remove a webhook",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#per-project-configuration",
        "text": "Per-project configuration",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#notification-preferences",
        "text": "Notification preferences",
        "level": 2
      },
      {
        "id": "cloud/integrations/microsoft-teams#flaky-test-alerts",
        "text": "Flaky test alerts",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#filter-notifications-by-tag-or-run-group",
        "text": "Filter notifications by tag or run group",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#message-content",
        "text": "Message content",
        "level": 2
      },
      {
        "id": "cloud/integrations/microsoft-teams#whats-included-in-every-message",
        "text": "What's included in every message",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#configurable-content-sections",
        "text": "Configurable content sections",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#display-modes",
        "text": "Display modes",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#example-configurations",
        "text": "Example configurations",
        "level": 2
      },
      {
        "id": "cloud/integrations/microsoft-teams#route-notifications-by-environment",
        "text": "Route notifications by environment",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#dedicated-flaky-test-triage",
        "text": "Dedicated flaky test triage",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#slim-ci-bridge-for-high-volume-projects",
        "text": "Slim CI bridge for high-volume projects",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#cross-team-visibility-with-focused-project-channels",
        "text": "Cross-team visibility with focused project channels",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#managing-channels",
        "text": "Managing channels",
        "level": 2
      },
      {
        "id": "cloud/integrations/microsoft-teams#mute-a-channel",
        "text": "Mute a channel",
        "level": 3
      },
      {
        "id": "cloud/integrations/microsoft-teams#per-project-muting-for-organization-channels",
        "text": "Per-project muting for organization channels",
        "level": 4
      }
    ]
  },
  "chunks": [
    {
      "id": "cloud/integrations/microsoft-teams#enable-the-microsoft-teams-integration",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Enable the Microsoft Teams integration",
      "heading_level": 2,
      "content_markdown": "## Enable the Microsoft Teams integration\n\n**Ownership Requirements**\n\nIn order to enable the Cypress integration for Microsoft Teams, you must be an admin or owner of both your Cypress Cloud organization and your Microsoft Teams workspace.\n\n### Per-organization configuration (all projects)\n\n1.  Go to Cypress Cloud [Organizations page](https://cloud.cypress.io/organizations) or open the organization switcher.\n    \n2.  Select the organization you wish to integrate with Microsoft Teams.\n    \n3.  Visit the selected organization's **Integrations** page via the side navigation.\n    \n4.  Click the **Enable** button in the Microsoft Teams section.\n    \n5.  Click the **Enable Teams** button in the Microsoft Teams section under 'Global Notifications'.\n    \n\n1.  You'll navigate to a window that manages webhooks as a way for Cypress Cloud to communicate with Microsoft Teams. First, you must configure an _Incoming Webhook_ to a Teams channel.\n    \n    In Microsoft Teams:\n    \n    *   Open the channel in which you want to add the webhook and select **•••** from the upper-right corner.\n        \n    *   Select **Workflows** from the dropdown menu.\n        \n    *   Search for **webhooks** and select **select webhook alerts to channel**.\n        \n    *   Select channel name from dropdown and click **Save**\n        \n    *   Copy and save the unique webhook URL present in the dialog. The URL maps to the channel and you can use it to send information to Teams.\n        \n        The webhook is now available in the Teams channel. For more information, see [Microsoft Teams - Create Incoming Webhooks](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=dotnet#create-incoming-webhooks-1).\n        \n2.  Then, add the Teams webhook to your Cypress Cloud Organization.\n    \n    In Cypress Cloud:\n    \n    *   Paste in the Teams webhook URL, choosing the types of notifications your team should receive.\n        \n    \n    Once you've configured and added your webhooks, the installation is complete! Cypress Cloud will post run results for **all** projects in your organization to the specified Microsoft Teams channel.\n    \n\n### Remove a webhook\n\nYou can have Cypress Cloud stop posting notifications to a channel. You cannot delete the global notification channels from a project.\n\n1.  Navigate to the **Integrations** page for the project with the installed integration.\n2.  Scroll down to the **Microsoft Teams Integration** section.\n3.  Select **Global Settings** then select **Delete**, you will get a prompt, click **Yes, Delete**\n    \n\n### Per-project configuration\n\nIf your organization has multiple teams working on separate projects, you can tailor the Microsoft Teams notifications of each project to match your teams' needs. You can have Cypress Cloud post run results for a specific project.\n\n1.  Select your organization in the organization switcher.\n    \n2.  Select the project you wish to integrate with Microsoft Teams.\n    \n3.  Go to the project's settings page and click the Integrations tab.\n    \n4.  Scroll down and click **Add Teams webhook** in the **Microsoft Teams** section.\n    \n5.  You'll navigate to a window that manages webhooks as a way for Cypress Cloud to communicate with Microsoft Teams. First, you must configure an _Incoming Webhook_ to a Teams channel.\n    \n    In Microsoft Teams:\n    \n    *   Open the channel in which you want to add the webhook and select **•••** from the upper-right corner.\n        \n    *   Select **Workflows** from the dropdown menu.\n        \n    *   Search for **webhooks** and select **select webhook alerts to channel**.\n        \n    *   Select channel name from dropdown and click **Save**\n        \n    \n    *   Copy and save the unique webhook URL present in the dialog. The URL maps to the channel and you can use it to send information to Teams.\n    \n    The webhook is now available in the Teams channel. For more information, see [Microsoft Teams - Create Incoming Webhooks](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=dotnet#create-incoming-webhooks-1).\n    \n6.  Then, add the Teams webhook to your Cypress Cloud Project.\n    \n    In Cypress Cloud:\n    \n    *   Paste in the Teams webhook URL, choosing the types of notifications your team should receive.\n        \n    \n    Once you've configured and added your webhooks, the installation is complete! Cypress Cloud will post run results for **this** project to the specified Microsoft Teams channel.\n",
      "section": "cloud",
      "anchors": [
        "enable-the-microsoft-teams-integration"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 819
    },
    {
      "id": "cloud/integrations/microsoft-teams#per-organization-configuration-all-projects",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Per-organization configuration (all projects)",
      "heading_level": 3,
      "content_markdown": "### Per-organization configuration (all projects)\n\n1.  Go to Cypress Cloud [Organizations page](https://cloud.cypress.io/organizations) or open the organization switcher.\n    \n2.  Select the organization you wish to integrate with Microsoft Teams.\n    \n3.  Visit the selected organization's **Integrations** page via the side navigation.\n    \n4.  Click the **Enable** button in the Microsoft Teams section.\n    \n5.  Click the **Enable Teams** button in the Microsoft Teams section under 'Global Notifications'.\n    \n\n1.  You'll navigate to a window that manages webhooks as a way for Cypress Cloud to communicate with Microsoft Teams. First, you must configure an _Incoming Webhook_ to a Teams channel.\n    \n    In Microsoft Teams:\n    \n    *   Open the channel in which you want to add the webhook and select **•••** from the upper-right corner.\n        \n    *   Select **Workflows** from the dropdown menu.\n        \n    *   Search for **webhooks** and select **select webhook alerts to channel**.\n        \n    *   Select channel name from dropdown and click **Save**\n        \n    *   Copy and save the unique webhook URL present in the dialog. The URL maps to the channel and you can use it to send information to Teams.\n        \n        The webhook is now available in the Teams channel. For more information, see [Microsoft Teams - Create Incoming Webhooks](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=dotnet#create-incoming-webhooks-1).\n        \n2.  Then, add the Teams webhook to your Cypress Cloud Organization.\n    \n    In Cypress Cloud:\n    \n    *   Paste in the Teams webhook URL, choosing the types of notifications your team should receive.\n        \n    \n    Once you've configured and added your webhooks, the installation is complete! Cypress Cloud will post run results for **all** projects in your organization to the specified Microsoft Teams channel.\n",
      "section": "cloud",
      "anchors": [
        "per-organization-configuration-all-projects"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 332
    },
    {
      "id": "cloud/integrations/microsoft-teams#remove-a-webhook",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Remove a webhook",
      "heading_level": 3,
      "content_markdown": "### Remove a webhook\n\nYou can have Cypress Cloud stop posting notifications to a channel. You cannot delete the global notification channels from a project.\n\n1.  Navigate to the **Integrations** page for the project with the installed integration.\n2.  Scroll down to the **Microsoft Teams Integration** section.\n3.  Select **Global Settings** then select **Delete**, you will get a prompt, click **Yes, Delete**\n",
      "section": "cloud",
      "anchors": [
        "remove-a-webhook"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 83
    },
    {
      "id": "cloud/integrations/microsoft-teams#per-project-configuration",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Per-project configuration",
      "heading_level": 3,
      "content_markdown": "### Per-project configuration\n\nIf your organization has multiple teams working on separate projects, you can tailor the Microsoft Teams notifications of each project to match your teams' needs. You can have Cypress Cloud post run results for a specific project.\n\n1.  Select your organization in the organization switcher.\n    \n2.  Select the project you wish to integrate with Microsoft Teams.\n    \n3.  Go to the project's settings page and click the Integrations tab.\n    \n4.  Scroll down and click **Add Teams webhook** in the **Microsoft Teams** section.\n    \n5.  You'll navigate to a window that manages webhooks as a way for Cypress Cloud to communicate with Microsoft Teams. First, you must configure an _Incoming Webhook_ to a Teams channel.\n    \n    In Microsoft Teams:\n    \n    *   Open the channel in which you want to add the webhook and select **•••** from the upper-right corner.\n        \n    *   Select **Workflows** from the dropdown menu.\n        \n    *   Search for **webhooks** and select **select webhook alerts to channel**.\n        \n    *   Select channel name from dropdown and click **Save**\n        \n    \n    *   Copy and save the unique webhook URL present in the dialog. The URL maps to the channel and you can use it to send information to Teams.\n    \n    The webhook is now available in the Teams channel. For more information, see [Microsoft Teams - Create Incoming Webhooks](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=dotnet#create-incoming-webhooks-1).\n    \n6.  Then, add the Teams webhook to your Cypress Cloud Project.\n    \n    In Cypress Cloud:\n    \n    *   Paste in the Teams webhook URL, choosing the types of notifications your team should receive.\n        \n    \n    Once you've configured and added your webhooks, the installation is complete! Cypress Cloud will post run results for **this** project to the specified Microsoft Teams channel.\n",
      "section": "cloud",
      "anchors": [
        "per-project-configuration"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 356
    },
    {
      "id": "cloud/integrations/microsoft-teams#notification-preferences",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Notification preferences",
      "heading_level": 2,
      "content_markdown": "## Notification preferences\n\nBy default, Cypress Cloud will post a Teams message to each configured channel only for failing runs. However, you can select any combination of the followings preferences:\n\n*   **Failed runs**: notifies on runs with a _failed_ or _errored_ status.\n*   **Passed runs**: notifies on runs with a _passed_ status.\n*   **Canceled runs**: notifies on runs with a _canceled_ status.\n*   **Timed out runs**: notifies on runs with a _timed out_ status.\n*   **Flaky tests**: notifies on runs that contain an identified _flaky_ test.\n\nTo set notification preferences:\n\n1.  Navigate to Teams configuration page\n2.  Select the notification preferences for each channel\n\n### Flaky test alerts\n\nThe **Flaky tests** preference works independently from the run status preferences. This means you can configure a channel to receive notifications _only_ when flaky tests are detected — even if you don't subscribe to passed or failed runs. See [Example configurations](#Example-configurations) for a concrete setup.\n\nWhen flaky test alerts are enabled, the Teams message includes flaky test counts in the test results section and lists flaky specs alongside failed specs in the specs for review section.\n\n**Premium Cypress Cloud Feature**\n\nFlaky test detection requires the flaky test management feature to be enabled for your organization. See [Flaky Test Management](/llm/markdown/cloud/features/flaky-test-management.md) for more details.\n\n### Filter notifications by tag or run group\n\nWhen configuring at the project-level, you can filter notifications posted to Teams based on a [tag](/llm/markdown/app/references/command-line.md#cypress-run-tag-lt-tag-gt) or [group](/llm/markdown/app/references/command-line.md#cypress-run-group-lt-name-gt) the run was recorded with. This is helpful for posting notifications only for certain runs, like those to a staging or release environment.\n\n1.  Navigate to the **Teams** configuration page.\n2.  Under **Tags**, select the **Tag** dropdown for the desired integration and select which tag(s) to filter. If more than one tag is selected, the Teams message will be sent if any of the tags were associated with the run.\n3.  Under **Run Groups**, select the **Run Group** dropdown for the desired integration and select which run group(s) to filter. If more than one run group is selected, the Teams message will be sent if any of the run groups were associated with the run.\n\nIf both a tag and run group are selected, only a run associated with both criteria will trigger a message to be sent to Teams.\n",
      "section": "cloud",
      "anchors": [
        "notification-preferences"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 501
    },
    {
      "id": "cloud/integrations/microsoft-teams#flaky-test-alerts",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Flaky test alerts",
      "heading_level": 3,
      "content_markdown": "### Flaky test alerts\n\nThe **Flaky tests** preference works independently from the run status preferences. This means you can configure a channel to receive notifications _only_ when flaky tests are detected — even if you don't subscribe to passed or failed runs. See [Example configurations](#Example-configurations) for a concrete setup.\n\nWhen flaky test alerts are enabled, the Teams message includes flaky test counts in the test results section and lists flaky specs alongside failed specs in the specs for review section.\n\n**Premium Cypress Cloud Feature**\n\nFlaky test detection requires the flaky test management feature to be enabled for your organization. See [Flaky Test Management](/llm/markdown/cloud/features/flaky-test-management.md) for more details.\n",
      "section": "cloud",
      "anchors": [
        "flaky-test-alerts"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 141
    },
    {
      "id": "cloud/integrations/microsoft-teams#filter-notifications-by-tag-or-run-group",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Filter notifications by tag or run group",
      "heading_level": 3,
      "content_markdown": "### Filter notifications by tag or run group\n\nWhen configuring at the project-level, you can filter notifications posted to Teams based on a [tag](/llm/markdown/app/references/command-line.md#cypress-run-tag-lt-tag-gt) or [group](/llm/markdown/app/references/command-line.md#cypress-run-group-lt-name-gt) the run was recorded with. This is helpful for posting notifications only for certain runs, like those to a staging or release environment.\n\n1.  Navigate to the **Teams** configuration page.\n2.  Under **Tags**, select the **Tag** dropdown for the desired integration and select which tag(s) to filter. If more than one tag is selected, the Teams message will be sent if any of the tags were associated with the run.\n3.  Under **Run Groups**, select the **Run Group** dropdown for the desired integration and select which run group(s) to filter. If more than one run group is selected, the Teams message will be sent if any of the run groups were associated with the run.\n\nIf both a tag and run group are selected, only a run associated with both criteria will trigger a message to be sent to Teams.\n",
      "section": "cloud",
      "anchors": [
        "filter-notifications-by-tag-or-run-group"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 221
    },
    {
      "id": "cloud/integrations/microsoft-teams#message-content",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Message content",
      "heading_level": 2,
      "content_markdown": "## Message content\n\nEach Teams notification includes run metadata and up to six configurable content sections. You can choose which sections appear in your messages and how they're displayed.\n\n### What's included in every message\n\nEvery run completion message includes the following run properties:\n\n*   **Run title**: The run number and commit message, linked to the run in Cypress Cloud.\n*   **Run status**: A color-coded status indicator (passed, failed, errored, timed out, or canceled).\n*   **Project**: The project name, linked to the project in Cypress Cloud.\n*   **Branch**: The branch name where the run was recorded.\n*   **Commit author**: The author of the commit that triggered the run.\n*   **CI build**: The CI provider and build number, linked to the CI build.\n\n### Configurable content sections\n\nYou can enable or disable any of the following content sections for each Teams channel:\n\n*   **Test results**: Shows pass, fail, skip, pending, and flaky counts. Each count links directly to the filtered view in Cypress Cloud.\n*   **UI Coverage results**: Shows the coverage percentage along with counts of tested and untested elements and links. Only appears when [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md) data is available.\n*   **Accessibility results**: Shows the accessibility pass percentage, failed rules broken down by severity (critical, serious, moderate, minor), and failed elements. Only appears when [Cypress Accessibility](/llm/markdown/accessibility/get-started/introduction.md) data is available.\n*   **Specs for review**: Lists up to 10 failed and flaky spec files with clickable links, the count of failed or flaky tests in each, and the run group name. If there are more than 10, a link to see all specs is included.\n*   **Run tags**: Displays the tags associated with the run.\n*   **Run groups**: Displays the run groups associated with the run.\n\nTo configure message content:\n\n1.  Navigate to the **Teams** configuration page.\n2.  Adjust the content sections for each channel.\n\n### Display modes\n\nYou can choose between two display modes for your Teams messages:\n\n*   **Stacked** (default): Each test result status appears on its own line with an icon and count. This is easier to scan when there are many statuses.\n*   **Compact**: All status counts appear on a single line, saving vertical space in your Teams channel.\n\nThe display mode applies to the test results, UI Coverage, and accessibility sections.\n",
      "section": "cloud",
      "anchors": [
        "message-content"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 497
    },
    {
      "id": "cloud/integrations/microsoft-teams#whats-included-in-every-message",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "What's included in every message",
      "heading_level": 3,
      "content_markdown": "### What's included in every message\n\nEvery run completion message includes the following run properties:\n\n*   **Run title**: The run number and commit message, linked to the run in Cypress Cloud.\n*   **Run status**: A color-coded status indicator (passed, failed, errored, timed out, or canceled).\n*   **Project**: The project name, linked to the project in Cypress Cloud.\n*   **Branch**: The branch name where the run was recorded.\n*   **Commit author**: The author of the commit that triggered the run.\n*   **CI build**: The CI provider and build number, linked to the CI build.\n",
      "section": "cloud",
      "anchors": [
        "whats-included-in-every-message"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 124
    },
    {
      "id": "cloud/integrations/microsoft-teams#configurable-content-sections",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Configurable content sections",
      "heading_level": 3,
      "content_markdown": "### Configurable content sections\n\nYou can enable or disable any of the following content sections for each Teams channel:\n\n*   **Test results**: Shows pass, fail, skip, pending, and flaky counts. Each count links directly to the filtered view in Cypress Cloud.\n*   **UI Coverage results**: Shows the coverage percentage along with counts of tested and untested elements and links. Only appears when [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md) data is available.\n*   **Accessibility results**: Shows the accessibility pass percentage, failed rules broken down by severity (critical, serious, moderate, minor), and failed elements. Only appears when [Cypress Accessibility](/llm/markdown/accessibility/get-started/introduction.md) data is available.\n*   **Specs for review**: Lists up to 10 failed and flaky spec files with clickable links, the count of failed or flaky tests in each, and the run group name. If there are more than 10, a link to see all specs is included.\n*   **Run tags**: Displays the tags associated with the run.\n*   **Run groups**: Displays the run groups associated with the run.\n\nTo configure message content:\n\n1.  Navigate to the **Teams** configuration page.\n2.  Adjust the content sections for each channel.\n",
      "section": "cloud",
      "anchors": [
        "configurable-content-sections"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 240
    },
    {
      "id": "cloud/integrations/microsoft-teams#display-modes",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Display modes",
      "heading_level": 3,
      "content_markdown": "### Display modes\n\nYou can choose between two display modes for your Teams messages:\n\n*   **Stacked** (default): Each test result status appears on its own line with an icon and count. This is easier to scan when there are many statuses.\n*   **Compact**: All status counts appear on a single line, saving vertical space in your Teams channel.\n\nThe display mode applies to the test results, UI Coverage, and accessibility sections.\n",
      "section": "cloud",
      "anchors": [
        "display-modes"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 95
    },
    {
      "id": "cloud/integrations/microsoft-teams#example-configurations",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Example configurations",
      "heading_level": 2,
      "content_markdown": "## Example configurations\n\nThe options above — notification preferences, tag and run group filters, content sections, display modes, and org-vs-project scoping — can be combined to build notification setups tailored to how your team works. Below are some common configurations.\n\n### Route notifications by environment\n\nCreate separate project-level channels for each environment and use tag filters to route runs to the right place. For example, a `#staging-tests` channel filtered to the `staging` tag with **Failed runs** and **Passed runs** enabled gives your QA team full visibility into staging health, while a `#prod-alerts` channel filtered to the `production` tag with only **Failed runs** enabled keeps production notifications focused on breakages.\n\n### Dedicated flaky test triage\n\nAdd a channel like `#flaky-triage` with only the **Flaky tests** preference enabled and no run status preferences selected. This channel will only receive a notification when a run contains flaky tests — regardless of whether the run passed or failed — so your team can triage new flake without the noise of every run result.\n\n### Slim CI bridge for high-volume projects\n\nFor projects with frequent CI runs, set up a channel with only the **Test results** content section enabled in **Compact** display mode. This gives your team a single-line pass/fail summary per run with a direct link to the CI build, keeping the channel scannable even at high volume.\n\n### Cross-team visibility with focused project channels\n\nConfigure an organization-level `#cypress-results` channel with **Failed runs** enabled so leadership and stakeholders can monitor test health across all projects. Then add project-level channels like `#team-checkout-tests` with additional content sections (specs for review, run tags) and extra notification preferences (passed runs, flaky tests) so individual teams get the detail they need for the projects they own.\n",
      "section": "cloud",
      "anchors": [
        "example-configurations"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 383
    },
    {
      "id": "cloud/integrations/microsoft-teams#route-notifications-by-environment",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Route notifications by environment",
      "heading_level": 3,
      "content_markdown": "### Route notifications by environment\n\nCreate separate project-level channels for each environment and use tag filters to route runs to the right place. For example, a `#staging-tests` channel filtered to the `staging` tag with **Failed runs** and **Passed runs** enabled gives your QA team full visibility into staging health, while a `#prod-alerts` channel filtered to the `production` tag with only **Failed runs** enabled keeps production notifications focused on breakages.\n",
      "section": "cloud",
      "anchors": [
        "route-notifications-by-environment"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 92
    },
    {
      "id": "cloud/integrations/microsoft-teams#dedicated-flaky-test-triage",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Dedicated flaky test triage",
      "heading_level": 3,
      "content_markdown": "### Dedicated flaky test triage\n\nAdd a channel like `#flaky-triage` with only the **Flaky tests** preference enabled and no run status preferences selected. This channel will only receive a notification when a run contains flaky tests — regardless of whether the run passed or failed — so your team can triage new flake without the noise of every run result.\n",
      "section": "cloud",
      "anchors": [
        "dedicated-flaky-test-triage"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 80
    },
    {
      "id": "cloud/integrations/microsoft-teams#slim-ci-bridge-for-high-volume-projects",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Slim CI bridge for high-volume projects",
      "heading_level": 3,
      "content_markdown": "### Slim CI bridge for high-volume projects\n\nFor projects with frequent CI runs, set up a channel with only the **Test results** content section enabled in **Compact** display mode. This gives your team a single-line pass/fail summary per run with a direct link to the CI build, keeping the channel scannable even at high volume.\n",
      "section": "cloud",
      "anchors": [
        "slim-ci-bridge-for-high-volume-projects"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 73
    },
    {
      "id": "cloud/integrations/microsoft-teams#cross-team-visibility-with-focused-project-channels",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Cross-team visibility with focused project channels",
      "heading_level": 3,
      "content_markdown": "### Cross-team visibility with focused project channels\n\nConfigure an organization-level `#cypress-results` channel with **Failed runs** enabled so leadership and stakeholders can monitor test health across all projects. Then add project-level channels like `#team-checkout-tests` with additional content sections (specs for review, run tags) and extra notification preferences (passed runs, flaky tests) so individual teams get the detail they need for the projects they own.\n",
      "section": "cloud",
      "anchors": [
        "cross-team-visibility-with-focused-project-channels"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 84
    },
    {
      "id": "cloud/integrations/microsoft-teams#managing-channels",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Managing channels",
      "heading_level": 2,
      "content_markdown": "## Managing channels\n\n### Mute a channel\n\nIf you want Cypress Cloud to temporarily stop posting Teams messages to a certain channel, you can **Mute** that channel. This allows you to easily pause and resume notifications for a specific channel without losing the configuration you've put in place.\n\n1.  Navigate to the **Teams** configuration page.\n2.  Toggle the **Active** selector for each Teams channel you want muted.\n\n#### Per-project muting for organization channels\n\nIf you have an organization-level Teams channel, you can mute it for specific projects without affecting other projects. This is useful when you want most projects to post to a shared channel but need to silence notifications for a particular project temporarily.\n\n1.  Navigate to the **Project Settings** page for the project you want to mute.\n2.  Click the **Integrations** tab.\n3.  Toggle the mute setting for the organization-level Teams channel.\n\nToggling the mute on an organization-level install will clear all project-level mute overrides for that channel. If you're using per-project muting, be aware that changing the global mute state resets those overrides.\n",
      "section": "cloud",
      "anchors": [
        "managing-channels"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 235
    },
    {
      "id": "cloud/integrations/microsoft-teams#mute-a-channel",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Mute a channel",
      "heading_level": 3,
      "content_markdown": "### Mute a channel\n\nIf you want Cypress Cloud to temporarily stop posting Teams messages to a certain channel, you can **Mute** that channel. This allows you to easily pause and resume notifications for a specific channel without losing the configuration you've put in place.\n\n1.  Navigate to the **Teams** configuration page.\n2.  Toggle the **Active** selector for each Teams channel you want muted.\n\n#### Per-project muting for organization channels\n\nIf you have an organization-level Teams channel, you can mute it for specific projects without affecting other projects. This is useful when you want most projects to post to a shared channel but need to silence notifications for a particular project temporarily.\n\n1.  Navigate to the **Project Settings** page for the project you want to mute.\n2.  Click the **Integrations** tab.\n3.  Toggle the mute setting for the organization-level Teams channel.\n\nToggling the mute on an organization-level install will clear all project-level mute overrides for that channel. If you're using per-project muting, be aware that changing the global mute state resets those overrides.\n",
      "section": "cloud",
      "anchors": [
        "mute-a-channel"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 231
    },
    {
      "id": "cloud/integrations/microsoft-teams#per-project-muting-for-organization-channels",
      "doc_id": "cloud/integrations/microsoft-teams",
      "heading": "Per-project muting for organization channels",
      "heading_level": 4,
      "content_markdown": "#### Per-project muting for organization channels\n\nIf you have an organization-level Teams channel, you can mute it for specific projects without affecting other projects. This is useful when you want most projects to post to a shared channel but need to silence notifications for a particular project temporarily.\n\n1.  Navigate to the **Project Settings** page for the project you want to mute.\n2.  Click the **Integrations** tab.\n3.  Toggle the mute setting for the organization-level Teams channel.\n\nToggling the mute on an organization-level install will clear all project-level mute overrides for that channel. If you're using per-project muting, be aware that changing the global mute state resets those overrides.\n",
      "section": "cloud",
      "anchors": [
        "per-project-muting-for-organization-channels"
      ],
      "path": "/llm/json/chunked/cloud/integrations/microsoft-teams.json",
      "token_estimate": 145
    }
  ]
}