diff --git a/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md b/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md
index 0b4ba194d21..ae1554affe7 100644
--- a/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md
+++ b/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md
@@ -285,6 +285,11 @@ The process to remove a site server in passive mode is the same as any site syst
 
 When you remove any other site system role, the site component manager (`sitecomp`) processes the request. When you remove a site server in passive mode, the failover manager processes the request. For status, monitor the **SMS_FAILOVER_MANAGER** component.
 
+After you have removed a passive site server role, the **SMS Provider** role is not automatically removed and you cannot remove the server from Configuration Manager because it still has a role. You need to start Configuration Manager Setup from the site server and select **Site Maintenance** to remove the **SMS Provider** role. 
+
+> [!NOTE]
+> Tenant attach will use the first **SMS Provider** server in the site. If you don't remove the **SMS Provider** role from the server, tenant attach will continue to use it even though the server no longer has a site server role.
+
 ## Next steps
 
 [Flowchart - Set up a site server in passive mode](passive-site-server-flowchart.md)