August month updates from Azure Bicep

Hi friends,

This month we have awesome updates from Azure bicep team that I am happy to share with all of you (Azure community, Deployment Automation, Resource management and Governance geeks πŸ™‚

The following list are August month updates:

  • Bicep Linter, Snippets, Scaffolding
  • Right click build
  • Deployment Stack updates
  • Bicep roadmap plans (v0.5 and eventually v1.0)
  • Bicep registry
  • OCI Artifact standardizations
  • Module registry functionality
  • Module Reference Syntax
  • Parameter Improvement options

Bicep Linter updates

The yellow squiggly lines indicate the Linter violations and complains where best practices are violated. Like, password param should not be checked into the code repository. Another one is using string concat function instead of string interpolation.

Right click build

The right click build on bicep file is a new convince feature that was also added on new build.

You can also use a shortcut keys Ctrl+Shift+B as an alternative way to build your JSON files from bicep files.

Scaffolding feature

This feature also arrived on a v0.4.6 build that provides required-properties to be auto populated to speed up your Azure resource coding. It is derived from a resources swagger spec and auto-populated for you. Yay!

New Code Snippets

You will love to discover that bunch of new snippets has been added.

Just type res- and you will scroll over all those starter boilplet code. Just imagine how much time you will be saving. It is Huge!!!

Bicep Roadmap annoncements

Well, Bicep team annonced that next build will bring the v0.5 and they do target v1.0 by th end of the year. What does it mean is – there will be no API level breaking changes starting from the version v1.0.

What is Next?

Keep tuned for upcoming v0.5 version. The Module registry updates and syntax updates on OCI Artifacts are going to be next Huge things, as they will add into the maturity of this AWESOME tool in Azure!

Check out for more @ GitHub – Azure/bicep: Bicep is a declarative language for describing and deploying Azure resources

Stay tuned for more Azure automation & Security related posts.

Fᴏʟʟᴏᴑ ᴍᴇ 🎯 α΄€Ι΄α΄… become α΄€ #cloudmarathoner β›…πŸƒβ€β™‚οΈπŸƒβ€β™€οΈ – 𝐋𝐄𝐓’𝐒 π‚πŽπππ„π‚π“ πŸ‘

 990 Reads

What is new in Azure Bicep v0.4?

Hello Cloud Marathoners,

I hope everyone getting a chance to enjoy the summer and spend some time with loved once.

That said – Azure Bicep team does not seem slowing down, and I love it!
New features and capabilities have been added to Azure Bicep product v0.4 version, and we will review those innovations on this post.

What is Azure Bicep?

Azure Bicep is a domain-specific language (DSL) that significantly simplifies the Azure resource authoring. It makes representation of your Azure digital estate concise with clean syntax by adding reliable type safety and code-reuse.

A typical Azure Bicep language code for an Azure storage account declaration will look as simple as the following code below – which basically explains why Bicep is called a DSL.

Why would you need it?

There are number of benefits in using Infrastructure-as-Code approach. Azure Bicep might be the right tool for you to use for Azure deployments, especially if you are trying to modernize and simplify the Azure deployment process.

Let’s look into scenarious where Bicep is the right tool to use:

βœ”οΈ Want to use language native to Azure?
βœ”οΈ Looking for fully integrated templates withing Azure platform?
βœ”οΈ Looking for fully supported product with Microsoft?
βœ”οΈ Don’t want to keep or worry about your resource state information
βœ”οΈ Looking to modernize and easy transition from JSON

Well, if your response is YES for above statements/questions then Bicep will be right tool for your solution.

New additions to Azure Bicep in version 0.4

There are numbers of enhancement and features has been added from this release. Let’s look at main Highlights of these features below:

βœ… Linter MVP – The Bicep linter will inspect your code and catch a customizable set of authoring best practices.Β 
βœ… Deprecated parameter modifiers removed – Strip out deprecated parameter modifier syntax
βœ… New code snippets – Suggestion with new code snippets added
βœ… Bug fixes – Number of bug fixes added, thanks to community support
βœ… Bicep Playground fixes – Playground doesn’t load after breaking change.
βœ… Documentation and examples update
βœ… Support for List method call on Azure resource references
βœ… Support for JSON literal string conversion
βœ… Support for using local json templates as modules
βœ… Support for object body completion snippets

What is next?

There are still number of milestones in-front of Bicep team, as the versioning # of Bicep project indicates. That said, starting from Bicep version 0.3 you can get an official Microsoft support.

Below is the sneak-pick preview on what is cooking for v0.5 – which is expected to be out sometimes around August month this year.

Here is an official reference to next milestone on Azure Bicep v0.5.

Thank you for reading till this point. Stay tuned for more Azure Cloud automation and Bicep related posts.

Fᴏʟʟᴏᴑ ᴍᴇ 🎯 α΄€Ι΄α΄… become α΄€ #cloudmarathoner β›…πŸƒβ€β™‚οΈπŸƒβ€β™€οΈ – 𝐋𝐄𝐓’𝐒 π‚πŽπππ„π‚π“ πŸ‘

#microsoftazure
#Bicep
#AzureBicep
#infrastructureascode
#bestpractices
#continuouslearning

 422 Reads

Error on Bicep module – on Azure CLI (2.22.0) for Windows 10

If you are seeing “fromisoformat” error while running az bicep version or any other az bicep command – you are not alone πŸ™‚

Check this open issue reported on GitHub by community member – https://github.com/Azure/azure-cli/issues/17718


After updating to the latest Azure CLI (2.22.0) for Windows 10, I am now seeing the same error as others have reported:

Any command such as “az bicep version” is producing the following error:

The command failed with an unexpected error.
Here is the traceback and detailed error:
type object 'datetime.datetime' has no attribute 'fromisoformat'
Traceback (most recent call last):
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 657, in execute
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 720, in _run_jobs_serially
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 691, in _run_job
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 328, in call
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/init.py", line 807, in default_command_handler
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/custom.py", line 3294, in build_bicep_file
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 63, in run_bicep_command
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 152, in _load_bicep_version_check_result_from_cache
AttributeError: type object 'datetime.datetime' has no attribute 'fromisoformat'

Is there a temp workaround?

One of the workarounds is to uninstalled Azure CLI 2.22.0 , and then install the prior version 2.21.0. You could confirm 2.21.0 version is working for you by running the same command.

Hope this will be helpful for you, as i faced with this issue hours before my demo to #GlobalAzure 2021 😐

 258 Reads

Are you ready to start your Bicep transformation journey in Azure?

Hello friends,

I am getting ready bits and pieces of the presentation and demo code for the #GlobalAzure 2021 event.

This is going to be my second year in a row, presenting at this global event, and I am pumped to contribute with two new sessions this year.

Feel free to check out the details of each session and links here .

Session banner for upcoming presentation on Global Azure 2021

WHY bother to transfrom your exising Azure ARM templates into Bicep?

  • Easy to understand and maintain code for your Azure infrastructure
  • Day zero support for all resource types & API versions
  • Nice transparent abstractionΒ for the underlying platform
  • Awesome Tooling – VS Code extension for Bicep
  • Deep integration with other Azure Services
  • Preflight validation – both Bicep/ARM does preflight validation on entire template
  • Provides high level of confidence that your code is ‘syntactically valid’ before deploying
  • Support – starting from v.03, Bicep is 100% supported by Microsoft Support Plans

This time, I am looking forward to share level 200 talk and demos, where we will ALL deep dive into challenges of transforming exisiting ARM templates into Azure Bicep.

We will inspect the ARM JSON decompiler, which comes with Azure Bicep and how to make it work your way.

Stay tunes, i hope to see you all during the event!

 241 Reads

Transfrom your Azure ARM into Bicep during the Global Azure 2021

Global Azure 2021 event in mid-April.

Hello eveyone,
I am very happy to share exciting news with all of you.

Few days ago, i have receieved an email confirming acceptance of my both Azure sessions for the Global Azure 2021 event. I am truely trilled to present on April 16th and 17th following two sesions for eveyone live:

I am looking forward for your participiation, and tune in to learn about latest developments in Microsoft Azure.

In my first session i will share the following new session with you.

Abstract of the presentation as is:

Infrastructure as a Code (IaC) is important strategy to manage your digital estate in any cloud environment. Simplifying management of your infrastructure while re-using code is even better. In Microsoft Azure, we have ARM (Azure Resource Manager) templates that could declaratively define your cloud project infrastructure.

However, it is not easy to author ARM JSON templates and maintain them when your project grows and requires changes. In this demo heavy session, we will introduce the Azure Bicep language and demonstrate how it simplifies authoring ARM templates for your Azure infrastructure. We will author a manageable, readable, and modularized Azure infrastructure code, while using familiar tools.

TheCloudMarathoner πŸ™‚

Please let me know, what topics are you interested in?

 355 Reads

Why “Start small and Expand” approach is good for your company business?

As cloud☁️ journey matures, each company 🏨 knows that service
requirements and needs will be changing. As cloud providers add new features and products, the new market opportunities and possibilities will rise.

There are several reasons why you would want to pursue the cloud landing zones. Using the start small and expand landing zone, you could get started with cloud adoption at a low-risk pace, and build up the security, governance, and regulatory policies over time.

As a benefit, with “start small and expand” you can use Azure Resource Manager templates and Azure Policy to create a CI/CD pipelines for subscriptions with Azure Blueprints.

As an ongoing improvement effort, you could expand and improve the landing zone with the Cloud Adoption Framework enterprise-scale design guidelines from Microsoft Azure β„’

Get started by learning “What is an Azure landing zone?” πŸ‘‰ https://lnkd.in/eD7xtWV #SharingIsCaring❀️

Fᴏʟʟᴏᴑ 🎯 theΒ #cloudmarathonerΒ β›…πŸƒβ€β™‚οΈπŸƒβ€β™€οΈ on LinkedIn α΄€Ι΄α΄… 𝐋𝐄𝐓’𝐒 π‚πŽπππ„π‚π“ πŸ‘

 313 Reads

Starting points in DevSecOps journey

Hello friends,

During my journey to become a Microsoft Azure Security professional, I have compiled set of useful resources in addition to the exam materials. These resources do complement cloud and application security with open-source tooling, and a book that is much needed for success.

I am excited to share this with my network and DevSecOps enthusiasts πŸ™‚

  1. WhiteSource Bolt – is a #free developer tool for finding and fixing open source vulnerabilities.
  2. Find Security Bugs – it is a SpotBugs plugin for security audits of Java web applications – https://find-sec-bugs.github.io/
  3. OWASP Zed Attack Proxy (ZAP) – one of the most popular free web security tool, actively maintained by a dedicated international team of volunteers – https://owasp.org/www-project-zap/
  4. Sqlmap – is an open source penetration testing tool that automates the process of detecting and exploiting SQL injection flaws and taking over of database servers – http://sqlmap.org/
  5. OpenVAS – Open Vulnerability Assessment Scanner is a full-featured vulnerability scanner. Its capabilities include unauthenticated testing, authenticated testing, various high level and low level Internet and industrial protocols, performance tuning for large-scale scans and a powerful internal programming language to implement any type of vulnerability test. – https://openvas.org/
  6. Recon-ng – is a full-featured Web Reconnaissance framework written in Python. Complete with independent modules, database interaction, built in convenience functions, interactive help, and command completion, Recon-ng provides a powerful environment in which open source web-based reconnaissance can be conducted quickly and thoroughly – https://tools.kali.org/information-gathering/recon-ng
  7. OWASP Glue – is a framework for running a series of tools. Generally, it is intended as a backbone for automating a security analysis pipeline of tools – https://github.com/OWASP/glue
  8. Awesome DevSecOps book. Inspired by the awesome-* trend on GitHub. This is a collection of documents, presentations, videos, training materials, tools, services and general leadership that support the DevSecOps mission. These are the essential building blocks and tidbits that can help you to arrange for a DevSecOps experiment or to help you build out your own DevSecOps program.
  9. #lambhack is A vulnerable serverless lambda application. This is certainly a bad idea to base any coding patterns of what you see here. It allows you to take advantage of our tried and true application security problems, namely arbitrary code execution, XSS, injection attacks and more.
  10. Black Duck is a commercial alternative to WhiteSource Bolt. It helps to manage the risks that come with the use of open source. Black Duck software composition analysis solutions and open source audits give you the insight you need to track the open source in your code, mitigate security and license compliance risks, and automatically enforce open source policies using your existing DevOps tools and processes.
  11. OWASP Honeypot-Project. Goal of the OWASP Honeypot Project is to identify emerging attacks against web applications and report them to the community, in order to facilitate protection against such targeted attacks. Based around the earlier OWASP/WASC Distributed Web Honeypots Project.
  12. Open Source Honeypots That Detect Threats For Free. You could read details on this interesting post.

Note: in noway this presents a complete guide. However, I hope it will guide your project into a more successful DevSecOps state.

I do encouragetoΒ comment and shareΒ your tips and resources here. This will ultimately help every community member to become a better security professional. Thanks!

 158 Reads

Journey to Azure DevOps Expert with a 3P mindset – People… Processes… Products

Hello my friends!

If you are looking to get some study tips on an Azure DevOps Engineer Expert certification then you landed in a right post πŸ™‚

So why Azure DevOps as a platform for your organization’s digital transformation? Well it is build for any language, and any platform. Yes, that is 100% true statement! Run the OSS (#opensourcesoftware) tools and frameworks on it, anything you want, in addition to Microsoft stack.

This weekend, I got loaded with fresh coffee and sit to wright-down experiences and resources I have used, along the journey to become an Azure DevOps Expert.Β 
This journey brings along a new credential inΒ Microsoft Certified: DevOps Engineer Expert. However, most importantly, it refreshes your understanding of latest developments in the DevOps ecosystem on Microsoft Azure platform.

Side note: I have been actively using Microsoft DevOps pipelines for the last 2.5 years. Having this experience provided a lot of help in understanding exam objectives and focusing on areas that I never touched.

Overall, Microsoft Expert exams are harder than Azure fundamentals and associate exams. They come with test scenarios, labs and tricky questions where you have to know the order of processes – in one way testing your real-world understanding of the processes and technologies and its interconnected components.

Earning the DevOps Engineer Expert certification demonstrates the ability to combine people, process, and technologies to continuously deliver valuable products and services that meet end user needs and business objectives. DevOps professionals streamline delivery by optimizing practices, improving communications and collaboration, and creating automation.

Microsoft Learn

Now, as you may expect, there are tons of material out there on how to get prepared for required two exams that qualifies you to Expert certification. I took a bit stiff hill to climb πŸ™‚ First, I went head-on with AZ-400 “Designing and Implementing Microsoft DevOps Solutions” exam and later focused on Azure Administrator Associate exam.

As an alternative, you could choose a developer path. It applies very well for the case, where you might already have an Azure Developer Associate certification and just need to pass AZ-400 to qualify for the DevOps Expert certification.

Study Materials and references

I primarily used Microsoft Learn – an online and free starting point to cover gaps in my knowledge and skills. by complementing it with Pluralsight videos. I have combined the following list of resources that you might find handy πŸ™‚

In summary, the important once are listed on top. They are all very important, as you would like to keep your knowledge up to date with developments on DevOps world.

In a nutshell, I tried my best to walk you through the process, options and resources that will help you along the way. Hopefully, this brief guide will help you on your journey to prepare and become an Expert DevOps Engineer!

Meanwhile, feel free to answer the following questions:

  • Comment on your exam preparation approach?
  • What challenges are you facing or already overcame?
  • What helped and what did not – in setting up for a DevOps journey?

Thank you and May The 4TH Be With You!

 302 Reads