Agent 365 Solution: Content Hub Update Detection Restored After Package ID Mismatch

What Changed

Agent 365 solution v3.1.1 restores the stable solution content ID pattern used by v3.0.1, fixing a packaging issue in v3.1.0 that broke Content Hub update detection.

Security Impact (Visibility & Fidelity)

The v3.1.0 packaging introduced a parameterized solution ID that diverged from the hard-coded ID pattern established in v3.0.1. Content Hub marks installed packages as deprecated when the installed package contentId cannot be matched to the catalog entry. Organizations running Agent 365 v3.1.0 would not receive notifications for newer versions, potentially leaving them on a version without security updates or new detection capabilities.

The fix removes the top-level solutionId parameter from the ARM template and restores the v3.0.1 stable pattern: azuresentinel.azure-sentinel-solution-a365observability with direct variable resolution rather than parameter-based resolution.

Per the release notes, v3.1.0 is now flagged as not recommended due to this Content Hub compatibility issue.

Affected Files

(packaging artefacts: 3.1.1.zip, ReleaseNotes.md, SolutionMetadata.json, Solution_A365.json, mainTemplate.json)