Make Building in Azure Super Easy 😮

Поделиться
HTML-код
  • Опубликовано: 6 окт 2024

Комментарии • 20

  • @bennyboy111
    @bennyboy111 2 года назад +2

    That's funny I just deployed your blueprint today! No idea it was yours, thanks.

    • @AzureAcademy
      @AzureAcademy  2 года назад +2

      LOL...VERY COOL! Thanks for letting me know!

  • @anthonydelagarde3990
    @anthonydelagarde3990 2 года назад +1

    Awesome video!!! Great production!

  • @christianibiri
    @christianibiri 2 года назад +1

    I love this video and landing zones are fantastic..

  • @anthonydelagarde3990
    @anthonydelagarde3990 2 года назад +1

    I love the graphics on this post!!!

  • @lfx2mlfx2m8
    @lfx2mlfx2m8 2 года назад +1

    can you make a video about how to set up a resource group that would host say a sharepoint in a different region, for example europe, if you are in the us?

    • @AzureAcademy
      @AzureAcademy  2 года назад +1

      Not sure I understand…Host a SharePoint? Do you mean a share point server build in north Europe and you are in the US??? Yes you can do that. There is NO default restriction where you build resources. Not sure I am following you thinking here…can you clarify?

  • @bennyboy111
    @bennyboy111 2 года назад +2

    Dean what are your thoughts on the hub and spoke topology? Doesn't this just increase costs for Vnet transit as opposed to having everything in one Vnet?

    • @AzureAcademy
      @AzureAcademy  2 года назад +3

      Great question Ben! Yes Hub and Spoke would have transit cost over the peers.
      The benefit is controlled isolation. Every vNET in Azure is isolated from every other VNET until you peer them...Once you peer, you need to control the traffic with a firewall or NSG to secure it. The alternative is to with have 1 very large VNET or a VNET with multiple address spaces and multiple subnets. This works as well...but it is harder or most traditional network admins to grasp how to secure it...so they are comfortable with Hub and Spoke...so this is kind of a chicken and egg situation. customers are used to hub and spoke and VLAN...so Azure does hub and spoke so it is familiar to them...but the Cloud is also a great place to start doing things in a new way, like you suggest. Both work...and I personally like fewer vnets with more address spaces...but if you don't secure it properly it is more risky. - GREAT QUESTION!

  • @techy2023
    @techy2023 Год назад +1

    Can I apply this to an environment that has some workloads already? let's say I have a VM that's already been setup with its own bastion, then if I apply this LZ, that VM will still use its own bastion instead of going through the HUB>Azure FW, etc. So, is this ideally for brand new environments ? Thanks Dean, great content!

    • @AzureAcademy
      @AzureAcademy  Год назад +1

      Yes you can because it builds into its own resource groups

  • @wssDrglatze
    @wssDrglatze Год назад +1

    is there a possibilty to not limit this landing zone to the US? Sadly i cant choose Europe as "Location" :(

    • @AzureAcademy
      @AzureAcademy  Год назад +2

      This specific LZ is limited to the US today
      But try this one instead👇
      ruclips.net/video/TwncejsWF8U/видео.htmlsi=oRTMckfO8vz5iyBU

  • @cloudpachehra1113
    @cloudpachehra1113 2 года назад +1

    🤟🤟

  • @mylearningaccount1
    @mylearningaccount1 2 года назад +1

    Please read less and talk "off the cuff" - It's more natural and easy to follow as though we're having a convo and not an audio readout of a Microsoft tech doc - Not knocking the video though, awesome content, thank you :)

    • @AzureAcademy
      @AzureAcademy  2 года назад +1

      Not sure what you mean…I DO talk off the cuff…can you explain?