From cd4ea6f32b8f4860f7e23a2a4be66aeff016fb31 Mon Sep 17 00:00:00 2001
From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Date: Mon, 3 Mar 2025 19:07:00 +0000
Subject: [PATCH] backport of commit e45ab9715dc1fa94f2cf924e53be35c724d8e056

---
 .../docs/concepts/host-discovery/azure.mdx    |  3 ++
 .../content/docs/release-notes/v0_19_0.mdx    | 32 +++++++++++++++++++
 2 files changed, 35 insertions(+)

diff --git a/website/content/docs/concepts/host-discovery/azure.mdx b/website/content/docs/concepts/host-discovery/azure.mdx
index 5010b4a104..19f5cf6976 100644
--- a/website/content/docs/concepts/host-discovery/azure.mdx
+++ b/website/content/docs/concepts/host-discovery/azure.mdx
@@ -7,6 +7,9 @@ description: >-
 # Azure dynamic host catalogs
 Boundary uses dynamic host catalogs to automatically discover Azure resources available through Azure Resource Manager (ARM) and add them as hosts.
 
+The Azure plugin supports Azure Virtual Machine Scale Sets in both Flexible and Uniform orchestration modes.
+It automatically discovers any individual virtual machines included in the scale sets and adds them as hosts.
+
 ## Create a host catalog to connect with Azure
 Boundary uses plugins to integrate with a variety of providers.   To use a
 dynamic host catalog to integrate with Azure, you create a host catalog of the
diff --git a/website/content/docs/release-notes/v0_19_0.mdx b/website/content/docs/release-notes/v0_19_0.mdx
index 99a801f5fe..79c4d56dc1 100644
--- a/website/content/docs/release-notes/v0_19_0.mdx
+++ b/website/content/docs/release-notes/v0_19_0.mdx
@@ -112,6 +112,20 @@ description: >-
     </td>
   </tr>
 
+  <tr>
+    <td style={{verticalAlign: 'middle'}}>
+      Azure Virtual Machine Scale Set support for dynamic host catalogs
+    </td>
+    <td style={{verticalAlign: 'middle'}}>
+      GA in version 0.19.1
+    </td>
+    <td style={{verticalAlign: 'middle'}}>
+    The Azure plugin now supports Azure Virtual Machine Scale Sets in both Flexible and Uniform orchestration modes for dynamic host catalogs. It automatically discovers any individual virtual machine instances that are part of the scale sets and adds them as hosts.
+    <br /><br />
+    Learn more:&nbsp;<a href="/boundary/docs/concepts/host-discovery/azure">Azure dynamic host catalogs</a>.
+    </td>
+  </tr>
+
   </tbody>
 </table>
 
@@ -199,5 +213,23 @@ description: >-
     </td>
   </tr>
 
+  <tr>
+    <td style={{verticalAlign: 'middle'}}>
+    0.19.0
+    <br /><br />
+    (Fixed in 0.19.1)
+    </td>
+    <td style={{verticalAlign: 'middle'}}>
+    Deleted auth tokens prevent reauthentication
+    </td>
+    <td style={{verticalAlign: 'middle'}}>
+    In previous versions, when the auth tokens associated with a user were deleted, Boundary deleted the user as well. When the user logged in later, Boundary would have to reload the user's resources before they could access them.
+    <br/><br />
+    Version 0.19.1 introduces a soft delete for when a cached user's auth tokens are deleted and there is a valid refresh token that is less than 20 days old. Boundary marks the user as deleted, so they do not show up in lists and searches. But it keeps their user information in the cache.
+    <br /><br />
+    When the user logs in again, Boundary changes the user's status to active and there is no need to reload the resources. When the refresh token is older than 20 days, Boundary deletes the user and their resources from the cache.
+    </td>
+  </tr>
+
   </tbody>
 </table>
\ No newline at end of file