Prerequisites

Before deploying the collector, ensure you have the following in place.

Azure / Microsoft 365

• A Microsoft 365 tenant with Teams calling activity.
• An Azure account with rights to create app registrations in Microsoft Entra ID.
• Rights to grant admin consent for Microsoft Graph application permissions.

The collector requires the following Graph permissions (application type, not delegated):

Permission	Purpose
CallRecords.Read.All	Retrieve call records and stream details
Reports.Read.All	Access Teams activity reports
ServiceHealth.Read.All	Access Microsoft service health announcements

See Azure Permissions for the step-by-step setup guide.

Collector Host

• Linux (recommended) or Windows server.
• Outbound network access to:
  • graph.microsoft.com
  • login.microsoftonline.com
  • reportsncu.office.com (Microsoft Graph report download redirect)
  • Your backend endpoint (Dynatrace or Splunk)
• Sufficient CPU and memory for your call volume.

Tip

The collector does not need to run on an ActiveGate or any Dynatrace component. Any host with the required network access and resources is suitable.

Note

For national cloud deployments (GCC High, DoD, China), the Microsoft Entra ID and Microsoft Graph endpoints differ from the global addresses listed above. Set cloud_deployment in your microsoft_authentication configuration — see Configuration for details.

Backend Access

Depending on your chosen backend:

Dynatrace

• Dynatrace SaaS (cloud) tenant with Grail enabled — Dynatrace Managed (on-premise) is not supported.
• Permissions to create buckets, OpenPipeline pipelines, and Credential Vault entries.
• Access to Dynatrace Hub (to install the app).

Splunk

• Splunk instance (Search Head) with admin access.
• Ability to create HTTP Event Collector (HEC) inputs and indexes.

License

A valid MS Teams Observability license is required to activate Live mode. Contact your vendor representative to obtain a license file before starting the deployment.