<?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>External-Identities on Ru Campbell MVP</title>
    <link>https://campbell.scot/categories/external-identities/</link>
    <description>Recent content in External-Identities on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 07 Jun 2020 10:47:31 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/categories/external-identities/index.xml" rel="self" type="application/rss+xml" />
    <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>
