<?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>Entitlement-Management on Ru Campbell MVP</title>
    <link>https://campbell.scot/tags/entitlement-management/</link>
    <description>Recent content in Entitlement-Management on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 05 Oct 2023 21:11:27 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/tags/entitlement-management/index.xml" rel="self" type="application/rss+xml" />
    <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>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>
  </channel>
</rss>
