How can an orchestration tool use my secrets without storing my credentials?
Keep the credential in a secret vault you control, give the orchestrator read access to just the secrets it needs, and configure jobs with a reference to the secret by name rather than its value. The orchestrator resolves the reference when it starts a run, so the value is never saved in its configuration, exports or job parameters, and rotating the secret in the vault takes effect on the next run without touching the orchestrator.
Why pasting secrets into a tool is a problem
- The tool's database becomes a second copy of the credential, with its own backups and administrators.
- Values typed into job parameters tend to appear in run logs, exports and screenshots.
- Rotation means updating every place the value was pasted.
The reference pattern
| Step | What you do |
|---|---|
| 1. Store | Put the credential in your vault: Azure Key Vault, AWS Secrets Manager, Google Cloud Secret Manager or HashiCorp Vault |
| 2. Grant | Give the orchestrator's identity read access to that vault, or to only the secrets it needs |
| 3. Reference | In the orchestrator, refer to the secret by vault and name |
| 4. Resolve | The orchestrator reads the value at dispatch time and uses it for that call |
| 5. Rotate | Change the value in the vault; the next run picks it up |
In Polysync
Link a vault once as a Secret Vault, then reference secrets as vault://<vault>/<secret> in platform settings or task parameters. Polysync reads the secret when a task is dispatched, and the value is not stored on the task. If you would rather not link a vault, Polysync can hold the credential in its own managed Azure Key Vault instead. Many Azure platforms can also use the Polysync service principal, which needs a role grant on the resource and no credential at all.
Frequently asked questions
Is a managed identity better than a stored secret?
Where the platform supports it, yes: there is no secret to leak or rotate. Use vault-held secrets for platforms or accounts that require keys or passwords.
What access does the orchestrator need on my Key Vault?
Read access to secrets, ideally limited to the specific secrets it uses. It does not need permission to create, change or delete them.
Does the secret appear in run history?
It should not. Check that your orchestrator resolves references only at dispatch time and does not echo resolved values into logs.
Microsoft, Azure, Azure Data Factory, Microsoft Fabric, Power BI, Logic Apps and Microsoft Marketplace are trademarks of the Microsoft group of companies. Apache Airflow and Airflow are trademarks of the Apache Software Foundation. Databricks and Lakeflow are trademarks of Databricks, Inc. All other product names are the property of their respective owners and are used for identification only. No endorsement by their owners is implied.