Skip to content

Commit a342285

Browse files
authored
Merge pull request #95106 from alexkarcher-msft/master
Adding Key Vault advisory
2 parents 4321f9d + f3dee80 commit a342285

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/azure-functions/functions-networking-options.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,6 +112,12 @@ When you create a function app, you must create or link to a general-purpose Azu
112112

113113
[Learn more about storage account requirements.](./functions-create-function-app-portal.md#storage-account-requirements)
114114

115+
### Using Key Vault references
116+
117+
Key Vault references allow you to use secrets from Azure Key Vault in your Azure Functions application without requiring any code changes. Azure Key Vault is a service that provides centralized secrets management, with full control over access policies and audit history.
118+
119+
Currently [Key Vault references](../app-service/app-service-key-vault-references.md) will not work if your Key Vault is secured with service endpoints. To connect to a Key Vault using virtual network integration you will need to call key vault in your application code.
120+
115121
## Virtual network triggers (non-HTTP)
116122

117123
Currently, to use function triggers other than HTTP from within a virtual network, you must run your function app in an App Service plan or in an App Service Environment.

0 commit comments

Comments
 (0)