Using federated workload identity in TORUS to authenticate into a CORP resource in AML

Ayleen Durasno 25 Reputation points Microsoft Employee
2026-01-23T14:52:03.2866667+00:00

Hello! I have a pipeline which fetches files from a repo in CORP tenant. This pipeline is however running in a TORUS environment. I have completed the following steps to enable access to the AML compute cluster.

  1. Created an app registration in TORUS and created a federated workload identity for the AML compute cluster
  2. Created a SP in CORP tenant which reflects the app registration in TORUS. This required a form.
  3. Gave genericRead perms to the SP.

When I run the pipeline however I receive an error that the api request to read the repo has failed. What could be happening?

Azure Machine Learning
{count} votes

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-01-23T14:52:14.2033333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It sounds like you have set up the federated workload identity correctly, but there may be a few areas to check that could be causing the API request failure:

    1. Permissions: Ensure that the service principal (SP) in the CORP tenant has the appropriate permissions to access the resources in the repo. While you mentioned giving genericRead permissions, double-check that these permissions are correctly assigned and that there are no additional required permissions for the specific API call you are making.
    2. Federated Identity Configuration: Verify that the federated workload identity is correctly configured in both the TORUS and CORP environments. Ensure that the issuer and subject claims are correctly set up and that the trust relationship is established properly.
    3. Token Acquisition: Check if the pipeline is successfully acquiring the token from the federated identity. If the token is not being issued correctly, it would lead to authentication failures when trying to access the repo.
    4. Network and Firewall Settings: Ensure that there are no network restrictions or firewall settings that might be blocking the API requests from the TORUS environment to the CORP resources.
    5. Error Logs: Look into the error logs for more specific information about the failure. The logs might provide insights into whether the issue is related to authentication, permissions, or something else.

    By reviewing these areas, you should be able to identify the root cause of the API request failure in your pipeline.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.