Update rules/store-your-secrets-securely/rule.md

Co-authored-by: Matt Wicks [SSW] <[email protected]>

rules/store-your-secrets-securely/rule.md

@@ -194,7 +194,7 @@ Pros:
 * Dynamically cycles secrets
 * Access granted based on Azure AD permissions - no need to 'securely' share passwords with colleagues
 * Can be used to inject secrets in your CI/CD pipelines for non-cloud solutions
-* Can also be utilized for on-premise secrets management by accessing it over a secure network connection to centralize and protect sensitive data.
+* Can be used by on-premise applications (more configuration - see [Use Application ID and X.509 certificate for non-Azure-hosted apps](https://learn.microsoft.com/en-us/aspnet/core/security/key-vault-configuration?view=aspnetcore-7.0#use-application-id-and-x509-certificate-for-non-azure-hosted-apps))
 
 Cons: