IoT Intelligence — Pricing, Plans & What's Included

IoT Intelligence is a Commercial Microsoft add-in family for Dynamics 365 Supply Chain Management, because the catalog offers Sensor Data Intelligence add-in SKUs rather than a standalone business application. It is intended to bring sensor-data intelligence into operations scenarios and to expand covered machine capacity through separate add-in options.

No, IoT Intelligence is not a standalone Dynamics 365 Supply Chain Management base license, because the available catalog entries identify it as add-ins for Dynamics 365 Supply Chain Management. A buyer should confirm the required Dynamics 365 Supply Chain Management base licensing and environment prerequisites before purchasing the add-in.

The Scenario Add-in licenses the Sensor Data Intelligence scenario option, while the Additional Machines Add-in is for expanding machine capacity, because Microsoft lists them as separate Commercial SKUs. Buyers should not assume the Additional Machines Add-in replaces the Scenario Add-in; confirm prerequisite sequencing and machine-count entitlement with IT Partner before purchase.

IoT Intelligence is best suited for Commercial organizations already using or planning Dynamics 365 Supply Chain Management sensor-data operations scenarios, because it is licensed as a Dynamics 365 Supply Chain Management add-in. It is especially relevant when the organization needs to enable the scenario itself or expand covered machine capacity.

IoT Intelligence is available with one-month, one-year, and three-year commitments in the Commercial catalog, because the source offer includes multiple term and billing combinations for both the Scenario Add-in and Additional Machines Add-in. One-month is paid monthly; one-year can be paid annually or monthly; three-year can be paid annually, monthly, or triennially depending on the selected SKU.

No trial is listed for IoT Intelligence in the available Commercial source data, because every listed SKU is a paid add-in offer and none is marked as a trial. If a proof of concept is needed, confirm technical pilot options, nonproduction environment plans, or implementation alternatives with IT Partner rather than assuming a Microsoft trial SKU exists.

IoT Intelligence includes the selected Commercial add-in SKU for Dynamics 365 Supply Chain Management, because Microsoft separates the Sensor Data Intelligence Scenario Add-in from the Sensor Data Intelligence Additional Machines Add-in. The purchase also includes the selected commitment and billing structure, but the exact operational entitlement depends on the SKU and should be confirmed before checkout.

IoT Intelligence does not include a standalone Dynamics 365 Supply Chain Management base license, because it is an add-in family. The available source data also does not confirm inclusion of Azure services, IoT devices, data ingestion, storage, Power Platform licensing, implementation services, or specific machine-count entitlements, so those should be validated separately.

The exact machine-count entitlement is not confirmed in the available catalog data, because the source identifies an Additional Machines Add-in but does not state whether it is per machine pack, per tenant, or another Microsoft-defined unit. A buyer should confirm the Microsoft-defined unit of measure, any included machine quantity, and expansion rules with IT Partner before ordering.

Possibly, but the prerequisite sequence is not confirmed in the available source data, because Microsoft lists separate Scenario and Additional Machines add-ins without detailing dependency rules. The safest licensing approach is to confirm whether the Sensor Data Intelligence Scenario Add-in is required before purchasing the Additional Machines Add-in.

No Teams or Copilot entitlement is listed as included with IoT Intelligence, because the source catalog only identifies Sensor Data Intelligence add-ins for Dynamics 365 Supply Chain Management. If users also need Teams collaboration, Copilot experiences, Power Platform, or related Microsoft 365 services, those should be licensed and configured separately as applicable.

Do not assume Azure IoT services, devices, gateways, data ingestion, or storage are included, because the IoT Intelligence catalog entries only describe Dynamics 365 Supply Chain Management add-ins. Technical architecture, Azure consumption, device onboarding, and integration services should be scoped separately before purchase.

A Commercial buyer should review Dynamics 365 Supply Chain Management security, tenant configuration, data residency, integration design, and sensor-data handling, because IoT Intelligence depends on operational data and connected machine scenarios. The catalog data does not specify deployment-region availability or compliance boundaries, so those must be confirmed for the customer’s environment.

The available source data lists IoT Intelligence only for the Commercial segment, because no Government, GCC, or GCC High offer is shown. Government buyers should not purchase the Commercial SKU for a regulated cloud requirement without confirming availability, residency, and compliance fit with IT Partner and Microsoft.

The available source data does not list Charity, Nonprofit, Education, student, or faculty offers for IoT Intelligence, because only the Commercial segment is present. Nonprofit and education organizations should confirm eligibility and any separate Microsoft program availability rather than assuming Commercial add-in terms apply to grant or academic licensing.

You should gather your Dynamics 365 Supply Chain Management environment details, target sensor-data scenario, machine-count assumptions, deployment region, integration requirements, and desired commitment term, because those factors determine whether the Scenario Add-in, Additional Machines Add-in, or both are appropriate. IT Partner can then validate prerequisites and SKU selection before checkout.

Yes, it may be part of a migration plan, but the add-in purchase alone is not a migration service, because the catalog only provides licensing for Sensor Data Intelligence add-in options. Data mapping, device integration, Azure architecture, testing, and implementation effort should be scoped separately with IT Partner.

A properly coordinated CSP transfer should not require a Dynamics 365 environment migration or user downtime, because the Microsoft tenant and service data can remain in place while the licensing relationship is changed. IT Partner should coordinate timing, subscription continuity, and renewal dates to avoid service gaps.

No, the Microsoft catalog offer for the same IoT Intelligence SKU, term, and billing option is the same Commercial offer, because changing CSP management does not change the underlying Microsoft product. The final customer invoice can still reflect partner terms, taxes, currency, or added services, so the quote should be confirmed before transfer.

Renewal, cancellation, reduction, and midterm change rules should be confirmed at checkout, because they depend on the selected commitment term, billing frequency, and current Microsoft commerce policies. In general, longer commitments provide term stability but reduce flexibility, so buyers should validate machine-count needs before committing.