In this SharePoint tutorial, we will discuss how to solve an error in the specified resource that does not exist in Azure blob storage, which comes up while trying to access Azure blob storage.
Recently, I was trying to deploy a SharePoint framework (spfx) web part through Microsoft Azure CDN, but it gave an error while I was adding the web part to a web part page in SharePoint Online.
The error comes as Failed to load URL <url> for resource… There was a network problem. This may be a problem with an HTTPs certificate. Make sure you have the right certificate.
When I tried to access the URL directly through the browser, then it gave an error The specified resource does not exist. It looks like below:
The specified resource does not exist Azure blob storage
The error was coming because, while creating the Azure container, the Access level was set to Private (By default).
We need to change the container’s access level to Anonymous access.
You can set the container’s public access level to grant anonymous users read access to a container and its blobs. When you grant public access to a container, anonymous users can read blobs within a publicly accessible container without authorizing the request.
Log in to the Azure portal and then go to the container, then click on the 3 dots (…), and then click on Change access level like below:
By default, the below 3 access levels will be presented.
- No public read access: The container and its blobs can be accessed only by the storage account owner. This is the default for all new containers.
- Public read access for blobs only: Blobs within the container can be read by anonymous request, but container data is not available. Anonymous clients cannot enumerate the blobs within the container.
- Public read access for container and its blobs: All container and blob data can be read by anonymous request. Clients can enumerate blobs within the container by anonymous request, but cannot enumerate containers within the storage account.
Here, select Blob (anonymous read access for blobs only) like below:
After this, the error the specified resource does not exist, azure blob storage will not come.
The SPFx web part will be added to the SharePoint page properly.
Here, we learned how to solve the error in the specified resource that does not exist in Azure blob storage.
You may also like:
- SharePoint client-side web part configurable properties in Property Pane using spfx
- can’t load the application on this page. use the browser back button to retry
- property ‘marquee’ does not exist on type ‘jsx.intrinsicelements’
I am Bijay a Microsoft MVP (10 times – My MVP Profile) in SharePoint and have more than 17 years of expertise in SharePoint Online Office 365, SharePoint subscription edition, and SharePoint 2019/2016/2013. Currently working in my own venture TSInfo Technologies a SharePoint development, consulting, and training company. I also run the popular SharePoint website EnjoySharePoint.com
Greetings, I’m sorry to ask about this old article.
In my opinion, this can’t be the solution. I don’t want my blob to change from private to public access. There must be solution for private access, weather it is by a service principle, a managed identity or something else. Do you have a proposal for this?