Skip to main content

How to connect Microsoft Teams

Step-by-step guide for connecting a Microsoft Teams channel so your colleagues get every update where they already work.

Written by Victor

Work in progress, coming soon!

Your colleagues are your best distribution channel — but only if reaching them is effortless. Connecting Microsoft Teams lets you push social posts and Broadcasts straight into a Teams channel, with a one-click link your team can use to share content to their own networks. No more copy-pasting links into a group chat and hoping someone picks them up.

This guide walks you through connecting Microsoft Teams to StoryChief, picking the right team and channel, and checking that everything works.

🔔 Note: Microsoft Teams is an Employee advocacy channel. You need permission to manage integrations in your workspace, and employee advocacy has to be included in your plan.


Before you get started

You'll need to have completed the following before starting:

  • A Microsoft work or school account that is a member of the team you want to publish to. Personal Microsoft accounts are not supported.

  • Membership of the specific Teams channel you want to publish to — StoryChief can only list teams and channels the connected user has joined.

  • Permission to manage integrations in your StoryChief workspace.

  • Depending on your organisation's settings, a Microsoft 365 administrator may need to approve StoryChief's access during sign-in. Check with your IT team if you expect this.


Start connecting Microsoft Teams

1. Add the destination

Step 1. Open your Channels page by expanding the top-right menu and clicking Integrations. 👉 Quick link.

Step 2. Choose the Employee advocacy category and select Microsoft Teams. 👉 Quick link.

Step 3. Click Add new destination. You'll be sent to Microsoft to sign in.

2. Sign in with Microsoft

Step 4. Pick the Microsoft work account you want to publish with, then review the permissions StoryChief asks for and click Accept.

StoryChief requests read access to your profile, the teams and channels you belong to, and permission to send messages to those channels. It never reads existing conversations.

🔔 Note: Messages are posted as the Microsoft user who signs in here. Your colleagues will see that person's name on every update, so connect with an account that makes sense for your team — a marketing or communications account works well.

⚠️ Caution: Some organisations require an administrator to approve third-party apps. If you see a message saying approval is needed, forward the request to your Microsoft 365 admin and complete the connection once they've approved it.

3. Choose your team and channel

Step 5. You'll land back in StoryChief. Open the Team and channel dropdown and select where your updates should be posted. Channels are listed as channel name at team name.

Step 6. Click Save settings. Your destination is now configured and ready to use.

💡 Tip: Channels marked with a 🔒 are private or shared channels. You can publish to them as long as the connected Microsoft user is a member.

Limitation: Each Teams channel can be connected once. Channels already in use appear as (already added) and can't be selected again. To post to several channels, add a separate destination for each one.

4. Rename and verify

Step 7. On the destination's settings page, update the Display name to something your team will recognise, then click Save settings. This name is internal — it's what you'll see when picking channels while publishing.

Step 8. Send something to test it. Create a social post or a Broadcast, enable your Microsoft Teams channel, and check that the message lands in Teams.

Your colleagues will see the message together with a link they can click to open the shareable version and post it to their own social networks.

💡 Tip: Employee advocacy channels don't collect analytics inside StoryChief. Track engagement on the shared posts themselves and in your Broadcast reporting.


If the connection breaks

Microsoft access tokens expire, and a password change or a revoked app approval can disconnect your channel. When that happens, the destination is flagged with an authentication error.

Step 1. Go to Integrations > Microsoft Teams.

Step 2. Click Reconnect next to the affected destination and sign in with the same Microsoft account.

🔔 Note: Reconnect with the account that set up the destination. Signing in with a different user can leave the destination pointing at a channel that user isn't a member of.


🎉 You're done, grab a coffee, you deserve it!

Check out the next steps below for more in-depth guides or follow-up actions.


📚 Next steps

Did this answer your question?