Microsoft Teams Setup Guide
Connect a Microsoft Teams channel to Oskuo so it can post messages on your behalf using a webhook URL.
Prerequisites
- check_circle A Microsoft Teams channel you want to post messages to
- check_circle Ability to create Power Automate Workflows (recommended) or Office 365 Incoming Webhooks (retiring April 2026)
- check_circle An active Oskuo account on any plan
Connecting Microsoft Teams to Oskuo
Recommended method (Power Automate Workflow):
-
1
Create a webhook URL. Recommended: In the Teams channel, click the ... menu → Workflows → search for "When a Teams webhook request is received" and follow the setup wizard. The generated URL will start with
logic.azure.com. Legacy: In the channel, go to Manage channel → Connectors → Incoming Webhook — this generates awebhook.office.comURL. - 2 Copy the generated webhook URL.
- 3 Open Settings → Connectors in Oskuo, find Microsoft Teams, and paste the webhook URL.
- 4 Click Test & Save. Add separate instances for each channel you want to post to.
What you can do
- check_circle Send formatted messages to a Teams channel
Try it out
Here are some things you can ask Oskuo to do:
- chat_bubble "Send to Teams: the deployment is complete"
- chat_bubble "Post a standup summary to Teams"
- chat_bubble "Send a reminder to the project channel that the deadline is Friday"
Good to know
- info Oskuo can only send messages — it can't read messages or see what others have posted in the channel.
- info Replying to specific threads isn't supported — messages are always posted as new top-level messages.
- info Direct messages to individual people can't be sent through this connector — it only posts to channels.
- info Each webhook URL is tied to one channel. To post to multiple channels, add a separate instance for each.
Keeping things secure
- lock Your webhook URL is encrypted at rest using AES-256-GCM encryption — it's never stored in plain text.
- lock Office 365 Incoming Webhooks retire on 30 April 2026 — migrate to Power Automate Workflows before then.
- lock Anyone with the webhook URL can post messages. Keep it confidential and revoke access by deleting the Workflow or webhook in Teams.
- lock All connector activity is recorded in your team's audit log so you can see exactly when messages were sent.
Troubleshooting
Messages are not appearing in the channel expand_more
Verify the webhook URL is correct and that the Power Automate workflow is still active (workflows can be paused or disabled). Check the workflow's run history in Power Automate for errors.
400 Bad Request error expand_more
The webhook URL may have expired or been deleted. Create a new webhook in Teams and update the URL in Oskuo under Settings → Connectors.
Webhook retired or no longer working expand_more
Legacy Office 365 Connectors (webhook.office.com URLs) are being retired on 30 April 2026. Switch to a Power Automate Workflow (logic.azure.com URL) to ensure continued operation.