Microsoft CSP Integration

Your CSP customers,
users, and licences.
All inside Halo.

Halo connects directly to your Microsoft Partner Center. Your CSP customer list becomes Organisations in Halo. Their users sync automatically. Their licence and subscription data is visible on every record.

Map your customers to Halo once. After that, the Halo Integrator keeps users and licences in sync automatically — no ongoing maintenance, no switching between Partner Center and your service desk.

Talk to us about the CSP integration View all integrations →

Halo ITSM — Organisation

Acme Corp

CSP Synced

47

Users synced

3

Subscriptions

3

Seats available

Microsoft Subscriptions

Microsoft 365 Business Premium
50 licences +3 free
Microsoft Intune
50 licences Included
Azure Plan
● Active

Synced automatically via the Halo Integrator

What Syncs

Three things Halo pulls from
your Partner Center. Automatically.

Connect once. Halo does the rest — keeping your service desk in sync with the actual state of your CSP customer estate.

Customers → Organisations

Your CSP customers mapped to Halo Organisations

Each Partner Center customer is mapped to a Halo Organisation via the Tenants tab — a one-time setup per customer. Manual mapping is recommended to avoid duplicates. Once mapped, the Halo Integrator keeps everything in sync. An optional setting can auto-create new Organisations when new tenants are detected.

Users → Contacts

Each customer's users sync into their Organisation

Halo syncs users from each customer's Entra ID tenant into the corresponding Halo Organisation as Contacts. Joiners are created automatically. Leavers are deactivated. The result is a live, accurate user list per customer — without anyone maintaining it manually.

Licences → Organisation Records

Licence and subscription data visible on every customer

Halo imports the Microsoft subscription and licence data for each customer — what they have, how many seats are assigned, and how many are available. Visible directly on the Organisation record. No Partner Center tab required.

Why It Matters

The problems MSPs face
without the integration.

Without a live connection between Partner Center and your service desk, you're working from stale data — and that has real consequences.

📋

Stale customer records

Customer and user lists in the service desk drift out of date. New customers aren't in Halo. Leavers still have open contacts. Someone has to maintain it manually — and usually doesn't.

🔀

Tab-switching to check licences

A customer asks about their M365 seats. The technician leaves Halo, opens Partner Center, finds the customer, checks the subscription. A two-minute distraction for every licence question.

⚠️

Supporting out-of-contract users

Without contract visibility in Halo, technicians support whoever raises a ticket — including users who've left the contract scope. Billing disputes and out-of-contract support follow.

🕐

Manual onboarding overhead

Every new CSP customer means someone manually creates an Organisation in Halo, imports users, and sets up the record. With 20, 40, or 80 customers, that overhead is significant.

The CSP integration eliminates all four.

Connect Halo to your Partner Center once. Customers, users, and licences stay in sync automatically from that point forward.

How It Works

Set up once. Syncs continuously.

The integration uses two Azure app registrations — one for partner-level access to your CSP portal, one for accessing each customer's tenant via GDAP. Allied ESM configures both as part of your Halo implementation.

1

Partner Center connection — Single Tenant app

A single-tenant Azure app registration connects Halo to your Microsoft Partner Center. This is how Halo retrieves your full managed customer list and their associated subscription data. This app operates at the partner level — it sees across your entire CSP estate.

2

Customer tenant access — Multi-Tenant app via GDAP

A multi-tenant Azure app registration uses your existing GDAP relationships to access each customer's Entra ID tenant. This is how Halo syncs users from individual customer directories. GDAP is the current Microsoft standard for CSP partner access, supported in Halo from version 2.108.

3

Map customers to Halo Organisations manually

In the Tenants tab of Halo's CSP configuration, you map each Partner Center customer to the correct Halo Organisation. Halo recommends doing this manually to avoid duplicates — particularly if customers already exist from other processes. There is an optional setting to auto-create new Organisations when new tenants are detected, but it is off by default.

4

Enable the Halo Integrator

Once you're happy with your configuration, you enable the Halo Integrator and select which modules to sync: Tenants, Licences, Users, Assets (Intune devices), and optionally Consumption Billing. This switches on automatic synchronisation — Halo recommends enabling it only after you've validated the setup manually first.

5

Users, licences, and devices stay in sync automatically

With the Integrator running, users from each customer's Entra ID are synced into their Halo Organisation — joiners created, leavers deactivated. Microsoft subscription data (licence names, seat counts, assigned vs available) is visible on every Organisation record. Intune devices sync into the CMDB per customer. No ongoing manual maintenance required.

FAQ

Common questions

Do we need to do anything in Partner Center to enable the integration?
You need to have GDAP relationships in place with your customers — this is Microsoft's current standard for CSP partner access and replaces the older DAP model. If you're already managing customers via GDAP in Partner Center, you have what's needed. Allied ESM will set up the two Azure app registrations required and configure the integration in Halo as part of your implementation.
Does Halo sync changes automatically, or is it a manual refresh?
Once you enable the Halo Integrator — a deliberate step recommended only after you've validated your configuration manually — the sync runs automatically. You choose which modules to include: Tenants, Licences, Users, Assets. Changes are picked up without further intervention. You can also trigger manual imports at any point from within Halo's CSP configuration screen. Halo also supports Azure Delta queries for incremental syncs, which allows user and group changes to be picked up more frequently without a full directory sync each time.
What happens to existing Organisations we've already set up in Halo?
Customer mapping is done manually via the Tenants tab in Halo's CSP configuration — Halo explicitly recommends this to avoid duplicates, particularly if customers already exist from CRM or other integration processes. You select each Partner Center customer and map it to the correct Halo Organisation. Allied ESM handles this mapping as part of your implementation, cross-checking existing records before creating anything new.
Does the integration support the new GDAP model or only legacy DAP?
Halo supports GDAP — it's been the standard since Halo version 2.108. The integration uses two separate Azure app registrations: one single-tenant app for partner-level Partner Center access, and one multi-tenant app for customer tenant access via GDAP. Legacy DAP is no longer recommended by Microsoft, and Halo's implementation aligns with the current GDAP model.
Can we use the integration to control which users can raise tickets in Halo?
Yes. Because Halo knows which users are covered under each customer's active Microsoft contracts, you can configure Halo to only allow contracted users to raise tickets. This gives you a clean contract compliance boundary — users outside the contract scope are flagged or blocked, depending on how you configure it.

Stop maintaining customer records
that go stale the moment you save them.

Allied ESM configures the Microsoft CSP integration as part of every Halo MSP implementation. Your Partner Center data flows into Halo — and stays current from day one.

Talk to Allied ESM View all integrations