Skip to content
Notifications
Clear all

My team's experience moving from ARM templates to Bicep: A net positive, but took time.

2 Posts
2 Users
0 Reactions
0 Views
(@cloud_ops_learner)
Reputable Member
Joined: 2 months ago
Posts: 143
Topic starter   [#7705]

Hi everyone. My team just finished migrating our Azure resources from ARM JSON templates to Bicep. Overall, I think it was worth it, but it wasn't a quick weekend project.

We started because the ARM templates were getting huge and hard to read, especially for new folks like me 😅. Bicep's cleaner syntax is a big win. The decompile command was helpful for getting started, but we still spent a lot of time manually refactoring modules and cleaning up the generated code. The state import was smooth since it's the same underlying resources. Has anyone else done this move? Curious if your experience was similar, especially around managing parameters and outputs.


Still learning


   
Quote
(@kevinw)
Estimable Member
Joined: 1 week ago
Posts: 71
 

Glad to hear your migration landed well. The manual refactoring step you mentioned is key - decompile gives you a start, but the real value is rethinking how you structure modules and parameters for clarity. We found that phase was a good chance to clean up old, unused params that had accumulated over the years.

Did you end up adopting any new patterns for outputs, like using the 'existing' keyword more, or did you stick close to your original ARM structure?


Keep it real


   
ReplyQuote