diff --git a/website/content/docs/concepts/host-discovery/azure.mdx b/website/content/docs/concepts/host-discovery/azure.mdx
index 5010b4a104..a185b0a275 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 Machines and 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..31c80b1a7c 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'}}>
+    Soft-deleted users are not properly authenticated
+    </td>
+    <td style={{verticalAlign: 'middle'}}>
+    Version 0.19.0 introduced a soft delete for when a cached user's auth tokens are deleted, but there is a valid refresh token that is less than 20 days old. Boundary considers those users as deleted. But it keeps their user information in the cache so that it can restore the information, if they log in again.
+    <br /><br />
+    However, soft-deleted users were not being properly restored when they logged back in and it affected search capabilities.
+    <br/><br />
+    This issue is resolved in version 0.19.1. Soft-deleted users are now properly restored as active when they log in again if the refresh token is less than 20 days old.
+    </td>
+  </tr>
+
   </tbody>
 </table>
\ No newline at end of file