Skip to content

Common FAQ

Use the trial request form in License and provide your Microsoft 365 tenant ID so the license can be generated for your tenant.

Use License Estimation, based on Microsoft Teams activity reports and MSTeams_CollectionHealth validation.

Do not edit the license JSON content. The signature field validates license_data, and modifications invalidate the license. See License.

For host-based deployment, the collector can run on Linux (recommended) or Windows with the required network access and resources. See Prerequisites.

Which outbound network targets are required?

Section titled “Which outbound network targets are required?”

At minimum:

  • graph.microsoft.com
  • login.microsoftonline.com
  • your backend endpoint (Dynatrace or Splunk)

For some Dynatrace setups, ip-api.com can also be required for geolocation enrichment. See Collector Troubleshooting and Configure Dynatrace.

The docs define required outbound hosts and HTTPS connectivity, but they do not publish a single fixed port matrix for every environment. Validate against your network policy and backend endpoint requirements.

What are the minimum CPU and memory requirements?

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

No fixed global baseline is documented. Size CPU and memory for your call volume. See Prerequisites.

Can I enable Auto Attendant and Call Queue collection?

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

Yes. The collector supports:

  • ms_teams_autoattendant_collection
  • ms_teams_callqueue_collection

See Configuration.

Are extra Microsoft permissions required for those features?

Section titled “Are extra Microsoft permissions required for those features?”

Yes. The permissions reference states that VAAC-specific permissions are required when these features are enabled. See Azure Permissions Reference.

What should I verify first when data is missing?

Section titled “What should I verify first when data is missing?”

Start with:

  1. auth and consent for Microsoft and the backend
  2. outbound connectivity
  3. at least one enabled output
  4. collector logs
  5. backend checks such as Grail, OpenPipeline, or Splunk HEC and index configuration

See Collector Troubleshooting, Dynatrace Troubleshooting, and Splunk Troubleshooting.

Run one cycle with --ignore_state, verify ingestion, then enable service mode and monitor status and logs. See Installation and Service Management.