Current + Addigy integration

If you manage Apple devices, Addigy is likely your MDM. Current's Addigy integration is a view-only evidence feed into the SBR/QBR module — it brings your managed-Mac fleet's health into strategic business reviews without changing anything in Addigy. It reads, it never writes.

What the integration does

Current consumes read-only signals from Addigy and stages them as evidence for AI-assisted Strategic Business Reviews. When you review a partner's environment, you can speak to the Apple side of their fleet with the same confidence as the Windows side — device coverage and policy compliance become concrete proof points instead of a gap in the story.

What data flows

• Managed Apple devices — the enrolled Mac, iPad, and iPhone fleet under Addigy management.
• Policy and compliance signals — evidence that the policies you're paid to enforce are actually applied across the fleet.
• Fleet health — a rollup that fits alongside your RMM and security evidence in a single review.

The feed is one-way and read-only by design. Current does not push policies, enroll devices, or alter your Addigy configuration. Addigy stays the source of truth for Apple management; Current simply uses the evidence.

A note on real-world Addigy setups

Addigy deployments vary — a single organization, or several child organizations each carrying dozens of policies. Current's evidence feed is built to handle a hybrid structure, so a multi-org Addigy tenant with many policy rows is mapped in cleanly rather than forcing an all-or-nothing assumption about how your account is shaped.

Why it matters

Apple fleets are often the part of an SBR that gets hand-waved, because the data lives in a separate MDM from the rest of the stack. Pulling Addigy evidence into the same review as your RMM, backup, and security signals gives partners one honest, complete picture — and gives you a review that covers every device you manage, not just the Windows ones.

Why Apple fleets need their own feed

Most MSP tooling assumes Windows, and an Apple estate managed through Addigy is frequently invisible in the reporting that results. That gap shows up at exactly the wrong moment: a business review that undercounts a client's device fleet because the Macs were never in the export, or a coverage conversation that misses an entire platform.

Reading Addigy alongside your other management tools closes that gap, so device counts and fleet posture reflect what the client actually runs rather than the Windows half of it.

What this feed is

View-only. Current reads from Addigy for reporting and business reviews; it does not push policy, deploy software, or change device configuration. Management stays where it belongs.

Where the data appears

• In Strategic Business Reviews, so the fleet section counts the whole estate.
• On the company record, giving account managers accurate device context.
• In endpoint counts, where an Apple fleet managed separately would otherwise be missed.

Matching matters

The practical work in any multi-tool fleet count is matching devices across systems so a machine managed by two tools is counted once. Where records can be matched confidently they are deduplicated; where they cannot, the count says so rather than silently guessing. A device count you can defend is worth more than a tidy one you cannot.