ImmyBot uses one Microsoft Entra app per MSP, added in ImmyBot as a user. Connect it once and every agent you enable can use it, with permissions you control per agent.
What Neo can do with ImmyBot
Software on demand
Install, update, repair or remove one piece of software from your ImmyBot library on a named computer, through a maintenance session.
Computers and inventory
Find the computer by name or by its user, and read its installed software, online status and primary user.
Maintenance results
Read each session and action with its logs, report the action that failed, and rerun a session or one action.
Scripts
Run a short script on one computer for a check or a fix that no library item does, and read its output.
Your clients are mapped automatically
Each ImmyBot tenant is one of your clients. Neo matches your ImmyBot tenants to the companies in your PSA and keeps the mapping on the ImmyBot card’s Organization Mapping tab, refreshed on each PSA metadata sync. Your own MSP tenant is left out. Neo first matches a tenant by the Azure tenant it is linked to in ImmyBot, against the Microsoft 365 tenant Neo holds for a company. A tenant with no such link is matched by name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). When two PSA companies share the name, Neo leaves the tenant for you to map, because the mapping decides which client’s computers an agent works on. Last comes an AI match for the long tail. An Azure or name match, or one you confirm, is handed straight to your agents, so they look for the computer in the right tenant. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.Next steps
Connect ImmyBot
Create a Microsoft Entra app, add it in ImmyBot as a user, save it in Neo and turn ImmyBot on for your agents.