<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AzureAD on John Billekens | Notes from the field</title><link>https://blog.j81.nl/tags/azuread/</link><description>Recent content in AzureAD on John Billekens | Notes from the field</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 John Billekens</copyright><lastBuildDate>Thu, 28 Oct 2021 15:22:49 +0000</lastBuildDate><atom:link href="https://blog.j81.nl/tags/azuread/index.xml" rel="self" type="application/rss+xml"/><item><title>Manipulate the 'NameID' SAML content - part 1</title><link>https://blog.j81.nl/posts/manipulate-the-nameid-saml-content-part-1/</link><pubDate>Thu, 28 Oct 2021 15:22:45 +0000</pubDate><guid>https://blog.j81.nl/posts/manipulate-the-nameid-saml-content-part-1/</guid><description>&lt;p&gt;Some companies want to allow other (guest) companies to connect to their environment and for example allow them to open a Citrix Desktop. This can be achieved by Connecting an existing Citrix environment to the guest company via SAML (and yes there are other possibilities). SAML is an authentication method based on a two-way trust. Two Microsoft products that can offer SAML authentication are ADFS (Active Directory Federation Services, an on-premises solution) and the other is and Enterprise App you can configure from the Azure portal. The other requirement is Citrix FAS (Federated Authentication Services). In this article I will show you a way to connect a guest (company) via SAML to allow them access to your Citrix environment without the need for adding the guest companies suffix to your domain. &lt;/p&gt;</description></item></channel></rss>