OCPBUGS-76945: Add Azure Resource Group in OCP console for ODF STS installation

[cajieh]

Verification Instructions:

1. Install ODF operator on an Azure STS cluster
2. Verify the Resource Group field appears and is required
3. Verify the subscription is created with the RESOURCEGROUP environment variable
4. Verify NooBaa can successfully create storage accounts using the provided resource group

It appears that the default ODF operator has not set annotation [features.operators.openshift.io/token-auth-azure](http://features.operators.openshift.io/token-auth-azure): "true".

Verified using the cert-manager Operator for Red Hat OpenShift

After: Verified using the cert-manager Operator for Red Hat OpenShift

All code passes linting and follows the existing patterns for AWS STS and GCP WIF implementations.

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-76945, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[cajieh]

/jira refresh

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-76945, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (ebenahar@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@cajieh: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[jhadvig]

/lgtm

[jhadvig]

@cajieh leaving the WIP removal and unhold to you.

[jhadvig]

/label acknowledge-critical-fixes-only

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cajieh, jhadvig

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS [cajieh,jhadvig]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[cajieh]

@cajieh leaving the WIP removal and unhold to you.

I haven't verified the change on Azure STS yet.
QE helped spin up the cluster last time, but they're off until next week.

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-76945, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (ebenahar@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Verification Instructions:

1. Install ODF operator on an Azure STS cluster
2. Verify the Resource Group field appears and is required
3. Verify the subscription is created with the RESOURCEGROUP environment variable
4. Verify NooBaa can successfully create storage accounts using the provided resource group

It appears that the default ODF operator has not set annotation [features.operators.openshift.io/token-auth-azure](http://features.operators.openshift.io/token-auth-azure): "true".

Verified using the cert-manager Operator for Red Hat OpenShift

After: Verified using the cert-manager Operator for Red Hat OpenShift

All code passes linting and follows the existing patterns for AWS STS and GCP WIF implementations.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[cajieh]

/verified later @yanpzhan

[cajieh]

/retest

[openshift-ci-robot]

@cajieh: This PR has been marked to be verified later by @yanpzhan.

Details

In response to this:

/verified later @yanpzhan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@cajieh: Jira Issue OCPBUGS-76945: All pull requests linked via external trackers have merged:

• openshift/console#16030

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-76945 has been moved to the MODIFIED state.

Details

In response to this:

Verification Instructions:

1. Install ODF operator on an Azure STS cluster
2. Verify the Resource Group field appears and is required
3. Verify the subscription is created with the RESOURCEGROUP environment variable
4. Verify NooBaa can successfully create storage accounts using the provided resource group

It appears that the default ODF operator has not set annotation [features.operators.openshift.io/token-auth-azure](http://features.operators.openshift.io/token-auth-azure): "true".

Verified using the cert-manager Operator for Red Hat OpenShift

After: Verified using the cert-manager Operator for Red Hat OpenShift

All code passes linting and follows the existing patterns for AWS STS and GCP WIF implementations.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-robot]

Fix included in accepted release 4.22.0-0.nightly-2026-02-26-092444