This is a clone of issue OCPBUGS-74498. The following is the description of the original issue:
—

Description of problem

The Control Plane Operator (CPO) is not setting the UserAgent in the Azure SDK telemetry options when creating Azure ARM SDK clients. This means Azure API requests from CPO do not include proper application identification for request tracing and telemetry purposes.

When authenticating to Azure Cloud, the Azure SDK's TelemetryOptions.ApplicationID is not configured, resulting in requests that cannot be properly attributed to the Control Plane Operator.

Version-Release number of selected component (if applicable)

4.20, 4.21, 4.22

How reproducible

Always

Steps to Reproduce

1. Deploy an OpenShift hosted control plane cluster on Azure
2. Trigger control plane operations that make Azure API calls
3. Monitor Azure API requests from the control-plane-operator
4. Observe the User-Agent header in requests to Azure ARM APIs

Actual results

Azure ARM SDK requests from CPO do not include a proper application User-Agent identifier. The requests are not easily attributable to the control-plane-operator in Azure telemetry/monitoring.

Expected results

Azure ARM SDK requests should include a User-Agent header identifying the Control Plane Operator for proper request tracing.

Additional info

The fix should add TelemetryOptions with ApplicationID to the Azure SDK client options:

options := &arm.ClientOptions{
    ClientOptions: azcore.ClientOptions{
        Cloud: cloudConfig,
        Telemetry: policy.TelemetryOptions{
            ApplicationID: "[cpo-useragent]",
        },
    },
}