Skip to main content

​
Microsoft Single Sign-On for Rogue

Enable seamless authentication for your team by connecting Rogue to your Microsoft Azure Active Directory. Once configured, your users can sign in with their existing Microsoft work accounts—no separate passwords to remember.
This integration allows your team to:
  • Sign in with their Microsoft work credentials
  • Maintain your organization’s security policies
  • Simplify user management through Azure AD

​
Prerequisites

You’ll need:
  • Admin access to your Azure portal
  • Authority to create app registrations in your organization
  • About 10 minutes to complete the setup

​
Setup Instructions

​
Step 1: Access Azure App Registrations

  1. Sign in to your Azure portal:
  2. Navigate to app registrations:
    • Search for “App registrations” in the search bar, or
    • Find it under Microsoft Entra ID (formerly Azure Active Directory)

​
Step 2: Create Your Rogue Application

  1. Click ”+ New registration”
  2. Configure your application:
    • Name: Enter “Rogue” or “Rogue Proposal Platform”
    • Supported account types: Select “Accounts in this organizational directory only”
    • Redirect URI:
      • Platform: Web
      • URI: https://app.userogue.com/auth/microsoft/callback
  3. Click Register to create your application

​
Step 3: Generate Authentication Credentials

​
Application ID

On the Overview page, locate and copy your Application (client) ID. This identifies your Rogue installation to Microsoft.

​
Client Secret

  1. Navigate to Certificates & secrets in the left menu
  2. Click ”+ New client secret”
  3. Add a description (e.g., “Rogue SSO”)
  4. Choose an expiration period (we recommend 24 months)
  5. Click Add
  6. Immediately copy the Value — you won’t be able to see it again
Store your client secret securely. If lost, you’ll need to generate a new one.

​
Step 4: Grant Required Permissions

  1. Go to API permissions in the left menu
  2. Click ”+ Add a permission”
  3. Choose Microsoft Graph
  4. Select Delegated permissions
  5. Check the box for User.Read
  6. Click Add permissions
This allows Rogue to read basic user profile information (name and email) when users sign in.

​
Step 5: Send Configuration to Rogue

Share these four pieces of information with your Rogue team:

Required Information
  • Azure Environment: Commercial or US Government
  • Tenant ID: Found on the Overview page
  • Application (Client) ID: From Step 3
  • Client Secret Value: From Step 3
Send these securely via:
  • Your preferred encrypted email service
  • A secure file transfer service
  • A phone call to your Rogue representative

​
What Happens Next

Once we receive your configuration:
  1. We configure your SSO (usually within 24 hours)
  2. We notify you when it’s ready
  3. Your team can start signing in with their Microsoft accounts
Users will see a “Sign in with Microsoft” button on the Rogue login page. Clicking it redirects them to your organization’s Microsoft login, then seamlessly back to Rogue.

​
Troubleshooting

​
”User not found” error

The user needs to be added to your Rogue organization first. Contact your Rogue admin to add them.

​
”Invalid redirect” error

Ensure the redirect URI is exactly: https://app.userogue.com/auth/microsoft/callback

​
Secret expired

Generate a new client secret in Azure and send it to the Rogue team.

​
Security Notes

  • Your credentials are encrypted and stored securely
  • We only request minimal permissions (user profile reading)
  • Users must still be authorized in Rogue to access your organization
  • You maintain full control through Azure AD

​
Need Help?

Contact your Rogue success team at success@userogue.com or through the in-app chat. We’re here to help you get your team connected.
⌘I