Skip to content

General FAQ

A trial license can be provided by the vendor or the team responsible for the product. It is required to activate the application and start testing in a target environment.

In your YAML config file, set license.filepath to the path of your license file:

license:
filepath: /etc/ms-teams-observability-agent/license.json

Backend-specific license fields are described in the backend pages: Standalone, Dynatrace Extension.

Is a full redeployment required after updating the license?

Section titled “Is a full redeployment required after updating the license?”

No. A reload of the configuration or a restart of the collector component is sufficient in most cases.

Can a Microsoft tenant error be caused by a missing or invalid license?

Section titled “Can a Microsoft tenant error be caused by a missing or invalid license?”

Yes. A missing, expired, or invalid license can prevent correct initialisation of certain features and produce tenant recognition or configuration errors.

What are the minimum configuration requirements?

Section titled “What are the minimum configuration requirements?”
  • A valid license file
  • Microsoft Graph credentials (tenant_id, client_id, and one auth method)
  • Required API permissions
  • Network connectivity between the Collector, Microsoft Graph API, and the output platform (Dynatrace, Splunk, or OTLP)

No, it is optional. However, without it the Sites dashboard will show all calls as “No Mapped Calls” and site compliance analysis will not be possible. See Sites File.

Yes. Pass --log-level DEBUG to the run command to enable verbose logging. Debug logs are strongly recommended for diagnosing authentication, collection, or configuration issues.

On any server meeting the technical and network prerequisites. It is not limited to a specific Dynatrace component unless your architecture requires it.

No. The essential requirement is that the host has the necessary network access, system resources, and permissions. ActiveGate is one option, described in the Dynatrace Extension FAQ.

Yes. The location can influence:

  • Network latency
  • Communication stability
  • Security compliance
  • Quality of data flows to Microsoft Graph and the output platform

What network flows and ports must be opened?

Section titled “What network flows and ports must be opened?”

The Collector must reach the required Microsoft Graph endpoints and your output platform. Validate:

  • Outbound flows to Microsoft Graph API
  • Outbound flows to the Dynatrace, Splunk, or OTLP endpoint
  • DNS resolution
  • Proxy configuration (if applicable)
  • Firewall/filtering rules

The docs define required outbound hosts and HTTPS connectivity, but no universal port matrix is valid for all enterprise proxies and backends. Validate endpoint and port requirements against your security policy.

What are the CPU, memory, and storage requirements?

Section titled “What are the CPU, memory, and storage requirements?”

They depend primarily on:

  • Call volume
  • Number of supervised users
  • Collection frequency
  • Level of detail in the collected data

No single baseline is published because usage varies by tenant call volume and enabled features. Start with standard VM sizing and monitor MSTeams_CollectionHealth plus host metrics.

How do I size the Collector for high call volumes?

Section titled “How do I size the Collector for high call volumes?”

Consider:

  • Total session count
  • Peak activity periods
  • Data granularity
  • Retry and recovery mechanisms
  • Local processing capacity

A pilot or load test is recommended for high-volume environments.

Is the solution compatible with Microsoft 365 GovCloud?

Section titled “Is the solution compatible with Microsoft 365 GovCloud?”

Compatibility with GCC, GCC High, or DoD must be explicitly validated. It depends on supported Microsoft endpoints, authentication mechanisms, and product compliance constraints. The national cloud is selected in configuration (microsoft_authentication.graph.cloud_deployment).

Does Microsoft Graph API usage incur additional costs?

Section titled “Does Microsoft Graph API usage incur additional costs?”

This depends on the APIs used, existing Microsoft licenses, and service conditions. Validate based on the actual functional scope implemented.

  1. Run ms-teams-agent validate --config ./config.yaml.
  2. Run ms-teams-agent test-connection --config ./config.yaml.
  3. Run one cycle with --ignore-state.
  4. Verify ingestion in backend.
  5. Enable or restart service mode.

Use Collector Troubleshooting if any step fails.

What should I verify first when data is missing?

Section titled “What should I verify first when data is missing?”
  1. Microsoft authentication and admin consent.
  2. Outbound connectivity to Microsoft and backend endpoints.
  3. At least one enabled output.
  4. Backend-side checks (Grail/OpenPipeline, HEC/index, or Loki).

Continue with the backend troubleshooting page: Dynatrace, Splunk, or Grafana, once collector checks are green.

Can I enable Auto Attendant and Call Queue collection?

Section titled “Can I enable Auto Attendant and Call Queue collection?”

Yes. Enable autoattendant_collection and callqueue_collection in configuration. Review prerequisites first: Configuration and Azure Permissions.