Microsoft Teams

Overview

The Microsoft Teams connector lets Nullify reach engineers where they already work. Once the Nullify app is installed in your Teams tenant, Nullify can:

• Escalate findings that need developer action — an open fix PR that hasn't been reviewed, a fix that's blocked, or a secret that needs rotating.

• Send campaign nudges and informational updates to keep teams aligned on remediation.

• Reply in-thread, so engineers can respond and ask Nullify for more context without leaving Teams.

Messages are delivered asynchronously, so teams stay productive inside Teams without hopping between tools.

The Teams connector mirrors Slack: escalations, channel messages, and direct messages are all driven by Nullify, and the same notification configuration controls where they land.

Ask Nullify directly

Engineers can start a conversation with Nullify at any time by @mention-ing it in a channel, sending it a direct message, or replying in a thread it's part of. Ask about:

• Findings across code, dependencies, containers, secrets, cloud posture, and pentests.

• Remediation campaigns and their progress.

• Security metrics and trends.

• Threat investigations and which repositories are affected.

Nullify replies in plain language and links to the relevant place in the dashboard. From a Teams thread you can also answer and resolve the action items Nullify raises — approve or dismiss an escalation, answer a question, or assign a team. For broader state changes like allowlisting a finding, triggering a fix, or creating a ticket, Nullify points you to the dashboard.

Connect Microsoft Teams

Connecting Teams has two parts: registering an Azure AD application that Nullify authenticates as, and installing the Nullify app package into Teams.

1. Register an Azure AD application (your Azure administrator does this in the Azure portal): create an app registration, grant it the Microsoft Graph permissions Nullify needs to list channels and users and send messages, and create a client secret.

2. Provide the credentials to Nullify. In the Nullify Dashboard, go to Configure → Connectors → Microsoft Teams and enter the application's Client ID, Client Secret, and Tenant ID.

3. Install the Nullify Teams app package. From the same connector page, download the Nullify Teams app package (a .zip containing the app manifest and icons) and upload it in the Teams admin center (or via Apps → Manage your apps → Upload an app).

4. Add the Nullify app to the team(s) whose channels you want it to post in.

Once Nullify verifies the connection, the connector is marked Enabled and you're ready to choose where escalations go.

Channel targeting

Nullify posts to a Teams channel you select from the dashboard — pick the channel and the destination is captured for you. Nullify only posts in teams the Nullify app has been added to. If a message doesn't appear, confirm the Nullify app is installed in that specific team, not just elsewhere in the tenant.

Configuring notifications & escalations

Escalations and channel destinations are configured the same way as Slack, under Configure → Connectors → Microsoft Teams.

An escalation is a high-priority nudge Nullify sends when a security finding needs developer action — for example, a fix PR is open but unreviewed, a fix is blocked, or a secret needs rotating. Each escalation carries the finding's facts (repository, and the file, package, CVE, or secret type), why it needs attention, the risk and SLA, and a link to the finding in the Nullify dashboard. Engineers can reply in-thread to discuss or ask Nullify for more context.

Delivery modes match the Slack connector:

• Direct message — DM the engineer who owns the finding.

• Channel — post escalations to a Teams channel you choose.

• Both — DM the owner and post to the channel.

Nullify's regular channel messages and campaign nudges are informational updates that follow the same channel configuration.