By integrating your Dynamics 365 Portal with Azure Blob Storage you can enjoy the quality of having a superior or more favorable position to save your files without using dynamics space. It have the same look and feel as you are utilizing the dynamics space. Files like: Web forms, web files, and entity forms are underpinned in its feature.

There will be a need of an account of Azure storage which will be created with the help of Resource manager in the deployment center. If you want to know that how to create Azure Storage Account? then click here.

Once you created the account of Azure Storage the next step is to configure your portal settings that will bind your Azure account with your Dynamics Portal. Here is the path of configuring the portal settings from Your Dynamics 365 CRM instance go to Settings -> Portal Settings 


Add New setting record by setting its name FileStorage/CloudStorageAccount.


To check and insert the Value: Go to your Azure Portal and get the connection string. Following are the steps to get the connection string from Azure portal:

Steps: Sign in to your Azure portal > Navigate to your Storage account > Select Access Keys


In resulting panel > Copy the value from a field named Connection String


Now paste it into the CRM (Portal Settings record) that has been created earlier:


Define Storage Location

For the first time there will be a need to create a Azure blob storage bucket in your Azure portal

In Microsoft Dynamics 365, go to Settings > Portal Settings, and add a new setting record labeled FileStorage/CloudStorageContainerName, applying the name of your bucket/container as the value:


Add Cross-Origin Resource Sharing Rule

Adding CORS rule is mandatory on the Azure Storage account that you are using by following the below mentioned codes. If the CORS rule will not get implemented then the cloud icon will get failed to see by the users and they will see the regular attachment icon:

  • Maximum age (seconds): Specify the max amount time for the browser shall cache the pref light OPTIONS request. For instance, 100.
  • Allowed headers: Specify the request headers that the origin domain may specify on the CORS request. For example, x-ms-meta-data*, x-ms-meta-target*.
  • Allowed origins: Specify your Dynamics 365 domain. For example, contoso.crm.dynamics.com.
  • Exposed headers: Specify the response headers that may be sent in the response to the CORS request and exposed by the browser to the request issuer. For example, x-ms-meta-*.
  • Allowed verbs: GET, PUT, DELETE, HEAD, POST

What is CORS Rule? Click here to know

By Applying above mentioned settings on Microsoft Dynamics 365 CRM Portal & Azure Blob storage account, you and your clients can enjoy the abilities to download or upload the files directly to/from Azure storage.

Hope this blog is informative for you guys so stay tuned for more exciting features of Microsoft Dynamics 365.

Leave a Reply

Recent Comments