Summary

  • Aligned Technology Partners describes capturing Microsoft licensing changes through Sherweb and Autotask as clients join or leave, instead of reconstructing them later.
  • The case's up-to-57% workload claim compares about three staff days with an estimated six-to-seven-day alternative; it is not a measured company-wide cost reduction.

Record the change before it becomes an audit task

A license added during onboarding should not have to be rediscovered at month-end. That is the operational idea behind the September 10 case published by Aligned Technology Partners and Sherweb. The North Texas MSP, formerly On-Site PC Services, says it supports more than 135 clients and separately manages more than 135 Microsoft contracts. Connecting Sherweb to Autotask is described as capturing licensing changes during onboarding and offboarding rather than reconciling them manually afterward. These are supplier-case claims, not inspected transaction logs. The case announcement.

The percentage needs its denominator. Existing licensing audits took around three staff days a month, according to the release. Adding Microsoft licensing review without integration was estimated to require another three to four days. The comparison is therefore work that would otherwise take six to seven staff days against about three with the integration. At the upper end, four days avoided out of seven gives roughly 57%. It does not establish that an observed seven-day historical workload fell to three, still less that payroll or total operating costs fell by 57%.

The more durable mechanism is earlier record capture. If a customer change reaches the right business record when it occurs, staff have less history to reconstruct later. Sherweb's public integration offering describes Autotask as synchronizing billing, proration and subscription details. That broad proposition, however, should be read alongside the field-level operating guide. Sherweb's integrations overview.

A cost update is not a pricing decision

The Autotask guide says Unit Cost is synchronized, whereas Unit Price must be configured manually in the service card. Frequencies also differ: recurring quota-based offers such as Microsoft 365 update immediately when changed in the portal; quantities for some usage-based products, including Azure, synchronize on the billing date. The guide requires offer and customer/contract mappings, distinguishes transaction dates according to the proration option and tells operators to resolve synchronization errors before billing. Its monthly configuration fields do not turn yearly-paid subscriptions into monthly-cancellable commitments. Autotask operating documentation.

Those distinctions keep commercial control visible. A new cost can arrive without a new customer price, and a usage record can have a different expected arrival time from a license-count change. Neither is evidence that this MSP has incorrect invoices. Both explain why an automated feed still needs an owner for mappings, dates, prices and exceptions.

The case describes a wider relationship: dedicated Microsoft support, account-by-account NCE reviews, a multi-year AWS-to-Azure migration and a transition of roughly 3,000 security endpoints. Those endpoints are not clients, and those projects are not the denominator of the licensing statistic. The September news is an account of ongoing operational support, not a newly signed partnership or proof that every business gain came from one integration.