diff --git a/docs/standard/microservices-architecture/multi-container-microservice-net-applications/data-driven-crud-microservice.md b/docs/standard/microservices-architecture/multi-container-microservice-net-applications/data-driven-crud-microservice.md index d28a9e4b170ba..e63d0ac606cc5 100644 --- a/docs/standard/microservices-architecture/multi-container-microservice-net-applications/data-driven-crud-microservice.md +++ b/docs/standard/microservices-architecture/multi-container-microservice-net-applications/data-driven-crud-microservice.md @@ -251,7 +251,7 @@ The docker-compose.yml files at the solution level are not only more flexible th Finally, you can get that value from your code by using Configuration\["ConnectionString"\], as shown in the ConfigureServices method in an earlier code example. -However, for production environments, you might want to explore additional ways on how to store secrets like the connection strings. An excellent way to manage application secrets is using [Azure Key Vault}(https://azure.microsoft.com/services/key-vault/). +However, for production environments, you might want to explore additional ways on how to store secrets like the connection strings. An excellent way to manage application secrets is using [Azure Key Vault](https://azure.microsoft.com/services/key-vault/). Azure Key Vault helps to store and safeguard cryptographic keys and secrets used by your cloud applications and services. A secret is anything you want to keep strict control of, like API keys, connection strings, passwords, etc. and strict control includes usage logging, setting expiration, managing access, among others. @@ -427,4 +427,4 @@ It is that simple. And because it is automatically generated, the Swagger metada >[!div class="step-by-step"] >[Previous](microservice-application-design.md) ->[Next](multi-container-applications-docker-compose.md) \ No newline at end of file +>[Next](multi-container-applications-docker-compose.md)