Rely.io
  • 📌What is Rely.io?
  • 💡How Rely.io works
  • 📑Getting Started Guide
    • Create an account for your organization
    • Add your first plugin
    • Import services into the Service Catalog
    • Make the Software Catalog your own
    • What's Next?
  • 🌈Basic Concepts
    • Entities
    • Blueprints
    • Property Data Types
    • Catalogs
    • Data Model
    • Plugins
    • User Blueprints vs Plugin Blueprints
    • Actions and Automations
      • Automation Rules
      • Self-Service Actions
    • Home Pages
    • Scorecards
  • 📚Guides & Tutorials
    • Enhancing Deployment Visibility through Gitlab Pipelines and Rely's API
  • 🖥️Software Catalog
    • Overview and Use Cases
    • Usage Guide
      • Creating a new Entity
      • Updating an Entity
      • Tracking Entity Changes
      • Customizing an Entity's Page
      • Customizing a Catalog
      • Creating a new Blueprint & Catalog
      • Updating a Blueprint
      • Tracking Blueprint Changes
    • Relevant Guides
    • Troubleshooting
  • 🥇Scorecards
    • Overview and Use Cases
    • Usage Guide
      • Creating a Scorecard
      • Updating a Scorecard
      • Evaluating Performance
    • Scorecard Examples
      • Production Readiness Scorecard Example
      • DORA Metrics Scorecard Example
      • Operational Maturity Example
  • 🎨Home Pages
    • Overview and Use Cases
    • Usage Guide
      • Creating a New Tab
  • ⚡Self-Service Actions
    • Overview and Use Cases
    • Usage Guide
      • Configuring your Self Service Agent
      • Managing your Actions Catalog
      • Self-Service Actions as Code
      • Running Actions
      • Tracking Action Runs
  • ↗️Plugins & Automation
    • What happens when you install a Plugin?
    • Self-Hosting Plugins using Galaxy
    • 🤖Automation Rules
      • Overview and Use Cases
      • Usage Guide
        • Creating an Automation Rule
        • Updating an Automation Rule
        • Tracking Automation Changes
        • Managing Automation Suggestion
    • 🔌Plugin Installation Guides
      • ⭐AWS
      • Bitbucket
      • ⭐Flux
      • GitHub
      • GitLab
      • ⭐Google Cloud Platform (GCP)
      • ⭐Kubernetes
      • ⭐OpsGenie
      • ⭐PagerDuty
      • ⭐Snyk
      • ⭐SonarQube
  • 🌐Public API
    • Audit Logs
    • Automations & Self-Service Actions
    • Automation Suggestions
    • Blueprints
    • Dashboards & Views
    • Entities
    • Scorecards
    • Self-Service Action Runs
    • Time Series
    • Users
    • Webhooks
  • ⚙️Invite Users
  • 🛡️Security & Compliance
    • Single Sign-On (SSO)
      • SAML with Google Workspace
      • SAML with Microsoft Entra ID
      • SAML with Okta
      • OIDC with Okta
      • OIDC with Google Workspace
  • 🏥Troubleshooting
  • ❓FAQ
Powered by GitBook
On this page

Was this helpful?

  1. Security & Compliance
  2. Single Sign-On (SSO)

SAML with Microsoft Entra ID

This guide will help you enable SSO from Microsoft Entra ID so your users can securely log into Rely.io without creating new credentials.

PreviousSAML with Google WorkspaceNextSAML with Okta

Last updated 3 months ago

Was this helpful?

This process can only be fully achieved in collaboration with our team.

Exact instructions are provided in the impacted sections below where this exchange of information is required.

Create a new SAML App in Microsoft Entra ID

In order to connect your Microsoft Entra ID directory to Rely.io you need to create a dedicated App by following the steps below.

  1. Log into your . Please ensure you have permissions to create Enterprise Applications and configure SSO. If you don't have the necessary permissions please reach out to an Administrator.

  2. In the search bar, type Entra ID and select Microsoft Entra ID to navigate to the correct management panel.

  1. In your directory page go to Enterprise Applications.

  1. On the top menu bar select New Application and then Create your own application.

  1. Now, specify the name that you would like to give to your application and select the last option as we want to integrate with an application you don't manage and doesn't exist in the Entra Gallery.

  1. Now that the Enterprise Application is created we can start the SSO configuration with SAML. Go to Single sign-on > SAML.

  1. To proceed with the SSO configuration is important that you specify the Identifier and the Reply URL on the Basic SAML Configuration section. Click the Edit button and provide the following values:

    1. Identifier (Entity ID): urn:auth0:relyio:<connection-name>

  1. (Optional) On step 2 - mapping - you can map additional properties such as groups. By default the email, full name, first name and last name are already mapped.

  1. Now we need to gather some information to provide Rely.io's team for configuration on their side. Start by downloading your certificate in .pem format. On step 3, click on Edit, then select the three dots next to the Active certificate and down the PEM certificate.

  1. Then, copy the Login URL and store it somewhere safe.

  1. Send the SSO URL and Certificate to Rely.io via one of the following means:

    1. Direct outreach to your dedicated Customer Success Manager

    2. In Slack via your Dedicated Channel (for Enterprise customers)

    3. Via your in-product chat bot

    4. Via email to support@rely.io

  2. You will receive in return a confirmation once all configurations are done on Rely.io's side.

  3. Once you get the confirmation, move to the final step of the wizard to test that the configuration worked.

That's it! You're SAML Connection to Rely.io from Microsoft Entra ID is now ready for your users to use.

Reply URL (ACS URL):

🛡️
https://auth.rely.io/login/callback
Microsoft Azure Portal
Navigate to Microsoft Entra ID
Navigate to Enterprise Applications
Create new application
Finalize creation process
Select SAML for SSO method
Configure Basic SAML Configuration
Add group information to your SAML payload
Download .pem certificate
Copy Login URL