<?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>Collaboration on Ru Campbell MVP</title>
    <link>https://campbell.scot/tags/collaboration/</link>
    <description>Recent content in Collaboration on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 02 Aug 2020 14:46:34 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/tags/collaboration/index.xml" rel="self" type="application/rss+xml" />
    <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>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>
  </channel>
</rss>
