<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft Intune on Anything About IT</title><link>https://www.verboon.info/tags/microsoft-intune/</link><description>Recent content in Microsoft Intune on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 28 Apr 2024 12:25:01 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/microsoft-intune/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Defender for Endpoint - Security Settings Management Internals 0x1</title><link>https://www.verboon.info/2024/04/microsoft-defender-for-endpoint-security-settings-management-internals-0x1/</link><pubDate>Sun, 28 Apr 2024 12:25:01 +0000</pubDate><guid>https://www.verboon.info/2024/04/microsoft-defender-for-endpoint-security-settings-management-internals-0x1/</guid><description>&lt;p&gt;In this post, we take a closer look at how &lt;strong&gt;Microsoft Defender for Endpoint Security Settings Management&lt;/strong&gt; works behind the scenes, especially for Windows Server scenarios.&lt;/p&gt;
&lt;h2 id="entra-id-device-registration"&gt;Entra ID Device Registration&lt;/h2&gt;
&lt;p&gt;Because Intune policy assignment is group-based, devices need an object in Entra ID. If a server already has an existing registration (for example Hybrid Join), that object is reused. If not, a synthetic device identity is created in Entra ID so the device can retrieve policy.&lt;/p&gt;</description></item></channel></rss>