Skip to content

Commit da2821f

Browse files
authored
Fixing typos
1 parent 1e51bc1 commit da2821f

1 file changed

Lines changed: 0 additions & 3 deletions

File tree

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

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,9 +31,6 @@ To use a secret, like a PAT, in your customization files, store it as a key vaul
3131

3232
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.
3333

34-
If your key vault is private, let trusted Microsoft services bypass the firewall because Dev Center doesn't yet support service tags.
35-
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 and set your Key Vault to allow trusted Microsoft services to bypass your rule. Please note that we do not currently support key vaults with private endpoints or private link integration for this scenario.
36-
3734
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.
3835

3936
The following screenshot shows the option to allow trusted Microsoft services to bypass the firewall in Azure Key Vault settings.

0 commit comments

Comments
 (0)