Skip to main content

Governing the Dataverse: Peaceful Living with Microsoft Power Apps

by James Townsend

Microsoft has created a business software platform which not only includes complete commercial products such as accounting and CRM, but also development tools which may be used by professional software developers and power users.  Microsoft is enpowering power users, sometimes called citizen developers, with tools that require less coding and more configuration through templates and wizards.

All these apps are connected through a shared data model called Dataverse (formerly Common Data Service).  Some apps such as Dynamics 365 Sales store their data in Dataverse.  Security is managed via Office 365 hosted in the Microsoft cloud.  With Power Apps, you can build standalone apps that tap the power of Dataverse.  

Dataverse and Power Apps are not the first tools to target citizen developers.  Microsoft Access, for instance, was a product that allowed end users to create database applications and connect to SQL Server which was often the enterprise data repository for an organization.  SharePoint was also geared toward end users creating sites, lists and other SharePoint objects with or without calling on IT professionals.  

This post is not about how to use these tools, but rather how communication and policies are needed to govern information architecture.  Without governance, business people may become confused on where to look for definitive data.  What happens if there are three independent places where sales or customer data is stored, with no method for reconciling differences?  

Here are some examples of areas that require governance:

  • Security. Microsoft provides authentication capability and a rich security model which allows fine control over who has access and control over what.  This does not mean that managing security is simple or easy.  Giving a large number of people full admin rights increases the chance of serious errors and detracts from accountability.  Security governance requires detailed processes for onboarding and offboarding employees, for instance.
  • Data model changes. Although adding a field to a table is easy, governance calls for a process to manage changes in order to avoid duplicate or ambiguous fields, and to ensure that fields are added to the correct table or tables.  Data model changes may also necessitate updates to documentation and training.  
  • Reports and business intelligence.  While reports and business intelligence visualizations and dashboards do not modify data or change the data model, they must be reviewed to ensure that they are correctly showing what they represent.  For instance, a sales commission report must be accurate to be valuable. 
  • Upgrades. Cloud computing has increased the pace of innovation and brought shorter upgrade cycles.  These must be managed to ensure that they take place and fix any errors that may come with new versions.
  • Resource management. Computing power and storage are now bought as needed.  Successful governance will monitor resource needs and costs, archiving unneeded capacity and allowing for growth. 
  • Monitoring and auditing. You can measure the health of your apps and understand how they are being used through logs and reports.  These findings may alert you before you run into a major disruption.
End user development can come into conflict with information technology managers.  End users may feel they do not have sufficient privileges on their hardware and software environment.  IT managers may feel increased demand for support from citizen developers and become stretched too thin across so many development efforts.  

Open communication is the first step to resolving conflicts between end users and IT managers.  Training and education can make citizen developers more productive and less likely to cause unintentional damage.  

Microsoft will keep promoting the Power Platform for end user development, and the need for governance will become clearer than ever for these solutions. 

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 such as  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: 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