A Facebook Page update can be copied into a Teams channel automatically, but the connection crosses two separate platforms. The clean route is a Make scenario with a Facebook Pages trigger and a Microsoft Teams action.
Make currently documents both Facebook Pages modules and Microsoft Teams modules. That supports the workflow described here. It does not prove that your tenant administrator will allow the required connections.
Before you build it
You need:
- permission to manage the Facebook Page
- a Microsoft 365 account that can post in the destination channel
- permission to connect both accounts to Make
- approval from whoever owns your organisation's data and connector policies
Make's Teams connection requests Microsoft Graph permissions for the operations it performs. Microsoft also notes that Power Platform data policies can restrict which connectors may exchange business data. Treat the Facebook post text, links and images as data leaving Meta and entering Microsoft 365.
Build the scenario
- Create a scenario in Make.
- Add Facebook Pages > Watch Posts. Choose the Page and set the point from which Make should start watching.
- Run the trigger once and publish a harmless test post. This gives Make a real sample bundle to map.
- Add Microsoft Teams > Send a Message.
- Choose a channel message, then select the Team and channel.
- Map only the fields you need, normally the Facebook post text, permalink and publication time.
- Add a fixed prefix such as
New Facebook Page post:so recipients know the source. - Save the scenario, choose a sensible schedule and turn it on.
Do not paste an unbounded social post into Teams. Microsoft's Teams connector documentation records an approximate 28 KB limit for messages posted by relevant connector actions. A short summary and link is more useful anyway.
Test the failure cases
Run four tests before relying on the automation: a text-only Page post, a post with a link, a post with an image and a deliberately long post.
Check the Make run history after each test. Confirm that the Teams message links to the correct Facebook post and does not expose internal Make data or an unusable image URL.
Facebook permissions and access tokens can change. If the scenario stops, inspect the failed module first, then re-authorise the affected connection. Do not silently add retries until you know whether the failure is temporary or a revoked permission.
Should you use Power Automate instead?
Use Power Automate when the trigger already lives inside Microsoft 365. For example, a SharePoint news item can trigger a cloud flow and post to Teams without adding Make.
For a Facebook Page trigger, Make provides the documented bridge. If company policy does not allow Make, use an approved social-management platform or redesign the source so an authorised RSS feed or webhook starts the Microsoft workflow.
Want help testing connector permissions, error handling and the Teams message design? Join Power Automate Builders.