Your colleagues are your best distribution channel when it's effortless to reach them. 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, as 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 and log in. If this wouldn't work, go back and choose 'Sign-in options' and 'Sign in to an organisation'. Here, you can fill in the Microsoft domain the company uses.
For example: company.onmicrosoft.com.
⚠️ 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.
Step 5. 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.
3. Choose your team and channel
Step 6. 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.
Optionally update the Display name to something your team will recognise.
Step 7. 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.
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.