Microsoft Teams Native Integration

Admin consent lets Zime receive meeting recordings and transcripts from your Microsoft 365 tenant. Without it, Zime cannot receive recording data from Teams.

Two roles are involved. A Zime admin starts the connection in Zime (Settings → Recording platforms → Connect Workspace), and a Microsoft 365 admin who can grant tenant-wide consent, such as a Global Administrator, approves it on Microsoft's consent screen. One person can do both if they hold both roles. Microsoft requires this approval for the level of permissions involved.

Go to Settings → Recording platforms and click the ⓘ next to MS Teams. If the first step, Admin connects workspace, shows ✓ Done, admin setup is complete.

The button on the MS Teams row tells you too:

• Connect Workspace (Zime admins) or Admin Setup pending (everyone else): admin setup is not done yet.
• Enable Native Recording that you can click, or Setup Complete: admin setup is done.
• Enable Native Recording grayed out: your own calendar is not connected yet, so the button cannot show admin status. Use the ⓘ checklist instead.

The Recording Active status on the same row does not mean native recording is set up. It means your calendar is connected and Zime can record your meetings on that platform, possibly with the Zime notetaker (the row then shows Company Notetaker as the recording method).

The Connect Workspace button is shown only to Zime admins, and only after their own calendar is connected to Zime; until then they see a grayed-out Enable Native Recording button. If you are not a Zime admin you see Admin Setup pending instead; ask your Zime admin. Approving the connection also needs a Microsoft 365 admin.

Not on your own. If you are a Zime admin, you can start it by clicking Connect Workspace, but a Microsoft 365 admin must sign in on Microsoft's consent screen and approve it. If you are not a Zime admin, ask your Zime admin to start it.

Admin consent gives Zime's native recording app two organization-wide Microsoft Graph permissions, both read-only, and approves the delegated permissions below for all users:

• OnlineMeetingRecording.Read.All: used only to receive Microsoft's notice that a meeting recording is ready
• OnlineMeetingTranscript.Read.All: used only to receive Microsoft's notice that a meeting transcript is ready

When each organizer enables native recording, they sign in, and Zime acts on their behalf with these permissions:

• openid, profile, email, offline_access and User.Read: sign in, stay connected, and read their basic profile (name and email address)
• OnlineMeetings.Read and OnlineMeetings.ReadWrite: find the organizer's meeting and turn on "Record and transcribe automatically"
• OnlineMeetingRecording.Read.All and OnlineMeetingTranscript.Read.All: download the recordings and transcripts of meetings that organizer organizes

Admin consent approves these delegated permissions for all users, but Zime can use them only for a user who has signed in to Zime.

Zime changes only one meeting setting: it turns on "Record and transcribe automatically" for eligible meetings. There is no access to chat, mail, files or calendars.

Yes. Revoke it in the Microsoft Entra admin center (or the Azure portal) under Enterprise applications. Zime's native recording app has application ID 8674ff13-6f04-4c3f-83d7-27a5318d6ea4.

Zime then stops receiving Teams recordings, and recordings already in Zime stay in Zime. If bot fallback is on for your workspace, the Zime notetaker records eligible meetings instead. Meetings where Zime already turned on "Record and transcribe automatically", including every later meeting of a recurring series, keep recording in Teams until the organizer turns that option off in the meeting options.

Yes. An admin approves Zime once for the whole company. After that, each person who organizes meetings connects their own Teams account in Zime, and native recording works for the meetings they organize.

Yes. Admin consent is company wide, and each user then connects their own Teams account. Native recording follows the meeting organizer, so roll out to users who organize their own customer meetings.

The Teams settings (step 1) and admin consent (step 2) are done once for the company and take a few minutes each. Wait at least 30 minutes between them so Microsoft can apply the Teams settings. Each organizer's own setup (step 3) takes under a minute. After any change in Zime, wait a few minutes and refresh the page.

Meeting organizers need a Microsoft 365 license that includes Teams meeting recording to the cloud; your Microsoft 365 admin can confirm which of your plans include it. Teams Premium is not needed: Zime turns on "Record and transcribe automatically" in each meeting's options, and Microsoft requires Premium only for meeting templates, which Zime does not use.

It works with Microsoft 365 plans that include Teams cloud meeting recording. Teams Premium is not required. Your admin should also set the Teams settings in Part 1 of the onboarding guide on the Overview tab: allow cloud recording and transcription, keep automatic recording allowed, and turn on transcript access for apps.

Only during setup. A Teams admin checks the Teams settings (step 1), and a Microsoft 365 admin approves admin consent once (step 2). After that, an admin is needed only to change those settings or to revoke consent. Day-to-day use needs no admin action.

Yes. Complete admin consent once, then have only your pilot users enable native recording in their settings. Native recording follows the meeting organizer, so pick pilot users who organize their own customer meetings. Recording preferences in Zime can also limit which meetings are eligible during the pilot.

Zime uses separate Microsoft apps for separate features:

• Native recording: application ID 8674ff13-6f04-4c3f-83d7-27a5318d6ea4, approved from Connect Workspace in Zime Settings
• Zime mobile app: application ID e9b17ec8-756d-4c74-9ba9-2b761c3b42cb
• Zime app inside Teams, for prep notes: bot ID 00c3a9ee-0b6f-4099-9eef-9011792c5c95

In Microsoft Entra, find them under Enterprise applications, not App registrations. App registrations only lists apps created inside your own tenant.

Enabling it connects your Teams account, so Zime can turn on recording for meetings you organize. Without it, meetings you organize are not recorded natively; if bot fallback is on for your workspace, the Zime notetaker records them instead.

A grayed-out Enable Native Recording button means your calendar is not connected to Zime yet; hover over it and it says "Connect calendar to continue." Connect your calendar first. If the button then reads Admin Setup pending, a Zime admin still needs to connect your company's Microsoft Teams (Part 2 of the onboarding guide on the Overview tab). When both are done, you can click Enable Native Recording. The ⓘ next to MS Teams shows which step is still open.

Only for the people who organize meetings. Native recording runs through the organizer's connected Teams account, so an eligible meeting can be recorded natively once its organizer has enabled native recording, whoever attends. Attendees do not need to enable it.

If the MS Teams row shows only a dash, your workspace records with a third party recorder (for example Gong or Fireflies), so native recording is not offered. Otherwise the integration may not be set up for your organization; ask your admin to check that admin consent is done.

Meetings they organize are not recorded natively. If bot fallback is on for your workspace, the Zime notetaker keeps recording their eligible meetings as before. They can enable native recording at any time from Settings.

Native recording uses Teams-native capture. There is no visible bot joining the meeting. The recording is handled through Microsoft's own recording infrastructure, which means:

• No bot presence in the participant list
• Recording behavior is governed by Teams policies
• The experience is more seamless for participants

If Zime cannot use Teams recording for a meeting, it can send the Zime notetaker instead so the meeting is not lost. See What is bot fallback?

When Zime cannot use Teams native recording for an eligible meeting, bot fallback sends the Zime notetaker (shown as Company Notetaker in Settings) to record it instead, so the meeting is not lost. It is a workspace setting, and it is on by default. If it is off, a meeting that cannot be recorded natively is not recorded. To check or change it for your workspace, contact support@zime.ai.

Yes, for eligible meetings. 10 minutes before the meeting, Zime turns on "Record and transcribe automatically" through the organizer's connected Teams account. This works when admin setup is done, the organizer has connected Teams in Zime, the meeting matches your recording preferences, and your Teams policy allows cloud recording.

Yes. The organizer's Teams meeting policy must allow cloud recording. For the best results it should also allow transcription (for speaker names) and keep automatic recording allowed, and your admin should let apps read meeting transcripts (Teams admin center → Meetings → Meeting settings → Transcript API access). You do not need to set meetings to record automatically; Zime switches on "Record and transcribe automatically" for each eligible meeting. If a meeting does not allow recording, Zime sends the Zime notetaker instead when bot fallback is on.

No manual start is needed. 10 minutes before each eligible meeting, Zime turns on "Record and transcribe automatically" for it. The one exception: if the meeting has already started by then, start the recording yourself (see I started the meeting a few minutes early. Is it still recorded?). If Zime cannot switch it on, for example because the organizer has not connected Teams, the Zime notetaker joins instead when bot fallback is on.

The recording comes from Microsoft Teams' own cloud recording. Zime receives it through Microsoft Graph notifications that are set up when your admin connects Zime (admin consent). For natively recorded meetings, no Zime bot joins: Zime only turns on Teams' own "Record and transcribe automatically" option.

Yes. Zime's native recording integration relies entirely on Microsoft's cloud recording infrastructure. If Teams cloud recording is unavailable or disabled by policy, Zime cannot capture the meeting through this integration. When Zime can tell before the meeting that Teams recording will not work, it sends the Zime notetaker instead if bot fallback is on.

It depends on when it fails. If Zime cannot switch on Teams recording before the meeting (for example the organizer has not connected Teams, or policy blocks recording), Zime sends its notetaker instead, when bot fallback is on. If Teams recording was switched on but then fails or is stopped during the meeting, Zime only receives what Teams recorded.

Native recording can improve reliability by removing the dependency on a bot joining the meeting. Since it uses Teams' own recording infrastructure, it avoids issues like bot join failures, network delays, or participant confusion about bot presence.

Pause and resume are controlled by Microsoft Teams. If the recording is stopped and started again, Teams can produce more than one recording; Zime keeps only the first one it receives.

When Zime cannot use Teams recording for a meeting and bot fallback is on for your workspace, it sends the notetaker so the meeting is not lost. The usual reasons:

• The organizer has not connected Teams in Zime.
• The organizer is outside your company.
• Your Teams policy blocks recording for that meeting.
• Zime's check 10 minutes before the meeting could not get an answer from Microsoft in time.
• Someone switched the notetaker on by hand for that meeting in Zime. That always sends the notetaker, even when native recording would have worked.

Speaker names come from the Teams transcript. Zime cannot name the speakers when transcription was off for the meeting, or when your organization does not let apps read meeting transcripts with speaker names (Microsoft keeps this off by default).

Ask your Teams admin to allow transcription in the meeting policy, and in the Teams admin center go to Meetings → Meeting settings → Transcript API access: turn Microsoft Graph access on, then select Configure and turn Include speaker attribution on.

If transcript access was turned on after your Zime admin connected Zime, also contact support@zime.ai. Zime sets up its transcript connection at the moment of connection and needs to redo that step.

Yes, if you start it no more than 10 minutes early: Zime turns on "Record and transcribe automatically" 10 minutes before the scheduled start. If the meeting is already running by then, Microsoft does not apply that setting to it, so start the recording yourself in Teams. Zime picks it up the same way, as long as the organizer has connected Teams in Zime.

A meeting is recorded when all of these are true:

• It matches your recording preferences in Zime (Settings → Recording setup → Call Recording): External meetings (External host), External meetings (Internal host) and Internal meetings. A meeting is external when any attendee is outside your company's email domains. A user's own preference wins over the company's.
• Your admin's block rules do not exclude it: blocked domains, emails, meeting links, or an attendee limit.
• It is a regular scheduled meeting: it has a meeting link, is not cancelled, does not have a Webex link or the word "webinar" in its link, and was on the calendar before it started.
• For native recording, the organizer has connected Teams in Zime. Otherwise the Zime notetaker records it when bot fallback is on.

No. Zime only records meetings that match the configured recording preferences. Eligibility is not automatic for all meetings: it depends on how recording preferences are set up in the Zime app at the company and user level.

An eligible meeting is one that Zime is allowed to record under your settings:

• It matches your recording preferences: External meetings (External host), External meetings (Internal host) or Internal meetings. A user's own preference wins over the company's.
• Your admin's block rules do not exclude it (blocked domains, emails, meeting links, or an attendee limit).
• It has a meeting link, is not cancelled, does not have a Webex link or the word "webinar" in its link, and was on the calendar before it started.

Being eligible is separate from setup. An eligible meeting is recorded natively when its organizer has connected Teams in Zime; otherwise the Zime notetaker records it when bot fallback is on.

Yes. Recurring meetings are supported as long as each occurrence matches the configured eligibility preferences in Zime and the required setup is in place. Once Zime turns on "Record and transcribe automatically" for a recurring series, Teams keeps it on for every later occurrence (see Can I turn recording off for one meeting?).

Rescheduled meetings are generally supported as long as the updated meeting still appears in the synced calendar and matches Zime's recording preferences. Some changes may only apply to upcoming synced calendar events.

If the meeting is part of a recurring series: once Zime turns on "Record and transcribe automatically" for the series, Teams keeps it on for every later occurrence (see Can I turn recording off for one meeting?).

They are not recorded natively. Native recording starts from a calendar meeting, so an ad hoc or "Meet Now" call without a calendar invite is not captured.

The new link must reach Zime through your calendar at least 10 minutes before the meeting starts, because that is when Zime switches on recording for the meeting link it has.

Zime keeps one recording per meeting, however many of your colleagues or teammates join. If the recording is stopped and started again during the meeting, Teams can produce more than one recording; Zime keeps only the first one it receives.

Yes. Native recording runs through the organizer's Teams account. The organizer must be a Zime user (normally a colleague in your company) who has connected Microsoft Teams in Zime. If not, Zime cannot record that meeting natively and sends its notetaker instead (when bot fallback is on).

Natively, only if the organizer uses Zime and has connected Microsoft Teams in Zime (normally a colleague). If the organizer has not connected Teams, or does not use Zime, the meeting cannot be recorded natively. Zime then sends its notetaker instead, when bot fallback is on for your workspace and the meeting is eligible.

Example: your manager sends the invite and has not connected Teams in Zime. With bot fallback on, the Zime notetaker joins, even though you enabled native recording.

Not natively. When a customer hosts, the recording belongs to their Microsoft tenant and Zime has no access to it. Zime sends its notetaker to that meeting instead, if your workspace allows recording meetings hosted by external people and bot fallback is on. If either setting is off, the meeting is not recorded.

Not natively. When a customer hosts, the recording belongs to their Microsoft tenant and Zime has no access to it. Zime sends its notetaker to that meeting instead, if your workspace allows recording meetings hosted by external people and bot fallback is on. If either setting is off, the meeting is not recorded.

The meeting should appear in your synced calendar for eligibility to apply. Whether accepting the invite is strictly required depends on your calendar sync configuration, but having the meeting in your calendar ensures Zime can evaluate it against your recording preferences.

Natively, only if the organizer uses Zime and has connected Microsoft Teams in Zime (normally a colleague). If the organizer has not connected Teams, or does not use Zime, the meeting cannot be recorded natively. Zime then sends its notetaker instead, when bot fallback is on for your workspace and the meeting is eligible.

Example: your manager sends the invite and has not connected Teams in Zime. With bot fallback on, the Zime notetaker joins, even though you enabled native recording.

No, not natively. "Meet Now" and other unscheduled calls have no calendar invite, and native recording starts from a calendar meeting.

Yes. Switch the notetaker off for that meeting in Zime at least 10 minutes before it starts. If a colleague on the same meeting still has it on, the meeting is still recorded.

Teams may still record it, because "Record and transcribe automatically" stays on once Zime has turned it on: for example, Zime turned it on for an earlier meeting in the same recurring series, or you switched the notetaker off less than 10 minutes before the start. To stop that, turn the option off in the Teams meeting options, or stop the recording in Teams.

If you switch the notetaker back on for that meeting, Zime sends the Zime notetaker instead of using native recording.

Usually within an hour of the meeting ending. Long meetings can take longer because Microsoft must finish processing the recording before it sends it to Zime. If Microsoft's download is slow, Zime retries automatically. If a recording is still missing the next day, contact support@zime.ai.

After Zime receives the recording and, if available, the Teams transcript. If no Teams transcript arrives, for example because transcription or transcript access for apps is off, Zime transcribes the recording itself; that starts 20 to 30 minutes after the recording arrives, and speaker names are missing. Longer recordings take longer.

Common reasons:

• Microsoft is still processing the cloud recording
• The notification from Microsoft is delayed
• The meeting was long

If a recording has not appeared an hour after the meeting ends, check your setup and contact support.

Check the following:

• Has the meeting organizer connected Teams in Zime?
• Is admin setup done?
• Does the meeting match your recording preferences?
• Is the meeting on a synced calendar?
• Does your Teams policy allow cloud recording?
• If you changed setup, wait a few minutes and refresh.

Native recording follows the meeting organizer. Meetings organized by people who have connected Teams in Zime are recorded natively; others are recorded by the Zime notetaker when bot fallback is on. Check which organizers have connected Teams, their recording preferences, and that your Teams policy allows cloud recording for them.

Inconsistent recordings usually indicate a setup gap. Check:

• Meeting organizers: have all of them connected Teams in Zime? Native recording follows the organizer.
• Recording preferences in Zime: are they consistent across users?
• Teams policies: do they apply to everyone who organizes meetings?
• Meeting types: are some meetings falling outside your recording preferences?
• Calendar sync: are all meetings appearing in synced calendars?

A recording you start yourself in Teams is picked up when the meeting's organizer has connected Teams in Zime, the meeting is on a synced calendar, and it is eligible. If it did not reach Zime, check those three things, wait up to an hour, then contact support@zime.ai.

Wait at least an hour after the meeting ends before reporting. If the recording still has not appeared, check your setup and recording preferences, then contact support@zime.ai with the meeting date, time and participants.

If your calendar disconnects, Zime cannot evaluate upcoming meetings against your recording preferences. Reconnect your calendar as soon as possible. Note that some configuration changes apply only to upcoming calendar events synced after the setting is enabled.

Zime's security is checked by independent auditors: Zime has a SOC 2 Type II report and ISO/IEC 27001:2022 certification (see Does this support GDPR / SOC2 / HIPAA?). For Teams, Zime connects through Microsoft's standard admin consent and asks only for meeting, recording and transcript permissions, with no access to chat, mail or files.

Zime stores your data in the United States, encrypted in transit and at rest. Zime keeps its own copy of each recording and does not delete the original from your Microsoft 365.

The native recording integration covers meeting recordings, transcripts and meeting details. Zime does not access Teams chat messages, files, or other content through this integration.

For your whole organization, Zime's native recording app has read-only access to meeting recordings and transcripts, which Zime uses only to get notified when one is ready. For each organizer who connects Teams in Zime, it can read that organizer's meetings, recordings and transcripts, and turn on "Record and transcribe automatically" for eligible meetings. That is the only meeting setting Zime changes. It has no access to chats, mail, files or calendars.

Zime does not read email: neither its Teams connection nor its calendar connection includes email access. The Teams connection has no calendar access either. Your calendar connection is read only (Microsoft: Calendars.Read; Google: read only access to calendar events), and Zime uses it to find your meetings and decide which ones to record.

Yes. Revoke them at any time in the Microsoft Entra admin center (or the Azure portal) under Enterprise applications. Zime's native recording app has application ID 8674ff13-6f04-4c3f-83d7-27a5318d6ea4.

Zime then stops receiving Teams recordings, and recordings already in Zime stay in Zime. If bot fallback is on for your workspace, the Zime notetaker records eligible meetings instead. Meetings where Zime already turned on "Record and transcribe automatically", including every later meeting of a recurring series, keep recording in Teams until the organizer turns that option off in the meeting options.

Zime is independently audited:

• SOC 2 Type II: Zime has a report covering Security, Availability, Processing Integrity, Confidentiality and Privacy.
• ISO/IEC 27001:2022: Zime is certified.
• GDPR: an independent audit (December 2025) found no non compliance, with 3 items on international data transfers still being completed. Zime signs a Data Processing Agreement that includes the EU Standard Contractual Clauses.
• HIPAA: Zime does not collect, process, store or transmit protected health information, as stated in an independent HIPAA assessment (October 2025), and Zime's Data Processing Agreement does not allow health information to be put into Zime.

The reports are shared under NDA. To request them, contact your Zime representative or support@zime.ai.

Yes. Recording preferences in Zime (Settings → Recording setup → Call Recording) decide which meeting types are recorded: External meetings (External host), External meetings (Internal host) and Internal meetings. They can be set at company level and user level. Your admin's block rules can also exclude specific domains, email addresses or meeting links.

Yes. Any user can switch the notetaker off for a single meeting in Zime, and recording preferences can exclude whole meeting types. Not enabling native recording on its own does not stop recording if your workspace uses the Zime notetaker.

Teams may still record a meeting Zime does not keep: once Zime has turned on "Record and transcribe automatically" for a meeting, it stays on, including for later meetings of a recurring series, until the organizer turns it off in the meeting options.

Your company decides which meetings Zime records, through its recording preferences, and as the data controller it is responsible for any recording consent your local law requires. For Teams native recording, Zime turns on Teams recording only for eligible meetings organized by someone who has connected Teams to Zime, and Teams shows its own recording notice to everyone in the meeting.

Yes. When recording is enabled in Teams, participants are notified through Teams' built-in recording notification. The process is transparent to all meeting participants.

Yes. Recording preferences in Zime exclude whole meeting types, your admin's block rules can exclude specific domains, email addresses or meeting links, and any user can switch the notetaker off for a single meeting (see Can I turn recording off for one meeting?).

Tell your Zime representative before your contract ends. Zime can export your data, such as recordings and transcripts, in a readable format, and deletes your data after the contract ends as set out in your Data Processing Agreement. The original recordings in your Microsoft 365 are not affected.

1. In Settings → Recording platforms, click the ⓘ next to MS Teams and check that Admin connects workspace shows ✓ Done.
2. Check that the meeting organizer has connected Teams in Zime (their MS Teams row shows Setup Complete).
3. Check that the meeting matches your recording preferences.
4. Check that your Teams policy allows cloud recording.
5. Check that the meeting is on a synced calendar.
6. If you changed setup, wait a few minutes and refresh.

Separate the diagnosis into three areas:

Microsoft (Teams policies and recording):

• Does the organizer's Teams policy allow cloud recording, transcription and automatic recording?
• Is transcript access for apps turned on?
• Did the recording appear in Teams or OneDrive?

User setup:

• Has the meeting organizer connected Teams in Zime?
• Is the calendar connected and synced?

Zime:

• Is admin consent active?
• Does the meeting match the recording preferences?
• Is the meeting visible in Zime's meeting list?

• Make sure everyone who organizes customer meetings connects Teams in Zime
• Keep recording preferences in line with how your team meets
• Keep calendars connected
• Make sure your Teams policy allows cloud recording, transcription and automatic recording
• Turn on transcript access for apps, with speaker attribution
• Review recording preferences periodically

Webinar support depends on Microsoft Teams' recording capabilities for webinar-type events. Check your Teams configuration and license to confirm whether cloud recording is available for webinars in your tenant.

Large meetings are supported as long as Teams cloud recording is available for the meeting size and type. Very large meetings may have different recording behavior depending on your Microsoft Teams configuration and license.

Teams Live Events have different recording behavior than standard meetings. Support depends on Microsoft's recording infrastructure for Live Events. This may not be fully supported through the native recording integration.

Zime records the main meeting. How breakout rooms are recorded is decided by Microsoft Teams, not Zime, so check Microsoft's own guidance: Manage breakout rooms in Microsoft Teams and Start, stop, and find meeting recordings in Microsoft Teams. Do not rely on native recording to capture conversations inside breakout rooms.

The native recording integration described in this guide applies specifically to Microsoft Teams. Users on Zoom would use Zime's Zoom integration separately. In hybrid environments, each platform's integration is configured independently.