Note: Azure AD is currently not an official supported IDP method. this post describes the way I have been able to get Azure AD working as a SAML IDP. Please do not raise support tickets with Nutanix if you have issues configuring this as it is not an official IDP so they will not be able to help.

Using an external Identity Provider (IDP) is a great way to further secure your Prism Central deployment. In a previous post, I detailed how to integrate your on-premises ADFS with Prism Central. However what if you have Azure AD and only want to use Azure AD for authentication purposes?

In this post I’ll be guiding you through configuring an Identity Provider within Prism Central to leverage Azure AD authentication. So let’s get to it!


The first thing we need to do is create a Non-Gallery Application in your Azure Portal.

  1. Navigate to
  2. When logged into Azure, go to the Azure Active Directory tab on the left hand menu.
  3. Select the Enterprise applications service.
  4. Click on the New application button.
  5. Select the Non-gallery application.
  6. Name it (e.g Prism_Central).
  7. Click on Add.

SAML Configuration

With the Non-gallery Application (Called Prism_Central-2FA in this example) successfully added we can now configure the Single Sign On mode.

  1. Select Single sign-on within the Non-gallery Application.
  2. Select SAML as Single Sign-on Mode.

Now you need to switch to your Prism Central interface to gather some info.

  1. Login to Prism Central and go to Settings.
  2. Select Authentication.
  3. Click on Download Metadata.

Now that you have the Prism Central specific URLs, switch back to the Azure Non-gallery Application configuration

  1. Edit the Basic SAML Configuration.
  2. Enter the EntityID captured earlier in the Identity field.
  3. Enter the AssertionConsumerService Location captured earlier in the ReplyURL field.
  4. For the User Attributes & Claims section, ensure Unique User Identifier is mapped to user.userprincipalname.
  5. On the SAML Signing Certificate section, download the Certificate (Base64). We’ll need this a bit later.
  6. Copy the Azure AD Identifier, Logout URL as we will need these to configure Prism Central.
  7. Go to the Properties of the App on the left hand side and copy the User Access URL. We will need this for the Prism Central config too.

Prism Central Configuration

Now it’s time to configure Prism Central to use the newly created Enterprise App.

  1. Login to Prism Central and go to Settings and select Authentication
  2. Click on New IDP
  3. Give the configuration a name (AzureAD, for example) and select Enter Configuration Manually.

This is now where we need the info from Azure.

  1. In the Identity Provider URL, enter the Azure AD Identifier from the Single-Sign on section of the Azure Enterprise App.
  2. In the Login URL, enter the User Access URL from the Properties section of the Azure Enterprise App
  3. In the Logout URL, enter the Logout URL from the Single-Sign on section of the Azure Enterprise App.
  4. Open up the certificate you downloaded earlier in a text editor and paste that into the Certificate section.
  5. Click Save to add the Identity Provider.

With the Identity Provider now configured we need to map roles in Prism Central to the new Identity Provider.

  1. In Prism Central settings, go to Role Mapping and select New Mapping.
  2. Select the name of your Identity Provider that you configured earlier (in my case, AzureAD).
  3. Select the Role.
  4. In the Values field, enter the UPN for each user that will use the new Identity Provider to login to Prism Central.
    NOTE: The UPN is case sensitive. So if your UPN in Azure AD has capitol letters, you must use capitol letters here. It’s best to just copy/paste the UPN from Azure AD.


Now that the configuration is done on both the Azure and Prisnm Central sides, it’s time to test.

Log out of Azure and Prism Central and a new browser to your Prism Central URL. Click the Login with AzureAD (or whatever you called your Identity Provider in Prism Central).

You should now be redirected to Microsoft Online to login with your Azure AD credentials (and MFA as well if you have that enabled).


You now have access to Prism Central through Azure AD (with MFA capabilities). 😀 


  1. Bart Donders August 27, 2019 at 5:40 pm

    Great post William… It helped us a lot…


  2. Patrick Damen February 17, 2020 at 11:57 pm

    Great info!!!

  3. francescm April 2, 2020 at 6:12 pm

    hi, which version of Prism Central did you use? I am following your nice instructions, but on Sign In attempt on AD, Microsoft complains:
    “Sign in
    Sorry, but we’re having trouble signing you in.

    AADSTS750054: SAMLRequest or SAMLResponse must be present as query string parameters in HTTP request for SAML Redirect binding.”
    (yes, I double checked it, there is no SAML assertion)
    My Prism Central is Version

    1. William Beckett April 3, 2020 at 9:46 am

      I deployed this on PC 5.10.
      I’ll update my lab to and see if I have the same issue you do and let you know.

      1. Posatorn Wirattikovit August 26, 2020 at 8:04 pm

        Hi, i try this on PC 5.17 and pc.2020.7, i found same error with @francescm.

        if you test successful and don’t have same issue with me and @francescm, Please let me know.

        Thank you very much

    2. Ramesh Jayaraman June 29, 2020 at 6:10 pm

      Hi, I too get same error with Prism Central version

  4. Ramesh Jayaraman June 29, 2020 at 6:22 pm

    Sign in
    Sorry, but we’re having trouble signing you in.

    AADSTS750054: SAMLRequest or SAMLResponse must be present as query string parameters in HTTP request for SAML Redirect binding.


Leave A Comment

Your email address will not be published. Required fields are marked *