![minify storage minify storage](https://webtools.mywebhostguru.com/components/storage/app/public/photos/1/webtoolslogo.png)
But did you know that there are settings that you can configure, to change how your files are served? Configure far future expiration Optimize how files from Azure Blob Storage are servedīy default, Azure blob storage just serves your files the way they have been uploaded. This is the setup for use with SharePoint Framework solutions. Every file in that container gets a URL, such as, that you can use in the browser to load the file. When uploading files to the Azure Blob Storage, you can configure the container to be publicly accessible.
![minify storage minify storage](https://i.pinimg.com/originals/d7/fd/57/d7fd57f276fefa0e59434a4a66b622e4.jpg)
Loading files from the Azure Blob Storage What's more, with a few additional configuration settings, you will ensure that your web parts load quicker and your costs for using the Azure Blob Storage are lower. As it's supported out of the box, this hosting option is extremely convenient to use. And these files can be stored anywhere: from an Apache server under your desk to a specialistic CDN.Īs a part of the toolchain, the SharePoint Framework offers you the ability to deploy your web part files to Microsoft Azure Blob Storage. The manifest contains a URL that points to the location where the web part files are stored. SharePoint Framework solutions consist of two main parts: a package with a manifest, deployed to the App Catalog and scripts and asset files deployed to a web server. However, when building SharePoint Framework solutions, things look differently. That way we would leverage its infrastructure and services. In the past, when building SharePoint customizations, Microsoft recommended us to integrate with SharePoint as closely as possible. Here is what you should do next to ensure that users will load these files as quickly as possible. Using the standard toolchain you can easily deploy your SharePoint Framework files to Microsoft Azure.