This post shows how Outlook, the O2S add-in, and Power Automate (formerly Flow) spark a Teams channel conversation every time a relevant email lands in your SharePoint library.
Are SharePoint alerts overwhelming you?
Most of us drown in generic SharePoint alerts yet still want to stay informed. That is where our blend of Outlook, O2S, Teams, and Flow delivers value.
So what are the options?
- Check the shared library every day?
- Coordinate with colleagues for each uploaded file?
- Turn on broad SharePoint alerts and risk a notification flood?
None of these options scale. Automation does.
Outlook O2S, Teams, and Flow as a smart combo
Since the deprecation of Skype we primarily communicate in Teams. Channels and dedicated team sites keep projects tidy, and the Outlook O2S add-in can file emails straight into the matching SharePoint library—perfect for kicking off a Flow.
Power Automate offers ready-made connectors for SharePoint and Teams. Our solution is simple: as soon as O2S stores an email in the project library, a Flow posts its key metadata into the right channel.
How the flow works
- Trigger: A
.msgfile appears in the SharePoint library. It originates from Outlook and was uploaded through O2S. - Validation: The Flow double-checks that the new file really is an email by inspecting the file extension.
- Read metadata: Sender, subject, and any other fields O2S already filled in are read and transformed into a concise Teams status update.
Actions at a glance
Power Automate’s “Post message as the Flow bot to a channel” action even allows @mentions so the right people see the update instantly.
Result inside Teams
This setup is a lightweight proof of concept. You can easily extend it with templates, branching, or additional notifications.
What’s next
We are already prototyping more capabilities in Office 2 SharePoint so admins and project teams can share new content even faster. Reach out if you need a tailored enhancement.
:)