Microsoft TeamsComing
Microsoft Teams to LinkedIn posts: built, waiting on Microsoft.
Not connectable yet outside our own organisation: the Microsoft Teams connector is built, and Microsoft's publisher verification has to clear before other organisations can consent to it. When it opens, you connect Microsoft 365 once, read-only, and about once a week Sonar reads your Outlook calendar's last seven days and, once your admin approves it, the transcripts of your Teams meetings, keeps the moments worth saying, and drafts LinkedIn and X posts in your voice from them.
Where it stands
Built. Waiting on Microsoft.
The connector is built and our own Microsoft 365 organisation has consented to it. Before people in other organisations can consent, Microsoft requires the publisher to be verified, and that verification is still pending. Until it clears, the switch is in Sonar but the consent will not go through for an organisation other than ours.
What is done
The Microsoft 365 connection, the Outlook calendar read, the Teams transcript read, the admin-consent hand-off, the row in Settings and the miners behind it. Nothing on this page is planned; it is written and waiting.
What is pending
Microsoft's publisher verification of the app. It is a Microsoft process with its own clock, and it is the one thing between this page and a live switch for every Microsoft 365 organisation.
What you can do
Email hello@meetdistilled.com and we will tell you the day it opens. Meanwhile Fireflies records Teams calls too, and connects today.
What Sonar reads
Two halves: the calendar for everyone, the transcripts once your admin says yes.
The base connection asks only for what a Microsoft 365 user can grant alone. Teams transcripts are a separate ask, because Microsoft requires an administrator's consent for that scope in your organisation. Here is exactly what each half reads, what stays, and what never does.
Reads, on the base connection
- Events on your Outlook calendar from the last seven days, up to 60.
- For each one: the day, the subject, up to six attendee names, and the first 160 characters of the invitation text.
- Through permissions a Microsoft 365 user can grant alone: your profile, your calendar, your online meetings, all read-only, plus the refresh that keeps the connection alive.
- Work or school accounts only.
Reads, once transcripts are approved
- The transcripts of your Teams meetings from the last seven days: of the week's meetings with a Teams link, the first five that have a transcript.
- Each transcript as text, speaker-attributed, up to 6,000 characters per meeting.
- Through one more permission, OnlineMeetingTranscript.Read.All, which only an administrator in your organisation can approve. Sonar asks for it only when you press Add Teams transcripts, and hands a non-admin the link to forward.
- If your organisation has switched off transcript access for apps, Sonar says so on the row instead of guessing.
Keeps
- The moments it mined: a title, an angle, one line of detail, and the meeting subject they came from.
- Two or three debrief questions from the calendar read, until you answer or dismiss them.
- A receipt of the read on the Microsoft 365 row in Connected sources: how many meetings and up to five subjects, and, once transcripts are on, how many transcripts and their subjects.
- A refresh token, so next week's read runs without asking you again.
Never keeps
- The calendar text or the transcript text. Each is assembled into one transient block, mined in a single pass, and discarded.
- The attendee list. It rides the week's text into the read so a 1:1 can be told from a team review, and leaves with it.
- Video or audio. Sonar reads the transcript file; the recording stays in Microsoft 365.
- Any moment past the retention you set, if you set one: 30 days, 90 days or a year.
From a Teams week to a post
The calendar knows a call happened. The transcript knows what was said.
With the calendar alone, Sonar asks you what came of the call. With the transcript, it already knows. An invented week, run the way yours would be.
01
On your Outlook calendar
Vendor renewal
Monday, 14:00 to 14:30 · 3 attendees · Teams
Sonar asks, on Home:what got decided in Monday's vendor renewal?
You, one line: we walked away from a 40% increase, and a new number arrived the next morning.
Read as one line: the day, the subject, who was there, the first 160 characters of the invitation. The calendar half runs on the base grant, no admin needed.
02
With the transcript, the moment arrives on its own
Decision · Teams: Vendor renewal
We walked away from a 40% renewal increase
Angle: the renewal price is a question, and the first answer is rarely the last.
Once transcripts are on, the call itself is read as text, and the moment needs no question. A title, an angle, one line of detail, and the meeting it came from; the transcript is discarded after the pass.
03
The draft that was waiting
LinkedIn draft · waiting for your approval
A vendor raised our renewal by 40%. We said no and ended the call. The new number was in my inbox before the next morning's coffee.
The freshest moments are dealt into your weekly deck as drafts in your voice, and every moment is one tap from a draft on Home. Keep one and it lands on your board.
Invented for this page. Look at what is not in it: the vendor's name, or the names of the people on the call. The meeting subject stays in Sonar as provenance for your eyes only; the moment and the post say "a vendor". That is the people rule, and it holds for every source, not only this one.
How it will connect
One switch for the calendar. One more for the transcripts.
- The Microsoft 365 switch.
- In Settings, Connected sources, the Microsoft 365 row sends you to Microsoft's consent screen with the base permissions only: your calendar and your online meetings, read-only. You approve as yourself; no administrator is involved.
- The first calendar read.
- You land back in Sonar and the first read runs on its own: the last seven days of your Outlook calendar, mined the same way Google Calendar is. Moments and two or three questions appear on Home, under Sonar asks, each naming a real meeting and day.
- Add Teams transcripts.
- The row shows an Add Teams transcripts button. Press it and Microsoft asks for the one transcript permission. If you are your organisation's Microsoft 365 administrator, you approve it there and then.
- Or forward the link to your admin.
- If you are not the administrator, Microsoft declines, and the row hands you a link to send your IT admin. One click on their side grants the permission for your organisation; they land on a confirmation page that tells them to send you back to Add Teams transcripts, and the next press finishes it.
- Teach your spoken register, if you want to.
- Teams transcripts name who said what, so with the switch in Settings, Voice turned on they can also teach how you talk. Off by default; the switch names every source it would read.
- Run it yourself any time.
- About once a week is the cadence. The Sync all button at the top of Connected sources runs every connected source now.
This is the flow as it is written, and it will be the setup guide on this page the day Microsoft's verification clears. Turning it off is the same switch: Sonar deletes the stored tokens and the row's receipt. Moments already mined stay yours to keep or delete in Settings, Intelligence, Moments. The same two-part design already runs for Google, where Google Calendar is the base and Meet transcripts are the upgrade.
FAQ
Questions about Teams.
Your week is already in Microsoft 365.
Sonar is ready for it; Microsoft's verification is the wait. Everything else connects today, from Google Calendar to Notion, all listed on Integrations. The full account of what is read and kept is the privacy policy. Anything else, ask support.