Skip to main content

Marketplace MS Teams Integration FAQ

This FAQ answers common questions about the marketplace Microsoft Teams integration, including capabilities, configuration, architecture, and data handling.

Why is there a new Teams marketplace app?​

The marketplace Microsoft Teams integration was introduced to align with Microsoft's recommended approach for Teams app distribution and to improve security, maintainability, and user experience. The marketplace integration leverages Microsoft's Bot Framework and Azure Bot Service, providing a more standardized and secure architecture compared to the legacy custom app.

Why the legacy custom app was deprecated:

  • Required custom authentication flows that diverged from Microsoft's recommended patterns
  • Limited scalability and alignment with Microsoft's Teams app roadmap
  • Security improvements needed to meet evolving Microsoft compliance standards

The marketplace integration addresses these limitations by using Microsoft's native Bot Framework infrastructure, simplifying installation through the Teams App Store, and ensuring better long-term compatibility with Microsoft's platform updates.

note

Learn more about Multi-tenant bot (Atlan's legacy Teams app) deprecation by Microsoft here.

What does the Microsoft Teams marketplace app support?​

The marketplace Microsoft Teams integration enables the following capabilities:

Notifications:

  • Glossary updates (new terms, changes to names, descriptions, owners, tags, etc.)
  • Workflow alerts (run status, failures, monitoring)
  • Announcements
  • Playbook runs

Bot features:

  • Microsoft-required commands (hello, help)

Integration scope:

  • Outbound notifications to configured Teams channels
  • 1 team per tenant configuration
  • Standard channels only (private/shared channels not supported)

Not supported:

  • Starred asset notifications not supported due to Microsoft architectural limitations

How do I configure the Microsoft Teams marketplace app?​

Atlan currently supports below configuration for the marketplace MS Teams integration.

  • Teams: 1 team per tenant (must disconnect existing to change)
  • Channels: Standard channels only (private/shared channels not supported)
  • Direction: Outbound notifications only to configured Teams channels
  • Commands: Supports only Microsoft-required commands (hello, help)
  • Notification level: Notifications can only be set up at the glossary level, not at individual term or category level

What data does the Microsoft Teams marketplace app store?​

The integration stores minimal configuration data and doesn't ingest Teams content or user information.

Stored data

FieldDescription
TenantIDAtlan tenant identifier
TeamsID and TeamNameConfigured team details only
ChannelID and ChannelNameConfigured channel details only

Not stored

  • Personal access tokens / User tokens
  • User information (names, emails, IDs)
  • Teams conversation content
  • Message history
  • User lists or activity streams
  • Files or attachments

These configuration details are retained until the integration is disconnected.

What does the Microsoft Teams marketplace architecture look like?​

The following components are involved in the marketplace Teams app flow.

Components

  • Microsoft Teams: "Atlan Assistant", the Atlan app on the Teams marketplace
  • Azure: Azure Bot Service hosted in Atlan's Azure infrastructure
  • AWS: Integration service (single endpoint for Azure Bot) and Vault

Architecture features

  • Internal access: Integration service for Azure Bot remains internal-only, not exposed on the public internet
  • VPN: Any Azure-to-AWS traffic goes over site-to-site VPN
  • Vault: Bot credentials storage
  • Multi-tenant: Events routed to the correct tenant back-end with data isolation
  • Data isolation: The Atlan Bot Service dynamically captures and stores the Microsoft service URL and channel ID upon installation, without requiring any broad search during the setup

How does traffic flow between Atlan and Microsoft Teams?​

Notifications flow outbound from Atlan to Teams channels, while events and commands flow inbound from Teams to Atlan.

Outbound notifications (Atlan → Teams)

  • OAuth 2.0 access token generated using Atlan Bot credentials
  • Sends notification via POST /conversations to Bot Framework API
  • Bot Framework → Bot Connector → Teams channel

Inbound events (Teams → Atlan)

  • Teams client (on user's device) → MS Bot Connector → Atlan Azure Bot → VPN → Integration service → Atlan back-end services

Inbound commands (Teams → Atlan)

  • User sends hello or help commands → MS Bot Connector → Atlan Azure Bot → VPN → Integration service → Generic response back to user

Need help​

If you have questions about the marketplace Microsoft Teams integration that aren't covered in this FAQ, contact Atlan support by submitting a support request.