List of operations Synced to Autotask

List of operations Synced to Autotask

To ensure accurate and up-to-date subscription management, CloudCockpit can synchronize the following operations to Autotask.

Update Subscription: Quantity

When a subscription's quantity is changed in CloudCockpit, a contract service adjustment is created in Autotask for the effective date of the change.
  1. Multiple adjustments on the same day will be overridden by the last change.
  2. If a promotion is applied to the updated subscription, the unit cost and price will be adjusted according to CloudCockpit's promotion settings.
  3. Changes to the billing cycle, friendly name, or auto-renew settings are not supported in Autotask and will result in a failed audit record for the connection operation.
AlertNotes
Note: Contract service adjustments should be done only through CloudCockpit. If you manually adjust contract services via Autotask, CloudCockpit will not be held responsible.



Update Subscription: Price Margin

When the price margin of an active or suspended subscription is updated, a contract service adjustment is created in Autotask for the start date of the billing period in which the change occurred.
  1. Adjustments for already approved billing periods take effect in the next period.
  2. Updates to Azure Plans price margins do not create adjustments in Autotask as fixed costs for Azure Plans are not supported.




Cancel Subscription

Canceling a subscription in CloudCockpit creates a contract service adjustment in Autotask, setting the subscription units to 0.
Alert
Users should be cautious as manual adjustments in Autotask can lead to overbilling.
Cloudcockit is not responsible if someone manually updates the contract service units in Autotask after the subscription was canceled.





Suspend Azure Plan

Suspending an Azure Plan creates a contract service adjustment in Autotask, setting its price to 0 for the subsequent billing periods. 
Alert
  1. Reactivating the plan in CloudCockpit does not affect Autotask, and manual adjustments can lead to overbilling.
  2. Suspending a Microsoft License Legacy subscription in CloudCockpit does not cancel the contract service in Autotask. See details about unsupported operations below.




Update Customer Margins

  1. Updating a customer’s provider margins will adjust the revenue of mapped active or suspended subscriptions in Autotask with an effective date matching the margin update completion date.
  2. Custom price margins on subscriptions are not affected.




Unsupported Operations for Subscriptions Mapped in Autotask

Subscription upgrades

Not supported.
If a subscription was upgraded, it's necessary to manually map the new subscription that originated from the upgrade and adjust the quantity of the old subscription in Autotask.


Subscription Renewal

Currently, price changes on the offer are not reflected in the contract service in Autotask upon renewal, therefore you are responsible for manually updating the price on the contract service.
The contract is not renewed, nor is its end date extended, you are responsible for manually extending the contract's end date.

Subscription Expiration

Currently, when a subscription expires, the respective contract service won't get canceled on Autotask, therefore you are responsible for manually adjusting its quantity to 0, on the next day after the end date of the subscription.
For example if you had a subscription whose creation date is 25th of November 2021 and its end date is 24th of November 2022, then the adjustment should have an effective date of 25th of November 2022.

Suspending a Microsoft License Legacy Subscription

Does not cancel the contract service in Autotask. The quantity is not adjusted to 0, even though billing stops in Microsoft.
Manual adjustment in Autotask is necessary.


Updating the Associated Reseller of a Subscription

Does not cancel the contract service of the original Reseller or CSP in Autotask.
Manual adjustment is necessary.


Operations Failed to sync to Autotask

If an operation fails to sync, the subsequent operations that are performed are not blocked and will still be sent to Autotask.
As a precaution, users should manually sync operations, before executing additional operations on the subscription.

Why Manual Syncing is Necessary:
  1. Previous failed sync operations may prevent proper synchronization.
  2. Avoids potential conflicts and data overwrites.
  3. To ensure proper billing.


    • Related Articles

    • Resolving Autotask Sync Failures

      If automatic sync fails, users should perform a manual sync before performing additional operations on the Subscription. When an operation fails to be automatically synced to Autotask, it will not prevent follow-up operations from happening. Why ...

    • Connect to Autotask Instance

      Follow these steps to establish a connection between CloudCockpit and your Autotask instance. This integration is only available for CSPs and Resellers. Review Related Documentation Before initiating the connection to your Autotask instance, ...

    • Map New Subscription to Autotask

      When you purchase a subscription on CloudCockpit, it can be directly mapped to an Autotask Contract. This ensures that no other steps are needed, saving users from having to visit the Subscription Mapping page later. A Subscription can only be mapped ...

    • Map CloudCockpit Offers to Autotask

      Follow this guide to map your CloudCockpit Offers to Autotask Recurring Services. Integrating CloudCockpit with your Autotask Instance requires mapping each Offer, acquired by your Customers, to the corresponding Autotask Services with matching Terms ...

    • Map Existing Subscriptions to Autotask

      Follow the steps outlined below to map existing CloudCockpit Subscriptions to Autotask Contracts. Autotask Contracts specify a billing arrangement with a Company during the contract's duration. Recurring Service Contract is the most common Autotask ...