Microsoft has started sending out emails to Dynamics 365 Customer Engagement customers to announce upcoming changes in the July 2017 Update and how the security of network connections is changing. The change is the version of the transport layer security, TLS, is changing to require a minimum of version 1.2, and not accept lower protocol versions anymore, including TLS 1.1 and 1.0. This requires changes to xRM Portals Community Edition (CE) to ensure compatibility.
In my previous post I introduced the Adoxio.Dynamics.DevOps PowerShell module and gave some history and purpose for Adoxio creating it. In this post I’ll cover how to install it and its dependencies so that it can be used to author and run import and export scripts for Dynamics 365 solutions and data.
Earlier today I published a new PowerShell module, Adoxio.Dynamics.DevOps, to GitHub and the PowerShell Gallery. This has been in the works for quite a long time, and was finally done today out of necessity and convenience to release a new version. Until today, it’s only been used internally and by a select few clients on projects we’ve delivered. By releasing this module as an open source project and publishing it on the PowerShell gallery, we’re hoping it will be useful to others as well.
Fully articulating and documenting this PowerShell module is going to be a much larger undertaking than I can forsee myself having a large block of time to do, so I’m going to start out small and begin by describing some of the motivations and goals behind it.
The first week of xRM Portals Community Edition has come and gone, and I’ve been thinking of some next steps to take with the project to make it useful and relevant to those who would like to use and/or contribute to it. GitHub has a projects feature where you can keep track of plans and tasks outside of issues, and I’ve added an initial first set of efforts I’d like to see happen.