Skip to main content

File Storage Options for Dynamics 365 Portal


Updated: Since the original posting, Microsoft introduced storage in SharePoint from Power Apps Portal.  I updated the post to reflect current support.-jt

Microsoft offers Power Apps Portal (formerly Dynamics Portal) as a way for external users to access information in Dynamics 365 (formerly Dynamics CRM). Portals are included in some Dynamics 365 subscriptions, and are used in scenarios such as customer service, employee self-service, online communities, and supplier portals. Dynamics Portal is also applicable for xRM solutions such as grant management, eligibility determination and other forms of case management.

In portal scenarios, you may have a requirement to allow users to submit or view file attachments such as grant or credit applications, presentations, photographs and other files.  This blog post introduces some options for where and how these file attachments are stored and accessed.

Microsoft supports three methods for storing file attachments in the Portal.  They are as file attachments in the Dynamics entities, SharePoint and Azure Blob Storage.

Store File Attachments in Dynamics

Storing file attachments in the Dynamics Notes entity or other entities is the default option in Dynamics 365, and is familiar to Dynamics 365 users.  These files may be accessed through the Dynamics Portal.  When files are attached in Dynamics Portal, they look something like this:

Source: https://community.dynamics.com/crm/b/crminogic/archive/2017/10/04/attach-documents-from-microsoft-dynamics-365-portal


Azure Blob Storage

Microsoft recently introduced support for Azure Blob Storage in Dynamics Portal.  You can choose Azure storage in Dynamics Portal when you configure the page to which the files are associated, such as web forms and entity forms. Here are step-by-step instructions for enabling Azure storage in the portal.  You can also configure Dynamics 365 forms to use Azure storage:



Note that the paper-clip icon has been replaced with a cloud icon which denotes that this file is stored in Azure Storage. You can continue to store attachments in Dynamics 365 which will be indicated with the paperclip icon.

SharePoint File Storage

Microsoft supports SharePoint storage for attachments in Power Apps Portal.  

Microsoft also supports SharePoint storage of Dynamics 365 for users of the application as well as the portal.  The Microsoft SharePoint integration for file attachments creates folders which correspond to the associated entities in Dynamics.  

Tradeoffs

With all these choices, what are the factors that will drive your decision?  Here are some considerations and tradeoffs:


Dynamics Notes Attachments
Azure Blob Storage
SharePoint
Supported by Microsoft
Yes
Yes
Yes
Files Stored in Dataverse
Yes
No
No
Performance

Highest

Storage cost
Higher
Lowest
Depends on SharePoint cost
Full Text File Search
Not supported but metadata searchable
Requires additional service
Included

If you store documents in Azure Blob Storage or SharePoint, these repositories are managed independently.  They are not backed up or migrated inside the Power Apps solution itself. This offers an advantage of you want to access the files outside the context of Power Apps.

The cost and performance tradeoffs are most relevant for customers with large volumes of file attachments.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan