Clarification of MSI Upgrading Behavior (#1349) (#1440)

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> (cherry picked from commit 277e29d) Co-authored-by: Thomas Youngs <58738491+tyoungs-estc@users.noreply.github.com> (cherry picked from commit 76ffa45)
elastic · Nov 6, 2024 · 5a37e5f · 5a37e5f
1 parent fa8b1be
commit 5a37e5f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/en/ingest-management/elastic-agent/install-agent-msi.asciidoc b/docs/en/ingest-management/elastic-agent/install-agent-msi.asciidoc
@@ -47,7 +47,7 @@ Installing using an MSI package has the following behaviors:
 [discrete]
 == Upgrading
 
-Upgrades are not supported and are prevented by the MSI itself. Instead, all of your {agent} upgrades can be managed in {fleet}.
+The {agent} version can be upgraded via {fleet}, but the registered MSI version will display the initially installed version. Attempts to upgrade outside of {fleet} via the MSI will require an uninstall and reinstall procedure to upgrade. 
 
 [discrete]
 == Installing in a custom location