Developers typically get the short end of the stick in lots of things, and consistent learning tools is one area I’d highlight, particularly in the Dynamics 365 space. Fortunately, this no longer appears to be the case, thanks to the release of exam MB-400.
A common gripe concerning Microsoft Azure App Service is the fact that you must pay an additional cost to deploy a TLS certificate. Fortunately, this concern is now a thing of the past, thanks to the introduction of the App Service Managed Certificate preview feature.
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…
Moving Azure subscriptions across multiple tenants is usually a doddle. I say “usually” because, recently, I hit a bit of brick wall when figuring out to move a Cloud Solutions Provider (CSP) subscription, with there being no obvious way of achieving this simple task.
I’ve worked with SQL Server for several years now, and I am continually amazed at its capabilities, Recently, my work in this area has focused on the products change tracking feature, a nifty tool that can assist you in monitoring how your data evolves.
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.
Dealing with “Your Azure credentials have not been set up or have expired” Error Message in a Azure Template Visual Studio Project
Keeping things simple is an idea I like to promote at all times, particularly in the world of IT. Adopting this mantra can lead to fewer headaches and, as a recent example involving Azure Template deployments within Visual Studio demonstrates, a much faster resolution to your particular problem.
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.