Thank you for checking in. I was able to get some help with this and I wanted to post the steps I was missing here in case anyone else hits this issue.
I needed to generate a new SAS key for our datastore, and here's how I did it:
- How to generate keys
a. From Azure Portal, search for and click on ‘Storage Account’
b. Click <your storage account>
c. Under Data storage, click ‘Containers’
d. Click <your container>
e. Under Settings, click ‘Shared access tokens’
f. Generate the key:
i. Set up the date of expiry
ii. Set up Permissions (select all)
iii. Click ‘Generate SAS token and URL’
iv. Copy those to save them in a secure location - Copy in the token (not the URL) into the location indicated by the Auth error
a. Go to ‘Data’ under Assets in the left bar
b. Under Data Source, click <your datastore>
c. Click ‘Update authentication’
d. Copy in the token and click 'Save'
After these steps, I followed the steps in https://learn.microsoft.com/en-us/azure/machine-learning/how-to-change-storage-access-key to sync the keys for the workspace (substituting n for w, since it appears that argument has changed since that tutorial was posted), and voila! It's working. Unfortunately, there don't seem to be any help forums particularly listing out these steps, so it appears that I was just supposed to know about this, or maybe I missed some tutorial somewhere, but either way, I hope this helps someone!
Thanks for the help! I cannot tell whether the key is expired. When I go to Settings-Keys in the Azure Portal, I see the message "You are unauthorized to view these contents." I imagine this is a permissions issue. Do you know which permissions I need in our Key Vault Resource in order to check this?
Also, I don't believe the key has been changed, as I am the only developer in our workspace. Unless it can get changed without human intervention?
Hello @Jason Hoffman ,
Please reach out to the owner of the subscription to confirm if the SAS token is expired or the account key is changed.
Hello @Jason Hoffman ,
Are you able to resolve the issue?
Follow up to see if you have had a chance to see the previous response. We need the following information to understand/investigate this issue further.
Sign in to comment