Added key vault requirements

Author: Manika Dhiman

azure-local/concepts/system-requirements-23h2.md

@@ -6,7 +6,7 @@ ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
 ms.custom: references_regions
-ms.date: 01/02/2025
+ms.date: 02/14/2025
 ---
 
 # System requirements for Azure Local, version 23H2
@@ -41,6 +41,8 @@ Here are the Azure requirements for your Azure Local instance:
    - Japan East
    - South Central US
 
+- **Azure Key Vault**: Make sure to enable public network access when you set up a key vault. This setting allows edge devices to connect to the key vault without any access issues.
+
 ## Machine and storage requirements
 
 Before you begin, make sure that the physical machine and storage hardware used to deploy Azure Local meets the following requirements:

azure-local/deploy/deployment-prerequisites.md

@@ -3,7 +3,7 @@ title: Prerequisites to deploy Azure Local, version 23H2
 description: Learn about the prerequisites to deploy Azure Local, version 23H2.
 author: alkohli
 ms.topic: conceptual
-ms.date: 10/15/2024
+ms.date: 02/14/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -44,10 +44,9 @@ Use the following checklist to gather the required information ahead of the actu
 |Custom location|(Optional) A name for the custom location created for your system. This name is used for Azure Arc VM management. <br> For more information, see the **Specify management settings** page in [Deploy via Azure portal](./deploy-via-portal.md#specify-management-settings).|
 |Azure subscription ID|ID for the Azure subscription used to register the system. Make sure that you are a user access administrator and a contributor on this subscription. This will allow you to manage access to Azure resources, specifically to Arc-enable each machine of an Azure Local instance. For more information, see [Assign Azure permissions for deployment](./deployment-arc-register-server-permissions.md#assign-required-permissions-for-deployment)|
 |Azure Storage account|For two-node systems, a witness is required. For a cloud witness, an [Azure Storage account](/azure/storage/common/storage-account-create) is needed. In this release, you cannot use the same storage account for multiple systems. For more information, see **Specify management settings** in [Deploy via Azure portal](./deploy-via-portal.md#specify-management-settings). <br> For naming conventions, see [Azure Storage account names](/azure/storage/common/storage-account-overview#storage-account-name).|
-|Azure Key Vault|A key vault is required to securely store secrets for this system, such as cryptographic keys, local admin credentials, and BitLocker recovery keys. For more information, see **Basics** in [Deploy via Azure portal](./deploy-via-portal.md#start-the-wizard-and-fill-out-the-basics). <br> For naming convention, see [Azure Key Vault names](/azure/key-vault/general/about-keys-secrets-certificates#object-identifiers).|
+|Azure Key Vault|A key vault is required to securely store secrets for this system, such as cryptographic keys, local admin credentials, and BitLocker recovery keys. For requirements, see **Azure Key Vault** in [Azure requirements](../concepts/system-requirements-23h2.md#azure-requirements). For creating a key vault during deployment, see **Basics** in [Deploy via Azure portal](./deploy-via-portal.md#start-the-wizard-and-fill-out-the-basics). <br> For naming conventions, see [Azure Key Vault names](/azure/key-vault/general/about-keys-secrets-certificates#object-identifiers).|
 |Outbound connectivity| Run the [Environment checker](../manage/use-environment-checker.md) to ensure that your environment meets the outbound network connectivity requirements for firewall rules.|
 
-
 ## Next steps
 
 - Prepare your [Active Directory](./deployment-prep-active-directory.md) environment.