Azure Readiness starts here...

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

Sending Emails from Azure DevOps using PowerShell and Azure LogicApps

Hi Readers, This post is merely for myself, documenting all the steps I needed to go through to be able to send emails from a PowerShell script, as part of an Azure DevOps YAML pipeline flow. And since I was documenting it for our internal application, I thought it would hopefully help someone out there looking for a similar solution. Why not using the built-in Email Notification system Azure DevOps provides email notification features, but this comes with a few assumptions.

Trigger a YAML Pipeline from a Classic Release Pipeline in Azure DevOps

Hi y’all! Over the last 18 months, I’ve been developing a tool for our internal Microsoft Trainer team, allowing them to deploy trainer demo scenarios in Azure using a Blazor Front-End web app, connecting to Azure DevOps pipelines using REST API calls. At the start of the project, Classic Release pipelines were still common, since YAML was too new, and rather unknown. However, over the last few months, more and more I was thinking of shifting from Classic to YAML Pipelines.

You do not have permissions to view this directory or page after publishing to Azure App Service

Earlier this week, I got an interesting phenomenon when publishing a code update to an existing Azure App Service. As this was a small project, I’ve always been deploying updates in a manual way from right-click / publish in Visual Studio. But than I said to myself, Peter, as a passionate DevOps engineer and trainer, just go out and create a pipeline for this. And that’s what happened. Running the release pipeline came back successful, but the site threw an error:

Collecting Feedback in ADO work items from Office Forms

Hey folks, I’m a fond user of Azure DevOps for testing application builds, running CI/CD pipelines to publish Azure demo scenarios and train our Microsoft global customers on it every few weeks out of AZ-400 training deliveries. One of the lesser-known, yet AWESOMELY POWERFUL features besides ‘running pipelines’ is Azure Boards, providing an end-to-end project methodology platform using Scrum, Agile, CMMI or custom approach. In this post, I mainly wanted to zoom in on the custom capabilities, capturing feedback from employees - which got entered through an Office Forms form, picked up by Azure Logic Apps, and stored in a customized Azure Boards Work Item.

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.