Connecting Microsoft Teams

This is a task for the Microsoft 365 admin. The connection applies to your whole organisation and is set up once, not per user.

With the Teams connection, recordings and transcripts of your meetings arrive in Converdo automatically, where they are written up and scored. No bot joins your meeting and nobody has to upload anything.

There are three actions, all one-off. All three are required: skip one and the connection will look healthy in Converdo while no conversation ever appears. Allow about half an hour, waiting time included.

What you need

A Microsoft 365 admin with the Teams administrator or Global administrator role.
A Windows computer where you can open PowerShell. It ships with Windows; there is nothing to install.
Owner rights in Converdo, because the connection applies to the whole workspace.

You will need Converdo's app ID twice. It is not a secret, so you can paste it as-is:

e1c313c1-288c-4512-9a4b-e0bc3fa35774

We send you a ready-made consent link. It looks like this, with your own tenant ID in it:

https://login.microsoftonline.com/{your-tenant-id}/adminconsent?client_id=e1c313c1-288c-4512-9a4b-e0bc3fa35774

Open the link, sign in as an admin and review what access Converdo is asking for. There are exactly two: read meeting recordings and read meeting transcripts. Click Accept.

You land on a confirmation page afterwards. Nothing else happens in this step, and that is fine.

Action 2: enable transcript access

Microsoft turns access to transcripts off by default, even after you have granted consent above. That switch is separate from the app permissions and has to be turned on independently.

Go to the Teams admin center (admin.teams.microsoft.com).
In the left-hand menu, click Meetings → Meeting settings.
Find the Transcript API access block and set Microsoft Graph access to On.
In that same block, click Configure and also set Include speaker attribution to On.

That second switch is what lets us see who said what. Without it the transcript still arrives, but without names, and then Converdo cannot tell the rep from the customer.

Save. Both switches should now read On.

Action 3: let Converdo access the meetings

Microsoft offers no screen for this. It can only be done through PowerShell. That sounds heavier than it is: you open a window, paste four lines and you are done.

Opening PowerShell

Click Start, type powershell and click Windows PowerShell.

Do NOT click "Run as administrator". This is not excessive caution but the mistake people actually make: a window running as administrator signs in under a different user context and gets stuck at the sign-in step. A regular window is exactly right.

The first two lines: signing in

Paste this line, press Enter and wait for it to finish:

Install-Module MicrosoftTeams -Scope CurrentUser -Force

This fetches the Teams administration module. It takes half a minute to two minutes and you will see a progress bar. If PowerShell asks whether you want to use an untrusted source, answer A and press Enter.

Then paste:

Connect-MicrosoftTeams

A browser window opens where you sign in with your admin account. When this goes well that window closes by itself and PowerShell prints a line containing your account name, your tenant and your tenant ID. That is your sign that you are connected.

Getting error code AADSTS530035? Then something is off about the way you are signing in, not about your permissions. Two causes, both fixable: you are using -UseDeviceAuthentication, or your window was started as administrator. Close the window, open a regular PowerShell window and use plain Connect-MicrosoftTeams with no additions. That opens the normal sign-in page and does work.

The last two lines: the access rule

Paste this block in one go. The backticks at the end of the lines belong there — they tell PowerShell that the command continues on the next line.

New-CsApplicationAccessPolicy -Identity Converdo-Meetings `
  -AppIds "e1c313c1-288c-4512-9a4b-e0bc3fa35774" `
  -Description "Converdo: read meeting recordings and transcripts"

And then:

Grant-CsApplicationAccessPolicy -PolicyName Converdo-Meetings -Global

When this goes well, very little happens on screen. PowerShell prints errors in red text; if your screen stays free of red, it worked. That feels anticlimactic, and it is nonetheless the normal outcome.

What -Global means: the rule applies to everyone in your organisation who does not have their own, different rule. If you would rather scope it to a single team or department, let us know and we will send the group-based variant.

Allow 30 minutes

This last step can take Microsoft up to 30 minutes to take effect. That is a property of Microsoft, not of Converdo. If no conversations show up during that half hour, wait it out before calling us — in the vast majority of cases it resolves itself.

Make sure there is something to collect

The three actions above give Converdo access. They do not cause a recording to exist. Four conditions in Teams itself govern that, and all four have been measured:

Transcription must be on. This is not optional if you want recordings: Microsoft does not hand over recordings at all for a meeting held without transcription. Enable it in your meeting policy, and note that it is both an organiser and a user setting.
Cloud recording must be on in the meeting policy (AllowCloudRecording).
The organiser needs OneDrive. Without OneDrive the recording lands in Microsoft's temporary storage instead of OneDrive or SharePoint, and it is gone after 21 days — for you too.
Only privately scheduled meetings are supported. The meeting has to be attached to a calendar appointment; channel meetings do not come through.

Using it

Once everything is in place there is nothing left to do.

Schedule a meeting in your calendar and start it.
Record. The recording belongs to the organiser of the meeting.
End the meeting.

Microsoft processes the recording and the transcript first; that takes a few minutes up to a quarter of an hour. The conversation then appears in your Meetings overview by itself, with transcript, summary and scores.

If it does not work

No conversation ever appeared, and the connection looks fine. This is the classic outcome of a skipped third action: consent and transcript access are in place, everything looks healthy, and the access rule is missing. Go through action 3 once more — and remember it needs 30 minutes.

The first conversation has not arrived, but it has been less than half an hour. Wait out the 30 minutes. Microsoft needs that time to apply the access rule.

AADSTS530035 appeared during sign-in. See the note under action 3: use a regular PowerShell window and plain Connect-MicrosoftTeams.

The conversation is there, but the speakers have no names. Then Include speaker attribution was off during that meeting. Turn it on for future meetings; it cannot be applied retroactively.

A channel meeting did not come through. That is expected: only privately scheduled meetings are supported. Schedule it as a regular calendar appointment instead.

The recording disappeared after three weeks. Then the organiser had no OneDrive. The recording went to temporary storage and Microsoft deletes it after 21 days.

What Converdo collects and stores

Converdo collects only the recording and the transcript of your meeting, plus light metadata about the meeting itself, such as the start time and the duration.

Converdo does not collect chat messages, files or email, does not look at your calendar, and does not change or delete anything in your Microsoft environment. Access is read-only and limited to meeting recordings and transcripts.

The data is stored within the EU and follows your workspace's retention period. The data processing agreement sets out exactly who processes which data.

Disconnecting

Let us know and we will stop the connection and remove the subscriptions on your tenant.

If you also want to withdraw it from your side, use this line in PowerShell:

Grant-CsApplicationAccessPolicy -PolicyName $null -Global

You can also revoke consent in the Entra admin center, under Enterprise applications → Converdo. From that moment no new meetings come in. Conversations already in Converdo are kept and follow your workspace's normal retention policy.