AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Microsoft intune windows defender11/29/2023 Microsoft Edge, File Explorer and Internet Explorer in these OSes: I grant you a nonexclusive, royalty-free right to use & modify my sample code & to reproduce & distribute the object code form of the sample code, provided that you agree: (i) to not use my name, my companies name, logo, or trademarks to market your software product in which the sample code is embedded (ii) to include a valid copyright notice on your software product in which the sample code is embedded and (iii) to indemnify, hold harmless, and defend me, Microsoft & our suppliers from & against any claims or lawsuits, including attorneys’ fees, that arise or result from the use or distribution of the sample code. They are provided ‘as is’ without warranty of any kind, expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. If I post any code, scripts or demos, they are provided for the purpose of illustration & are not intended to be used in a production environment. All posts are provided “AS IS” with no warranties & confers no rights. Let us know if you have any additional questions by replying to this post or reaching out to on Twitter.Ġ5/25/23: updated post to include clarity on the behavior between the Intune, Azure AD and Defender for Endpoint portals.Ġ8/11/23: updated post to clarify these updates pertain to Microsoft Defender for Endpoint (MDE) attached devices.Disclaimer: The views expressed in my posts on this site are mine & mine alone & don’t necessarily reflect the views of Microsoft. For example, if you have rules that use the “equals” or “not equals” operator, then you must explicitly update the rule to reference “Windows Server.” If you have rules that use the “contains” or “like” operator, then the rule won’t be impacted. Look to update the dynamic group rules to include Windows Servers specifically. If you’re using Azure AD dynamic device groups with specified rules that reference “Windows,” this will now exclude Windows Servers. If you have any custom scripts that refer specifically to the Windows platform, they will not include the new “Windows Server” value for the deviceType and will need to be updated. In Intune, the OS platform will show up as ‘Windows’ in the All devices list and the hardware details found on the device object page will show up as blank to represent Windows Servers. If you have Windows Server devices configured in your tenant, expect the OS platform to update to “Windows Server” in your reporting views for Azure AD and MDE device lists. What should customers do to prepare for the change? Windows Server 2016 with Microsoft Defender for Down-Level Devices.
0 Comments
Read More
Leave a Reply. |