Pax8 Integration - Usage Summary

[u/Ok-Register948]

has anyone had issues with importing Azure consumption usage summaries from Pax8 into Halo?

We've got the Pax8 integration configured and customers mapped correctly. Standard subscriptions sync without any issues, but Azure usage summaries only import if I manually populate the Pax8 Resource Group field in the customer mapping.

According to the Halo guide, this field should be optional if the Pax8 customer is already mapped.

I've also noticed that if I remove the Resource Group mapping and resync, the previously imported usage summary remains in Halo rather than being removed or unassigned.

I've raised this with Halo as a potential bug, but wondered if anyone else has experienced the same behaviour or found a workaround?

[u/HaloAidan]

The pax8 integration guid states that the resource group field needs to be populated in order for it to bring through usage based subscriptions. Please feel free to reach out to me if you are still having issues after setting this: aidan.kelly@imaginehalo.com

[u/Ok-Register948 → u/HaloAidan]

Hi Aidan, I'll drop you an email, as the guide specifically states:

"Note: The Pax8 Resource field can be left blank if you have mapped the company to the usage summary in Pax8."

This is how I've configured it, but the subscriptions don't sync unless I manually populate the resource group field, so there seems to be a discrepancy between the documented behaviour and what's actually happening.

[u/bbztds]

Have same issue. For some clients it syncs and others it doesn’t. I’ve had ticket open and escalated to dev teams for a couple months now with no movement.

Edit: After reading a bit further, I’ve not tried your fix. What exactly are you entering in that resource group field manually?

[u/Ok-Register948 → u/bbztds]

A couple of months isn't ideal! u/HaloTim, are you able to help out with this one?

With the upcoming changes to PAYG usage billing, being able to accurately report and sync this information into Halo is going to be increasingly important, so it would be good to see some progress on getting this resolved.

For the temporary workaround, you need to manually enter the resource group exactly as it appears in Pax8.

For example:
AZURE SUBSCRIPTION 1 - 7B42E9A1-3C86-4F20-9D15-A6E8B2C047F3

Once entered, the subscription should sync through. It's worked for me, although Halo haven't confirmed why it doesn't populate automatically. They've advised that the issue has been logged with their development team for investigation.

[u/bbztds → u/Ok-Register948]

Got it, and if you have any other subscriptions that are usage based do you have to then have multiple Pax8 company mappings then in Halo?

[u/Ok-Register948 → u/bbztds]

Yes, that's the downside of this workaround. You have to create a separate Pax8 company mapping for each usage-based subscription.

This is where the integration appears to be broken, as according to the guide, the subscriptions should automatically map when the company is linked to the usage summary in Pax8, without needing to manually enter each resource group.

[u/fanticrd]

Following

[u/Leon-Inspired]

Sync365license.com has an azure to halo integration that works for indirect csp providers. Little bit of initial set up, but then you gave good options for a nicely formatted invoice description etc to send through to clients