Merge pull request #299242 from dknappettmsft/avd-shu-key-vault-issue

AVD SHU key vault clarification

Author: prmerger-automator[bot]

articles/virtual-desktop/session-host-update-configure.md

@@ -71,7 +71,7 @@ Before you update session hosts using session host update, you need:
 
    - Configure the key vault access configuration to allow [Azure Resource Manager for template deployment](../azure-resource-manager/managed-applications/key-vault-access.md#enable-template-deployment).
 
-   - Configure the key vault network settings to [Allow public access from all networks](/azure/key-vault/general/how-to-azure-key-vault-network-security).
+   - Configure the key vault network settings to [Allow public access from all networks](/azure/key-vault/general/how-to-azure-key-vault-network-security). This requirement is a known issue; support for key vaults that don't allow public access is planned.
 
 - For any custom configuration PowerShell scripts you specify in the session host configuration to run after an update, the URL to the script must be resolvable from the public internet.
 

articles/virtual-desktop/session-host-update.md

@@ -93,7 +93,7 @@ With only a reduced number of session hosts available, you should schedule an up
 
 Here are known issues and limitations:
 
-- The current session host configuration version isn't displayed in the session host blade in the portal. Until this issue is fixed, you can access the portal using [this portal URL](https://portal.azure.com/?feature.hostpoolVirtualMachinesBladeV3=false#home) to view the current configuration version.
+- Session host update only supports key vaults that are configured to [allow public access from all networks](/azure/key-vault/general/how-to-azure-key-vault-network-security).
 
 - Session host update is only available in the global Azure cloud. It isn't available in other clouds, such as Azure US Government or Azure operated by 21Vianet.