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 Sep 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
SCORING_DATASTORE_STORAGE_NAME, SCORING_DATASTORE_ACCESS_KEY are described as optional, but never covered #313
+1 having the exact same issue... I want to setup batching scoring, so I:
created a new storage account
added the storage account name/key to the appropriate variables in the variable group (as outlined in the "getting started" guide
even ensured the service principal used for my AzDO -> AML service connection is set as Contributor for the new storage account (the whole resource group, actually)
It appears something is mis-configured and causing fallback to interactive Azure CLI authentication, which of course does not work very well in a CI build. :-)
What's odd is that the training pipeline seems to work fine... its unclear why.
Activity
jplane commentedon Jul 18, 2020
+1 having the exact same issue... I want to setup batching scoring, so I:
I get the same error in the same place as Chris Mayo (@cmayomsft)
It appears something is mis-configured and causing fallback to interactive Azure CLI authentication, which of course does not work very well in a CI build. :-)
What's odd is that the training pipeline seems to work fine... its unclear why.
j-so commentedon Jul 24, 2020
There definitely needs to be more documentation about those environment variables.
Will try to repro the issue.
shivp950 commentedon Aug 4, 2020
jitghosh have you ran into this issue before? can you take a look?