Prerequisites
- An ImmyBot instance, such as
acme.immy.bot, with your customers set up as tenants. - An administrator in the Microsoft Entra tenant you sign in to ImmyBot with, to create an app registration.
- An ImmyBot administrator, to give that app a user and a role.
How to connect
ImmyBot’s API uses a Microsoft Entra app registration. You create it in your own Entra tenant, then let it into ImmyBot.1
Create the app registration
In the Microsoft Entra admin center of the tenant you sign in to ImmyBot with, open App registrations and click New registration. Name it (for example, Rallied ImmyBot), keep Single tenant only as the supported account type, leave the redirect URI empty and click Register. On the app’s Overview, copy the Application (client) ID and the Directory (tenant) ID.
2
Create a client secret
On the app, open Certificates & secrets and click New client secret. Copy its Value, not its Secret ID. Entra shows the value only once.
3
Copy the app's Object ID
Open Enterprise applications, find the same app and copy its Object ID. This is a different ID from the app registration’s.
4
Add the app as a person in ImmyBot
In ImmyBot, open Settings → People and click New. Enter a first name, a last name and an email (ImmyBot requires one; any label works, such as
immybot-api@yourdomain.com), paste the Object ID into Azure Object ID, and click Create.5
Make that person a user with a role
Open Settings → Users & Roles and click Add New User. Select the person you created and click Create Users. Under Direct Role Assignments, give it a role that can see every tenant and run scripts, such as System Administrator (Legacy), and click Assign.
6
Connect ImmyBot
In Rallied, go to Settings → Integrations, find the ImmyBot card and click Connect. Enter your ImmyBot instance (
acme for https://acme.immy.bot), the Directory (tenant) ID, the Application (client) ID and the Client secret, and click Connect. The card shows Connected when it’s ready.Mapping tenants to clients
When you connect, and once a day after that, Rallied syncs the tenants in your ImmyBot instance. A tenant Rallied can’t link by itself waits for you: click Match companies at the top of the integration’s detail page and pick its client. The Companies tab lists the linked tenants. Click Sync from ImmyBot there to pick up tenants you’ve added since. Rallied doesn’t list:- Your own MSP tenant. It’s never a client.
- Inactive tenants, or tenants marked for deletion. If a tenant is missing, check that it’s active in ImmyBot, then sync again.
How the agent uses it
A typical “my computer is missing an app” ticket goes like this. The agent:- Finds the computer by name, serial number or user, and checks whether it’s online.
- Reads what ImmyBot says needs attention and the latest result of each maintenance item, then the logs of the session that failed.
- Searches your ImmyBot software library for the app.
- Proposes installing it on that computer and waits for a technician’s approval.
- After approval, starts the deployment and notes the ImmyBot session on the ticket.
- Comes back on its own to check the session, then reports the result and finishes the ticket.
Running PowerShell
When the read tools and your library can’t answer or fix the problem, the agent can propose a PowerShell script it wrote. The script runs on that one computer, as SYSTEM, and the agent gets its output back. It never runs on the ImmyBot server.- Every script needs a technician’s approval, even when you set the tool to Auto, and a workflow can’t approve it in advance.
- The approval shows the full script and a script analysis of what it reads and changes.
- A script stops after 60 seconds.
Limits
- The agent installs an app, or updates it to the latest version. To install a specific older version, use ImmyBot.
- The agent doesn’t uninstall software, run tasks that take parameters, onboard computers or move them between tenants. A technician does those in ImmyBot.
- The agent doesn’t create or change deployments. It reads the deployments made for a client’s tenant only, not those that target several tenants.
- A session can be re-run only when it maintains one item, not a full maintenance or onboarding run, and its own settings suppress reboots, install no Windows updates, email no one, skip offline computers and reach no other tenant. Otherwise the agent deploys the app or runs the task again instead.