Azure Blob

here's a step by step guide to help you connect your azure blob storage container with cloudfiles 1 add cloudfiles application search for cloudfiles in microsoft entra gallery click on cloudfiles and click "create" to add an instance of cloudfiles application in your azure portal if the above doesn't work for you, alternatively you can click the button below to authorize cloudfiles this will add cloudfiles automatically to your enterprise applications list 2 create a storage account navigate to azure portal log in to your azure portal create a new storage account go to the 'storage accounts' section and click on 'add' to create a new storage account configure the storage account follow the on screen instructions to configure your storage account, selecting the appropriate subscription, resource group, and other relevant settings 3 create a container in storage account open storage account once the storage account is created, open it create container in the storage account dashboard, locate the 'containers' section and create a new container assign a name and set the access to private (no anonymous access) 4 update storage account configuration enable storage account key access in the storage account settings, go to configuration ensure allow storage account key access is enabled, which is essential for cloudfiles integration update cors settings in the storage account settings, go to resource sharing (cors) add cors rules to allow get/put methods for the origin, enter your salesforce domain and https //salesforce cloudfiles io ensure you include both sandbox and production urls, depending on where the account will be used cloudfiles url is required to view files inside salesforce allowed origin allowed methods allowed headers \<your salesforce domain>(https //cloudfiles lightning force com) get, put https //salesforce cloudfiles io get,put make sure to not include / at the end of the url add storage blob delegator permission in the storage account settings, go to access control (iam) create a new role assignment select the role "storage blob delegator" on members screen, search for "cloudfiles" service principal 5 update container access control add storage blob data contributor permission in the container settings, go to access control (iam) create a new role assignment select the role "storage blob data contributor" on members screen, search for "cloudfiles" service principal 6 configure azure storage in cloudfiles open cloudfiles setup in salesforce log into your salesforce account and navigate to the cloudfiles app launcher go to libraries section in document management app, select azure blob enter the 'storage account name' and 'container name' (optional) enter 'prefix' the prefix defines the folder path within your azure container that cloudfiles will use this allows you to organize data within a single section of the container instead of using the entire container when connecting a container for the first time, you can choose any prefix if you reuse an existing container in another org, each connection must use a unique, non overlapping prefix to prevent conflicts for example, team a/ and team b/ are valid, but team a/ and team a/subfolder/ are not enter 'drive label' the drive label is the display name for the storage connection in cloudfiles this label is what users will see in the ui when accessing or selecting a storage location, making it easier to identify and distinguish between multiple connected drives it is optional for the first container connected in the org but required for any additional connections to ensure each drive can be easily identified connect note a prefix is mandatory every time you connect the same container more than once, whether within the same org or across different orgs — this ensures paths do not overlap if you are connecting the same container a second time within the same org, both the original and the new connection must have a prefix, so if the first connection was made without one, disconnect it and reconnect with a prefix before adding the second a drive label is mandatory from the second container onward within the same org, regardless of whether the containers are the same or different 7 update trusted urls in salesforce add the following url to trusted urls in salesforce https //{storageaccountname} blob core windows net for example, if storage account name is cloudfiles , url will be https //cloudfiles blob core windows net 8 enable auto sync in azure (optional) if you wish to have a 2 way sync to view your files in azure through the cloudfiles widget, please follow the steps mentioned in docid\ tpsmysugvjfd3xaobbksi 9 enable sync in cloudfiles turn on enable sync to automatically sync changes between your azure container and cloudfiles (completing step 8 is mandatory if you wish to turn this toggle on) once enabled, any files or folders that are uploaded, updated, or deleted in azure will be reflected in cloudfiles note sync only applies to changes made after the toggle is enabled existing files in your azure container will not appear automatically in cloudfiles to make historical data available, a custom (paid) migration is required please contact support\@cloudfiles io for more details column configuration for azure you can customize the columns displayed in widgets through the library configuration tab in document management for azure refer to the images for visual understanding disconnect azure containers users can disconnect azure containers directly from the salesforce app this action will remove the storage connection along with any associated metadata within the app