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 }}
Repository navigation
Unable to Find Function App with Multi-Subscription SPN #144
It seems when the service principal has multiple subscriptions available, the function app is not found if it is not in the default subscription.
The action should search all subscriptions, support specifying a subscription ID, or have the documentation state the limitation and workaround with az acount set --subscription.
Chandni Patel (@patelchandni) These are existing service principals that have defined subscriptionId values in the JSON already as required by other tasks that also only search the default subscription. I can't change that value. Hence why I think it would be ideal if this task (and those others) allowed us to specify a subscription ID or search across all available subscriptions if that is provided. The simplest way is specifying the subscription as an optional parameter, otherwise searching across all subscriptions could end up with duplicates or ARM API request quota issues.
Or it could be mentioned in the documentation that using az account set --subscription as a command prior to running this task, you can specify something different. Just for completeness sake.
Activity
patelchandni commentedon Aug 12, 2022
Drew (@nerddtvg) Did you create service principle using the recommended steps in README?
nerddtvg commentedon Aug 12, 2022
Chandni Patel (@patelchandni) These are existing service principals that have defined
subscriptionIdvalues in the JSON already as required by other tasks that also only search the default subscription. I can't change that value. Hence why I think it would be ideal if this task (and those others) allowed us to specify a subscription ID or search across all available subscriptions if that is provided. The simplest way is specifying the subscription as an optional parameter, otherwise searching across all subscriptions could end up with duplicates or ARM API request quota issues.Or it could be mentioned in the documentation that using
az account set --subscriptionas a command prior to running this task, you can specify something different. Just for completeness sake.