---
title: "11.7.1.xxx Hotfix Release Notes"
slug: "11-7-0-xxx-hotfix-release-notes"
status: "update"
updated: 2026-06-09T07:35:21Z
published: 2026-06-09T07:35:21Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 11.7.1.xxx Hotfix Release Notes

## 11.7.1.31

### Fixed

Improved login reliability to ensure users retain access after authentication.

## 11.7.1.29

### Changed

#### OAuth 2.0 Authentication with Microsoft Entra ID for the SysTrack AI MCP Server

The SysTrack AI MCP server now supports OAuth 2.0 bearer token authentication with Microsoft Entra ID, in addition to the existing SysTrack API key header. See [SysTrack AI Authentication](/documentation/docs/systrack-ai-authentication#oauth-20-bearer-token-authentication-with-microsoft-entra-id).

### Fixed

Data egress size estimation and exports now complete successfully when report view tables contain unexpected date values.

## 11.7.1.22

### Changed

#### User-to-System Authorization for SysTrack AI End-User Channels

SysTrack AI now enforces user‑to‑system authorization for conversations in end‑user channels like SysTrack AI for Microsoft Teams, Voice, and programmatic access via API and MCP. Users must provide a system name, and SysTrack validates that the system is associated with the requesting user. MCP integrations can retrieve eligible systems using a [new tool](/documentation/docs/systrack-ai-mcp-server-documentation#get-user-systems), while API integrations use a [new endpoint](/api/apidocs/get-systems-linked-to-a-user). This update improves security and aligns system access with expected user ownership. For more information, see [User Identity and Access Enforcement in SysTrack AI](/documentation/docs/user-identity-and-access-enforcement-in-systrack-ai).

## 11.7.1.18

### Fixed

Pulse: Find and Run Automation enabled on tenants configured with custom domains.

## 11.7.1.16

### Fixed

Reporting (RPT) tables don't include rows for systems that have been removed. (16046)
