Skip to main content

Energize your Intranet with Microsoft Power Apps and Customer Voice

Power Apps model designer

by James Townsend

This is a followup to my earlier post "Replacing Microsoft InfoPath with Power Apps" which discussed the discontinuation of the InfoPath form tool which was previously used in conjunction with SharePoint for many internal corporate applications typical on an intranet. Since then, Microsoft renamed the Forms Pro product Dynamics 365 Customer Voice. This is not to be confused with Microsoft's Voice of the Customer product which was deprecated in July 2020 to be replaced by Forms Pro. 

Power Apps is the platform on which Microsoft Dynamics 365 apps, at least those apps derived from what was formerly called Dynamics CRM, are built.  You can use Power Apps to create two types of apps -- canvas apps which are designed in a drag-and-drop fashion for relatively simple standalone needs and model-driven apps which are based on the Dynamics 365 Unified Interface and which can support sophisticated workflows in the same way that they are handled by Dynamics 365. 

I feel that intranets have fallen out of fashion a bit, and we do not hear as much as we once did about products like SharePoint which are geared toward internal use.  Instead, the focus has shifted to real time collaboration powered by Microsoft Teams, Zoom, GoToMeeting and other products.

The need for internal apps remains, and the appeal of low code/no code technology is strong.  Your internal apps may have fewer users than customer apps, and you may value flexibility as your internal processes change.  Power Apps is a great way to automate internal work flows such as:

  • Routing and approval. Timesheets, vacations, expenses and other data need automated workflows for approval, and Power Apps canvas apps can be simple to build, with all the functions you may need. 
  • Request tracking. Power Apps forms can gather information from employees to kick off a request workflow such as resource requests.  You may also want to consider Dynamics 365 Customer Service for this, especially if you want a knowledge base and a pre-built tech support portal. 
  • External lookups and integrations.  Power Apps can simplify accessing other databases for quick lookups which are accessed in teams or SharePoint. 

Microsoft offers several ways to integrate your apps with one another.  SharePoint can offer access to corporate documentation, document management for version control, simple lists of data and other content. Teams provides an interface which may be used as the jumping off point for these Power Apps. 

For more information, see my related posts:

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/ by James Townsend 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