Cloudmore-Datto Autotask Integration FAQ

What is this integration about? How does it work?

Datto Autotask users can integrate their companies or accounts with Cloudmore to synchronize Microsoft billing reports from Cloudmore to Autotask.

What are the pre-requisites for this integration?

Disable any other third-party billing integration settings in your Datto Autotask portal to avoid duplicate contracts from being syncronized.

How can I enable this integration?

Please refer to our guide on detailed steps for integration.

When enabling the integration, why do I have to enter an identifier for product billing code.

When a product is created in Autotask, all products will be created with this billing code.

How do I map the Datto Autotask terms and functions to that in Cloudmore?

Please refer to the mapping of Cloudmore terms and its Datto Autotask equivalent here.

After configuring the integration, should I add the Datto Autotask service to each organization in Cloudmore?

No. There is no need to add the service separately to each organization. As long as the Microsoft 365 or Azure service is active for the organization in Cloudmore, any available billing data will be exported automatically.

How will Cloudmore know what data to export?

If the Microsoft 365 or Azure service is active and added to the Organization in Cloudmore, subscription billing data will be exported, provided the organization has a corresponding Datto Autotask company or account identifier setup in Cloudmore.

If there are subscription types (Azure, CSP 365, Marketplace, Perpetual Licenses etc) that should not be exported, they could be deselected during service setup in the Marketplace while still keeping the services added to the Organization in Cloudmore.

How and when are billing reports exported to Datto Autotask? 

A check runs every 24 hours to detect any new billing reports generated four days earlier, after which an export to Autotask is performed.

For example, if a check runs on October 10, it detects and exports a billing report generated on October 6 (four days prior).

What billing report data for CSP 365 is exported to Autotask from Cloudmore?

The unit cost price, unit sales price, and largest quantity for each subscription from the billing report are exported to Autotask as a contract charge.

Each subscription is checked to determine whether the product and subscription already exist in Autotask and updated accordingly. If they do not exist, the product and/or subscription are created in Autotask as a product and contract. Product pricing is taken from the broker price list and stored at the product level in Autotask.

What billing report data for Azure is exported to Autotask from Cloudmore?

Azure services and subscriptions from the billing report are exported, and Cloudmore will either create or update contracts.

Each type (for example, Azure Plans or Reserved Instances) is created as a single product in Autotask, and the unit cost price, unit sales price, and quantity are exported as a contract charge. Product pricing is not stored in Autotask.

Will all CSP 365 products be exported to Autotask if an export is done?

No. Microsoft 365 products from the broker price list are created or updated in Autotask only if the product is associated with a subscription on the current month’s billing report.

Will each Azure usage items be exported to Autotask?

No. A single product, named Azure Plan, is created that contains the total cost price and sales price as a single contract charge.

The same approach applies to Marketplace, Reserved Instances, Perpetual Licenses, and Software Subscriptions: one product or service is created and reused.

How are renewals handled in Autotask?

The existing contract’s end date is updated to the new end date.

How will companies or accounts be managed between Autotask and Cloudmore?

• To match Cloudmore organizations to Autotask companies or accounts, Cloudmore uses the Autotask account or company identifier stored as a custom property in Cloudmore, visible under each organization’s properties. This mapping is a manual process that must be maintained going forward. Please refer to the documentation here.

• If a new organization is created in Cloudmore, the Autotask company or account identifier should be added in Cloudmore in order for the organizations data to be exported.

• If there are any organizations where subscriptions should not be exported, the field should be left empty.

If I have an existing Autotask instance, what will happen to my existing contracts, services and products?

• Cloudmore will create new contracts and products. Contracts are created only if the subscription appears on the billing report.

• Do not delete contracts created by Cloudmore in Autotask without first confirming with Cloudmore, as data must remain synchronized. Any changes or adjustments made to contracts may be overwritten by subsequent exports if they differ.

Why do Azure Plans and Perpetual Licenses not contain actual subscription start and end dates?

• Subscription start and end dates are used to create contracts, except for Azure Plan and Perpetual License subscriptions.

• Azure Plans are consumption‑based, so the start date is set to the first day of the invoice month and the end date to 12/31/2099.

• Perpetual Licenses subscriptions do not have start and end dates, so the charge start and end dates are used instead.

Is it possible to have multiple subscriptions inside a contract?

No, every subscription will have its own contract in Autotask.