Skip to content

Upgrade Standalone

This guide covers routine patch/minor upgrades for the standalone collector.

Prerequisites

New standalone package/binary compatible with your OS
Access to current collector host
Access to current config.yaml, license file, and collector state database
Maintenance window long enough for one restart

Backup Checklist

Back up before any change:

config.yaml
license file referenced by license.filepath
state.db (and state.db-shm / state.db-wal if present)

Example (Linux):

cp ./config.yaml ./backup/config.yaml.bak
cp /etc/ms-teams-observability-agent/license.json ./backup/license.json.bak
cp ./state.db* ./backup/

Upgrade Procedure

Replace old binary/package with the new Standalone patch/minor version.
Restart collector service/process.
Validate configuration.
Test connectivity.
Confirm healthy operation.

1) Install new binary/package

Replace the executable with the new patch/minor release from your standard distribution channel.

2) Restart service or process

Linux (systemd)
Windows

sudo ms-teams-agent service restart --instance default
sudo ms-teams-agent service status --instance default

Restart the service or scheduled task that runs ms-teams-agent.

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

3) Validate configuration

ms-teams-agent validate --config ./config.yaml

4) Test authentication and output connectivity

ms-teams-agent test-connection --config ./config.yaml

Post-Upgrade Checks

Collector logs show regular successful cycles
ms-teams-agent state show returns expected state
Data arrives in your configured backend

For operational checks and troubleshooting, see Runbook and Installation.

Quick Rollback

If validation fails after upgrade:

Stop the upgraded collector.
Restore previous binary/package.
Restore backed up config.yaml, license, and state.db if needed.
Start collector again and re-check health.