Recently Azure has announced retirement of Azure Cache for Redis and Azure Cache for Redis Enterprise. This of course leads folks to look at Azure Managed Redis. Note that underneath Azure Cache for Redis and Azure Managed Redis use the same resource type but with different SKUs. Overall my general impression is that not many existing customers have moved from Azure Cache for Redis to Azure Cache for Redis Enterprise. The integration with Redis to other services and applications in most cases happen via providing connection string with credentials. It is well known how to list the credentials from Azure Cache for Redis with Bicep but may be it is not so known with how to do that with Azure Managed Redis due its different Azure architecture.
Category: Bicep
Enabling Defender for APIs on Azure APIM APIs with Azure Bicep
Azure APIM is essential feature in building AI applications. Being part of that it is important to protect your APIs and couple years ago Azure has provided such capability in Defender for Cloud called Defender for APIs. Previously I have demonstrated how to configure Defender for Cloud plans in Enable Defender for Cloud Auto provisioning agents via Bicep. For Defender for APIs plan it is the same resource type Microsoft.Security/pricings but the name of the resource is ‘Api’. Additionally, you will set pricingTier to Standard to enable it and subPlan to P1, P2, P3, P4 or P5. As this is the initial configuration only in this blog post we will look at what to do next.
Deploying Azure APIM MCP Servers with Bicep
Azure API Management (APIM) service is one of the building blocks for AI applications. At the same time MCP (Model Context Protocol) server is one of the latest capabilities around AI. Not so long ago APIM announced support for exposing either existing MCP servers or existing APIs as MCP servers. I have played around with this functionality lately and what it turned out is that these MCPs Servers in APIM are just API resource underneath which means it can be easily deployed with Azure Bicep. In this blog post I will show you how to do it with examples.
Generate Documentation for Azure Bicep Modules with GitHub Copilot
Bicep modules provide this awesome feature to be able to create schema for your Bicep modules via User-defined data types. When you reference Bicep module in bicep template or bicep parameters file you get nice intellisense in VSC to understand the structure of the parameters, whether they are required or not and additional information. This is the same experience when you start to define a resource. I was one of the first requestors and adopters of the feature and I heavily use it every day. Although the feature provides great experience within VSC there is still a need to document that schema in some other place just like it is done for Azure resource. This trivial task is not so easy to do but today I will show you how easy it is by using GitHub Copilot.
Master IaC with Azure Bicep at Global Azure Bootcamp Bulgaria 2025
On the 10th of May I have presented Master IaC with Azure Bicep session at Global Azure Bootcamp Bulgaria 2025. As this was local event and I have publish the examples online you can check them at GitHub repository even if you haven’t attended.




