CIPP connects on its own, without a Microsoft 365 connection

If your shop manages Microsoft 365 tenants through CIPP, Rallied no longer needs its own Microsoft 365 connection before it can talk to CIPP. CIPP connects, edits, and disconnects on its own from the integrations tab.

What changed

CIPP has been a standalone integration since July, with its own card in the integrations tab and the same dialog reachable from the Microsoft 365 page. Until this week, opening that dialog on an MSP without Microsoft 365 connected returned an error, so the connect, edit, and disconnect buttons did nothing. That check is gone. CIPP now resolves its own credentials and works whether or not Microsoft 365 is connected.

Why it matters

Some MSPs run CIPP for tenant administration and never connect Rallied to Microsoft 365 directly. On those accounts the integrations tab showed an error toast on every visit and CIPP could not be configured at all, which meant no tenant list and no CIPP-backed actions. Those accounts can now set CIPP up in one visit.

What it does not do

It does not change who can do what. Token, role, and MSP access checks run exactly as before. Actions that read Microsoft 365 settings directly still need that integration connected.

Also in CIPP

The CIPP page has a read-only Companies tab that lists every tenant CIPP manages and flags the ones not yet onboarded in Rallied, so you can see the gap without opening CIPP. Because MSPs self-host CIPP and update it on their own schedule, Rallied also detects the CIPP version and shapes each request to match, with one retry when an install answers differently than expected.

How to turn it on

Nothing to switch on. Open Integrations, choose CIPP, and enter your CIPP URL and credentials. Setup details are in the docs at https://docs.rallied.ai.