Tanium Cloud Automate Updates & Release Notes

Tanium Automate now runs your existing Ansible playbooks on Tanium-managed Linux endpoints for Tanium Cloud customers. You hand an Ansible playbook to Tanium Atlas and pick a computer group; the Tanium Client delivers that playbook to each endpoint, and Ansible runs it there against that endpoint alone.

Features

• Introduced Ansible Playbook Runs in Atlas, letting you run Ansible playbooks on Linux endpoints through the automate.ansible_playbook.run.v2 automation operation, driven from Atlas in plain language. Every run requires approval before anything reaches an endpoint.
• Introduced support for inline YAML or an uploaded archive as the source of a playbook run. Paste a single Ansible playbook into the prompt for a quick fix, or upload an archive of your repository. For uploads, Tanium returns a SHA-256 hash that identifies the archive on later runs.
• Introduced check mode drift detection, letting you run any Ansible playbook as a dry run. Endpoints report what would change and write nothing. The run returns DRIFTED and names every endpoint that no longer matches.
• Introduced targeting by group or host list. Target an existing computer group by name, or name hosts explicitly. Drifted hosts from a check run become the targets of the remediating run.
• Introduced per-endpoint results reporting. Each run reports play statistics (ok, changed, failed, unreachable) and names endpoints that failed, drifted, went unreachable, or never responded, with the failing task and Ansible's own message. The Automate - Ansible Run Log sensor returns the last lines of output on request.
• Introduced a content model where content stays on your network. Tanium never connects to your Git repository or downloads Ansible content on your behalf. You build the upload yourself, so credentials and internal repository content stay with you.

Known Limitations

• Linux endpoints with the Tanium Client, plus Python 3.10+ and ansible-core 2.11+ installed system-wide. Uploading Ansible playbook archives requires write package permission on a content set.
• Ansible playbooks must run against the local host only. Plays that batch across hosts (serial), delegate to another host, or use a non-local connection are rejected, and your repository's ansible.cfg is not applied.
• Each operator needs to saves an Automate playbook once before their first run, so Automate can issue a platform token. Runs execute as the requesting user, not a service account.
• Not in the preview: Windows and macOS endpoints, Ansible Vault, cross-host orchestration such as rolling restarts, direct Git integration, scheduled drift checks, and a console page for playbook runs. Atlas is the interface.

Improvements

• Added a Scope field for OAuth 2.0 authentication configurations, so client credentials grants can be completed against providers like Azure/Entra that require a scope parameter in the token request.
• Added playbook step summaries in Atlas for additional step types

Resolved Issues

• Resolved an issue where playbook schedules and triggers could become permanently stuck and stop running when the owning user's API token expired, with no indication that they were no longer active.
• Resolved an issue where a Ring Deployment step's endpoint targeting using Question Criteria with multiple sensors, including at least one parameterized sensor, dropped the parameter and caused all rings to compute 0 eligible endpoints.
• Resolved an issue where a Ring Block step showed 0 eligible endpoints per ring for Intune entity targets even when eligible Intune entities existed.
• Resolved an issue where Endpoint Execution and Software Deployment steps could be saved without endpoint targeting, which could cause unpredictable failures at run time.
• Resolved an issue where a run could show as finished while a step remained incorrectly stuck in progress as earlier steps were still completing background result collection.
• Resolved an issue where a playbook trigger's Enable action remained unavailable after the trigger was edited, even though it was no longer disabled due to missing overrides.

Features

• Introduced a Playbooks list component in Atlas that displays Automate playbooks in a sortable data grid with columns for name, author, last modified, content set, schedules, triggers, and active runs
• Introduced a Playbook Runs list component in Atlas that shows active and recent runs, and added the runs list to the playbook component view
• Introduced Pause, Resume, and End controls on the Playbook Run component in Atlas, with confirmation prompts when actions are agent initiated
• Introduced detailed per step summaries in the Atlas playbook component

Improvements

• Added action status counts (Completed, Failed, Running) and a direct link to Action History in email notifications when a playbook step fails, so recipients can see why a step failed without opening the run
• Added additional playbook details to the Atlas playbook component, including description, last modified information, and content set, for parity with the classic view
• Added a View Playbook Details button and renamed View Details to View Run Details on the Playbook Run component for clearer navigation
• Added a No Results message to the playbook run view when a step completes with zero endpoint results, such as when targeting matched no endpoints
• Added an explanation for the endpoint count difference when pivoting from a Reporting dashboard into an Automate playbook, since Reporting counts cached endpoints while Automate counts endpoints currently online

Resolved Issues

• Resolved an issue where playbook triggers retried indefinitely on an API token authentication failure
• Resolved an issue where findings based subscriptions could fail to establish at service startup due to a race with the message bus connection, preventing findings triggers from firing
• Resolved an issue where the Enable action for a trigger remained greyed out after the user edited the trigger to correct missing parameter overrides
• Resolved an issue where the Enable action for a schedule was not greyed out after the schedule was disabled due to missing parameter overrides

Features

• Introduced endpoint sequence steps, improving the speed of running sequenced actions directly on endpoints.

Improvements

• Added an "Interrupted" status for playbook runs so it is clear when a ring deployment stopped because its progression criteria were not met, rather than appearing paused.

Resolved Issues

• Resolved an issue where using Apply Latest Configuration on selected playbooks updated every playbook that used the API configuration, not just the ones selected.
• Resolved an issue where parts of the Automate interface displayed in English even when the console was set to another language.
• Resolved an issue where email notification failures showed a generic error message, making the actual problem hard to identify.
• Resolved an issue where a user could skip the wait between deployment rings on playbook runs they did not have permission to manage.
• Resolved an issue where resuming a ring deployment step did not appear in the step's event history.
• Resolved an issue where a ring deployment step continued to show as "In Progress" even after its playbook run had completed.
• Resolved an issue where endpoint targeting did not include Endpoint Provider entities, such as Microsoft Intune devices, preventing them from being targeted in playbooks.
• Resolved an issue where the "Start Next Ring" button remained visible on a ring that failed its progression criteria, even after the next ring had already started.

Features

• Introduced the API step, enabling playbooks to make outbound HTTP API calls to external systems

Improvements

• Added enhanced API support for Atlas.

Resolved Issues

• Resolved an issue where playbooks could get stuck in a "pausing" state.
• Resolved an issue where a user could not disable triggers they did not create, despite having the appropriate permissions.
• Resolved an issue where a ring with no applicable endpoints still progressed to the next ring
• Resolved an issue where Wait steps show time remaining for the playbook rather than the parameterized value

Features

• Introduced playbook triggers, allowing playbook runs to be automatically launched on a time-based schedule without manual intervention.
• Introduced an enabled/disabled toggle on the trigger edit form, giving users direct control over activating or deactivating a playbook trigger without deleting it.
• Introduced a warning banner on the Playbook Detail page when a step's source package has drifted from the current version.
• Introduced a "View Package Details" option on the Edit Preview panel for both derived and source packages, making it easier to inspect package configuration before saving changes.

Improvements

• Added an Automate playbook display component to Atlas, enabling AI-assisted agents to view playbooks through the Atlas interface.

Resolved Issues

• Miscellaneous bug fixes and performance improvements

Features

• Introduced additional common platform actions including start/stop/restart service, service - set start mode, and remove custom tag, for easier accessibility when creating playbooks.

Improvements

• Added Computer Group visibility filtering to step targeting, so users only see groups they're entitled to.
• Added a Last 7 Days default filter on the Playbook Runs page, in replacement of the Last 30 days filter.
• Added clearer step completion status displays, making completion state easier to undestand.

Resolved Issues

• Resolved an issue where cron shortcut expressions were not being properly recognized.
• Resolved an issue where adding or editing a schedule on a non-parameterized playbook incorrectly took the user to the Steps tab.
• Resolved an issue where users without Patch permissions could attempt to start playbooks that used Patch steps with Patch Lists.
• Resolved an issue where Patch User Notification settings could not be edited without modifying other settings.

Improvements

• Added the playbook list to default to sort by Last Modified.
• Added the ability to fuzzy search by playbook ID or name for playbook runs and ring deployments.

Resolved Issues

• Resolved an issue where playbooks could not be exported.
• Resolved an issue where the entire playbooks connection was nulled out when an export failed.
• Resolved an issue where the playbook and overview pages would crash when navigating to a page and then clicking the menu item for that same page.
• Resolved an issue where the View in Patch link was missing from runs with Install Patch steps.
• Resolved an issue where playbooks containing steps with deleted computer groups could still be run.
• Resolved an issue where "Apply for" was misleadingly disabled when targeting had a missing sensor.
• Resolved an issue where the playbook details schedules list did not show more than 20 items.