[Implementation] Enhance MSAL Client-Side Telemetry

[gladjohn]

Task type

Development

Description

• Add tracking for MSI source (IMDS, App Service, Service Fabric, AKS, IMDSv2, etc.).

Expose MSI source as a new telemetry field.

• Capture Token Revocation Events for MSI V1

Log occurrences of bypass_cache=true when set.

• Capture Token Revocation Events for MSI V2

Capture error_code responses from /credential endpoint.

• Detect and Log Certificate Type Used for MSI Authentication

Track if platform certificates, developer-provided certificates, or in-memory self-signed certificates are used.
Ensure telemetry provides insights into bound token adoption.

• Capture Failure Reasons for MSI Token Acquisition

Log and categorize token acquisition failures: Authentication failures, Network issues, HTTP 404 errors

Solution

No response

[bgavrilMS]

Is this still actual ?

There is a separate work item for the MSI source. The revocation events are captured by server side telemetry. We already capture errors.