Connect Microsoft Teams in four steps
Someone on your sales team asked you to authorise superglass. This page is written for you, not for them. It takes about fifteen minutes and needs a Teams administrator and a Global Administrator - often the same person.
Everything below is reversible, and nothing takes effect for any employee who has not been individually named.
What this actually does
Teams already transcribes meetings when someone turns transcription on. superglass does not record, join or listen to anything. It asks Microsoft Graph for the transcript your tenant already produced, turns it into a structured sales note, and discards the text. There is no bot in the meeting and nothing to install on any device.
What superglass can and cannot see
Access is narrower than the permission names suggest, because the application access policy in step 4 is what actually decides scope. Until you name a user in that policy, superglass can read nothing about them.
It can read
- Transcripts of meetings organised by the specific people you name in step 4, and only those people.
- The subject line and invitee list of those same meetings, used to work out which customer the meeting was about.
- Directory lookups of your users by email address, so a sales rep's superglass account can be matched to their Microsoft account.
It cannot read
- Meetings organised by anyone you have not named, including everyone outside the sales team.
- Meeting recordings. superglass never requests audio or video, only the text transcript.
- Meetings hosted by another organisation. Those transcripts live in the host's tenant and are not reachable from yours at any permission level.
- Email, chat messages, files, SharePoint, OneDrive, or calendars beyond the meetings described above.
Before you start
- A Microsoft 365 licence that includes Teams transcription - Business Standard or above. Teams Essentials and Business Basic do not produce transcripts at all.
- Transcription allowed in your Teams meeting policy. If the Transcription toggle is off, no transcript is created and there is nothing for superglass to read.
- Teams PowerShell module version 7.9.0 or newer, for steps 2 and 4. Install with: Install-Module MicrosoftTeams
- The Global Administrator or Privileged Role Administrator role, to grant consent in step 1.
- The email addresses of the sales reps who should have their meetings noted. Nobody else needs to be included.
Grant admin consent
Your colleague starts this from inside superglass: Team settings, then Notetaker, then Connect Microsoft 365. That sends you to a standard Microsoft consent screen listing the permissions below. Approving it registers superglass in your tenant as an enterprise application, which you can inspect and revoke at any time.
The permissions you will be asked to approve
- OnlineMeetingTranscript.Read.All - read meeting transcripts. Narrowed to named users by step 4.
- OnlineMeetings.Read.All - read the subject and invitee list of those meetings, to identify the customer.
- User.Read.All - look up a user by email address, to link a superglass account to a Microsoft one.
These are application permissions, so they carry no user sign-in. That is deliberate: it means superglass holds no employee credentials and no refresh tokens, and removing the enterprise application cuts off access instantly and completely.
Turn on Graph API access to transcripts
This is the step almost everyone misses. Since 29 July 2026 Microsoft ships every tenant with Graph API access to transcripts switched OFF. Admin consent alone is not enough - with this setting off, every request returns 403 Forbidden and no meeting is ever noted.
In the Teams admin center
Teams admin center, then Meetings, then Meeting settings, then the Transcript API access section. Set Microsoft Graph access to On.
Or in PowerShell
Connect-MicrosoftTeams
Set-CsTeamsMeetingConfiguration -EnableGraphTranscriptAccess $trueThis setting is tenant-wide and governs which applications may read transcripts at all. It does not itself grant superglass anything - step 4 is what decides whose meetings are in scope.
Allow speaker attribution
A second, separate switch in the same place controls whether transcripts are returned with speaker names attached. It is also off by default.
Why it matters here
Without it, superglass still receives the transcript and still produces a note - but the note cannot tell who said what. Since the whole point is to record which commitments the customer made and which the rep made, an unattributed transcript produces a noticeably weaker note. superglass will show your team that attribution is unavailable rather than guessing.
Same screen as step 2: Transcript API access, then Include speaker attribution. This option only appears once Microsoft Graph access is on.
Name the people whose meetings may be read
This is the step that defines scope. An application access policy tells Microsoft which users superglass may act for. Anyone not named in a granted policy is invisible to it, regardless of the consent you gave in step 1.
Run these in Teams PowerShell
Create the policy once, naming the superglass application:
New-CsApplicationAccessPolicy `
-Identity superglass-notetaker `
-AppIds "<superglass application id>" `
-Description "superglass meeting notetaker"Then grant it to each sales rep individually, by their sign-in address:
Grant-CsApplicationAccessPolicy `
-PolicyName superglass-notetaker `
-Identity "[email protected]"A word on the tenant-wide alternative
Microsoft also allows granting a policy to the whole tenant with -Global. We recommend against it: it puts every employee's meetings in scope, including HR and one-to-ones, for no benefit. Name the sales team and nobody else.
Changes to application access policies take up to 30 minutes to take effect. If step 5 fails immediately after this, wait and try again before changing anything.
Check it worked
Back in superglass, your colleague opens Team settings, then Notetaker, and clicks Test connection. That runs a real end-to-end check: it creates a transcript subscription for one named user and deletes it again. It reports each of the four steps separately, so a failure names the step to fix.
- Consent - confirms step 1 registered superglass in your tenant.
- Transcript access - confirms step 2, by attempting the exact call that fails when the tenant switch is off.
- Application access policy - confirms step 4 covers the user being tested.
- Speaker attribution - reported after the first real meeting, because Microsoft only reveals it when transcript content is actually requested.
If something does not work
These four errors cover almost every failed setup. Each maps to exactly one step above.
| What you see | What it means | What to do |
|---|---|---|
| 403 GraphAccessToTranscriptsDisabled | The tenant-wide transcript switch is off. This is the default state of a new tenant. | Complete step 2. Nothing else will work until this is on. |
| 403 SpeakerAttributionNotAllowed | Transcripts are readable, but speaker names are withheld. | Complete step 3 if you want attributed notes. Notes are still produced without it. |
| No application access policy found for this app | Step 4 has not been done, or the policy does not cover this particular user. | Grant the policy to that user, then wait up to 30 minutes. |
| We could not find that person in your Microsoft directory | The rep's superglass email address differs from the address they use to sign in to Teams. | Correct the address in superglass, or tell your colleague which address to use. |
Nothing fails, but no notes appear
Two causes, in order of likelihood. Either nobody turned transcription on in the meeting - Teams does not transcribe automatically unless the organiser sets it in the meeting options - or the meeting was organised by the other company. A transcript belongs to the tenant of whoever created the meeting, so when your customer sends the invite, the transcript is theirs and no permission on your side can reach it. Ask your reps to send the invitation when they want the meeting noted.
How to revoke access
Three independent ways, any of which is immediate and needs no cooperation from superglass.
- Remove one person: withdraw the application access policy from that user with Remove-CsApplicationAccessPolicy, or ask your colleague to un-enrol them in superglass.
- Stop all transcript access, for every application: set EnableGraphTranscriptAccess back to $false. This is the fastest switch and affects any vendor, not just us.
- Remove superglass entirely: Microsoft Entra admin center, then Enterprise applications, then superglass, then Delete. This revokes the consent from step 1 and every token issued under it.
What happens to the transcript
superglass fetches the transcript text, extracts the sales information from it, and discards the text. The transcript is held only for the duration of that processing and is never stored: what remains is a short summary and structured fields your rep reviews and approves before anything is written to your CRM. No audio or video is ever downloaded. Our processors are named on the security page.
Questions before you approve anything
Security reviews are a normal part of this. Tell us what your team needs and we will answer directly - and if your policy requires it, we will walk through the permissions with you on a call.