Migrate from Standalone to Extension

This page covers the steps to stop an existing standalone agent (v1 or Standalone) and switch to the Dynatrace Extension.

Tip

You can configure and validate the extension while the standalone agent is still running — both will collect data in parallel without causing errors. However, running both simultaneously duplicates log ingestion and increases Dynatrace costs. Stop the standalone agent once you have confirmed the extension is working.

Step 1 — Stop the standalone agent

Linux (systemd)

sudo systemctl stop ms-teams-observability-agent@default.service
sudo systemctl disable ms-teams-observability-agent@default.service
# Confirm the service is stopped
sudo systemctl status ms-teams-observability-agent@default.service

If the agent runs via cron instead of systemd:

crontab -e
# Remove the line that invokes ms-teams-agent

Windows (Task Scheduler)

schtasks /End /TN "<your-ms-teams-agent-task>"
schtasks /Delete /TN "<your-ms-teams-agent-task>" /F

Or open Task Scheduler (taskschd.msc), locate the task, and delete it.

Step 2 — Install and configure the extension

Follow the Extension Installation guide.

Step 3 — Post-migration cleanup

Once the extension is confirmed working:

1. Remove the standalone agent binary and configuration files from the host.
2. Remove the license file from disk (credentials are now managed by Dynatrace).
3. Remove any cron jobs or scripts that launched the standalone agent.

Note

The extension does not import the standalone agent’s previous state file. On the first run it may re-process recent calls (within maxCallDuration hours). Duplicate events are idempotent in Dynatrace Logs, so this is safe.