Dynamics 365 Call Intelligence Minutes Add-on — Pricing, Plans & Prerequisites

Dynamics 365 Call Intelligence Minutes Add-on is a paid Commercial add-on SKU for customers who need additional Dynamics 365 Call Intelligence Minutes. It is an add-on because the source offer identifies it as non-core, so it should be attached to a qualifying Microsoft environment rather than treated as a standalone Dynamics 365 application.

No, Dynamics 365 Call Intelligence Minutes Add-on is not a standalone core Dynamics 365 application because it is categorized as an add-on. Before buying it, a Commercial customer should confirm the required Dynamics 365 base license or prerequisite workload with IT Partner.

The Commercial offer includes a paid Dynamics 365 Call Intelligence Minutes Add-on SKU with monthly or annual commitment options. The exact number of minutes, reset period, pooling behavior, assignment scope, and exhaustion or overage behavior are not provided in the source pack, so those details should be confirmed before ordering.

Dynamics 365 Call Intelligence Minutes Add-on does not include a standalone Dynamics 365 application, a trial, or confirmed base-license entitlements because the source pack lists it only as a paid add-on. It also should not be assumed to include telephony service, carrier charges, calling plans, phone numbers, or phone system configuration unless those are separately confirmed for the tenant.

No, you should not assume Teams Phone, calling plans, carrier services, or phone numbers are included because the offer is specifically a Dynamics 365 Call Intelligence Minutes add-on. If your scenario uses Teams, a contact center, or a calling provider, confirm the required telephony licensing and integration separately before purchase.

No, this add-on should not be treated as a Copilot license because the listed product is only Dynamics 365 Call Intelligence Minutes Add-on. If your call intelligence scenario depends on Copilot, sales conversation intelligence, or AI-generated summaries, confirm the required Copilot and Dynamics 365 licenses separately with IT Partner.

The required base license is not specified in the source pack, so a buyer should confirm prerequisites before ordering. This matters because add-ons normally require a qualifying parent service, and buying the add-on without the correct Dynamics 365 entitlement may leave it unusable.

Choose monthly commitment when flexibility is more important than long-term commitment, because it generally allows the shortest commitment period. Choose annual paid upfront when you want the best relative rate among the listed Commercial options, and choose annual billed monthly when you want an annual commitment with payment spread across the term.

No, the current source pack does not list a trial for Dynamics 365 Call Intelligence Minutes Add-on. A Commercial buyer should plan this as a paid add-on purchase and validate prerequisites, minute quantity, and usage behavior before committing.

You should size the add-on based on expected call intelligence usage because the included minute quantity and pooling model are not stated in the source pack. Before buying, confirm whether minutes are tenant-pooled, assigned per user, tied to another scope, and whether unused minutes reset or carry over.

The source pack does not specify exhaustion, overage, throttling, or additional-purchase behavior, so you should not assume calls will continue with automatic overage. Confirm with IT Partner whether your tenant can buy more units, whether minutes reset on a defined cycle, and what user experience occurs when minutes are depleted.

Yes, Dynamics 365 Call Intelligence Minutes Add-on has a Commercial offer, so it is appropriate to evaluate for standard business tenants that meet the prerequisites. It should not be purchased until the qualifying Dynamics 365 license, supported workloads, countries or regions, languages, and telephony dependencies are confirmed.

This FAQ is for the Commercial segment, not GCC or GCC High, because government cloud availability and residency rules can differ from Commercial cloud offers. Government buyers should confirm the exact government-cloud SKU, data residency, compliance boundary, and supported calling scenarios before assuming this Commercial add-on applies.

A nonprofit should not assume the Commercial add-on is the right purchasing route because Charity eligibility, nonprofit discounts, and grant coverage are separate from standard Commercial licensing. The source pack indicates a Charity segment exists, but it does not state grant eligibility for this add-on, so nonprofit buyers should confirm the correct charity offer and any grant applicability with IT Partner.

Education customers should not assume the Commercial add-on is the correct license because student, faculty, and staff eligibility can use different Education offers and terms. The source pack indicates an Education segment exists, but student-versus-faculty entitlement details are not provided, so academic buyers should validate the correct segment and user population before purchase.

You should review call recording, monitoring, transcription, consent, retention, and HR/legal requirements because call intelligence scenarios can involve regulated communications data. The add-on purchase itself does not prove your configuration is compliant, so confirm policies, supported regions, and tenant settings before deployment.

No, you should not infer data residency from the add-on name because the source pack does not specify storage location, processing region, or compliance boundary. Data location may depend on the Dynamics 365 workload, tenant geography, connected telephony services, and Microsoft cloud environment, so confirm residency requirements before buying.

Start by confirming the qualifying Dynamics 365 base license and the add-on assignment or enablement model because the source pack does not define those mechanics. Then validate supported workloads, telephony integrations, calling providers, countries or regions, languages, and compliance settings before enabling users or scenarios.

Yes, a CSP transfer can typically be handled without service downtime when the customer tenant is kept in place and subscriptions are not cancelled before replacement or transfer is coordinated. The Microsoft service, data, and tenant remain with the customer; IT Partner should sequence the reseller relationship and licensing change so entitlement coverage continues.

Moving the CSP relationship to IT Partner should not change the Microsoft list price for the same Commercial offer, SKU, term, and billing option, because the underlying Microsoft subscription offer is the same. Partner services, taxes, currency handling, promotions, or commercial terms can differ, and renewal, cancellation, and quantity-change rules still follow the selected commitment term.

Cancellation and reductions depend on the CSP New Commerce commitment term because monthly and annual commitments have different flexibility. In general, annual commitments are not the same as month-to-month service even when billed monthly, so confirm the current cancellation window, renewal date, and reduction rules before placing the order.