An Azure service that provides a flexible, self-service deployment of fully managed OpenShift clusters.
Hello Ashi,
Thank you very much for your cooperation and for taking the time to work with us offline during the troubleshooting. We truly appreciate your patience while we coordinated with the ARO team to better understand the cause of the issue.
From the investigation, it was found that the issue is related to a subscription-level policy that is currently blocking the resource creation request. Specifically, the policy restricts Managed Identity Federated Credentials based on approved issuer types, and as a result, the request is being denied. At the moment, the issuer eastus2.oic.aro.azure.com and westus3.oic.aro.azure.com is not included in the list of allowed issuers, which is preventing the ARO cluster creation from completing successfully.
To help move forward, you may consider either using a subscription that is not governed by this policy or updating the policy to include a wildcard entry such as *.oic.aro.azure.com, if that aligns with the guidelines.