Skip to main content

Dynamics 365 Power Apps: When You Want CRM Power without Sales, Customer Service or Marketing


My company InfoStrat has been working with Dynamics 365 for over 13 years since version 3.0 of Dynamics CRM was released.  For more than half of our customers, we have been using Dynamics for line of business solutions which are not the typical sales, customer service and marketing applications that make up customer relationship management (CRM).

Microsoft offers a subscription for these users who do not need sales, customer service or support.  This subscription is called Power Apps, and provides the same user interface, platform and development tools as are used for the CRM apps.

Power Apps offers significant savings -- the U.S. list price is $40/user/month compared to $95/user/month for each of the sales and customer service apps or $115/user/month for the Customer Engagement bundle which includes sales, customer service, project service and field service.

Another way that customers can save is through combining the subscription types so that users are only paying for the services that they need based on their role.

The Power Apps subscription is not a lower powered subscription for for occasional or read-only users like the Team Member subscription insofar as Power Apps gives users full access to custom entities as well as some shared entities.

The Dynamics licensing guide provides full details on what each subscription type provides.

The InfoStrat Cost Calculator helps you estimate your subscription costs.

See also:

Microsoft Dynamics 365: So Many Apps, So Little Time
Understanding Dynamics 365 and Office 365 Admin Roles
Dynamics 365 and xRM: What Comes Next?
Ten Things You Need to Know About Microsoft Software Licensing

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