<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>michaelkolzem Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>michaelkolzem Tracker</description>
    <pubDate>Thu, 23 Nov 2023 14:48:39 GMT</pubDate>
    <dc:date>2023-11-23T14:48:39Z</dc:date>
    <item>
      <title>Best Practice for publishing Exchange using VMware NSX Advanced Load Balancer and SAML Access Policy</title>
      <link>https://communities.vmware.com/t5/Networking-Members/Best-Practice-for-publishing-Exchange-using-VMware-NSX-Advanced/m-p/2883106#M90</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;we currently try to publish Microsoft Exchange (OWA) through VMware NSX Advanced Load Balancer including a SAML Access Policy and AD FS 4 using this description:&amp;nbsp;&lt;A href="https://avinetworks.com/docs/21.1/saml-avi-integration-with-adfs/" target="_blank"&gt;https://avinetworks.com/docs/21.1/saml-avi-integration-with-adfs/&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Unfortunately the solution does not work for us and we receive Empty Responses from AD FS. Load Balancer version is 21.1.1 2p3 (including a patch for SAML signing).&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know how to deploy Exchange (OWA) through the Load Balancer like described above?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 16:56:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/Best-Practice-for-publishing-Exchange-using-VMware-NSX-Advanced/m-p/2883106#M90</guid>
      <dc:creator>michaelkolzem</dc:creator>
      <dc:date>2021-12-13T16:56:24Z</dc:date>
    </item>
  </channel>
</rss>

