So I’ve been tasked with creating a complete solution to keeping our Microsoft Partner Center licenses and Autotask contracts in sync for all our customers.
There’s a lot of 3rd party offerings out there, but none of them exactly fitted our needs - or demanded an absolute fortune for features we wouldn’t be using at all.
PSUniversal to the rescue.
The homepage
Should speak for itself. It’s the home page after all 
NCE Subscriptions
Where most of our employees would find all relevant information about active subscriptions for each customer tenant.
The first section shows a few details about the selected customer tenant.
- Tenant name (+ tenant domain)
- Last subscription sync timestamp
- Quick links to the related Partner Center page for the selected tenant and the respective Autotask company details
Autotask Mapping - Customers
This is where the configurations are taken care of by the employees with the required role to do so.
Not everyone has access, for obvious reasons.
Here we see the mapping status for all tenants to their respective Autotask Company, or if they were configered to be ignored entirely.
There’s also an indicator for when there is no mapping yet.
The actions column has the same quick links to Partner Center, Autotask Company details, editing the configuration and to copy the tenant Id to the clipboard (which is only visible to a few roles, for QoL purposes)
To edit the mapping configuration for a tenant that is set to “Ignored”, the following modal pop ups:
Which allows the user to undo the Ignore setting or reset all mapping configurations entirely for this tenant. When the configuration changes, the user will immediately have the ability to select the Autotask Company to map the tenant to instead.
When editing the mapping for an already mapped tenant, the modal shows accordingly:
This behavior and functionality is then also available for mapping the Microsoft Offerings/Subscriptions to their respective Autotask Services, with the additional option to create the service if none is found in Autotask that fits the templated/pre-defined naming scheme.
Autotask Mapping - Contracts
Where the fun actually began… 
Bla bla bla...
When the customer/tenant is selected, all subscriptions will be sorted into “Suggested Contracts”, based on their Term (P1M, P1Y, P3Y) and respective Term Start Date + Term End Date.
A tenant might have multiple monthly term subscriptions, all starting on a different day of the month - making them incompatible to be used on the same Autotask contract - that will renew every month on a set date.
Thus, the subscriptions will only be on the same contract when the start and end date align.
When the subscriptions are not yet found on an active contract in Autotask, the tool will present the option to create it. If all subscriptions are on a contract, the user will be able to open that contract in Autotask or force the contract to update.
Updating a contract might be required when one of the shown subscriptions indicates an error in the “On Contract” column, or the table shows a red exclamation mark in the “Quantity” column - caused by the sync job not being run yet (in the background).
There’s a lot more to talk about that goes on in the background, but as this has already become quite the large post - I’ll leave that for any conversations outside of this topic