<?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>Pim on Ru Campbell MVP</title>
    <link>https://campbell.scot/tags/pim/</link>
    <description>Recent content in Pim on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 19 Nov 2023 14:01:41 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/tags/pim/index.xml" rel="self" type="application/rss+xml" />
    <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>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>
  </channel>
</rss>
