ValidSign
Getting started

Configuring Signer SSO with Microsoft Entra ID (Azure AD)

Step-by-step guide to setting up Signer SSO between ValidSign and Microsoft Entra ID (Azure AD) via SAML, including claim configuration.

4 min readLast updated: 2026-11-04

With Signer SSO, internal signers use their existing company account as additional verification when signing documents. This guide explains how to set up the Signer SSO connection between ValidSign and Microsoft Entra ID (formerly Azure AD) based on SAML. Would you first like to know how signing with Signer SSO works? Then read the article 'How does signing with Signer SSO work in ValidSign?'.

Before you start

  • Signer SSO is an add-on module that must be activated for your environment by our support team. Please contact support@validsign.eu.

  • Signer SSO uses its own app in your identity provider. Do you already use Single Sign-On to log in to ValidSign? Then create a second, separate app for Signer SSO. The setup is similar to the regular SSO app, but the entity ID is different.

  • Do you use SURFconext? Then you do not need to create an app. Please contact support@validsign.eu and we will set up the connection with you.

  • The setup on your side takes about 15 minutes.

Step 1: Create the app in Microsoft Entra ID

  1. Log in to your Azure AD tenant as a global administrator;

  2. In the left menu, click 'Microsoft Entra ID';

  3. Then click 'Enterprise applications';

  4. Click the 'New application' button at the top;

  5. Click the 'Create your own application' button at the top;

  6. Enter a name for the app, for example 'ValidSign Signer SSO'. This makes it easy to tell apart from any existing ValidSign SSO app;

  7. Select the option 'Integrate any other application you don't find in the gallery (Non-gallery)' and click 'Create'.

Step 2: Configure SAML

  1. You will now see the overview page of the app. Click 'Single sign-on' and select 'SAML';

  2. Under 'Basic SAML Configuration', click 'Edit' and enter the following details:

    1. Identifier (Entity ID)
      urn:saml:signer-sso:production:ValidSign:eu
      Please note: this value differs from the regular SSO connection (urn:saml:sso:production:ValidSign:eu). For Signer SSO, always use the value containing 'signer-sso'.

    2. Reply URL (Assertion Consumer Service URL)
      You will receive this URL from us after you have shared the metadata (see step 4). For now, enter https://my.validsign.eu as a temporary value.

    3. Sign on URL
      You will also receive this URL from us after you have shared the metadata.

  3. Click 'Save' at the top.

Step 3: Configure the claims

Have you already set up a Signer SSO app (or a regular SSO app)? Then copy the claim configuration on the Entra ID side from that app. Make sure the claim names below are used exactly as shown.

  1. Under 'Attributes & Claims', click 'Edit';

  2. Delete all default 'Additional claims' that start with 'http://schemas.xmlsoap.org/' using the three dots and 'Delete';

  3. Use 'Add new claim' to add the following three claims. Each time, enter the 'Name', select the 'Source attribute' and click 'Save':

Name

Source attribute

email

user.mail

firstname

user.givenname

lastname

user.surname

Please note: the 'accountId' and 'roleId' claims from the regular SSO guide are not needed for Signer SSO.

Step 4: Share the metadata with ValidSign

  1. In the app, go to 'Single sign-on' and scroll down to the 'SAML Certificates' section;

  2. Copy the value of 'App Federation Metadata Url' (or download the Federation Metadata XML file);

  3. Send the Metadata URL or the XML file to your ValidSign consultant or to support@validsign.eu. Please mention that it concerns Signer SSO.

Step 5: Complete the configuration

  1. We will set up the connection on our side and then send you the Reply URL (ACS) and the Sign on URL;

  2. Enter these values under 'Basic SAML Configuration' (see step 9) and click 'Save';

  3. Assign the employees who should be able to sign via Signer SSO to the app. You can do this under 'Users and groups' of the app, via 'Add user/group'.

    Please note: this group may differ from the group that has access to your ValidSign app for regular SSO. No ValidSign account is required to sign with Signer SSO. Therefore, assign all employees who need to sign documents as internal signers, even if they are not ValidSign users themselves.

The connection is now ready. From now on, internal signers can sign with Signer SSO.

Questions?
Do you have questions about the configuration? Please contact your consultant or our support team at support@validsign.eu.

Was this article helpful?

Need help?

Contact our support team

Contact us