Scope explained

Download Teams chat history without admin access

You can archive a conversation already rendered for your account without requesting tenant-wide Microsoft Graph or compliance permissions — but only within the boundaries of what the browser can see and access.

What “without admin access” means

Chat Exporter does not ask an administrator to approve a Microsoft Graph application. It runs after your explicit click in the Teams web tab and reads the conversation currently available to that signed-in account.

This is appropriate for a personal working archive, migration of your own accessible conversation, or local records where organizational policy permits it. It is not a substitute for legal discovery, retention, audit, or organization-wide backup.

Visible-chat export vs. administrator export

CapabilityLocal visible-chat exportGraph / Purview / eDiscovery
SetupInstall extension and open a conversationTenant configuration, roles, consent, or compliance access
ScopeCurrent personal or group chat rendered for the userPotentially broader mailbox, tenant, legal, or policy scope
AttachmentsAttempts files accessible to the current browser sessionDepends on official API and compliance workflow
OutputLocal ZIP with HTML, JSON, CSV, links, and reportsAPI records, cases, PST or other administrator-managed outputs
Authorization bypassNoneNone; uses formal administrator/compliance permissions

Why the extension still needs browser permissions

The three Manifest V3 permissions are narrow and user-triggered:

  • activeTab gives temporary access after you invoke the extension.
  • scripting injects local code into that tab so it can inspect the rendered virtualized chat and use the signed-in page context.
  • storage remembers only the disclosure acknowledgement and file preference.

There are no static host permissions and no persistent content script that watches every Teams page.

Respect organizational policy

Technical access does not automatically grant organizational permission to archive data. Follow your employer's confidentiality, retention, legal, and acceptable-use rules. Protect the resulting ZIP because it may contain personal data, business records, or confidential attachments.

The extension cannot make prohibited data export permissible. It also cannot bypass retention, Conditional Access, CORS, deleted files, or permissions.

Practical workflow

  1. Confirm that local archiving is permitted.
  2. Open the exact Teams personal or group chat.
  3. Start Chat Exporter and choose whether to include files.
  4. Keep the tab open until the ZIP is ready.
  5. Store the archive in an approved location with appropriate access controls.
  6. Delete temporary copies when your policy requires it.

Need the exact archive format?

See how HTML, JSON, CSV, and file diagnostics work together.

Compare formats