Skip to main content

MS Teams

Reading time: 0 minute(s) (0 words)

The MS Teams alert method sends alerts through MS Teams to notify Nobl9 users whenever an incident is triggered.

Authentication​

Webhook URL
​

deprecated webhook URL

According to Microsoft's announcement, all MS Teams connectors will be deprecated by the end of 2024.

Existing MS Teams alerts configured with the old webhook URLs will remain functional until Microsoft officially deprecates them.

You can continue using the deprecated webhook URL to set up new alerts in MS Teams until August 15. After this date, we recommend switching to using the Workflow URL.

If you're currently using the deprecated webhook URLs, we recommend configuring both URL types for a while. This approach will help ensure a smooth transition and avoid any disruption in your alerts.

MS Teams Webhook URLs

To set up the MS Teams integration, you’ll need to provide an MS Teams Webhook URL. This allows you to send an automated notification to a channel of your choice. For details, see MS Teams documentation.

MS Teams Workflow URL
​

To set up the MS Teams integration, you’ll need to provide an MS Teams Workflow URL.

Follow the steps below to create the Workflow URL:

  1. In Microsoft Teams, click on Workflows from the sidebar.

    ms-teams-step-1
  2. Choose the template β€œPost to a channel when a webhook request is received.”

    ms-teams-step-2
  3. Enter a name for your flow in the Flow name field.

    ms-teams-step-3
  4. Specify Team and Channel:

    • Select the team and channel where notifications will be sent.
    ms-teams-step-4
  5. Click Create Flow to finalize the setup. Once the workflow is created, you can copy the webhook URL provided.

    ms-teams-step-5
  6. If you encounter issues, verify that your configuration matches the screenshot below.

    ms-teams-step-6

Configuring the MS Teams alert method​

You can configure your MS Teams alert method directly in the Nobl9 UI, or by applying a YAML file in sloctl.

Nobl9 UI​

To set up the alert method in the Nobl9 UI, follow these steps:

  1. Navigate to Integrations > Alert Methods.
  2. Click .
  3. Click the relevant Alert Method icon.

Then, in the MS Teams Configuration Wizard:

  1. Enter the URL.
    This is your MS Teams Workflows URL. For more information, refer to the Authentication section.
  1. Select a Project.
    Specifying a project is helpful when multiple users are spread across multiple teams or projects. When the Project field is left blank, Nobl9 uses the default project.
  2. Enter a Display Name.
    You can enter a user-friendly name with spaces in this field.
  3. Enter a Name.
    The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-alert-method-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
  4. Enter a Description.
    Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
  5. Click Add Alert Method.

YAML configuration for MS Teams alerts​

General YAML sample for MS Teams alert method
apiVersion: n9/v1alpha
kind: AlertMethod
metadata:
name: string # Mandatory
displayName: string # Mandatory
project: string # Mandatory
spec:
description: string # Mandatory
msteams:
url: string # Mandatory, requires https://, secret field

The only field that is specific to MS Teams is url. This field is kept secret and will be replaced with the [hidden] string when returned from sloctl. The https:// prefix is required.

Testing the MS Teams alert method in the UI​

You can test alert methods for all notification services supported by the Nobl9 platform through the UI.

To verify the correctness of your alert method configuration:

  1. Navigate to Integrations > Alert Methods.
  2. Click the required alert method.
    Its Details page opens.
  3. Click Test under the alert method name:
    • For the correct configuration, Nobl9 displays Test completed successfully! under the button
    • Otherwise, Nobl9 displays the Test failed message, specifying what is set incorrectly
For a more in-depth look, consult additional resources: