MDE Device Tagging through Dynamic Asset rule management using Microsoft Defender XDR

-
 

My last couple of blog posts have been about MDE device tagging where I covered bulk tagging for macOS and iOS\iPadOS devices using Intune. In this blog post, I will be covering another method for bulk tagging which can work independently of any MDM solution.

Asset rule management in Microsoft Defender

Asset rule management in Microsoft Defender has been around for some time for assigning device tags based on certain criteria. This is done through asset rules that can be based on device name, domain, OS platform, internet facing status, onboarding status and manual device tags.

Here is how one can go about creating asset rules:

2. In the navigation pane, select Settings > Microsoft Defender XDR > Asset Rule Management.
3. Select Create a new rule.
4. Enter a Rule name and Description.
5. Select Next to choose the conditions you want to assign. I am pulling in al end user OS platforms.


6. Select Next and choose or create the tag to apply to this rule. I am creating a tag under the name MDMLabDevices

7. Select Next to review and finish creating the rule and then select Submit.

You should see the dynamic tag (in this case MDMLabDevices) assigned in the Device Inventory view. Note: It can take up to 1 hr for changes to reflect in the portal.


Unlike device tags configured using Intune that show up as RegistryDeviceTag in Advanced hunting, device tags configure thought asset rule management will show up under DeviceDynamicTags.

Until next time..

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting pr
Read more