Leverage Bicep: Standard model to Automate Azure IaaS deployment (2 of 3)

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.

Chapter 2

<< Chapter 1          Chater 3 >>

 

 

  • Tips
    Install extensions from VS Code
    AkiraKoike_0-1682664306262.png

    -- Only GitHub Copilot is available for a fee.


    Azure Resource manager Tools Extensions

    AkiraKoike_0-1682673652583.png


    Bicep Extensions

    AkiraKoike_1-1682673946759.png

     

    Bicep Visualizer
    AkiraKoike_0-1682674265111.png


    GitHub Copilot
    AkiraKoike_1-1682674522578.png

     

  • Sample code and explanation

    localtemplate/bicep/BICEP at master · akkoike/localtemplate (github.com)

    - Application sequence mapping
    AkiraKoike_0-1682681099339.pngAkiraKoike_0-1682682528998.pngAkiraKoike_1-1682682585973.png

     

    Based on vNET Hub&Spoke environment. Frequently updated settings were individually defined in JSON configuration files. Azure KeyVault was created first because I wanted to obtain a secure password using the getSecret function. RBAC and Diagnostic Setting are done at the end of the process for extended functions. NSG rules and Azure Firewall ruleset basically stated only the targets that should be allowed. All external communication from Azure VM is configured with a default route through Azure Firewall. Only Log Analytics with AMPLS may not work properly.

    Almost 30 USD / day
    AkiraKoike_2-1682682832324.png

     

>> Next Chapter (Traps and Avoidance)

<< Chapter 1

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.