DevOps and Dynamics 365/the Common Data Service can go together like peaches and cream, with a bit of effort and utilisation of some community tools. And, as always, you may end up having to contend with pesky errors, such as one I had recently involving a TimeoutException...
A few weeks ago, I did a post on the process involved when migrating Microsoft Azure Cloud Solutions Provider (CSP) subscriptions across tenants. Having done some actual work relating to this since then (shock horror!), I thought I'd follow up with a new post, sharing some additional thoughts and lessons learned.
One of the best things about Azure Data Factory is its ability to incorporate continuous integration and automated deployments quickly alongside your solution. However, if you’re working with SQL Server data sources and are using square brackets to interact with tables, then you may be in for a bumpy ride…
Obscure error messages can be the bane of an IT professionals life, often hampering or even preventing outright any successful resolution of issues. An example of this happened to me recently, during what appeared to be a run-of-the-mill Azure SQL automated deployment.
Migrating across from Microsoft Flow to Azure Logic Apps is ridiculously easy. However, there are some critical feature differences that you must make yourself aware of. One difference relates to how triggers actions work, particularly in tandem with an Azure template.
We saw a few weeks ago how to utilise Azure Active Directory (AAD) Security Groups to manage Azure SQL database access at scale. When using this feature, you must ensure database changes are deployed out using an AAD administrator account or similar, a task which may be difficult to achieve in an Azure DevOps Pipeline.
Validating your Azure templates manually can be a challenging task to complete at scale. Fortunately, with the functionality available within Azure Pipelines, this entire process can be fully automated. This post will show you just how easy it is to implement automatic validation an deployment of your Azure templates within a CI process.
Working with variables within your Azure DevOps Pipeline can give you a high degree of latitude when planning your software deployments. When utilised as release variables, additional functionality is exposed, allowing you to alter the conditional flow within your pipeline dramatically. In this week's post, we'll find out how to use them in practice.
It's essential to understand the precise behaviour your Azure templates will have when deployed, to avoid any unexpected issues or even data loss that could occur. This week's post will explore an example of why this is so important, involving Azure App Service application settings.
Getting your Azure Board backlog working correctly may require some tinkering, particularly if you decide to take advantage of certain features after you have begun using the application. In this post, I'll show you how to get the Team Board/Backlog configured to show work items from all sub-areas within your project.