This website uses cookies to ensure you get the best experience.
Learn more.
A trusted CI workflow deploys Foundry infrastructure. The organization wants to avoid long-lived stored application secrets. Which approach fits?
Published
- A model output used as an Azure credential
- A public Global Administrator password in the workflow
- Anonymous Azure resource mutation
- Workload identity federation with constrained trust and scoped roles
Comments — 0
Sign in to comment