INTEGRATIONS · MICROSOFT TEAMS · NEW

Your ISMS posts in your Teams channel.

People who rarely work in Varmo see in Teams when an approval is waiting or an incident has been reported. The notification only states the type and ID; what lies behind it, each person sees in Varmo.

Included from the Pro plan
Events selectable per channel
Test notification and log in Varmo

Varmo

Approvals
Incidents
Risks
Functional roles
Tasks

sends

Microsoft Teams

Channel
Workflow

Flows:

Type
ID
Organisation
Link

Not:

Titles
Descriptions
People
Ratings

AT A GLANCE

From Pro, Varmo sends notifications to a Microsoft Teams channel via a Teams workflow: pending approvals, reported incidents and risks, vacant functional roles and, once a day, newly overdue tasks – each with an ID and a link, without titles or content.

Request a demo Try it free

Requirements

Plan: Varmo Pro or Ultimate
In Varmo: The “Manage integrations” right
Microsoft 365: Teams and permission to create workflows in Teams (Power Automate; your IT department can restrict this)
Channel: A standard or shared channel. According to Microsoft, the workflow cannot yet post as a bot in private channels.

By default, the ISMS managers have this right in Varmo.

Missing permissions when creating the workflow?

The person who creates the workflow in Teams needs a licence that includes Teams.
If Teams reports missing permissions, create the workflow with an account that has a Teams licence; anyone with “Manage integrations” can then connect the channel in Varmo.
In Switzerland and the EU, Teams is sometimes licensed separately (e.g. “Microsoft Teams EEA”).

2 STEPS

Setup

1
Step 1: Create a workflow in Teams
In the channel you want, create a workflow from the template for webhook alerts.
Menu path: Channel › “…” (More options) › “Workflows”
Template:“Send webhook alerts to a channel”German: “Webhookwarnungen an einen Kanal senden”
Important:Copy the address shown and treat it like a password: anyone who knows it can post to the channel.
Details
Give it a name, e.g. “Varmo”, confirm the sign-in, check the team and channel and save.
The address starts with https:// and ends at Microsoft (…powerplatform.com).
Step 2: Connect the channel in Varmo
Enter a name, paste the address, choose the events and save.
Menu path: ISMS settings › Integrations › Microsoft Teams › “Connect channel”
Result: “Send a test notification”: the test notification appears in the channel within seconds.

Which notifications there are

Approval pendingSubmitted for approval:PolicyDocumentExceptionProtection requirements assessmentBaseline checkData protection impact assessmentStatement of ApplicabilityRisk acceptanceTreatment plan
Incident reportedWith the incident’s ID.
Risk reportedA new risk is waiting for review (imports excluded).
Functional role vacantA functional role that workflows depend on has lost its last member.
Tasks overdueOnce a day, a summary with the IDs of newly overdue measures and expired exceptions, plus the number of overdue risk reviews.

Notifications only state the type, identifier and link; only people who open the link in Varmo see the content.

Data and security

A channel is not a person: all members see every notification. That is why the notification only contains the type, the ID (e.g. “Exception X003”), the name of your organisation in Varmo and a link.

No contentVarmo does not send titles, descriptions, people or ratings.
Own permissionsAnyone who opens the link signs in to Varmo and only sees what they are allowed to see there.
At MicrosoftMicrosoft stores the notifications like other Teams messages.
Address encryptedVarmo stores the address encrypted and never displays it again.
Teams workflows onlyVarmo only sends to addresses of Teams workflows at Microsoft and does not follow redirects.
Logged and retriedChanges to and removal of channels are recorded in the change log. If Teams is temporarily unavailable, Varmo retries several times over a few hours.

If something doesn’t work

If a notification is not delivered, everyone with “Manage integrations” in Varmo receives a task.

“The address does not come from a Teams workflow”

Copy the address from the workflow again; addresses of the old Office 365 connectors (…webhook.office.com) do not work, as Microsoft is retiring them.

“The workflow no longer exists or is switched off”

Check and switch it on in Teams › Workflows, or create it again and enter the new address.

“Teams rejected the address (invalid signature)”

The address is incomplete; copy it again.

“The workflow rejected the notification”

Create the workflow again using the template “Send webhook alerts to a channel”.

Switch off

In Varmo

Edit the channel › switch off “Send notifications to this channel”, or remove the channel (the address is deleted)

In Teams

You delete the workflow there under “Workflows”

The workflow belongs to the person who created it. If they leave the company, first add another person as owner in Power Automate.

Microsoft, Entra, Intune and Teams are trademarks of Microsoft Corporation; JIRA is a trademark of Atlassian; ServiceNow is a trademark of ServiceNow, Inc. Their mention does not imply a partnership.

Frequently asked questions

What content does Varmo send to Teams?

Only the type of notification, the ID (e.g. “Exception X003”), the name of your organisation in Varmo and a link. Varmo does not send titles, descriptions, people or ratings.

Do the old Office 365 connectors work?

No. Varmo only sends to addresses of Teams workflows (template “Send webhook alerts to a channel”). Microsoft is retiring addresses of the old connectors (…webhook.office.com).

Can Varmo post to a private channel?

According to Microsoft, the workflow cannot yet post as a bot in private channels. Use a standard or shared channel.

How close are you to ISO/IEC 27001?

In a personal demo, we show you the way to the readiness report, with no obligation. Or try it free for 30 days with every feature.