Microsoft just announced pricing for Microsoft Entra External ID M2M Authentication.
Starting November 1, 2025, every access token issued via the Client Credentials Flow will cost $0.001.
The feature isn’t going away — it’s simply entering its “production maturity” phase.
It’s time to pay more or less.
I’ve tried this before.
Starting a blog. Writing something.
And every time, I failed.
Not because of the tools. I know how to set up a blog.
I failed because I wasn’t sure what to say.
Every topic I thought about… I told myself:
So I stopped. Again and again.
In today's software development landscape, securely handling confidential data is not just a priority but an indispensable quality requirement. In my presentation, I will demonstrate how developer teams can protect sensitive information within the Azure cloud environment. From utilizing Azure Key Vault to leveraging Managed Identity and Infrastructure as Code (IaC) - discover how these techniques not only bolster security but also enhance flexibility in the development process. Join me on this exploration and gain practical, proven strategies.
https://basta.net/cloud-azure-serverless/azure-security-key-vault-managed-identity/
You're working on an ongoing project, but you're tired of manually applying any infrastructure changes to all environments. Not to mention documenting the changes. Ideally, the team would focus on delivering features. Regardless of the project's progress, Infrastructure as Code (IaC) can be used to make that happen. However, it is not easy to get started, and you quickly fall into "Infrastructure by clicking". What are the risks of this approach, and why is it worthwhile to rely on IaC? What tools are available, and which is suitable for your team? This talk will demonstrate how you can integrate Azure Bicep into your CI/CD pipeline using examples and best practices. This way, your team quickly delivers new features to the customer.
https://basta.net/cloud-azure-serverless/infrastructure-as-code-oder-klick-klick-bang/
You're working on an ongoing project, but you're tired of manually applying any infrastructure changes to all environments. Not to mention documenting the changes. Ideally, the team would focus on delivering features. Regardless of the project's progress, Infrastructure as Code (IaC) can be used to make that happen. However, it is not easy to get started, and you quickly fall into "Infrastructure by clicking". What are the risks of this approach, and why is it worthwhile to rely on IaC? What tools are available, and which is suitable for your team? This talk will demonstrate how you can integrate Azure Bicep into your CI/CD pipeline using examples and best practices. This way, your team quickly delivers new features to the customer.
https://basta.net/cloud-azure-serverless/infrastructure-as-code-oder-klick-klick-bang/
Monitoring is the best way to give team members a good night's sleep. No one wants to be woken up in the morning by a call from an angry supervisor: "The system is not working; fix it now!". Granted, monitoring doesn't just help restful sleep but relatively quick feedback from real users. After all, we all strive for feedback in agile teams. With monitoring, real and fast feedback becomes possible, where tests only allow it with a lot of effort or are not feasible at all.
But how can agile teams establish monitoring in their daily routine? How do you get the metrics for monitoring? Who is responsible for monitoring, and when is monitoring the right tool?
In this talk, I will show by example the path to continuous and proactive monitoring in agile teams and where they should pay attention to. For this purpose, the possibilities of Azure Monitoring are used, and Infrastructure as Code is used to set up the selected monitoring solution.
Monitoring is the best way to give team members a good night's sleep. No one wants to be woken up in the morning by a call from an angry supervisor: "The system is not working; fix it now!". Granted, monitoring doesn't just help restful sleep but relatively quick feedback from real users. After all, we all strive for feedback in agile teams. With monitoring, real and fast feedback becomes possible, where tests only allow it with a lot of effort or are not feasible at all.
But how can agile teams establish monitoring in their daily routine? How do you get the metrics for monitoring? Who is responsible for monitoring, and when is monitoring the right tool?
In this talk, I will show by example the path to continuous and proactive monitoring in agile teams and where they should pay attention to. For this purpose, the possibilities of Azure Monitoring are used, and Infrastructure as Code is used to set up the selected monitoring solution.