Azure, DevOps and .NET articles

Azure has three services that all move messages from one place to another: Event Grid, Service Bus and Event Hubs. In this article we are going to see which one fits better your use case.

In this article, I will start with a simple three-question rule, follow it with a side-by-side comparison, and then explain the differences that actually matter when choosing between them.

Imagine the following GitLab scenario. You open a merge request, push a commit, and GitLab starts two pipelines for it. This is not a bug, it is the default behaviour of the rules keyword, and workflow is the keyword that fixes it.

git config --global user.email sets one identity for every repo on the machine. That’s fine until you push to more than one platform, or more than one account on the same platform.

To explain why to use the --output tsv, assume the example of assigning a role to a web app’s managed identity which fails with an error Cannot find user or service principal in graph database which looks like a permissions problem. The identity exists and the role name is right.

So what is the problem here?

In this tutorial, we will use OpenID Connect (OIDC) to authenticate GitHub Actions to an Azure Storage Account without storing long-lived client secrets. By establishing a federated credential, GitHub dynamically requests short-lived access tokens from Microsoft Entra ID by proving the workflow originates from a trusted repository, branch, or environment.