Cody Murray-BruceProduct Marketing Manager Ben Johnson-StaubSoftware Engineer Many observability platforms authenticate to Microsoft Azure by using client secrets. Teams must create, store, and periodically rotate these secrets to keep receiving the telemetry data that they need. This recurring maintenance adds operational overhead and increases the risk of ingestion outages that occur when secrets expire.
Secretless authentication removes the burden of credential management for Datadog’s Azure integration, replacing client secrets with an identity-based authentication model. You no longer need to create, store, or rotate client secrets, and Datadog no longer stores a long-lived authentication secret.
In this post, you’ll learn how secretless authentication works and how you can configure or migrate to secretless authentication.
How secretless authentication works
Secretless authentication replaces static client secrets with a trust relationship based on identity. A federated identity credential in Microsoft Entra ID establishes trust between your Azure app registration and Datadog’s OpenID Connect (OIDC) issuer.
