Skip to main content
Connect your Duo MSP parent account and the agent handles Duo user requests in each customer’s subaccount, with a technician approving every change. The agent can look up a user, create one and email them the enrollment link, turn a user off or back on, update their details, and add or remove them from groups. A typical use is onboarding: a new-hire ticket ends with the user created in the right customer’s Duo and the enrollment email sent.

Prerequisites

  • A Duo MSP parent account, with one subaccount per customer. Rallied rejects a key from a single Duo account, because it can’t reach your customers’ subaccounts.
  • The Owner role in the parent account. Only an Owner can create an Admin API application.

How to connect

1

Create an Admin API application

Sign in to the Duo Admin Panel of your parent account. Open Applications → Application Catalog, find Admin API and click + Add.
2

Grant the subaccount permissions

Under Subaccount permissions, check Grant accounts - Read, Grant resource - Read and Grant resource - Write. Click Save. The boxes under Permissions apply to the parent account only, so Rallied doesn’t need them.
3

Connect Duo

In Rallied, go to Settings → Integrations, find the Duo card and click Connect. Enter the Integration key, Secret key and API hostname of the Admin API application.
4

Save and confirm

Click Connect. Rallied checks that the key can list your subaccounts and read inside them, then syncs them. The card shows Connected when it’s ready.
If Rallied says the key can’t list subaccounts, check that the application was created in the parent account and that Grant accounts - Read is checked. If it says the key can’t read inside them, check Grant resource - Read and Grant resource - Write under Subaccount permissions.

Mapping subaccounts to clients

When you connect, Rallied syncs the subaccounts of your parent account. Review how each subaccount maps to a Rallied client on the Companies tab of the integration’s detail page. Click Sync subaccounts to pick up customers you’ve added since. On a client’s ticket, the agent works only in that client’s subaccount. It fills in the subaccount ID automatically. End users can’t run any Duo tool.

How the agent uses it

A typical new-hire ticket asks to give the person access. The agent:
  1. Looks the person up by username or email, so it never creates a duplicate.
  2. Proposes the enrollment in its plan: the username, the work email and how long the link stays valid (7 days unless the ticket asks otherwise, up to 30).
  3. After a technician approves, sends the enrollment email and Duo creates the user.
For a leaver, the agent proposes turning the user off. A disabled user can’t sign in through Duo until someone turns them back on.
Users synced from a directory (Active Directory, Microsoft Entra ID or Okta) are read-only in Duo. For those users the agent explains in an internal note that the change belongs in the directory, instead of proposing it in Duo.
The agent never turns off MFA for a user, re-enrolls an existing user, deletes users, or removes phones. Do those in the Duo Admin Panel. For a lost or replaced phone, the agent lists the user’s current phones in its note so a technician can reset them. Duo isn’t used to verify who is asking. To confirm a requester’s identity with a push to their Duo Mobile app, connect Traceless.

Tools

Reads default to Auto. Every change defaults to Approval needed. To change a default, open the Policies tab on Settings → Integrations → Duo. See Approval settings.

See also