Azure Readiness starts here...

The best way to know the future, is to learn it

AzCopy failing in Azure Devops with error ServiceCode=AuthorizationPermissionMismatch

Hi all, This is one of the nail biting challenges of our industry, failing in running a straight-forward task. Especially when it is failing… What happened? I was creating a pipeline in Azure DevOps to deploy an ARM template for VM setups with VM Extensions. To prep this deployment, the artifacts (DSC scripts) should be copied to Azure Blob Storage, in order for the Azure DevOps build agent to “find” it.

Azure Back To School (with Azure DevOps)

Hey everyone, Wow, it’s September already! Where has summer been? And honestly, where has the (nice) year been? Most of you, just like myself, are probably still working from home, and I guess the same are your kids. Where September used to feel like a fresh start (remember that smell of your new school outfit, the new school equipment, fresh-sharpened pencils, the excitement of learning new things, meeting new class mates,… almost seems like I want to go back to school myself.

Azure DevOps Pipelines - YAML or Classic Designer

During several of my AZ-400 Designing and Implementing Microsoft DevOps Solutions training deliveries, one recurring point of conversation is Should we use YAML or the Classic Designer for our Release pipelines? So I thought sharing my view in another blog post could be helpful. Before answering the question more accurately, let’s go over each scenario a bit more in detail: Classic Designer Classic Designer has been the long-standing approach on how Azure DevOps Pipelines have been created.