S02E25 - Scope Tags, Scope Groups & Roles - Securing Intune w/ Role Based Access Control - (I.T)

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

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

  • @PriyaSharma-bb8qt
    @PriyaSharma-bb8qt Год назад +1

    Duse explained the scope tags and explained why the scope tags section in the "custom role" part is confusing and yet left the audience confused. Bravo!!

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

    U are doing great work, present everything clearly but with a sense of humor. Thanks

  • @guilhermegaspar2688
    @guilhermegaspar2688 2 года назад

    Great video!
    Amazing Content

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

    Is there anyway to dynamically assign scope tags to devices? I feel like I'm missing something.

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

      May groups with dynamic membership rules. Then assign scope tags to all group members.

    • @joshp614
      @joshp614 2 года назад

      @@IntuneTraining how do you suggest using dynamic groups in terms of identifying devices? I think I figured one way via our naming scheme and using a dynamic group that way. Was very odd I couldn't find much info on this.

  • @garethrobson799
    @garethrobson799 2 года назад

    Thank you for the many videos, Do you have to have an AAD role to allow access to intune and what is the most restrictive AAD role you can set allowing this access?

  • @gn1us
    @gn1us 3 года назад

    Great video! This has been confusing me so much

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

    Is it possible that you can create a video showing how a Windows 10 AAD registered device is converted to a hybrid AAD join device?
    Thank you for the many great videos from you! =)

  • @AmjadShurbaji
    @AmjadShurbaji 3 года назад

    Love your work guys! Keep it up!
    One thing I ran into is that the permission to read device's Bitlocker key is an AAD permissions and not Intune (microsoft.directory/bitlockerKeys/key/read) which makes it impossible to give the regional IT person access to read Bitlocker keys of their scoped devices without giving them Security Reader/Device Administrator/Helpdesk Administrator in AAD which is not subject to Intune scoping. Any ideas?

  • @Sladeofdark
    @Sladeofdark 3 года назад +1

    This.
    Because i have given everyone in my environment that need to enroll devices "Intune Administator" lol. please make it make sense !

  • @gabrielluizbh
    @gabrielluizbh 6 месяцев назад

    This seems very confusing. Watching the video many times to understand.
    It's worth writing a detailed article about this. I can't find this content anywhere.

  • @johnduncan5117
    @johnduncan5117 3 года назад

    The really confusing thing must be when you have compliance/config defaults and then someone with the right to create compliance/config for a specific scope comes in and adds their stuff no ? Then you end up with confusion and conflict. I say this because I'm managing Intune for my company and we have to give some rights to the IT for one of our divisions - but only on devices of theirs, not other divisions.

  • @mattiasmelkersen5643
    @mattiasmelkersen5643 3 года назад

    AAD Adam. AAD not AD :D you guys are funny and please keep talk with your mouse, it is funny.