Microsoft Teams is a collaboration platform that supports communication, meetings, file sharing, and app integration in a unified workspace. You can integrate Microsoft Teams with HP Workforce Experience Platform (WXP) to receive real-time alert and workflow notifications in Teams channels. You can also use the WXP Teams Bot to send Custom Pulses directly to users. This integration helps teams respond faster and work more efficiently.
The Microsoft Teams integration supports two notification methods:
Webhooks: Integrate webhooks with WXP to send alert and workflow notifications to Teams channels.
WXP Teams Bot: Integrate the bot with WXP to send Custom Pulses directly to selected end users.
This article provides step-by-step guidance to integrate WXP with Microsoft Teams.
Note: This feature is available with the WXP Pro and Elite plans.
Key Features
Seamless Integration: Create channel webhooks to receive WXP notifications in Microsoft Teams.
Enhanced Collaboration: Centralize WXP notifications in Microsoft Teams so that users can respond promptly.
Customized Reach: Use the WXP Teams Bot to send Custom Pulses directly to selected users.
Prerequisites
Before you begin, ensure that:
You have the Connector Admin role in WXP to access integrations and connectors.
Your Microsoft Teams account is active.
You are a member of one or more Teams channels where you want to receive WXP notifications.
For additional information about roles and permissions, see the Role-Based Access Control (RBAC) section in Authentication.
Adding a Webhook
Use Microsoft Teams webhooks to send WXP alert and workflow notifications to Teams channels. Create a separate webhook for each Teams channel where you want to receive notifications.
Complete the following steps to configure webhook notifications.
Creating a Webhook for Teams Channels
Create a webhook in each Teams channel where you want to receive WXP alert or workflow notifications.
Note: You do not need to be the Teams channel owner. Any channel member can create a webhook.
In the Microsoft Teams app, go to Teams and channels and locate the channel where you want to receive notifications.
.png?sv=2026-02-06&spr=https&st=2026-10-16T01%3A06%3A20Z&se=2026-10-16T01%3A24%3A20Z&sr=c&sp=r&sig=v2qXlE7hWtUK78132FYopDUA2X9rhQgLQUCYc%2BPo2m8%3D)
In the Teams and channels list, point to the channel name, and then click More options (Ellipsis icon).
.png?sv=2026-02-06&spr=https&st=2026-10-16T01%3A06%3A20Z&se=2026-10-16T01%3A24%3A20Z&sr=c&sp=r&sig=v2qXlE7hWtUK78132FYopDUA2X9rhQgLQUCYc%2BPo2m8%3D)
From the More options menu, select Workflow. The Workflows dialog box is displayed.
.png?sv=2026-02-06&spr=https&st=2026-10-16T01%3A06%3A20Z&se=2026-10-16T01%3A24%3A20Z&sr=c&sp=r&sig=v2qXlE7hWtUK78132FYopDUA2X9rhQgLQUCYc%2BPo2m8%3D)
In the Workflows dialog box, enter Send webhook alerts from people in an org to a channel in the Find templates search bar, and then select the corresponding workflow.
.png?sv=2026-02-06&spr=https&st=2026-10-16T01%3A06%3A20Z&se=2026-10-16T01%3A24%3A20Z&sr=c&sp=r&sig=v2qXlE7hWtUK78132FYopDUA2X9rhQgLQUCYc%2BPo2m8%3D)
In the Workflows dialog box, verify that the selected team and channel are correct, and then click Save.
.png?sv=2026-02-06&spr=https&st=2026-10-16T01%3A06%3A20Z&se=2026-10-16T01%3A24%3A20Z&sr=c&sp=r&sig=v2qXlE7hWtUK78132FYopDUA2X9rhQgLQUCYc%2BPo2m8%3D)
Click Copy webhook link to copy the generated webhook URL.
.png?sv=2026-02-06&spr=https&st=2026-10-16T01%3A06%3A20Z&se=2026-10-16T01%3A24%3A20Z&sr=c&sp=r&sig=v2qXlE7hWtUK78132FYopDUA2X9rhQgLQUCYc%2BPo2m8%3D)
For each additional Teams channel where you want to receive WXP alert or workflow notifications, repeat Steps 2 through 6.
Activating the Connector
After creating the webhooks, complete the following steps to connect WXP to Microsoft Teams and activate the connector.
From the left menu of WXP, click Integrations. The Integrations page is displayed.
On the Integrations page, locate Microsoft Teams and click Connect.
If a subconnector is already connected, click Manage.
Multiple connector options may appear. Under Add a Webhook, click Configure.
In the Channel Name field, enter an alias for the Teams channel. The alias does not need to match the Teams channel name
In the Webhook URL field, paste the Webhook URL you copied earlier.
Refer to the Creating Webhooks for Teams Channels section above for instructions.
Click Save.
To configure another channel, click Add Webhook, and then enter the channel alias and webhook URL.
After configuring all the required channels, click Save.
In the Microsoft Teams dialog box, under Add a Webhook, click Connect.
In the Microsoft Teams dialog box, click Connect.
.png?sv=2026-02-06&spr=https&st=2026-10-16T01%3A06%3A20Z&se=2026-10-16T01%3A24%3A20Z&sr=c&sp=r&sig=v2qXlE7hWtUK78132FYopDUA2X9rhQgLQUCYc%2BPo2m8%3D)
Sign in with your Microsoft credentials.
On the Permissions requested page, leave Consent on behalf of your organization cleared, and then click Accept.
The Microsoft Teams connector requires the following permissions:
open_id: Allows users to sign in to the app with their work or school accounts and allows the app to view basic profile information.
offline_access: This scope is used for token refresh and fetching an updated token.
https://service.flow.microsoft.com//User: Allows the application to execute the webhook on behalf of the user.
Once connected, the connector card shows Connected in green.
Configuring Alert Notifications
After setup, configure WXP alerts to send notifications to Teams channels.
Prerequisites
You must have the IT Admin role in WXP to configure alerts in Alerts Management.
Procedure
From the left menu of WXP, click Alerts Management.
Follow the steps in the Configuring Alerts in Workforce Experience Platform guide to add Teams notifications to an alert.
When the configured alert is triggered, a notification appears in the selected Teams channel.
Each Teams alert message includes:
A title identifying the notification as an HP WXP Alert
The alert name
The severity level, such as Low, Medium, High, or Critical
The number of impacted devices
The following example shows a WXP alert notification with battery wear details for multiple devices.
.png?sv=2026-02-06&spr=https&st=2026-10-16T01%3A06%3A20Z&se=2026-10-16T01%3A24%3A20Z&sr=c&sp=r&sig=v2qXlE7hWtUK78132FYopDUA2X9rhQgLQUCYc%2BPo2m8%3D)
Note: When configuring an alert, select the Teams channel where you want to receive notifications.
Configuring Workflow Notifications
After configuring the connector, configure a workflow to send notifications to Teams channels.
Prerequisites
You must have the IT Admin role in WXP to configure a workflow.
Procedure
From the left menu of WXP, click Labs > Try Workflow.
For additional details, see Configuring Workspace Notifications for WXP Workflows to configure a workflow and send workflow notifications to Teams channels.
When the configured workflow is triggered, a notification appears in the selected Teams channel.
Each workflow notification in the selected Teams channels includes:
A title identifying it as a WXP Workflow notification
The workflow name
The date and time when the workflow was completed
Device details, including the number of devices completed, canceled, failed, and not processed
The following example shows a WXP workflow notification in a Teams channel:
Managing the Microsoft Teams Integration
You can remove individual Teams channels or disconnect the Microsoft Teams connector.
Important: WXP protects notification settings used by active workflows with a Live or Scheduled status.
Depending on your assigned roles, WXP may prevent you from removing a channel or disconnecting the Microsoft Teams connector when an active workflow is using the channel:
If you have both the Connector Admin and IT Admin roles, a dialog box is displayed showing active workflows that use the channel and prevents the channel from being removed.
If you only have the Connector Admin role, a confirmation message will appear to confirm with your IT Admin and ensure no active workflows are being used before disconnecting.
Removing a Channel
On the Integrations page, locate the Microsoft Teams connector, and then click Configure.
For the channel that you want to remove, click the Bin icon next to the channel details.
After removing the selected channels, click Save.
Disconnecting the Microsoft Teams Connector
On the Integrations page, go to the Microsoft Teams connector.
In the Microsoft Teams dialog box, under Add a Webhook, click Disconnect.
Installing a Bot to Send Pulses
Integrate HP Workforce Experience Platform (WXP) with the WXP Teams Bot to send Custom Pulses directly to employees in Microsoft Teams.
Additional Prerequisites
You must have the Teams Administrator role in Microsoft Teams.
Activating the Connector
From the left menu of WXP, click Integrations. The Integrations page is displayed.
On the Integrations page, locate Microsoft Teams and click Connect.
If a subconnector is already connected, click Manage.
Multiple connector options may appear. Under Install a bot to send Pulses, click Connect.
In the dialog box Install a bot to send Pulses, click Connect again to begin the installation process.
Sign in with your Microsoft credentials.
On the Permissions requested page, leave Consent on behalf of your organization cleared.
Click Accept.
The WXP Teams Bot connector requires the following permissions:
open_id: Allows users to sign in to the app with their work or school accounts and allows the app to view basic user profile information.
offline_access: Refreshes authentication tokens and retrieves updated tokens.
User.Read: Retrieves basic organization info, such as Microsoft 365 Tenant ID and email.
User.ReadBasic.All: Lists users in the organization.
AppCatalog.ReadWrite.All: Allows WXP to query users in the organization for the Teams bot installation status.
TeamsAppInstallation.ReadWriteSelfForUser: Allows the Teams bot application to install itself for users in the Microsoft tenant.
Once connected, the connector card displays Connected in green.
Sending a Pulse
After configuring the connector, create a Custom Pulse and send it to the selected users. A Teams Pulse can contain:
A direct message
An optional hyperlink
An optional survey
An optional company logo when a survey is included
Prerequisites
You must have the IT Admin or Pulse Admin role in WXP to create and publish a Custom Pulse.
Procedure
From the left menu of WXP, click to Pulses. The Pulses page is displayed.
Follow the steps in the Configure the Pulse content guide to create a Custom Pulse and publish it the selected users.
After the Pulse is delivered, recipients can view and respond to it in Microsoft Teams.
The following example shows a WXP Pulse notification sent directly to a user through the Workforce Experience Bot:
Disconnecting the Connector
Important: WXP protects notification settings used by Pulses with a Live or Scheduled status.
Therefore, you may be prevented from disconnecting the Install a bot to send Pulses connector when an active Pulse is configured, depending on your assigned roles:
If you have the Connector Admin role and either the IT Admin or Pulse Admin role, a dialog box identifies the active Pulses and prevents you from disconnecting the connector.
If you have only the Connector Admin role, a confirmation message instructs you to contact your IT Admin or Pulse Admin and verify that no active Pulses use the connector before you continue.
On the Integrations page, go to the Microsoft Teams connector.
Click Disconnect on the Install a bot to send Pulses.
Troubleshooting Tips
Scenario: I am unable to view the Microsoft Teams connector.
Cause: Your current WXP plan may not support the Microsoft Teams connector. The Pro or Elite plan is required to view and manage this connector.
Solution: Upgrade your WXP plan to the Pro or Elite tier.
Scenario: The Microsoft Teams Bot app displays Installed for no one in the Teams Admin Center
Cause: This value represents users or groups for whom an administrator has configured the app to be installed. It does not indicate the number of employees who installed the app independently.
Solution: This is expected behavior. The app can display this value when an employee installs the app manually or when a delegated application installs it through Microsoft Graph APIs. In app-centric management, administrators can configure installations for everyone or for selected users and groups. Microsoft also distinguishes administrator preinstallation from users installing available apps themselves. For additional Microsoft guidance, see Preinstall Teams apps for your organization’s users.
Scenario: No results appear in the Users table in the Audience tab when I try to send a Pulse to users.
Cause: The user list may not be available immediately after connector activation.
Solution: Wait a few minutes for the user list to appear. The synchronization time depends on the number of eligible users.
Scenario: I cannot view the Microsoft Teams connector.
Cause: Your current WXP plan may not support the Microsoft Teams connector. The Pro or Elite plan is required to view and manage this connector.
Solution: Upgrade your WXP plan to the Pro or Elite tier.
Contact Us
For any assistance, [create a support case] or email support@wxp.hp.com.