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
- Sign in to entra.microsoft.com with your partner tenant admin account.
- Go to Applications → App registrations → + New registration.
- 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.
- For Name, enter something recognizable, such as
- Click Register.
- 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
- In the app registration, go to Certificates & secrets → + New client secret.
- Set a description (for example,
Rallied production) and an expiration (24 months recommended). - Click Add.
3. Add the API permission
Go to API permissions → + Add a permission → Microsoft Graph → Application permissions and addDirectory.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.
4. Grant admin consent
Still on the API permissions page:- Click Grant admin consent for [your organization] at the top.
- Confirm in the dialog.
- Check that the Status column shows a green checkmark (“Granted”) next to
Directory.Read.All.
Phase 2: Connect in Rallied
- In Rallied, go to Settings → Integrations → Microsoft 365.
- Click Connect.
- Enter the Application (Client) ID and Partner Tenant ID from Phase 1, Step 1, and the Client Secret from Phase 1, Step 2.
- Click Submit.
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.
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.- Connect CIPP
- Approve yourself
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 example12 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.
Which roles count
WithUser-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:
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.- In Entra, go to Identity → Roles & admins.
- Open the role:
- Exchange Administrator for distribution groups, shared mailboxes, mailbox permissions, and the forwarding and inbox-rule tools.
- User Administrator for password resets, user enable and disable, and deletion. Another role that allows them also works.
- Click Add assignment.
- Switch the picker to show service principals, and add the Rallied app.
Permissions Rallied requires
Who needs which role
Troubleshooting
Site-permission reads fail with Forbidden, but site search and everything else work
Site-permission reads fail with Forbidden, but site search and everything else work
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.Cloud App Admin / App Admin can't grant consent
Cloud App Admin / App Admin can't grant consent
Role assignments don't propagate between tenants
Role assignments don't propagate between tenants
GDAP template missing required roles
GDAP template missing required roles
Tools returning 403 after setup
Tools returning 403 after setup
App not appearing in role assignment picker
App not appearing in role assignment picker
Connect fails with an invalid client secret error
Connect fails with an invalid client secret error
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.Admin consent fails with no reply address registered
Admin consent fails with no reply address registered
AADSTS500113: No reply address is registered for the application.The app has no Redirect URI. On the app’s Overview page in Entra, click Add a Redirect URI, add any URL you control as type Web, and try the consent again.I approved a tenant but the permission is still missing
I approved a tenant but the permission is still missing
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.Status shows Ready · update available for a tenant that was fully set up
Status shows Ready · update available for a tenant that was fully set up
A row is stuck on Processing…
A row is stuck on Processing…
Related
- Microsoft 365 agent tools
- CIPP
- GDAP least-privileged roles by task (Microsoft)
- User and admin consent overview (Microsoft)
- App-only auth in Exchange Online (Microsoft)