Schedule Refresh with Multiple Azure Blobs

[Anonymous]

I am attempting to set up a scheduled refresh for reports containing data from two seperate Azure Blob instances (One for development data and another with live production data). When trying to set up a scheduled refresh, I verify the credentials for each source and attempt to refresh. However, it seems that PowerBI is only using the key that I enter most recently for these sources instead of keeping the unique keys for each. Therefore, I am receiving an error when refreshing for the source that adopted the wrong key.

I am able to refresh these sources seperately from PBI Desktop and republish, but unable to do a scheduled refresh.  Does anyone have experience setting up scheduled refresh for multiple Blob sources? And does anyone have a clue why it won't accept unique keys for the unique Blob instances?

Thanks in advance for any help you can provide!

[v-qiuyu-msft]

Hi @Anonymous,

If you get data from multiple Azure BLOB Storage accounts, after publish to the service,please go to the Dataset Settings, there should have multiple data sources. We need to enter corresponding access key for each account.

Best Regards,
Qiuyun Yu

[Anonymous]

Thanks Qiuyun for your reply, however, whenever I press "edit credentials" and enter the key for the Azure Blobs I am using, the keys do not stay distinct. Instead, they take the value of whatever the last key I entered. For example, if I enter the key for Blob1 and then edit the credentials for Blob2, the key for Blob2 willl be assigned to Blob1. So I am unable to schedule the refresh for both the Blob sources I am using. I'm not sure if this is a PowerBI limitation, bug, or my own error but will try to recreate this and post the procedure. 

[v-qiuyu-msft · Accepted solution]

Hi @Anonymous,

The dataset get data from multiple Azure BLOB Storage accounts can be refreshed successfully on my side. It seems the issue related to Power BI cluster. I would suggest you create a support ticket to get dedicated support from Microsoft engineer.

Best Regards,
Qiuyun Yu