Skip to main content

DevOps for Microsoft Dynamics

The repository for DevOps for Dynamics 365 Customer Engagement https://github.com/devkeydet/dyn365-ce-devops
Much has been written about how Microsoft Dynamics may be used to create software solutions using configuration to replace extensive coding needed for traditional software development.  This "low code" approach can save time and reduce costs for building and implementing business solutions for some scenarios.

At the same time, development tools and processes for "low code" are not as mature as those for most software development, especially for large and complex projects with multiple developers.  The tools are catching up and Dynamics implementers and administrators are adopting best practices for rolling out Dynamics solutions.  One of the most important of these approaches is DevOps. The goal of DevOps is to shorten the time between software iterations by integrating development and operations processes.  One of the chief ways to accomplish this goal is through automation of the software build and deployment processes.

Last weekend I attended a session on DevOps for Microsoft Dynamics at the Washington, DC 365Saturday event, presented by Microsoft's Carlton Colter.   Mr. Colter explained how Dynamics developers can implement DevOps in their organization, and highlighted features in Azure DevOps (formerly Visual Studio Team Services). He demonstrated how to automate build and deployment steps.

Microsoft's Marc Schweigert has long been a leader in Microsoft developer tools and recently has focused on Dynamics 365.  He shared his insights at this session and answered questions from the audience.  Mr. Schweigert has created a series of videos to explain DevOps for Dynamics, starting with these introductions:



From Build and deployment automation of PowerApps & Flow using Azure DevOps

Intro to DevOps for Dynamics 365

Step-by-step videos provide additional detailed information:



part 1


part 2

If Dynamics saves you development time, you want to be sure that it is not wasted in the testing and deployment process.  Automation can help with many of the tasks and lead to solutions with fewer defects. 

The DevOps automation process can be complex, and it requires code, but in the long run it will save money for nearly any organization committed to "low code" development. 

Additional Sources




Popular posts from this blog

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

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

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