Restrict admin access to specific privileged workstations - Heres How!

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

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

  • @petecullen
    @petecullen Месяц назад +3

    Once again Dean you've published a video on something I'm currently doing for a customer, so it's extremely welcome as ever 🤩

  • @MrMarcLaflamme
    @MrMarcLaflamme Месяц назад +1

    6:43 - arrrggg this is the type of thinking that still gets me with CA. My brain doesn't work that way normally and that's why a bunch of our CA policies are probably not doing what I think they're doing... For your example though, how would you do it like "If it's not a PAW, block, but if it IS a PAW then let them in but require MFA"?

  • @thepete1338
    @thepete1338 Месяц назад +2

    Great topic! Reminds me of learning more about Graph 🙂

  • @InsideEntra
    @InsideEntra Месяц назад

    Will this prevent login to hybrid join devices ?

  • @pa1089
    @pa1089 23 дня назад

    Hello Dean. Thank you for the informative video. I was a impression we need to sync this via AD Connect? Is AD connect only applicable for hybrid scenarios? Thank
    you

    • @DeanEllerbyMVP
      @DeanEllerbyMVP  11 дней назад

      AD Connect is required for Hybrid scenarios, yes - it syncrhonises users, groups, objects, and devices to Entra / AAD.
      Most places sync Users so they're Hybrid.
      It became common to sync Devices, too.
      Now we're trying to encourage cloud-native (not hybrid sync'd) devices, but normal users can be Hybrid still.
      Entra Privileged Users (Global Admins, Intune Admins, etc) should always be cloud-native, though.