<?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>Posts on Ru Campbell MVP</title>
    <link>https://campbell.scot/post/</link>
    <description>Recent content in Posts on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 30 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/post/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Test: Syntax Highlighting and Table of Contents</title>
      <link>https://campbell.scot/post/test-syntax-and-toc/</link>
      <pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://campbell.scot/post/test-syntax-and-toc/</guid>
      <description>Verification post — confirms Chroma syntax highlighting, Hugo native ToC, and OG meta tags are all working correctly.</description>
    </item>
    <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>Thoughts on Copilot for Security’s Early Days</title>
      <link>https://campbell.scot/thoughts-on-copilot-for-securitys-early-days/</link>
      <pubDate>Mon, 13 May 2024 07:22:42 +0000</pubDate>
      <guid>https://campbell.scot/thoughts-on-copilot-for-securitys-early-days/</guid>
      <description>&lt;p&gt;April 1, 2024, seen the release of Microsoft Copilot for Security to general availability (GA). It is a generative AI solution integrating with Defender XDR, Entra, Purview, and Intune. Just over a month later, it&amp;rsquo;s time to write down some thoughts.&lt;/p&gt;
&lt;p&gt;In cybersecurity, we face the challenge of scarce resources — time, finances, attention, will — to identify, protect, and respond to threats and vulnerabilities.&lt;/p&gt;
&lt;p&gt;There&amp;rsquo;s an old joke. One economist asks another, &amp;ldquo;How&amp;rsquo;s your wife?&amp;rdquo;. The other economist replies, &amp;ldquo;Compared to what?&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[Updated Feb 2024] Ultimate Comparison of Defender for Endpoint Features by OS</title>
      <link>https://campbell.scot/feb-2024-ultimate-comparison-of-defender-for-endpoint-features-by-os/</link>
      <pubDate>Fri, 16 Feb 2024 17:13:38 +0000</pubDate>
      <guid>https://campbell.scot/feb-2024-ultimate-comparison-of-defender-for-endpoint-features-by-os/</guid>
      <description>&lt;p&gt;Finally, it&amp;rsquo;s time for a refresh.  It&amp;rsquo;s been a while!  Due to personal circumstances, I haven&amp;rsquo;t been able to keep the Ultimate Comparison of MDE by OS updated.  I&amp;rsquo;ve had time to dive into the changes since v5 and it&amp;rsquo;s really been amazing to see MDE grow in scope.&lt;/p&gt;
&lt;h2 id=&#34;what-is-mde-and-why-do-we-need-an-ultimate-comparison&#34;&gt;What is MDE and why do we need an &amp;lsquo;ultimate comparison&amp;rsquo;?&lt;/h2&gt;
&lt;p&gt;Microsoft Defender for Endpoint (MDE) is a massive stack of endpoint protection and endpoint detection and response (EDR) capabilities.  It integrates with the broader Microsoft Defender XDR and is available for almost any OS you&amp;rsquo;ll find in an enterprise.  This cross-platform nature of MDE makes it difficult to understand and track what features and capabilities are available on each OS.  It&amp;rsquo;s not always intuitive, and you may be in for some surprises.  Hence by I began the &lt;strong&gt;Ultimate Comparison of Defender for Endpoint Features by OS&lt;/strong&gt; up to date to keep you aware of what you&amp;rsquo;re getting and what you need to go start implementing if you haven&amp;rsquo;t already.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender for Cloud Apps - Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/microsoft-defender-for-cloud-apps-common-microsoft-security-mistakes-series/</link>
      <pubDate>Fri, 09 Feb 2024 17:30:41 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-for-cloud-apps-common-microsoft-security-mistakes-series/</guid>
      <description>&lt;p&gt;Defender for Cloud Apps (MDA) is such a hidden gem. When talking with Microsoft 365 E5 customers, it&amp;rsquo;s amazing how few of them really grab MDA and squeeze all they can out of it. It&amp;rsquo;s often classified as a cloud access security broker (CASB) but that&amp;rsquo;s an oversimplication: the product can do so much more such as SaaS security posture management (SSPM) and, most topical in light of &lt;a href=&#34;https://www.microsoft.com/en-us/security/blog/2024/01/25/midnight-blizzard-guidance-for-responders-on-nation-state-attack/&#34;&gt;recent events&lt;/a&gt;, OAuth app governance.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Entra ID Protection - Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/entra-id-protection-common-microsoft-365-security-mistakes-series/</link>
      <pubDate>Wed, 07 Feb 2024 17:54:59 +0000</pubDate>
      <guid>https://campbell.scot/entra-id-protection-common-microsoft-365-security-mistakes-series/</guid>
      <description>&lt;p&gt;Signals from across Microsoft&amp;rsquo;s services and ecosystems inform Entra ID Protection to detect risk. The risk detections can alert administrators or, better still, combine with other Entra and Defender XDR capabilities to perform remediation and prevention. The most obvious example of this may be preventing a risky sign in. Contrary to popular understanding, not all of Entra ID Protection&amp;rsquo;s detections are limited to the Entra ID P2 license: the nonpremium risks listed &lt;a href=&#34;https://learn.microsoft.com/en-us/entra/id-protection/concept-identity-protection-risks#sign-in-risk-detections&#34;&gt;here&lt;/a&gt; don&amp;rsquo;t require P2.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Entra Self Service Password Reset - Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/entra-self-service-password-reset-common-microsoft-security-mistakes-series/</link>
      <pubDate>Sat, 03 Feb 2024 11:32:34 +0000</pubDate>
      <guid>https://campbell.scot/entra-self-service-password-reset-common-microsoft-security-mistakes-series/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s a trope in IT circles: users forget their passwords. The greater your scale, the more time this can occupy with tickets, service desk calls, and so on. If you use Microsoft Entra ID (previously Azure Active Directory), &lt;strong&gt;self service password reset&lt;/strong&gt; (SSPR) is a capability that can help reduce this overhead. SSPR offers a user-driven admin-less approach, where users verify they are authorised to reset forgotten passwords then can do so.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender Vulnerability Management - Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/microsoft-defender-vulnerability-management-common-microsoft-365-security-mistakes-series/</link>
      <pubDate>Sat, 03 Feb 2024 10:57:52 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-vulnerability-management-common-microsoft-365-security-mistakes-series/</guid>
      <description>&lt;p&gt;Microsoft Defender Vulnerability Management (MDVM) is an often overlooked service that can be licensed standalone or is included in other Microsoft Defender licenses. In my experience, I&amp;rsquo;ve never seen it licensed standalone, but customers with Defender for Endpoint (MDE) P2, Defender for Servers  (MDS) P1, and Defender for Business (MDB) benefit from it&amp;rsquo;s &lt;em&gt;core capabilities&lt;/em&gt;.  In addition to the core capabilities, &lt;em&gt;add-on capabilities&lt;/em&gt; are available in the standalone license, Defender for Servers P2, or as an upgrade to the P1 licenses.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Exchange Online Protection &amp; Defender for Office 365 - Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/exchange-online-protection-defender-for-office-365-common-microsoft-365-security-mistakes-series/</link>
      <pubDate>Tue, 19 Dec 2023 08:26:45 +0000</pubDate>
      <guid>https://campbell.scot/exchange-online-protection-defender-for-office-365-common-microsoft-365-security-mistakes-series/</guid>
      <description>&lt;p&gt;Exchange Online Protection (EOP) and Microsoft Defender for Office 365 (MDO) are the email and collaboration security services native to Microsoft 365. EOP is included at all levels of licensing for Exchange Online, with MDO bringing additional security capabilities to license levels such as Business Premium, Microsoft 365 E3, and Microsoft 365 E5.&lt;/p&gt;
&lt;p&gt;In this blog, I&amp;rsquo;ll review five of the most common security mistakes I see in tenants regarding EOP and MDO. Realistically, this list could go to fifty mistakes, but I&amp;rsquo;ll focus on ones I think you can quickly convert into quick wins or just may have never crossed your mind.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Privileged Identity Management (PIM) – Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/pim-common-microsoft-365-security-mistakes-series/</link>
      <pubDate>Sun, 19 Nov 2023 14:01:41 +0000</pubDate>
      <guid>https://campbell.scot/pim-common-microsoft-365-security-mistakes-series/</guid>
      <description>&lt;p&gt;Entra ID&amp;rsquo;s P2 license (previously Azure AD Premium P2) unlocks the Privileged Identity Management (PIM). PIM is part of broader &lt;em&gt;identity governance&lt;/em&gt; features, and is most known for enabling just-in-time admin rights. For example, you are &lt;em&gt;eligible&lt;/em&gt; to become an administrator for a maximum of &lt;em&gt;X&lt;/em&gt; hours, at which point the permissions expire and you need to reactivate.&lt;/p&gt;
&lt;p&gt;This blog covers five of the common misconfigurations and misunderstandings I see with customers. Intuitive as PIM may appear, there are some gotchas you need to be aware of. It is a follow up from my previous &lt;a href=&#34;https://campbell.scot/conditional-access-common-microsoft-365-security-mistakes-series/&#34;&gt;Conditional Access – Common Microsoft 365 Security Mistakes Series&lt;/a&gt; article.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Conditional Access - Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/conditional-access-common-microsoft-365-security-mistakes-series/</link>
      <pubDate>Thu, 05 Oct 2023 21:11:27 +0000</pubDate>
      <guid>https://campbell.scot/conditional-access-common-microsoft-365-security-mistakes-series/</guid>
      <description>&lt;p&gt;Conditional Access (CA) is front and center of any attempt to secure Microsoft 365. If you&amp;rsquo;ve spent any time securing your tenant and Entra resources, you&amp;rsquo;ll know what Conditional Access is by now, so we&amp;rsquo;ll assume at least a level 200 understanding, skip the introduction, and instead dive into the most common mistakes I see when helping folks out with it.&lt;/p&gt;
&lt;p&gt;These aren&amp;rsquo;t listed in any particular order, and the devil&amp;rsquo;s in the details, so make sure you read the full post instead of just skimming the bullet points! There are also &lt;em&gt;way&lt;/em&gt; more than five mistakes you can make with Conditional Access, but let&amp;rsquo;s start with these.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Improves and Simplifies Defender for Endpoint Management Capabilities</title>
      <link>https://campbell.scot/microsoft-improves-and-simplifies-defender-for-endpoint-management-capabilities/</link>
      <pubDate>Mon, 10 Jul 2023 20:47:03 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-improves-and-simplifies-defender-for-endpoint-management-capabilities/</guid>
      <description>&lt;p&gt;In one of the biggest changes to Microsoft Defender for Endpoint (MDE) in its product history, you no longer need a separate management engine to configure endpoint settings.&lt;/p&gt;
&lt;p&gt;In this blog, we&amp;rsquo;ll look at what that change is, why it was necessary, initial impressions, and what you might want to do next.&lt;/p&gt;
&lt;h2 id=&#34;historic-management-architecture-needed-simplifying&#34;&gt;Historic management architecture needed simplifying&lt;/h2&gt;
&lt;p&gt;MDE (and it&amp;rsquo;s Windows client, Microsoft Defender Antivirus (MDAV)) always stood out from the crowd of endpoint protection platforms as being, well, a bit &lt;em&gt;weird&lt;/em&gt; in terms of management architecture. With most platforms, you get a central admin console which pushes out endpoint settings. Think scan schedules, quarantine rules, exclusions, CPU throttling, etc. MDE/MDAV, on the other hand, instead relied on an external management tool such as Intune (MDM), Configuration Manager, or Group Policy.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stop Making These Conditional Access Mistakes</title>
      <link>https://campbell.scot/stop-making-these-conditional-access-mistakes/</link>
      <pubDate>Tue, 16 May 2023 09:14:28 +0000</pubDate>
      <guid>https://campbell.scot/stop-making-these-conditional-access-mistakes/</guid>
      <description>&lt;p&gt;Conditional Access is the most important security feature you will configure in Azure AD. You need to get this right, or most other things don&amp;rsquo;t even matter.&lt;/p&gt;
&lt;p&gt;Compared to on-premises AD, which requires line of sight to a domain infrastructure often limited to physical or VPN access, Azure AD is wide open by default. Users can authenticate from anywhere, on any device.&lt;/p&gt;</description>
    </item>
    <item>
      <title>[Feb 2023] Ultimate Comparison of Defender for Endpoint Features by OS</title>
      <link>https://campbell.scot/mde-comparison-feb-2023/</link>
      <pubDate>Sun, 19 Feb 2023 15:46:12 +0000</pubDate>
      <guid>https://campbell.scot/mde-comparison-feb-2023/</guid>
      <description>&lt;p&gt;Microsoft Defender for Endpoint (MDE) is a massive stack of endpoint protection and endpoint detection and response (EDR) capabilities.  It integrates with Microsoft 365 Defender (the broader XDR platform) and is available for almost any OS you&amp;rsquo;ll find in an enterprise.  This cross-platform nature of MDE makes it difficult to understand and track what features and capabilities are available on each OS.  It&amp;rsquo;s not always intuitive, and you may be in for some surprises.  I try to keep this &lt;strong&gt;Ultimate Comparison of Defender for Endpoint Features by OS&lt;/strong&gt; up to date to keep you aware of what you&amp;rsquo;re getting and what you need to go start implementing if you haven&amp;rsquo;t already.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ultimate Comparison of Defender for Endpoint Features by OS [Updated August 2022]</title>
      <link>https://campbell.scot/mde-comparison-august-2022/</link>
      <pubDate>Fri, 26 Aug 2022 07:32:32 +0000</pubDate>
      <guid>https://campbell.scot/mde-comparison-august-2022/</guid>
      <description>&lt;p&gt;This is the updated &amp;ldquo;matrix&amp;rdquo; of OS supported for the almost 80 features, services, and important components that make up Microsoft Defender for Endpoint. This follows up on my March 2022 release of the comparison.&lt;/p&gt;
&lt;p&gt;What&amp;rsquo;s new?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Now available in Excel format, which was the biggest request :)&lt;/li&gt;
&lt;li&gt;Added the new Microsoft Defender Vulnerability Management capabilities (add-on license required)&lt;/li&gt;
&lt;li&gt;Added macOS tamper protection support&lt;/li&gt;
&lt;li&gt;Added macOS network and web protection&lt;/li&gt;
&lt;li&gt;Added iOS and Android&amp;rsquo;s mobile network protection&lt;/li&gt;
&lt;li&gt;Added Linux cloud-delivered protection support&lt;/li&gt;
&lt;li&gt;Added Windows troubleshooting mode&lt;/li&gt;
&lt;li&gt;Added macOS, iOS, and Android support for network indicators of compromise&lt;/li&gt;
&lt;li&gt;Updated host firewall reporting supported OSs&lt;/li&gt;
&lt;li&gt;Updated attack surface reduction (ASR) rule supported Windows and Windows Server versions&lt;/li&gt;
&lt;li&gt;Updated block at first sight (BAFS) supported OSs (thanks Polle Vanhoof + Thomas Verheyden)&lt;/li&gt;
&lt;li&gt;Updated Windows Server support for indicators of compromise (thanks Polle Vanhoof + Thomas Verheyden)&lt;/li&gt;
&lt;li&gt;Removed preview references for the unified agent for Windows Server 2012 R2 and 2016&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Obligatory disclaimers:&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>Exploring Microsoft 365&#39;s NOBELIUM Defence Capabilities</title>
      <link>https://campbell.scot/exploring-microsoft-365s-nobelium-defence-capabilities/</link>
      <pubDate>Fri, 24 Dec 2021 19:37:50 +0000</pubDate>
      <guid>https://campbell.scot/exploring-microsoft-365s-nobelium-defence-capabilities/</guid>
      <description>&lt;p&gt;I recently read through an &lt;a href=&#34;https://www.mandiant.com/resources/russian-targeting-gov-business&#34;&gt;excellent article by Mandiant&lt;/a&gt;, which recently split with FireEye, on their findings and analysis of the continued actions of suspected nation-state actor NOBELIUM.  This group appeared on most IT pro&amp;rsquo;s radar because of their SolarWinds&amp;rsquo; software supply chain.  You are probably familiar with it by now, but if not, the tl;dr is that SolarWinds&amp;rsquo; Orion IT software was &amp;ldquo;trojanised&amp;rdquo; via an attack on their software supply chain.  Orion is (probably now &amp;ldquo;was&amp;rdquo;) used by enterprise customers to monitor their servers, network, etc, so not only was SolarWinds compromised, so too potentially were its customers.&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>Tons of Microsoft Defender for Endpoint Improvements for Server 2012 R2 &amp; 2016</title>
      <link>https://campbell.scot/tons-of-microsoft-defender-for-endpoint-improvements-for-server-r/</link>
      <pubDate>Fri, 08 Oct 2021 11:36:48 +0000</pubDate>
      <guid>https://campbell.scot/tons-of-microsoft-defender-for-endpoint-improvements-for-server-r/</guid>
      <description>&lt;p&gt;New protection capabilities for Microsoft Defender for Endpoint (MDE) customers have landed in public preview, Oct 7 &amp;lsquo;21, for Windows Server 2012 R2 and Windows Server 2016.  With the public preview released today, Windows Server 2012 R2 and 2016 gain &amp;rsquo; &lt;a href=&#34;https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/defending-windows-server-2012-r2-and-2016/ba-p/2783292&#34;&gt;functional equivalence&lt;/a&gt;&amp;rsquo; to 2019, thanks to the use of a new agent that is being described as the &amp;lsquo;unified solution&amp;rsquo;.&lt;/p&gt;
&lt;h2 id=&#34;historically-a-significant-gap&#34;&gt;Historically, a significant gap&lt;/h2&gt;
&lt;p&gt;Previously, as I&amp;rsquo;ve detailed &lt;a href=&#34;https://petri.com/understanding-microsoft-defender-for-endpoint-and-how-it-protects-your-data&#34;&gt;here&lt;/a&gt; and &lt;a href=&#34;https://campbell.scot/the-big-comparison-of-defender-for-endpoint-features-by-operating-system/&#34;&gt;here&lt;/a&gt;, there was a large feature gap between Windows Server 2019 and these &amp;ldquo;down-level&amp;rdquo; OSs. The onboarding process was also different.  To get devices into MDE, you had to deploy the Microsoft Monitoring Agent (MMA).  This was required as the EDR sensor wasn&amp;rsquo;t built-in, unlike with Server 2019.  While Server 2016 shipped with Microsoft Defender Antivirus (MDAV) installed already, to get any kind of scanning and endpoint protection capability in Server 2012 R2, you had to install System Centre Endpoint Protection.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Hygiene, Azure Security Center, and Secure Score</title>
      <link>https://campbell.scot/security-hygiene-az-security-center-secure-score/</link>
      <pubDate>Sun, 01 Aug 2021 16:17:21 +0000</pubDate>
      <guid>https://campbell.scot/security-hygiene-az-security-center-secure-score/</guid>
      <description>&lt;h3 id=&#34;the-basics&#34;&gt;The basics&lt;/h3&gt;
&lt;p&gt;Let&amp;rsquo;s start this article with some basic cybersecurity terminology.  Security hygiene, or cyber hygiene, is a general term used to describe the ongoing practice of keeping your technology and IT estate in a healthy and protected state.  The metaphor with physical hygiene is valid because we know with our bodies that there&amp;rsquo;s no such thing as &amp;ldquo;set it and forget it&amp;rdquo;: if we don&amp;rsquo;t maintain regular hygiene practices and exercise, we atrophy.  It&amp;rsquo;s a continual effort comprised of daily discipline, habit, and ritual.&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>Reauthorise Windows Server DHCP with One Line of PowerShell</title>
      <link>https://campbell.scot/reauthorise-windows-server-dhcp/</link>
      <pubDate>Sat, 26 Jun 2021 19:23:38 +0000</pubDate>
      <guid>https://campbell.scot/reauthorise-windows-server-dhcp/</guid>
      <description>&lt;p&gt;This will be a brief blog, as I am certainly not a DHCP expert or day-to-day administrator.  I do, however, run a DHCP server on Windows Server 2019 constantly in my lab environment, but sometimes encounter a problem whereby the server is no longer authorised, and when I use the GUI to do so, I get the error &lt;strong&gt;the specified servers are already present in the directory service&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://campbell.scot/wp-content/uploads/2021/06/the-specified-servers-are-already-present-in-the-directory-service.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;The PowerShell I use to resolve this does the following:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying Office 365 with Intune as a Win32 App (and Why You&#39;d Want To)</title>
      <link>https://campbell.scot/deploying-office-365-with-intune-as-a-win32-app/</link>
      <pubDate>Tue, 15 Jun 2021 15:26:14 +0000</pubDate>
      <guid>https://campbell.scot/deploying-office-365-with-intune-as-a-win32-app/</guid>
      <description>&lt;p&gt;Office 365, or Microsoft 365 Apps for Enterprise, or whatever it&amp;rsquo;s called this month, can be deployed by Intune to Windows 10 devices using a built-in wizard.  The advantage of this is you don&amp;rsquo;t need to package anything: you fill out some nice drop-downs and options in a GUI, assign it like any other app, and Microsoft takes care of the rest.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://campbell.scot/wp-content/uploads/2021/06/Office-365-Intune-Deployment-Wizard.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;In the background, this is using the Office CSP to deploy the client, which makes it quite unique compared to the deployment of other apps, which are best done with Win32 packaging.  I wrote a general guide about that for &lt;a href=&#34;https://petri.com/how-to-package-and-deploy-windows-applications-with-intune&#34;&gt;Petri.com, available here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Three Cool Things To Do With Azure Information Protection</title>
      <link>https://campbell.scot/three-cool-things-to-do-with-azure-information-protection/</link>
      <pubDate>Sun, 13 Jun 2021 17:38:11 +0000</pubDate>
      <guid>https://campbell.scot/three-cool-things-to-do-with-azure-information-protection/</guid>
      <description>&lt;p&gt;In my last blog, I wrote about &lt;a href=&#34;https://campbell.scot/3-considerations-for-aip-deployments/&#34;&gt;three considerations for your Azure Information Protection deployments&lt;/a&gt; and commented on often overlooked potential downsides, or at least areas with which to be cautious. In hindsight, it all feels a bit negative.  I am, for the record, an advocate of Microsoft 365 customers using AIP (sensitivity labels) in basically any circumstance it&amp;rsquo;s appropriate to do so.  So in this blog, I&amp;rsquo;ll counter the earlier post with three often overlooked useful things you can do with it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Three Considerations for Azure Information Protection Deployments</title>
      <link>https://campbell.scot/3-considerations-for-aip-deployments/</link>
      <pubDate>Sat, 15 May 2021 08:25:46 +0000</pubDate>
      <guid>https://campbell.scot/3-considerations-for-aip-deployments/</guid>
      <description>&lt;p&gt;Azure Information Protection (AIP) - more accurately exposed to Microsoft 365 now as &lt;strong&gt;sensitivity labels&lt;/strong&gt;- is close to the top of my favourite wins for securing your data in a Microsoft ecosystem.  While designing a detailed labelling and classification system is far from quick, it &lt;em&gt;is&lt;/em&gt; quick to get up and running with baseline policies that protect your confidential company data from getting read outside the company.  Simply by applying a sensitivity label that limits access to confidential data to users in your domain, you&amp;rsquo;ve covered a massive chunk of data loss scenarios.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Automatically Hide IP Addresses When Recording Demos or Screen Sharing</title>
      <link>https://campbell.scot/automatically-hide-ip-addresses-when-recording-demos-or-screen-sharing/</link>
      <pubDate>Mon, 03 May 2021 19:47:24 +0000</pubDate>
      <guid>https://campbell.scot/automatically-hide-ip-addresses-when-recording-demos-or-screen-sharing/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/clarkio/azure-mask&#34;&gt;Azure Mask&lt;/a&gt; browser extension is a really great tool when either recording on-screen demos or sharing your screen.  Available for Edge/Chrome and Firefox, &lt;a href=&#34;https://twitter.com/_clarkio&#34;&gt;@_clarkio&lt;/a&gt;&amp;rsquo;s extension censors sensitive tenant information, so that your recording or viewers can&amp;rsquo;t see it.  For example, the tenant ID within Azure AD&amp;rsquo;s overview page is blurred out.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://campbell.scot/wp-content/uploads/2021/05/01-azure-ad-tenant-info.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re doing a demonstration of any kind of security software with logs and auditing information, chances are you&amp;rsquo;ll get IP addresses on-screen too.  If you&amp;rsquo;re running a lab environment at home or you&amp;rsquo;re showing off your own business&amp;rsquo;s production environment, you probably don&amp;rsquo;t what those seen by everyone, particularly if the session is going to be recorded.&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>Revoke Access to Office Files with Sensitivity Labels and Azure Information Protection</title>
      <link>https://campbell.scot/revoke-access-to-office-files-with-sensitivity-labels-and-azure-information-protection/</link>
      <pubDate>Thu, 08 Apr 2021 06:16:40 +0000</pubDate>
      <guid>https://campbell.scot/revoke-access-to-office-files-with-sensitivity-labels-and-azure-information-protection/</guid>
      <description>&lt;p&gt;Most of us have had that &amp;ldquo;oh &amp;lt; &lt;em&gt;blank&lt;/em&gt; &amp;gt;&amp;rdquo; moment where we have given someone access to someone only to immediately or later need to undo that access.  Azure Information Protection has historically been able to help us there.  AIP allowed us to create protected (encrypted) documents and also let us remove access.  However, in the move from &amp;lsquo;classic&amp;rsquo; AIP to the new &lt;strong&gt;unified labelling&lt;/strong&gt; with &lt;strong&gt;sensitivity labels&lt;/strong&gt;, the ability to revoke was lost in the transition.  Now it&amp;rsquo;s back in preview, but unlike the classic version, it&amp;rsquo;s managed on the client and not a web portal.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Conditional Access: Skip MFA for Company Devices on the Company Network</title>
      <link>https://campbell.scot/conditional-access-skip-mfa-for-company-devices-on-the-company-network/</link>
      <pubDate>Wed, 31 Mar 2021 07:13:29 +0000</pubDate>
      <guid>https://campbell.scot/conditional-access-skip-mfa-for-company-devices-on-the-company-network/</guid>
      <description>&lt;p&gt;A common Conditional Access policy is to add trusted locations as an exception to multi-factor authorisation requirements.  The logic goes, if you accessing resources such as Office 365 from a location such as the corporate office, that&amp;rsquo;s an element of verification in itself that your login should be trusted, so we should improve your user experience by removing MFA.  Personally, I support the use of MFA &lt;em&gt;regardless&lt;/em&gt; of where you are authenticating (at the very least, if you have an Azure AD admin role assigned).  However, doing something like this is a great option if you are introducing MFA from scratch: you will improve user buy in the less you change their standard experience.  Then, increase the scope gradually.&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>How Conditional Access Assignments and Access Controls Work</title>
      <link>https://campbell.scot/how-conditional-access-assignments-and-access-controls-work/</link>
      <pubDate>Sun, 21 Mar 2021 19:47:39 +0000</pubDate>
      <guid>https://campbell.scot/how-conditional-access-assignments-and-access-controls-work/</guid>
      <description>&lt;p&gt;When you authenticate with Azure AD, Conditional Access policies let you apply if-then rules for licensees of Azure AD Premium P1 or P2.&lt;/p&gt;
&lt;p&gt;The &lt;em&gt;conditions&lt;/em&gt; within Conditional Access (CA) are called &lt;strong&gt;assignments&lt;/strong&gt;, but you may also see them referred to as signals, session details, or criteria.  They make up the &lt;em&gt;if&lt;/em&gt; part of if-then, and the &lt;em&gt;then&lt;/em&gt; part is referred to as the &lt;strong&gt;access control&lt;/strong&gt; or enforcement.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;if&lt;/em&gt; the authentication attempt is for an administrative role (assignments / signals / session details / criteria)&lt;/li&gt;
&lt;li&gt;&lt;em&gt;then&lt;/em&gt; enforce multi-factor authentication (MFA) (access control / enforcements)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Assignments are broken down into&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender Antivirus – Schedule &amp; Install Updates via Network Shares</title>
      <link>https://campbell.scot/microsoft-defender-antivirus-schedule-install-updates-via-network-shares/</link>
      <pubDate>Sat, 13 Mar 2021 21:28:12 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-antivirus-schedule-install-updates-via-network-shares/</guid>
      <description>&lt;p&gt;Although not common, there are scenarios out where you will have LAN-only devices onboarded in Microsoft Defender for Endpoint (MDE), or at least using Microsoft Defender Antivirus (MDAV).  With no line of sight to the internet, you can use options such as WSUS, but in this blog, I&amp;rsquo;ll explore using a network share, as WSUS isn&amp;rsquo;t always an option.&lt;/p&gt;
&lt;h2 id=&#34;set-up-the-network-share-for-updates&#34;&gt;Set up the network share for updates&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Create a directory on your file server with subdirectories for the different CPU architectures you&amp;rsquo;ll be supporting.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://campbell.scot/wp-content/uploads/2021/02/01-create-update-folders-on-server.png&#34;&gt;2. On the server, we&amp;rsquo;ll be installing a script provided by Microsoft.  In PowerShell with elevated rights:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender Network Protection - Not Enabling via Intune - Troubleshooting &amp; Fix</title>
      <link>https://campbell.scot/microsoft-defender-network-protection-not-enabling-via-intune-troubleshooting-fix/</link>
      <pubDate>Sun, 07 Mar 2021 13:27:29 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-network-protection-not-enabling-via-intune-troubleshooting-fix/</guid>
      <description>&lt;p&gt;When configuring Defender for Endpoint (MDE) customer recently, I ran into a problem when trying to enable network protection.  Network protection is a feature of MDE and Microsoft Defender Antivirus (MDAV) that takes the filtering capabilities of SmartScreen and applies them to all network traffic.  It is a prerequisite for things such as MDE&amp;rsquo;s web content filtering and URL/domain indicators of compromise.&lt;/p&gt;
&lt;p&gt;This blog details the specific problem I had enabling it with Intune (Microsoft Endpoint Manager), and general troubleshooting steps to follow that will help for that problem and hopefully others you may experience.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Information Protection Sensitivity Labels - Custom User Permissions and Do Not Forward</title>
      <link>https://campbell.scot/microsoft-information-protection-sensitivity-labels-custom-user-permissions-and-do-not-forward/</link>
      <pubDate>Thu, 25 Feb 2021 15:02:30 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-information-protection-sensitivity-labels-custom-user-permissions-and-do-not-forward/</guid>
      <description>&lt;p&gt;With Microsoft Information Protection, you can apply &lt;strong&gt;sensitivity labels&lt;/strong&gt; to files, emails, and containers such as SharePoint Libraries.  These labels apply &lt;strong&gt;protection&lt;/strong&gt; which, in the context of files and emails, really means &lt;strong&gt;encryption&lt;/strong&gt; using AES-128 or 256 (key size depends on file type).  The great thing about Information Protection is that you control an access control list of who is allowed to access the content and it&amp;rsquo;s managed as a cloud service by Microsoft.  The document or message, when opened, checks who is authenticated (who is signed to Outlook or the Office 365 app, for example) and only allows access if they have permission.&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>Use Intune to Manage Microsoft Defender for Endpoint Tags and Device Groups</title>
      <link>https://campbell.scot/use-intune-to-manage-microsoft-defender-for-endpoint-tags-and-device-groups/</link>
      <pubDate>Thu, 11 Feb 2021 21:24:59 +0000</pubDate>
      <guid>https://campbell.scot/use-intune-to-manage-microsoft-defender-for-endpoint-tags-and-device-groups/</guid>
      <description>&lt;p&gt;In &lt;strong&gt;Microsoft Defender for Endpoint&lt;/strong&gt; (MDE), &lt;strong&gt;tags&lt;/strong&gt; can be attached to a device for reporting, filtering, and as a dynamic attribute for membership of a &lt;strong&gt;device&lt;/strong&gt; &lt;strong&gt;group&lt;/strong&gt;.  Device groups (previously machine groups), are used to assign devices different rules and administrative ownership.  A device can only belong to one group and controls settings such as auto-remediation level and which Role-Based Access Control (RBAC) roles have administrative permissions over it.&lt;/p&gt;
&lt;p&gt;While you can assign tags, and therefore determine group membership, manually from the Security Center, this doesn&amp;rsquo;t exactly scale well.&lt;/p&gt;</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>Understanding Modern vs. Legacy Authentication in Microsoft 365</title>
      <link>https://campbell.scot/understanding-modern-vs-legacy-authentication-in-microsoft-365/</link>
      <pubDate>Sun, 24 Jan 2021 13:46:35 +0000</pubDate>
      <guid>https://campbell.scot/understanding-modern-vs-legacy-authentication-in-microsoft-365/</guid>
      <description>&lt;p&gt;Since October 2019, Microsoft has enabled Security Defaults by default in new Microsoft 365 tenants.  Security Defaults are a group of best-practice security settings, and one of note is the disablement of all &lt;strong&gt;legacy authentication&lt;/strong&gt;, which itself has been off in Exchange Online and SharePoint Online, by default, since August 2017.&lt;/p&gt;
&lt;p&gt;The term legacy authentication doesn&amp;rsquo;t refer to one particular protocol, but rather any that do not support Multi-Factor Authentication (MFA).  Protocols that support MFA are described as &lt;strong&gt;modern authentication&lt;/strong&gt;.  In the context of Microsoft 365 and Azure Active Directory, which handles Microsoft 365&amp;rsquo;s authentication, these are protocols such as ADAL and OAuth.&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>
    <item>
      <title>The 10 Technical IT Books of Most Influence on Me</title>
      <link>https://campbell.scot/the-10-technical-it-books-of-most-influence-to-me/</link>
      <pubDate>Wed, 28 Oct 2020 19:34:29 +0000</pubDate>
      <guid>https://campbell.scot/the-10-technical-it-books-of-most-influence-to-me/</guid>
      <description>&lt;p&gt;In the name of transparency, or maybe stating the bleeding obvious, I confess I am &lt;em&gt;that guy&lt;/em&gt; who can happily read an IT reference book or something like &lt;a href=&#34;http://docs.microsoft.com&#34;&gt;docs.microsoft.com&lt;/a&gt; or &lt;a href=&#34;https://practical365.com/&#34;&gt;Practical 365&lt;/a&gt; in the way someone else would read a popular fiction book.  It&amp;rsquo;s partly an inability to turn off from the job, and partly just because I like learning how everything works.  I&amp;rsquo;ve digested a ton of them over the last decade, so this blog is kind of my &amp;lsquo;acknowledgements&amp;rsquo;, where I&amp;rsquo;m recognising and conveying my gratitude to the ones most influential in the formation of my learning, writing style, and career.&lt;/p&gt;</description>
    </item>
    <item>
      <title>PowerShell: Run Cmdlet If Another Was Successful (And Keep Trying Until It Is)</title>
      <link>https://campbell.scot/powershell-run-cmdlet-if-another-was-successful-and-keep-trying-until-it-is/</link>
      <pubDate>Fri, 23 Oct 2020 17:30:52 +0000</pubDate>
      <guid>https://campbell.scot/powershell-run-cmdlet-if-another-was-successful-and-keep-trying-until-it-is/</guid>
      <description>&lt;p&gt;Today I&amp;rsquo;m sharing a useful bit of PowerShell I gracelessly punt from script to script whenever I need to make sure a prerequisite it met before running something and to &lt;em&gt;keep checking&lt;/em&gt; until it&amp;rsquo;s met, then run what I need: &amp;ldquo;do X when Y is ready and keep checking Y until it&amp;rsquo;s ready&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;The original use for this was my script to create a new Microsoft 365 user, but hold off on some parts of it - such as time zone settings - until the Exchange Online mailbox is provisioned.  That takes some time, so I wanted to keep checking and as soon as I could, continue the script.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Difference Between Cloud App Security Discovery (CAD), Office 365 Cloud App Security (OCAS), and Microsoft Cloud App Security (MCAS)</title>
      <link>https://campbell.scot/the-difference-between-cloud-app-security-discovery-cad-office-365-cloud-app-security-ocas-and-microsoft-cloud-app-security-mcas/</link>
      <pubDate>Mon, 07 Sep 2020 19:15:17 +0000</pubDate>
      <guid>https://campbell.scot/the-difference-between-cloud-app-security-discovery-cad-office-365-cloud-app-security-ocas-and-microsoft-cloud-app-security-mcas/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Microsoft Cloud App Security&lt;/strong&gt; (MCAS), Redmond&amp;rsquo;s cloud app security broker (CASB) offering, is a powerful tool for investigating and pro-actively controlling your SaaS estate.  It includes tools such as reverse proxying to control sessions and sits inside the &lt;strong&gt;Microsoft Threat Protection&lt;/strong&gt; stack alongside Defender ATP, Office 365 ATP, and Azure ATP.  MCAS started life as Adallom prior to Microsoft&amp;rsquo;s acquisition of that company in 2015.  It&amp;rsquo;s included in Microsoft 365 E5 and numerous other licensing subsets, including EMS E5, E5 Security (an add-on for Microsoft 365 E3), Information Protection &amp;amp; Governance, or standalone.  In all cases, you&amp;rsquo;d need to make sure it includes or you also get a license for Azure AD Premium for the reverse proxy benefits, delivered via &lt;strong&gt;Conditional Access App Control&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protecting Sensitive Information in Windows 10 with Microsoft Endpoint Data Loss Prevention (DLP)</title>
      <link>https://campbell.scot/protecting-sensitive-information-in-windows-with-microsoft-endpoint-data-loss-prevention-dlp/</link>
      <pubDate>Sun, 23 Aug 2020 17:30:21 +0000</pubDate>
      <guid>https://campbell.scot/protecting-sensitive-information-in-windows-with-microsoft-endpoint-data-loss-prevention-dlp/</guid>
      <description>&lt;p&gt;After being released to Public Preview last month (July 2020), I have finally had a chance to test out Microsoft Endpoint DLP.  The management of endpoint DLP - that is, preventing sensitive information from leaving the host computer - comes up frequently in my discussions with companies I help with security and compliance.  Often, they have third-party tools doing it and are looking to centralise under Microsoft&amp;rsquo;s stack.&lt;/p&gt;
&lt;p&gt;In this blog, I&amp;rsquo;ll give an overview of:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Getting Started with Azure AD Identity Governance – Part 3: Privileged Identity Management (PIM)</title>
      <link>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/</link>
      <pubDate>Sun, 16 Aug 2020 14:13:09 +0000</pubDate>
      <guid>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/</guid>
      <description>&lt;p&gt;This blog is the last in a small series on Azure AD Premium P2&amp;rsquo;s Identity Governance toolkit.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/&#34;&gt;Part 1: Entitlement Management&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/&#34;&gt;Part 2: Access Reviews&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/&#34;&gt;Part 3: Privileged Identity Management (PIM) (this post)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;PIM is an Azure AD P2 feature that enables just-in-time (JIT) admin rights in Azure and Azure AD.  Historically, best practice has been for users to have a separate account for admin tasks, as protection against the primary account if breached.  While this is still supported under PIM, it&amp;rsquo;s less of a requirement - PIM makes admin rights time bound on the same account and optionally require approval to activate.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Getting Started with Azure AD Identity Governance – Part 2: Access Reviews</title>
      <link>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/</link>
      <pubDate>Sun, 02 Aug 2020 14:46:34 +0000</pubDate>
      <guid>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/</guid>
      <description>&lt;p&gt;This blog is the second in a small series on Azure AD Premium P2&amp;rsquo;s Identity Governance toolkit.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/&#34;&gt;Part 1: Entitlement Management&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/&#34;&gt;Part 2: Access Reviews (this post)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/&#34;&gt;Part 3: Privileged Identity Management (PIM)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;Historically, the apps, groups, and rights a user had were all under central and constant management by IT.  Azure AD and modern management have pushed this towards &amp;lsquo;self-service&amp;rsquo;, including guest users, which improves productivity.  The goal of Azure AD access reviews is to improve the management of user rights and access, in this modern environment, throughout their lifecycle in your tenant.  It empowers you with automated tools to control their groups, apps, and roles (admin rights).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Getting Started with Azure AD Identity Governance - Part 1: Entitlement Management</title>
      <link>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/</link>
      <pubDate>Sun, 26 Jul 2020 17:27:32 +0000</pubDate>
      <guid>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/</guid>
      <description>&lt;p&gt;This blog is the first in a small series on Azure AD Premium P2&amp;rsquo;s Identity Governance toolkit.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/&#34;&gt;Part 1: Entitlement Management (this post)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/&#34;&gt;Part 2: Access reviews&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/&#34;&gt;Part 3: Privileged Identity Management (PIM)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;Azure AD entitlement management is a bit of an overlooked gem.  It&amp;rsquo;s a feature that automates the processes for giving users access to resources. The typical scenario is a user has just joined a new department or is a new employee.  Over time, the resources their team need access to have sprawled across the M365 estate and it would be laborious to give permission to them all manually - if you even remember them all.  Additionally, you want to ensure the user&amp;rsquo;s access is time-controlled so that as their role changes, their access does too.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender for Endpoint Web Content Filtering - Migrate Rules from Existing Security Software</title>
      <link>https://campbell.scot/microsoft-defender-atp-web-content-filtering-migrate-rules-from-existing-security-software/</link>
      <pubDate>Sat, 04 Jul 2020 14:15:32 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-atp-web-content-filtering-migrate-rules-from-existing-security-software/</guid>
      <description>&lt;p&gt;In my &lt;a href=&#34;https://campbell.scot/microsoft-defender-atp-web-content-filtering-administration-limitations-and-user-experience/&#34;&gt;last blog&lt;/a&gt;, I wrote about web content filtering in MDATP and how it now allows you to block website categories on the client across all apps.  Category blockers are great because, with one easy checkbox, you ban hundreds of thousands of dangerous on inappropriate websites.  Nothing is perfect, though, and anyone who&amp;rsquo;s ever worked a helpdesk or SOC will attest that false positives and false negatives are common.&lt;/p&gt;
&lt;p&gt;The engine for MDATP web content filtering is &lt;a href=&#34;https://www.cyren.com/&#34;&gt;Cyren&lt;/a&gt;, and you can check if a website is caught by its category rules using their online &lt;a href=&#34;https://www.cyren.com/security-center/url-category-check&#34;&gt;category check tool&lt;/a&gt;.  This takes a bit of time, as each check is subject to a &lt;a href=&#34;https://developers.google.com/recaptcha/docs/v3&#34;&gt;Google reCAPTCHA test&lt;/a&gt;.  If you&amp;rsquo;re migrating anything of scale to MDATP, you don&amp;rsquo;t have the time to do this, and also do not want to risk important websites later being swept up by category rules even if they are fine for now.  When you allowed or blocked websites on your existing solution, it&amp;rsquo;s assumed you&amp;rsquo;ve done the due diligence, and you want to take the remediation you&amp;rsquo;ve applied against those (potential) false positives and false negatives with you.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender for Endpoint Web Content Filtering - Administration, Limitations, and User Experience</title>
      <link>https://campbell.scot/microsoft-defender-atp-web-content-filtering-administration-limitations-and-user-experience/</link>
      <pubDate>Sun, 28 Jun 2020 16:37:29 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-atp-web-content-filtering-administration-limitations-and-user-experience/</guid>
      <description>&lt;p&gt;Historically, one of the big features missing &amp;ldquo;out of the box&amp;rdquo; with MDATP was web content filtering.  Customers typically look at MDATP as an option when their existing endpoint security is due for license renewal, and compare their existing solution against it.  They would be moving from one of the big security vendors such as Sophos, Norton, and McAfee, which all supported web content filtering.  Higher lever stakeholders often listed the ability to block websites as essential, and as Microsoft did not maintain such a categorisation database, if you wanted it with Defender ATP, you&amp;rsquo;d be looking at other solutions too.  This took away from Defender ATP&amp;rsquo;s &amp;ldquo;single pane of glass&amp;rdquo; selling point.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sign In to Azure AD Using Google with Azure AD External Identities</title>
      <link>https://campbell.scot/sign-in-to-azure-ad-using-google-with-azure-ad-external-identities/</link>
      <pubDate>Sun, 07 Jun 2020 10:47:31 +0000</pubDate>
      <guid>https://campbell.scot/sign-in-to-azure-ad-using-google-with-azure-ad-external-identities/</guid>
      <description>&lt;p&gt;External Identities is a new public preview feature of Azure AD which allows external users to authenticate with a non-Microsoft account such as their Google or Facebook identity.  This has been available in Azure AD B2C for some time, but that solution is really targetted at highly customised applications with potentially millions of users.  External Identities opens up that idea to you ordinary Azure AD tenant so that any SAML or WS-Fed IdP can be used.  You are essentially federating Azure AD with the external IdP, not a million miles off in construct to how you might federate your Active Directory Domain Services domains to trust others.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Differences Between (and History of) the Microsoft 365 Security Centre, Compliance Centre, and Security &amp; Compliance</title>
      <link>https://campbell.scot/the-differences-between-and-history-of-the-microsoft-365-security-centre-compliance-centre-and-security-compliance/</link>
      <pubDate>Mon, 01 Jun 2020 07:11:37 +0000</pubDate>
      <guid>https://campbell.scot/the-differences-between-and-history-of-the-microsoft-365-security-centre-compliance-centre-and-security-compliance/</guid>
      <description>&lt;p&gt;There are currently &lt;strong&gt;three&lt;/strong&gt; separate admin consoles in Microsoft 365 for administrators to view or configure security and compliance policies, alerts, and reports.  Believe it or not, this is down from &lt;strong&gt;four&lt;/strong&gt; at the peak of just-tell-me-where-to-go-to-do-this.  This doesn&amp;rsquo;t even include consoles such as Microsoft Cloud App Security (MCAS).  The direction things are heading is good, as I&amp;rsquo;ll explain in this blog, but the situation does highlight Microsoft&amp;rsquo;s relatively new culture and position of continual small updates rather than delivering fully finished products.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Connect Microsoft Store for Business to Intune in Microsoft Endpoint Manager</title>
      <link>https://campbell.scot/connect-microsoft-store-for-business-to-intune-in-microsoft-endpoint-manager/</link>
      <pubDate>Fri, 29 May 2020 19:32:29 +0000</pubDate>
      <guid>https://campbell.scot/connect-microsoft-store-for-business-to-intune-in-microsoft-endpoint-manager/</guid>
      <description>&lt;p&gt;When you link up the Microsoft Store for Business to Intune, you can centrally deploy store apps, automatically keep them up to date, and access volume-purchases.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; In MEM, browse to &lt;strong&gt;Tenant administration&lt;/strong&gt; &amp;gt; &lt;strong&gt;Connectors and tokens&lt;/strong&gt; &amp;gt; &lt;strong&gt;Microsoft Store for Business&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://campbell.scot/wp-content/uploads/2020/05/0102.png&#34;&gt;&lt;strong&gt;2.&lt;/strong&gt; Set the state to &lt;strong&gt;Enable&lt;/strong&gt; and follow the link to &lt;strong&gt;Open the business store&lt;/strong&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://campbell.scot/wp-content/uploads/2020/05/03-2.png&#34;&gt; &lt;strong&gt;3.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hybrid Azure AD Join &#43; Intune Enrollment - Prerequisites Checklist and Process Flow</title>
      <link>https://campbell.scot/hybrid-azure-ad-join-intune-enrollment-prerequisites-checklist-and-process-flow/</link>
      <pubDate>Mon, 25 May 2020 17:22:04 +0000</pubDate>
      <guid>https://campbell.scot/hybrid-azure-ad-join-intune-enrollment-prerequisites-checklist-and-process-flow/</guid>
      <description>&lt;p&gt;I&amp;rsquo;m a simple person, and sometimes it just helps to have a checklist to refer to when you&amp;rsquo;re troubleshooting rather than navigating the sparse pages of docs.microsoft.com.  In this blog, I  explain the prerequisites for the Hybrid Azure AD Join (HAADJ) + automatic (GPO controlled) Intune MDM enrollment scenario and the process from start to end, as simply and concisely as I can (not easy!)  There are no screenshots and it&amp;rsquo;s not a click-by-click: this is a quick reference for when you&amp;rsquo;re pulling your hair out wondering what could be stopping you.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft 365 Updates from Build 2020</title>
      <link>https://campbell.scot/microsoft-365-updates-from-build-2020/</link>
      <pubDate>Thu, 21 May 2020 17:55:43 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-365-updates-from-build-2020/</guid>
      <description>&lt;p&gt;Build 2020 had some nice bits of M365 related news.  Microsoft deserves commendation for sticking to the schedule and pulling this off (remotely) during the COVID-19 lockdown - Apple has delayed WWDC and Google just gave up on I/O.  I&amp;rsquo;ve summarised (bullet points!) my favourite updates below.  I will update it I find I&amp;rsquo;ve missed something good.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Azure AD&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://aka.ms/publisherverification&#34;&gt;Publisher Verification&lt;/a&gt; lets developers verified through the Microsoft Partner Center stick a verified badge on their AAD apps.  There is a new setting in &lt;strong&gt;AAD&lt;/strong&gt; &amp;gt; &lt;strong&gt;Consent and permissions&lt;/strong&gt; to &lt;strong&gt;Allow for apps from this organisation and verified publishers&lt;/strong&gt;, which is Microsoft&amp;rsquo;s recommendation (as opposed to allowing user consent for all/none).&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://azure.microsoft.com/en-us/services/active-directory/external-identities/&#34;&gt;External Identities&lt;/a&gt; is now in public preview.  This allows invited external users to &amp;lsquo;bring their own identity&amp;rsquo; (BYOI) and sign in with a federated service like Google, Facebook, or another SAML2/WS-Fed IdP.&lt;/li&gt;
&lt;li&gt;Microsoft Authentication Libraries (MSAL) &lt;a href=&#34;https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-v2-angular&#34;&gt;now support Angular&lt;/a&gt; and the &lt;a href=&#34;https://github.com/AzureAD/microsoft-identity-web/wiki&#34;&gt;ASP.NET web libraries are in public preview&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Development&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Register Domain-Joined Computers as Devices - The Redundant and Broken Hybrid Azure AD Join GPO</title>
      <link>https://campbell.scot/register-domain-joined-computers-as-devices-the-redundant-and-broken-hybrid-azure-ad-join-gpo/</link>
      <pubDate>Tue, 19 May 2020 19:11:46 +0000</pubDate>
      <guid>https://campbell.scot/register-domain-joined-computers-as-devices-the-redundant-and-broken-hybrid-azure-ad-join-gpo/</guid>
      <description>&lt;p&gt;The group policy object &lt;strong&gt;Register domain-joined computers as devices&lt;/strong&gt;, or &lt;strong&gt;Automatically workplace join client computers&lt;/strong&gt; in older templates, was previously a requirement for enabling Hybrid Azure AD Join.  After configuring Azure AD Connect and your Seamless SSO GPOs, this had to be enabled.&lt;/p&gt;
&lt;p&gt;Since Windows 10 1607 (&amp;ldquo;Anniversary Update&amp;rdquo;), in Azure AD Connect environments, on-premises Active Directory joined computers become Azure Active Directory registered when a synchronised user signs in to a synchronised computer; regardless of the GPO existing.  Prior to this, on Windows 10 1511 (&amp;ldquo;November Update&amp;rdquo;) and before, only if this GPO, or other configuration to create this registry value, was used.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Connect a Work or School Account - MDM vs. MAM in Self Enrolment</title>
      <link>https://campbell.scot/connect-a-work-or-school-account-mdm-vs-mam-in-self-enrolment/</link>
      <pubDate>Sat, 16 May 2020 06:13:47 +0000</pubDate>
      <guid>https://campbell.scot/connect-a-work-or-school-account-mdm-vs-mam-in-self-enrolment/</guid>
      <description>&lt;p&gt;A Windows 10 user can self-enrol in MDM or MAM from &lt;strong&gt;Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;Accounts&lt;/strong&gt; &amp;gt; &lt;strong&gt;Access work or school&lt;/strong&gt; &amp;gt; &lt;strong&gt;Connect&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://campbell.scot/wp-content/uploads/2020/05/01-1.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;What happens next depends on how &lt;strong&gt;Mobility (MDM and MAM)&lt;/strong&gt; is configured in Azure Active Directory and &lt;strong&gt;device ownership&lt;/strong&gt;.  For a personal device, if &lt;strong&gt;user scope&lt;/strong&gt; for both MDM and MAM overlaps for the enrolling user, MAM will win.  The opposite is true of corporate devices. [wptb id=277]&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Information Protection (WIP) App Protection Policies: Protected and Exempt; Denied and Allowed - What Do They Mean?</title>
      <link>https://campbell.scot/windows-information-protection-wip-app-protection-policies-protected-and-exempt-denied-and-allowed-what-do-they-mean/</link>
      <pubDate>Thu, 14 May 2020 21:05:30 +0000</pubDate>
      <guid>https://campbell.scot/windows-information-protection-wip-app-protection-policies-protected-and-exempt-denied-and-allowed-what-do-they-mean/</guid>
      <description>&lt;p&gt;One of things that strikes me as vague in Windows Information Protection (WIP) policies in Intune is configuring targeted apps:  what&amp;rsquo;s the &lt;em&gt;exact&lt;/em&gt; difference between a protected app and an exempt app; and what does allow or deny &lt;em&gt;exactly&lt;/em&gt; do for both of those?&lt;/p&gt;
&lt;p&gt;A recap on some terminology before explaining what-does-what.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Targeted apps&lt;/strong&gt; are ones the WIP service will implement controls over.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Unenlightened apps&lt;/strong&gt; cannot differentiate between work and personal data.  They have no idea what WIP is as the developer has not incorporated it.  They can only implement controls if the device is MDM enrolled.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Enlightened apps&lt;/strong&gt; have incorporated WIP into the design and can differentiate between work and personal data.  For example, Outlook knows if the email account is tenant one or not.  They can implement controls even if it&amp;rsquo;s just using MAM.  Such a scenario is called &lt;strong&gt;WIP Without Enrollment&lt;/strong&gt; or &lt;strong&gt;WIP-WE&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Enterprise context&lt;/strong&gt; is the ownership of data in the application.  You can review this by adding the column in Task Manager.  Data will either belong to the &lt;strong&gt;tenant&lt;/strong&gt; (work) or &lt;strong&gt;personal&lt;/strong&gt; (not work).  It can also be &lt;strong&gt;exempt&lt;/strong&gt;, which means waived from rules.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In the example below, every app you see - protected and exempt - will be controlled if an MDM scenario, but only enlightened ones can be in a MAM scenario.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using Intune to Deploy the Azure Information Protection (AIP) Unified Labeling Client (Win32 MSI)</title>
      <link>https://campbell.scot/using-intune-to-deploy-the-azure-information-protection-aip-unified-labeling-client-win32-msi/</link>
      <pubDate>Sat, 18 Jan 2020 22:47:50 +0000</pubDate>
      <guid>https://campbell.scot/using-intune-to-deploy-the-azure-information-protection-aip-unified-labeling-client-win32-msi/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Unified labels&lt;/strong&gt; refer to a movement whereby &lt;strong&gt;Azure Information Protection (AIP) labels&lt;/strong&gt; are now being replaced by &lt;strong&gt;sensitivity labels&lt;/strong&gt;.  Sensitivity labels offer encryption, watermarks, etc as AIP labels did before them, but are now managed in the new &lt;a href=&#34;https://security.microsoft.com/sensitivity?viewid=sensitivitylabels&#34;&gt;Microsoft 365 Security Centre&lt;/a&gt;, with several other benefits beyond the scope of this post.&lt;/p&gt;
&lt;p&gt;With this change comes a new AIP client, called the &lt;strong&gt;unified labeling client&lt;/strong&gt;, that replaces the old one, now called the &lt;strong&gt;classic client&lt;/strong&gt;.  The AIP unified labeling client will refer to the M365 Security Centre to download labels, but note that (and &amp;lsquo;unified&amp;rsquo; gives this away) labels created on either the old Azure AIP dashboard or new M365 Security Centre will sync to each other after you have enabled unified labeling.  Current guidelines from Microsoft are that, unless you have a &lt;a href=&#34;https://docs.microsoft.com/en-us/azure/information-protection/rms-client/use-client#compare-the-labeling-clients-for-windows-computers&#34;&gt;use case that isn&amp;rsquo;t a feature of the unified labeling client&lt;/a&gt;, this is what you should be installing.  This post holds your hand through a deployment of the client using Intune.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploy Microsoft Store Apps using Intune with Configuration Manager (SCCM) Co-Management (Fix &#39;Not Applicable&#39; Status)</title>
      <link>https://campbell.scot/deploy-microsoft-store-apps-using-intune-with-sccm-co-management-fix-not-applicable-status/</link>
      <pubDate>Fri, 10 Jan 2020 21:00:30 +0000</pubDate>
      <guid>https://campbell.scot/deploy-microsoft-store-apps-using-intune-with-sccm-co-management-fix-not-applicable-status/</guid>
      <description>&lt;p&gt;Intune provides an interface to easily deploy apps from the Microsoft Store to your registered users and devices, but even if you have SCCM (Config Manager) Co-Mangement enabled with the default workloads shifted to Intune in Co-Management properties, there is more to be done.  If you don&amp;rsquo;t follow these steps, you will receive the status of &lt;strong&gt;Not applicable&lt;/strong&gt; in the Intune client apps user and device install status pages.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;00.-Not-Applicable-in-Intune&#34; loading=&#34;lazy&#34; src=&#34;//wp-content/uploads/2020/05/00.-not-applicable-in-intune.png&#34;&gt;&lt;strong&gt;Prerequisite:&lt;/strong&gt; This only works with SCCM 1806+.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Prerequisites and Planning for Centrally Deploying Office 365 Outlook Add-Ins</title>
      <link>https://campbell.scot/prerequisites-and-planning-for-centrally-deploying-office-365-outlook-add-ins/</link>
      <pubDate>Sun, 05 Jan 2020 21:00:38 +0000</pubDate>
      <guid>https://campbell.scot/prerequisites-and-planning-for-centrally-deploying-office-365-outlook-add-ins/</guid>
      <description>&lt;p&gt;Deploying Outlook add-ins (&amp;ldquo;apps&amp;rdquo;) for your O365 tenant is an intuitive experience via AppSource.  As a Global Administrator, click &lt;strong&gt;GET IT NOW&lt;/strong&gt; on the app&amp;rsquo;s page and you are immediately redirected to the &lt;strong&gt;Services &amp;amp; add-ins&lt;/strong&gt; page of the M365 Admin Center.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;1&#34; loading=&#34;lazy&#34; src=&#34;//wp-content/uploads/2020/05/1.png&#34;&gt;&lt;img alt=&#34;2&#34; loading=&#34;lazy&#34; src=&#34;//wp-content/uploads/2020/05/2.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;From there, you can configure add-ins for the whole tenant, just yourself, or by group.  All AAD group types, except non-email enabled ones, are supported.  If a group is nested, the top-level group gets it, but none of the nested ones.  You then choose to deploy as &lt;strong&gt;fixed&lt;/strong&gt;, which means enforced, &lt;strong&gt;available&lt;/strong&gt;, which means shown when users search for apps, or &lt;strong&gt;optional&lt;/strong&gt;, which means installed but can be removed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Manage MyAnalytics Weekly Insight Digest Emails and App Availability</title>
      <link>https://campbell.scot/manage-myanalytics-emails-and-app-availability/</link>
      <pubDate>Mon, 21 Oct 2019 14:25:45 +0000</pubDate>
      <guid>https://campbell.scot/manage-myanalytics-emails-and-app-availability/</guid>
      <description>&lt;p&gt;Made available to more than just E5 licencees &lt;a href=&#34;https://www.microsoft.com/en-us/microsoft-365/blog/2019/01/02/myanalytics-the-fitness-tracker-for-work-is-now-more-broadly-available/&#34;&gt;earlier this year&lt;/a&gt;, MyAnalytics will, by default, send users weekly emails regarding their work patterns.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;image-1&#34; loading=&#34;lazy&#34; src=&#34;//wp-content/uploads/2020/05/image-1.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Users can control this themselves in settings pane of the &lt;a href=&#34;https://myanalytics.microsoft.com/&#34;&gt;MyAnalytics web app&lt;/a&gt;.&lt;/p&gt;
&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;//wp-content/uploads/2020/05/image-2.png&#34;
         alt=&#34;image-2&#34;/&gt; &lt;figcaption&gt;
            &lt;p&gt;image-2&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;Administrators cannot, in bulk, keep MyAnalytics enabled for users but disable the email digest. The following PowerShell example instead disables MyAnalytics across all your Microsoft 365 Business licensed users, and therefore removing these emails.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
