Skip to main content

6 Reasons to Choose Microsoft for your Low Code Application Platform


by James Townsend

Low code software development has been in the news in 2020.  The COVID crisis has disrupted many businesses, and they have been forced to transform themselves rapidly.  We have never seen so much digital transformation since that term was coined in 2012.  Low code development platforms have been chosen for many of these efforts because they can bring software solutions to fruition more quickly than traditional development methods.

Businesses and other organizations are choosing which low code platform they need, and these products are maturing quickly.  This post highlights six reasons why organizations choose Microsoft for low code application development.

  1. Microsoft has the most complete platform. No software vendor comes close to offering as a wide a set of capabilities as Microsoft.  These include database (Dataverse), business intelligence (Power BI), reporting tools, integrated document management (SharePoint), email (Outlook), spreadsheet (Excel) and even artificial intelligence tools. The breadth of products makes Power Platform a fit for a wide variety of business scenarios.  
  2. Product maturity.  The Dynamics precursors of Power Platform such as Dynamics CRM have been well well established for many years and are familiar to many IT departments. Microsoft invests extensive resources to continuously improve its products, so you can expect new features to continuously appear. 
  3. The Microsoft cloud. Today's strongest low code platforms are hosted in the cloud, and Microsoft has the second most popular cloud offering after Amazon Web Services.  For business and government, Office 365 is the leading cloud productivity suite, so users already have Microsoft cloud accounts.  Microsoft hosts government clouds in the United States and other countries which achieve the highest security accreditations.  Microsoft bears the expense of upgrading the cloud and provides a financially-backed guarantee of uptime. 
  4. The Microsoft ecosystem. Microsoft has tens of thousands of resellers and implementation partners worldwide.  Some of them specialize in Microsoft low code development. Microsoft AppSource is a marketplace for Dynamics solutions which can be installed in Power Apps either as complete solutions in themselves or as components of a low code solution.  
  5. Security integration. The Power Platform exists in the context of Office 365, making security management much more efficient than when multiple platforms are used.  The permissions model is quite granular and powerful. 
  6. Mobile apps. Microsoft creates and maintains mobile apps which you can download from the leading app stores.  Mobile computing has continued to grow in importance, and these prebuilt apps represent significant savings of time and money from building custom mobile apps. 
While companies can choose more than one low code platform, this undermines the benefits of going low code in the first place.  Standardizing can ensure compatibility and interoperability as well as save on subscription costs and support personnel. 

For more information, see my related posts:

Popular posts from this blog

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

Updated 8/15/2022 To understand Microsoft Dynamics 365 (formerly Dynamics CRM) and Power Apps, 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.  These concepts also apply to Power Apps.  The main difference is that with Power Apps you are not starting with a Microsoft app but more of a blank canvas for your custom apps.  This post introduces some key terms and how these concepts are important for planning your implementation. While Dynamics 365 is still 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 in several countries. 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 uni

My Favorite Microsoft Power Apps Bloggers and their Blogs

  by James Townsend Updated 7/5/2022 Microsoft Power Apps is one of my favorite subjects, and I enjoy reading blog posts from members of this thriving technical community.  Here are some of my favorite bloggers and their blogs: The Official Microsoft Power Apps Blog   I have to start with the official Microsoft Power Apps blog.  It has many contributors, largely Microsoft program manager, including frequent posters Denise Moran ,  Greg Lindhorst , Kartik Kanakasabesan , and  Adrian Orth .  This is the place to go for product announcements, updates and technical how-to for a broad range of Power Apps topics.  April Dunnam April Dunnam was formerly focused on SharePoint and now devoting herself to Power Platform.  April offers highly understandable explanations of Power Platform, Dataverse and other top Power Apps topics. She joined Microsoft in late 2019 and has a thriving YouTube channel .  Carl De Souza Power Apps Blog and eBook This is one of the most extensive and best organized blo

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