We've dealt with a fair share of Azure Resource Manager (ARM) template errors in the blog previously. So why not take a look at another one, this time involving Linux App Service Plans and a .NET Core web application...
Azure Data Factory (ADF) remains a massive area for me, and within the projects I'm involved in. Previously, those looking to use ADF to map into Owner or Customer fields in the Common Data Service may have hit a few issues. Thankfully, this is now all in the past.
Secure authentication between Azure Logic App and Function Apps has been possible for a while. What's less clear is whether we can automate the setup of this as part of an Azure Resource template deployment. So, that leaves us with only one option - let's find out!
It's relatively rare that you will find differences between what's available in Power Automate flows and Logic Apps. The Common Data Service is perhaps the exception to this rule, as its missing some options to allow you to define which attribute data to return from your instance...
Azure API Management and resource manager templates are not natural bedfellows, as I recently discovered. Although it's possible to get them working alongside each other, there is a bit of trial and error involved. That's why I thought I'd share my recent experiences working with them both.
If you are building applications leveraging Azure Active Directory, you may already be aware of the new OAuth 2.0 V2 endpoints to use when generating access tokens. And, although it requires a refactor, it’s possible to utilise them today when connecting to Dynamics 365 / the Common Data Service.
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...
Are you considering enabling Security Defaults on your Azure Active Directory tenant? If so, you may want to think twice before flipping that button so that you can prepare for the potential disruption involved...
Application users within Dynamics 365 / the Common Data Service arguably provide a far superior option when compared to traditional service accounts with a user name and password. In today's post, we'll dive and find out more about them.
The Dynamics 365 / Common Data Service Web API allows developers to leverage a wide variety of functionality, from almost any conceivable location - such as, for example, an Azure Data Factory V2 pipeline. With this in mind, let’s dive in and see how to achieve this.