First part is to integrate Microsoft Defender for Endpoint and Microsoft Intune if not already integrated. Integration has two parts in configuration. Snippet from Azure Active Directory, Devices View Note that not all of the AAD Joined devices are listed in Intune. Snippet from Microsoft Intune, Endpoint Security Node, All Devices ViewĪlso, on the Azure AD portal we can see the devices that are already joined to the tenant. When looking at the Endpoint Manager console for all devices, we would see only the ones that are managed are listed: Snippet from Microsoft Defender for Endpoint, Endpoints Node, Configuration Management View As you can see from the following snippet, no devices security settings are enforced by MDE in the initial status. Snippet from Microsoft Defender for Endpoint, Device Inventory ViewĬonfiguration management view also shows the same information focused on Security Enforcement feature in graph view. As you can see from the device inventory view in MDE two of them are managed directly by Intune (MEM), one of them is managed by Configuration Manager agent and a two listed as “Unknown” in managed by column. ![]() I have started configuration by onboarding several devices to MDE tenant. However, it is always a good idea to check for updated capability documentation to check for future capability improvements while making a decision. Once communication is started with Intune, status is reported, and policy information is pushed down and applied to the endpoint.įrom capabilities perspective, Intune – MDE integration provides fundamental security policy management such as antivirus configuration, antivirus exclusions, firewall configuration, firewall configuration exclusions and EDR configuration. Also, an Azure AD trust is required to communicate with AAD & Intune. However it is always a good idea to check the official documentation for an updated list of supported platforms.Īrchitecture of Microsoft Defender for Endpoint Integration with Microsoft Endpoint ManagerĬonceptually, devices need to be enrolled to Microsoft Defender for Endpoint service to be able to have policies applied. So let’s have a look at the configuration requirements and components of the solution first and start configuring on our test tenant and validate the configuration afterwards:įirst, supported platforms while this document was written were Windows Server operating systems starting from Windows Server 2012 R2 up to Windows Server 2022 and Windows 1x clients. Unified Endpoint Security Management Experience Architecture Also, Intune and Configuration Manager integration provided similar management capabilities for on-prem (ConfigMgr) managed devices.įinally, security configuration enforcement integration between MDE and Intune helps security teams to use the same admin interface – Intune console – to deploy Security policies to the devices that are enrolled to MDE only. For Intune managed devices, either cloud-only or co-management scenarios provided the endpoint security management capabilities. About Us Hyper-converged infrastructure experts for the Microsoft cloud platformįrom the endpoint security management architecture perspective, this scenario fulfills the gap of managing endpoint security features on unmanaged devices.Microsoft Cloud Glossary Terms used with Microsoft cloud infrastructure.Microsoft Cloud Library Collection of articles from industry experts.Articles From Argon Systems Original content of technical articles.Learning Center Free resources from Argon Systems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |