You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 20, 2023. It is now read-only.
I have a question about using a service principal to access a storage account that lives in a different subscription to the subscription of my batch account.
I have the following configuration in my credentials.yaml file:
credentials:
batch:
account_service_url: https://batchxyz.westeurope.batch.azure.comstorage:
batchxyzstorage:
resource_group: rg-batchxyzaccount: batchxyzstorageotherstorage:
resource-group: rg-otheraccount: otherstorage # This storage account lives in another subscriptionmanagement:
subscription_id: xyz
I run shipyard and pass the aad-directory-id, aad-application-id and aad-auth-key of a service principal. The service principal is in the Contributor role on subscription xyz where the batch account and batch storage account live. It also has read access to the otherstorage storage account that lives in another subscription. Shipyard fails because it assumes that otherstorage is in subscription xyz.
I've looked through the documentation and cannot figure out how to use AAD in conjunction with a storage account in another subscription. Is this possible? Thanks in advance for any pointers.