key-vault | Latest verified image digest hosted on Docker Hub | Identity Management library

Try to use ClientSecretCredential to do this :

Update:
You should declare a variable first by click blank, then you can select a variable at step3:

After you added ADF managed identity permissions to Get and List secrets.

1. Add a secret to the key valut. Here my secret name is mysecret.
   

2. So your URL should looks like https://your-keyvault-name.vault.azure.net/secrets/mysecret?api-version=7.0
   

3. Add dynamic content @activity('Web1').output.value to your Set variable1 activity.
   

I write a simple demo for you. Just try the C# console app below about azure blob client-encryption with azure KeyVault:

You just need to use another user (who has access to the Azure key vault) to sign into Visual Studio and then you can access your secrets.

For how to assign the access (RBAC role) to another user, please refer to Assign Azure roles using the Azure portal.

You can find the key vault in Azure portal to do the operation (for example, assign the Owner role of the key vault to the user).

If the another user is the owner of the Azure subscription, you do not need to make additional RBAC role assignments. He already has permission to access this key vault.

From https://docs.microsoft.com/en-us/azure/machine-learning/how-to-manage-workspace?tabs=python#limitations

If you want to use existing services from a different Azure subscription than the workspace, you must register the Azure Machine Learning namespace in the subscription that contains those services.

So, in order to use the ACR in that different subscription, you need to register resource provider Microsoft.MachineLearningServices in that subscription contains ACR. For information on how to see if it is registered and how to register it, see the Azure resource providers and types article.

To register a resource provider, use:

Here is a troubleshooting advice:

The error "Host key verification failed." doesn't just occur when the key is incorrect. Most of the time, it doesn't refer to your key.

So I recommend you firstly try the connection with a simple value to see if it works on Azure DevOps.

What's more, maybe an SSH service connection can help you with what you're doing. Go to Project Settings -> Service connections -> Create service connection -> SSH to create one.

You can get the Service Principal's Client Id and Tenant Id using CLI command like below:

Update:

As you update in the comment, the issue comes from the app is not registered in CorporateSub.

Original Answer:

I can reproduce the error:

Please make sure the application id is correct or you have log in the correct account.

The app I tested is owned applications:

In my case, I didn't realize there's a tenantId parameter when getting credentials. I needed to supply tenantId: