Merge pull request #310613 from lacomc/dev-box-private-kv-fix

Update supported key vault scenarios in Dev Box documentation

Author: prmerger-automator[bot]

articles/dev-box/how-to-customizations-connect-resource-repository.md

@@ -31,7 +31,7 @@ To use a secret, like a PAT, in your customization files, store it as a key vaul
 
 To configure key vault secrets for use in your team or user customizations, make sure the Dev Center project's managed identity has the Key Vault Secrets User role on your key vault.
 
-If your key vault is private, let trusted Microsoft services bypass the firewall because Dev Center doesn't yet support service tags.
+If your organization's policies require you to keep your Key Vault private from the internet, you can create a firewall rule to disable or limit public access. You will need to let trusted Microsoft services bypass the firewall because Dev Center doesn't yet support service tags. Key vaults with private endpoints or private link integration are not currently supported for this scenario.
 
 The following screenshot shows the option to allow trusted Microsoft services to bypass the firewall in Azure Key Vault settings.