Skip to main content
Setup has three phases: configure your partner tenant, connect in Rallied, then onboard each customer tenant. For what the agent can do once a tenant is ready, see Microsoft 365 agent tools. You need Global Administrator or Privileged Role Administrator in your partner tenant, and MSP integration access in Rallied. See Who needs which role for each step.
Already running CIPP? Connect it and Rallied approves every customer tenant for you in Phase 3.

Phase 1: Configure the MSP’s partner tenant

You do these steps once, in the MSP’s own Entra tenant.

1. Create an app registration

  1. Sign in to entra.microsoft.com with your partner tenant admin account.
  2. Go to Applications → App registrations → + New registration.
  3. Fill in the form:
    • For Name, enter something recognizable, such as Rallied Integration. This display name appears in role pickers across all customer tenants.
    • For Supported account types, select “Accounts in any organizational directory (Multitenant)”.
    • For Redirect URI, add one of type Web, with any URL you control (for example, your Rallied URL). Rallied doesn’t use it at runtime, but Phase 3’s admin-consent step needs one registered.
  4. Click Register.
  5. On the Overview page, save the Application (client) ID and Directory (tenant) ID. You need both to connect in Rallied.

2. Generate a client secret

  1. In the app registration, go to Certificates & secrets → + New client secret.
  2. Set a description (for example, Rallied production) and an expiration (24 months recommended).
  3. Click Add.
Copy the secret Value immediately. It disappears after you navigate away from this page.

3. Add the API permission

Go to API permissions → + Add a permission → Microsoft Graph → Application permissions and add Directory.Read.All. Rallied uses it to list your customer tenants from your partner tenant. It also reads what your app declares, so Rallied can tell you before each tenant approval if a permission is missing from the app. It’s the only permission you need to connect.
Azure lists Delegated permissions and Application permissions as two separate tabs with the same permission names under each. Add this one under Application permissions.
Rallied grants everything else in each customer tenant after you connect. See Permissions Rallied requires. Still on the API permissions page:
  1. Click Grant admin consent for [your organization] at the top.
  2. Confirm in the dialog.
  3. Check that the Status column shows a green checkmark (“Granted”) next to Directory.Read.All.
Granting consent requires Global Administrator or Privileged Role Administrator in the partner tenant. Cloud Application Administrator isn’t enough for Microsoft Graph application permissions.

Phase 2: Connect in Rallied

  1. In Rallied, go to Settings → Integrations → Microsoft 365.
  2. Click Connect.
  3. Enter the Application (Client) ID and Partner Tenant ID from Phase 1, Step 1, and the Client Secret from Phase 1, Step 2.
  4. Click Submit.
Rallied validates the credentials by acquiring an app-only token from Microsoft Entra ID. If that works, the integration shows as connected.

Phase 3: Onboard customer tenants

Right after you connect, Rallied opens a two-step guided setup on the Companies tab. On a fresh connection, it runs through to the end. If you come back to it later from the Continue setup banner, you can leave with Exit setup.
The Microsoft 365 Companies tab in Rallied, listing customer tenants with their status

Step 1: Sync tenants

This step starts on its own. Rallied lists every customer tenant your partner tenant has delegated access to. Each tenant starts as Not yet consented. The setup continues once at least one tenant is listed. If Microsoft returns none, add the partner relationships in Partner Center and click Sync again. Later, Sync from Microsoft picks up new tenants.

Step 2: Choose how Rallied gets access

Pick one of the two options in the guide. You only do this once per MSP.
Click Connect CIPP and enter its credentials. Rallied then pushes admin consent into your tenants through CIPP, and rows go from Processing… to Ready. See CIPP for the credentials and what CIPP adds.
With CIPP, directory roles aren’t part of a tenant’s status.

Change the access method

On the Companies tab, click Change next to Access method: Through CIPP or You approve each tenant to reopen the two cards. To move to CIPP, pick it and connect CIPP there. To leave CIPP, pick Approve yourself, disconnect CIPP with Manage CIPP, then add the two permissions.

Step 3: Approve your tenants

The setup then points at the first tenant’s Grant admin consent button, one click per tenant. The header counts tenants, for example 12 companies · 8 ready · 3 with an update available. Hover a status to see the exact permission or role it’s waiting on. Details on the row shows three things:
  • Permissions lists every application permission and directory role the app holds there, directly or through a group. Rallied reads it live from Microsoft Graph.
  • History lists every consent, permission, and role Rallied pushed, granted, or found.
  • The last check time.
For a consent push, History also records what Rallied asked for, what the tenant held right before, and what landed. When nothing landed through CIPP, History also shows the lines CIPP’s logbook wrote for that tenant and what CIPP’s access check says about its GDAP relationship. Rallied keeps statuses current on its own. Sync from Microsoft runs the full check right away.
Microsoft caches role permissions for 30 minutes to 2 hours after a role is assigned. A tenant can read Finishing setup… for a while after Rallied assigned the role, and tools may return 403 during that window even when everything is correct.

Which roles count

With User-PasswordProfile.ReadWrite.All approved, the Rallied app resets a non-admin user’s password with no directory role. Roles still matter for enabling, disabling, and deleting users, for tenants whose approval predates that permission, and as the second path for resets. MFA resets need no role. Rallied assigns User Administrator when it sets a tenant up itself. If you assign roles manually, use one of these: The verification records which role it found.
If Microsoft refuses a user change with 403 Authorization_RequestDenied, Rallied retries it through CIPP when CIPP is connected. Otherwise the step fails after the technician’s approval. The agent then escalates the ticket and names the tenant and the role to assign. Rallied doesn’t refuse the request up front based on its own records. The next check after you assign a role corrects the status.

Alternative: assign the directory roles manually

Without the two Step 2 permissions, consent still works, but Rallied can’t assign roles. Assign them yourself in each customer tenant. You need Privileged Role Administrator there.
  1. In Entra, go to Identity → Roles & admins.
  2. Open the role:
  3. Click Add assignment.
  4. Switch the picker to show service principals, and add the Rallied app.
The row moves to Ready on Rallied’s next daily check, or right away after Sync from Microsoft.
When a tenant reads Ready, the agent can manage users, groups, passwords, and mailboxes for that customer. To confirm, ask it to list users or distribution groups for that company.

Permissions Rallied requires

Nothing to add on your side. With either option in Phase 3, Step 2, Rallied grants these in each tenant itself. If neither works for your MSP, add them to the app registration yourself (API permissions → Add a permission, type Application) and click Grant admin consent on each tenant’s row.
Rallied also needs the Exchange Administrator and User Administrator roles on its app. See Which roles count. When Rallied adds a permission here, earlier tenants show Ready · update available. See the status table. The check before each approval also tells you if anything in this list is missing from the registration.

Who needs which role

Troubleshooting

Rallied authenticates with a client secret and no signed-in user, so Delegated permissions produce a token with no real access. Adding them by mistake in Phase 1, Step 3 doesn’t error until you sync tenants or run tools. Remove the Delegated ones, re-add them under Application permissions, and grant admin consent again.
Allow for propagation either way. The next check records the role once Microsoft shows it.
msgraph-get-site-permissions needs Sites.FullControl.All, which this tenant’s approval predates. The row reads Ready · update available. See the status table. With CIPP or the two Step 2 permissions, Rallied also applies it the moment a tool call is refused there. Otherwise add the permission to the app registration and click Grant admin consent on the row. Rallied tells you before the page opens if it isn’t declared yet.
Assigning a directory role (Exchange Administrator, User Administrator) in the partner tenant doesn’t grant that role in customer tenants. Each customer tenant needs its own assignment.
To run consent and role assignment through GDAP without a customer admin, the GDAP relationship must include Global Administrator or Privileged Role Administrator. Check your GDAP template before you start.
Role permissions take up to 2 hours to propagate. Wait for the next daily check, or click Sync from Microsoft.
The display name you set in Phase 1, Step 1 is what appears in role pickers across all tenants. If you can’t find it, search by the Application (client) ID instead.
AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID...Rallied needs the secret Value, not the Secret ID shown next to it. If in doubt, generate a new secret and copy the Value before you leave the page.
Consent grants only what the app declares at that moment. If you added the permission later, or as Delegated, the approval didn’t include it. Rallied warns about this before opening the Microsoft page. It reads your app registration with the Directory.Read.All permission granted at connect time. In your partner tenant, check App registrations → the Rallied app → API permissions for the permission with type Application and status Granted. Then approve the tenant again as a Global Administrator or Privileged Role Administrator of that tenant, directly or through GDAP.
Rallied added a required permission since this tenant approved. Everything already approved keeps working. See the status table row. A line above the table lists all affected tenants.
Microsoft normally reflects a consent within a minute or two, or up to 15 minutes through CIPP. If you closed the Microsoft consent page without approving, the row clears within a few minutes and Grant admin consent comes back. A CIPP push that hasn’t landed after 15 minutes goes back to Not yet consented with the cause on the status. Rallied looks once more an hour later.
For CIPP issues, see CIPP troubleshooting.