Block Deletes Using the New DenyAction Azure Policy Effect

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

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

  • @NTFAQGuy
    @NTFAQGuy  Год назад +4

    Hey everyone, welcome to this new video looking at the new DenyAction effect we can use to stop people deleting resources even if they are owner! Please make sure to read the description for the chapters and key information about this video and others.
    ⚠ P L E A S E N O T E ⚠
    👂 I have manually updated the captions to be as accurate as possible. Enable the subtitles and from there you can translate to your native language via the auto-translate feature in settings! ruclips.net/video/v5b53-PgEmI/видео.html for a demo of using this feature.
    🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc.
    🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there!
    🕰 I don't discuss future content nor take requests for future content so please don't ask 😇
    Thanks for watching!
    🤙

  • @yulaw3289
    @yulaw3289 3 месяца назад

    enjoying this video for today learning, thanks a lot!

  • @steveng.42
    @steveng.42 Год назад +1

    Fantastic, thank you sir! Your timing is impeccable as always, I was literally just starting to dig into this the past few days! Definitely looks like a better alternative to locks and then some once it goes beyond just Delete.

    • @steveng.42
      @steveng.42 Год назад

      Something that just popped in my head while watching this. Today most resources a "rename" has to be a delete and redeploy. So if relying on the naming convention on a resource for the policy, we'll all need to sort out a process for the times you do indeed need to delete something of course.

  • @rn9085
    @rn9085 Год назад

    Thanks John for making aware of this feature. We urgently need this in our organisation.
    Using blueprints would have been an option, but as they are in preview since always, we wouldn't use it...

  • @TommyDucks
    @TommyDucks Год назад +3

    Seems more sophisticated solution to enterprise protection than busting devops engineers to Contributor for 'reasons'.

  • @MohamedRoushdy
    @MohamedRoushdy Год назад

    Thanks..

  • @UmerAzeem
    @UmerAzeem Год назад

    great