From 277e29d0b2c3f0b43f0f335c19cf6fb181747405 Mon Sep 17 00:00:00 2001
From: Thomas Youngs <58738491+tyoungs-estc@users.noreply.github.com>
Date: Wed, 6 Nov 2024 08:54:56 -0500
Subject: [PATCH] Clarification of MSI Upgrading Behavior (#1349)

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
---
 .../ingest-management/elastic-agent/install-agent-msi.asciidoc  | 2 +-
 1 file changed, 1 insertion(+), 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
index b3b882d4b..1b574f327 100644
--- 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