Microsoft Entra Installation Guide (SAML)

🚧

SAML not recommended

Moveworks recommends that you set up your Microsoft Entra apps via OIDC. Our OIDC installation will provide a better experience. You can follow the instructions here (🔗).

Prerequisites

Microsoft Entra Prerequisites

  • Ensure you have Access to the Azure Admin Portal with the appropriate IAM permissions in Azure to register a new Enterprise Application.

Moveworks SSO Prerequisites

  • Your Moveworks organization should be initialized (verify with your account team)

  • Note the following values.

    • data_center_domain - the data center where your organization is hosted (see table below).

    • subdomain - your organization's login subdomain. This will generally match your customer_id, but you can verify or customize it in General Information.

      🚧

      Warning

      Make sure you ONLY note your unique subdomain. For example, if you're organization's login subdomain is acme.moveworks.com, then your subdomain is acme and your data_center_domain is moveworks.com

    • [Optional] customer_id - unique identifier for your organization (can not be changed). This is stored as Org Name under Organization Details > General Information


Data Centerdata_center_domain
United States (default)moveworks.com
Canadaam-ca-central.moveworks.com
EUam-eu-central.moveworks.com
Australia / Asia Pacificam-ap-southeast.moveworks.com
Government Secure Cloudmoveworksgov.com

Configuration Steps

Install Application

  1. Navigate to https://portal.azure.com

  2. Go to Enterprise applications and select New Application

  3. Search Moveworks, select our application, and select Create

Configure Moveworks Settings

  1. On the Single sign-on tab select SAML


  2. Select Edit for the Basic SAML Configuration (Step 1)

  3. Configure your SAML variables using your organization's information and hit Save

    • Reply URL: https://{{subdomain}}.{{data_center_domain}}/login/sso/saml
    • Sign-on URL: https://{{subdomain}}.{{data_center_domain}}
    • Relay State: {{customer_id}}
  4. Select Edit for SAML Certificates next to Token signing certificate(Step 3)

  5. Validate that the following values are set

    • Signing Option: Sign SAML response and assertion
    • Signing Algorithm: SHA-256

Enable User Access

  1. Go to Manage > Properties

  2. Make sure that your app is visible to users.

Add SAML Configuration in MyMoveworks

  1. On the Single Sign-on tab, download your X.509 Certification (x509_certificate) by clicking on the Download link next to Certificate (Base64)

  2. Open the downloaded file in a text editor. It should look something like this.

    -----BEGIN CERTIFICATE-----
    ****************************************************************************
    ****************************************************************************
    ****************************************************************************
    ****************************************************************************
    ****************************************************************************
    ****************************************************************************
    ****************************************************************************
    *********************
    -----END CERTIFICATE-----
    
  3. From Step 4 in the Single Sign-on tab, copy the remaining SAML variables

    • Login URL: this is your idp_url
    • Microsoft Entra Identifier: this is your idp_issuer
  4. Navigate to SSO Settings in MyMoveworks


  5. If you already see a studio config, edit it. Otherwise, choose Create.

  6. Add your configuration using the values you've noted above

    • Moveworks Product: studio
    • Select Connector: okta or moveworks
    • Authentication Protocol: SAML
    • IDP Sign On / SSO URL: {{idp_url}} (From Step 3)
      • e.g. https://login.microsoftonline.com/c3662339-1217-4e03-ac19-15f31311cca7/saml2
    • IDP Issuer: {{idp_url}}(From Step 2)
      • e.g. https://sts.windows.net/c3662339-1217-4e03-ac19-15f31311cca7/
    • IDP Public Certificate: x509_certificate (From Step 1)
  7. Click Submit.

  8. Wait a few minutes, then attempt to log into your instance at https://{{subdomain}}.{{data_center_domain}}