# Elastic Agent Container - Secrets Management

**URL:** <https://discuss.elastic.co/t/elastic-agent-container-secrets-management/323067>\
**Category:** Elastic Agent\
**Tags:** elastic-stack-security\
**Created:** [January 12, 2023, 11:28pm UTC](https://discuss.elastic.co/t/elastic-agent-container-secrets-management/323067 "2023-01-12T23:28:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MoreCowBell](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@MoreCowBell](https://discuss.elastic.co/u/MoreCowBell)\
**Post date:** [January 12, 2023, 11:28pm UTC](https://discuss.elastic.co/t/elastic-agent-container-secrets-management/323067/1 "2023-01-12T23:28:10Z")

</div>

I'm looking to further harden the security of passing secrets into the elastic agent configuration at runtime. I'm wondering if the following would work.

Scenario:  
Integration: Azure Active Directory

Sensitive Values:

- Storage Account Key
- EventHub Connection String

Can these values be passed as environmental variables to the container, and referenced in the GUI configuration using standard format of ${VAR\_NAME}?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 9, 2023, 11:28pm UTC](https://discuss.elastic.co/t/elastic-agent-container-secrets-management/323067/2 "2023-02-09T23:28:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.