<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Windows on Ru Campbell MVP</title>
    <link>https://campbell.scot/categories/windows/</link>
    <description>Recent content in Windows on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 28 Nov 2025 13:42:07 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/categories/windows/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Microsoft 365: The Essential 10 Security Considerations</title>
      <link>https://campbell.scot/microsoft-365-the-essential-10-security-considerations/</link>
      <pubDate>Fri, 28 Nov 2025 13:42:07 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-365-the-essential-10-security-considerations/</guid>
      <description>&lt;p&gt;When we talk about Microsoft 365 security, we are talking about two things:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Securing Microsoft 365 &lt;em&gt;the platform&lt;/em&gt;, such as Exchange Online, SharePoint Online, Microsoft 365 Copilot; ensuring they are hardened and monitored in proportion to risk appetite.&lt;/li&gt;
&lt;li&gt;Using Microsoft 365 &lt;em&gt;security tooling&lt;/em&gt;, such as Defender, Purview, Entra, and Intune; ensuring they are deployed, well configured, and you&amp;rsquo;re not paying for capabilities gathering dust.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The latter can be used to achieve the former, as well as other (non-Microsoft 365) platforms. For example, using Defender for Endpoint on a Linux server in AWS, or using Entra for single sign on to Salesforce.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Updated March 2022: Ultimate Comparison of Defender for Endpoint Features by Operating System</title>
      <link>https://campbell.scot/march-22-defender-for-endpoint-feature-comparison/</link>
      <pubDate>Tue, 29 Mar 2022 07:27:18 +0000</pubDate>
      <guid>https://campbell.scot/march-22-defender-for-endpoint-feature-comparison/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s been about 5 months since I last updated my comparison of Defender for Endpoint features by OS.  This is a &amp;ldquo;matrix&amp;rdquo; of the &lt;em&gt;tons&lt;/em&gt; of features, services, and important components that make up Microsoft Defender for Endpoint.&lt;/p&gt;
&lt;p&gt;Three months later, it&amp;rsquo;s overdue an update.  So here it is :)  I&amp;rsquo;ve also decided to rename it to The Ultimate Comparison of MDE Features by OS&amp;hellip; because renaming&amp;rsquo;s what we do, right?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Updated October 2021: Availability of Defender for Endpoint Features by Operating System</title>
      <link>https://campbell.scot/october-2021-comparison-of-defender-for-endpoint-features/</link>
      <pubDate>Tue, 19 Oct 2021 20:36:54 +0000</pubDate>
      <guid>https://campbell.scot/october-2021-comparison-of-defender-for-endpoint-features/</guid>
      <description>&lt;p&gt;In July, I released v1 of The Big Comparison of Defender for Endpoint Features by Operating System (or, what I think is much catchier, TBCMDEFOS).  This was a &amp;ldquo;matrix&amp;rdquo; of the &lt;em&gt;tons&lt;/em&gt; of features, services, and important components that make up Microsoft Defender for Endpoint.&lt;/p&gt;
&lt;p&gt;Three months later, it&amp;rsquo;s overdue an update.  So here it is :)&lt;/p&gt;
&lt;p&gt;The headline news is that, in preview anyway, there&amp;rsquo;s a bunch of additions to Windows Server 2012 R2 and 2016 thanks to a new agent-based deployment (&amp;ldquo;unified solution&amp;rdquo;) that replaces the need for the Microsoft Monitoring Agent and System Centre Endpoint Protection.  You now get almost feature parity with Windows Server 2019&amp;rsquo;s security features: ASR rules, next-generation protection, block at first sight, etc.  For a guide on how to get up and running with it, &lt;a href=&#34;https://petri.com/how-to-install-defender-for-endpoint-server-2012-r2-2016&#34;&gt;check out my writeup on Petri&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Big Comparison of Defender for Endpoint Features by Operating System</title>
      <link>https://campbell.scot/the-big-comparison-of-defender-for-endpoint-features-by-operating-system/</link>
      <pubDate>Sun, 11 Jul 2021 09:59:10 +0000</pubDate>
      <guid>https://campbell.scot/the-big-comparison-of-defender-for-endpoint-features-by-operating-system/</guid>
      <description>&lt;p&gt;Microsoft Defender for Endpoint (MDE) is a massive platform.  It&amp;rsquo;s not a single product, and it&amp;rsquo;s more than just a service.  It&amp;rsquo;s a platform of &lt;em&gt;tons&lt;/em&gt; of security features, portals, services, and controls.  The more you dig in, the more elements of general Microsoft security have been included in the MDE &amp;ldquo;branding&amp;rdquo;.  It&amp;rsquo;s not only endpoint detection and response (EDR), but also Windows 10 security settings.  It&amp;rsquo;s not just the security software on the device, it&amp;rsquo;s also ongoing threat and vulnerability management.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Troubleshooting Hybrid Azure AD Intune Automatic Enrollment</title>
      <link>https://campbell.scot/troubleshooting-hybrid-azure-ad-intune-automatic-enrollment/</link>
      <pubDate>Mon, 19 Apr 2021 20:02:44 +0000</pubDate>
      <guid>https://campbell.scot/troubleshooting-hybrid-azure-ad-intune-automatic-enrollment/</guid>
      <description>&lt;p&gt;As I have blogged about &lt;a href=&#34;https://campbell.scot/hybrid-azure-ad-join-intune-enrollment-prerequisites-checklist-and-process-flow/&#34;&gt;a&lt;/a&gt;&lt;a href=&#34;https://petri.com/how-to-automatically-hybrid-azure-ad-join-and-intune-enroll-pcs&#34;&gt;lot&lt;/a&gt;, there are a bunch of hoops to be jumped through and prerequisites to be met for a successful hybrid Azure AD join and automatic, GPO-invoked Intune enrollment. But sometimes, you have to go back to the basics when you&amp;rsquo;re banging your head off the table, and laugh off the embarrassment of not checking the fundamentals.&lt;/p&gt;
&lt;p&gt;I was recently setting up hybrid Azure AD join and Intune enrollment, as I&amp;rsquo;ve done hundreds of times before, but this time I was hitting a strange problem.  Hybrid Azure AD join went fine, but for the Intune MDM enrollment, I was getting nowhere.  Devices showed in the Azure AD admin centre, but never showed an MDM, and therefore never showed in Endpoint Manager.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Update BitLocker Unique Identifiers with Intune</title>
      <link>https://campbell.scot/update-bitlocker-unique-identifiers-with-intune/</link>
      <pubDate>Mon, 22 Mar 2021 18:01:18 +0000</pubDate>
      <guid>https://campbell.scot/update-bitlocker-unique-identifiers-with-intune/</guid>
      <description>&lt;p&gt;BitLocker unique identifiers are values used to identify the ownership of an encrypted volume.  The device that performs the encryption holds the unique identifier and as encryption begins, it also records this against the metadata of that encrypted volume.&lt;/p&gt;
&lt;p&gt;The identifiers are typically used in tandem with the BitLocker removable data-drive setting &lt;strong&gt;write access to devices configured in another organisation&lt;/strong&gt; which, if set to &lt;strong&gt;block&lt;/strong&gt;, will prevent write operations on devices where the unique identifier of the removable drive doesn&amp;rsquo;t match a list of unique identifiers managed on the device.  The idea here is you want to enforce BitLocker on removable drives to improve data loss (encrypted drives, if found, are unreadable without the means to decrypt them), &lt;em&gt;but&lt;/em&gt; you only want them to be encrypted within your organisation: someone can&amp;rsquo;t encrypt their device elsewhere and then copy data to it.  You may want to do this because it means you, as an administrator, would not be able to decrypt it if required.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender for Endpoint - Offline Onboarding for Windows 10 via a Proxy</title>
      <link>https://campbell.scot/microsoft-defender-for-endpoint-offline-onboarding-for-windows-10-via-proxy/</link>
      <pubDate>Thu, 18 Feb 2021 07:30:40 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-for-endpoint-offline-onboarding-for-windows-10-via-proxy/</guid>
      <description>&lt;p&gt;Getting your devices into Defender for Endpoint is referred to as &lt;strong&gt;onboarding&lt;/strong&gt; and can be done in lots of different ways, depending on the scenario.  The tools you use for Windows Server 2008 R2, for example, are different from the tools you use for Windows Server 2019, which are different from the tools you use for Windows 10, and so on.&lt;/p&gt;
&lt;p&gt;The common denominator behind most onboarding methods is internet connectivity.  Your device connects directly to the cloud service and provides all that telemetry goodness via a direct line of sight.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Block LSASS.exe using Attack Surface Reduction</title>
      <link>https://campbell.scot/block-lsass-exe-using-attack-surface-reduction/</link>
      <pubDate>Sat, 13 Feb 2021 21:10:23 +0000</pubDate>
      <guid>https://campbell.scot/block-lsass-exe-using-attack-surface-reduction/</guid>
      <description></description>
    </item>
    <item>
      <title>Turn Existing Azure AD Devices into Windows Autopilot Devices</title>
      <link>https://campbell.scot/turn-existing-azure-ad-devices-into-autopilot-devices/</link>
      <pubDate>Sat, 06 Feb 2021 09:19:13 +0000</pubDate>
      <guid>https://campbell.scot/turn-existing-azure-ad-devices-into-autopilot-devices/</guid>
      <description>&lt;p&gt;To provision Windows 10 PCs using Autopilot and Intune, they must first be registered as &lt;strong&gt;Windows Autopilot devices&lt;/strong&gt; in the &lt;strong&gt;Device Directory Service&lt;/strong&gt;, which is really the cloud Autopilot service.  When a device is registered to the Autopilot service, its &lt;strong&gt;hardware hash&lt;/strong&gt; is used to generate a &lt;strong&gt;Zero Touch Device ID&lt;/strong&gt;(ZTDID) - a globally unique identifier for that device based on hardware information such as (but not only) MAC address, disk serial number, and system serial number.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Understanding Application Guard for Office, Now Generally Available</title>
      <link>https://campbell.scot/understanding-application-guard-for-office-now-generally-available/</link>
      <pubDate>Sat, 30 Jan 2021 22:13:50 +0000</pubDate>
      <guid>https://campbell.scot/understanding-application-guard-for-office-now-generally-available/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Application Guard&lt;/strong&gt; first appeared in Windows 10 1709 (&amp;ldquo;Fall Creators Update&amp;rdquo;) to isolate Edge browser activity within a Hyper V container.  Microsoft now extends that same idea to Word, Excel, and PowerPoint in Office 365 ProPlus Microsoft 365 Apps for Enterprise on Windows 10&amp;hellip;&lt;/p&gt;
&lt;p&gt;&amp;hellip; if you have Microsoft 365 E5 or E5 Security.  You knew that was coming!&lt;/p&gt;
&lt;p&gt;With &lt;strong&gt;Application Guard for Office&lt;/strong&gt;, your files can open in a sandbox without access local or network storage.  This provides an additional layer of protection against threats such as ransomware, for which Office apps are infamous as an attack surface.  There&amp;rsquo;s a significant catch: a standard configuration of Application Guard &lt;em&gt;will&lt;/em&gt; allow users to bypass it if they say they trust the file, therefore executing it in the normal way; resource access included.  You can change this default behaviour though, so keep reading.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Store BitLocker Recovery Keys in Azure AD for Devices Already Encrypted</title>
      <link>https://campbell.scot/store-bitlocker-recovery-keys-in-azure-ad-for-devices-already-encrypted/</link>
      <pubDate>Fri, 15 Jan 2021 18:18:36 +0000</pubDate>
      <guid>https://campbell.scot/store-bitlocker-recovery-keys-in-azure-ad-for-devices-already-encrypted/</guid>
      <description>&lt;p&gt;As you move from on-premises or third-party infrastructure to Microsoft 365 and Azure AD, you will want to keep those BitLocker recovery keys safe.  You can store those keys either in on-premises Active Directory or in the cloud with Azure AD.&lt;/p&gt;
&lt;p&gt;The behavior of the BitLocker / Azure AD relationship is that the recovery keys will only be stored against the device object in Azure AD if the encryption happens when the device is already Azure AD or Hybrid Azure AD Joined.  You can then retrieve the recovery keys from the Azure AD portal or Microsoft Endpoint Manager (which really just takes you back to Azure AD&amp;rsquo;s properties for the device).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
