pricing & licensing
150 TopicsBusiness Central Device Licensing - Service Management
I posted this in the CSP area but realized this is where it should have been. Reposting. Suggestion...there really needs to be a category for licensing questions...and ideally a subcategory for Dynamics products...both cloud and on-prem. I'm posting this under the CSP category because I couldn't find a more suitable one. As a side note, understanding and figuring out licensing for various scenarios on the Business Central side is one of the most frustrating things we have to do. Microsoft really needs to form a dedicated licensing team that understands licensing thoroughly across all products to provide clear answers on these scenarios. We have a prospect for a new Business Central implementation that has a large number of field technicians. Our plan was to use Anveo's mobile app for field service which we've implemented previously on NAV. I reached out to Anveo to confirm pricing and they informed us that EVERY FIELD TECHNICIAN WILL NEED A FULL PREMIUM USER LICENSE. This is insane! We are priced out of this deal based on licensing. I can accept that a Team Member license is not sufficient here, but the fact that we can't use device licenses boggles my mind. We are priced out of competing in this space. I'm not even sure what I'm looking for here...I suppose confirmation that a full license is in fact required here as a first step. Microsoft seriously needs to review licensing rules for scenarios like this ASAP to reposition things to compete in markets such as this one. Our customer absolutely cannot afford a tier one ERP system like F&O...and this licensing policy will have us priced way higher than our competition in the tier two space. Very frustrating.Business Central Device license
I thought customers must have at least one Essentials or Premium SAL when purchasing Device license, but I can't find any description of this prerequisite in the license guide nor license term. To purchase a Team Member license, customers must have Dynamics 365 user SLs other than the Team Members SL according to the license term according to the license term. https://www.microsoft.com/licensing/terms/en-us/productoffering/MicrosoftDynamics365Services/MCA#Addons Is this not same for Device license or are customers allowed to purchase Device license only without other user licenses? If customers are required to have other user licenses to purchase one Device license, can we apply a 30day-trial license (Business Central Premium) for the initial month?Licensing a Dataverse environment for external users
Looking for some advice and opinions please. This is for a standalone Dataverse environment. Not Dynamics 365, or Power Apps, or Power Pages. The question is about using a Dataverse environment with the native Dataverse web APIs, where a portal is developed (not Power Pages) that allows the external users to interface (read/write) data. My opinion is that because this is not Dynamics 365 and Power Pages are not being utilised to facilitate the access then there is no requirement for user (D365, Power App, or Power Pages capacity) licensing. I would still need Dataverse capacity licenses, but that is all. Appreciate any thought and insights. Thanks, NickSolvedCOCP
I got questions with regards to the Change Of Channel Partner (COCP) rule which has been introduced with the start of the new FY of MSFT. When is COCP being enforced? Is that already with the start of FY27? For transfers executed prior to start COCP will the partners still earn incentives after start date COCP? Eg. start date being July 1st, but the transfer was executed in April. Will the new partner keep earning their incentives after July? n When executing a CSP transfer, both the license costs and incentives are fully prorated. Eg. existing partner received a annual payment in September 2026 (getting full year costs and full year incentives) and executes a CSP transfer in December, they get credit of 8 months costs but also need to return the incentives for 8 months. Everything is prorated. Now with COCP the new partner would not earn the Core/Strategic incentives anymore, thus the new partner only get the 8 months costs, but not the 8 months of incentives. Is this correct? A Reseller switching between Disti's is considered COCP and thus won't be earning any Core/Strategic incentives anymore. Does this apply to both the existing Reseller and new Disti? During the community call yesterday it was mentioned that the only focus is on growth with regards to incentives. Resellers might be switching from a transactional Disti (one that doesn't support growth) to a added-value Disti (one that does support additional growth). But due to COCP guidelines, this is now strongly discouraged and punished by MSFT. Why are Resellers being punished for such a Disti switching, by loosing their Core/Strategic incentives? Same goes for customer tenants switch from partner to partner. The new partner would not earn any Core/Strategic incentives anymore, even though they might be the better partner for that customer to increase up- and cross-sell (realize growth). Now the new partner is being punished for being the better partner and taking over the customer tenant. Why? Hope to get some insights on how COCP will actually work, and the thoughts behind it from MSFT on why they introduced it. Cheers, MartijnSolved495Views5likes3CommentsGuidance on licensing requirements for using managed environments
Is it sufficient to have a per-app premium licence assigned when using a managed environment or is a per-user premium licence required? I have read this guidance from https://learn.microsoft.com/en-us/power-platform/admin/managed-environment-licensing "Every user running an app in a managed environment must have one of the following licenses: a Power Apps Premium, a Power Automate Premium license, or a Dynamics 365 Enterprise license that gives premium Power Apps usage rights *. If you use capacity-based licenses, a managed environment must have Power Apps per app plans such as app passes allocated to it. Use of Power Apps capabilities included with Dynamics 365 Pro licenses must be only within the context of the licensed Dynamics 365 application." Does the line that I have highlighted in red mean that you can in fact use per-app licences? or is this referring to something else? Thanks RosieD365 Finance/Finance Premium mix&match for purchasing minimum?
Hi, can someone confirm if it's obligatory to meet the purchasing minimum requirements for both Finance and Finance Premium, i.e. if we purchase 20 regular Finance licenses, can we purchase only 5 Finance Premium or does it have to be the minimum 10? I've found resources online that say these 2 SKUs can be mixed & matched, but I can't seem to find definitive confirmation of this in the D365 Licensing Guide or any of MSFT resources. Thanks!SolvedPrice increase D365, impact on Base/Attach model?
Hi all, Microsoft announced a general price increase of D365 licenses, with a increase of 10-15% for certain suites. See following blog: New pricing for Microsoft Dynamics 365 effective October 2024 - Microsoft Dynamics 365 Blog. I wonder how this price increase will affect the Base/Attach model and combinations you can make. Eg. the D365 Sales Enterprise license with increase from $95 --> $105. While the D365 BC Premium will remain on $100 (no increase for BC). This means, Sales Enterprise will be more expensive than BC Premium. Currently we can attach Sales Enterprise on a BC Premium license: General rule of thumb is that the Base license must be the highest priced license, and Attach licenses should be the cheaper licenses. But with this price change this will be turned around between Sales/BC. So how will this price increase impact the Base/Attach model for such cases and existing customers? Cheers, MartijnSolved4.4KViews4likes17CommentsD365 CSP Embed Licenses (Legacy → NCE): Is Admin Center Reassignment Required if Capacity Exists?
We are managing a CSP‑managed tenant that uses Dynamics 365 embedded licenses (for example, Dynamics 365 Sales Enterprise embedded, Dynamics 365 Customer Service embedded, or other service‑provisioned Dynamics entitlements). In this tenant: Legacy CSP subscriptions exist for the Dynamics 365 embedded licenses Equivalent NCE subscriptions are ordered (or will be ordered) with equal or greater capacity Migration tooling is not available for these embedded Dynamics SKUs In Microsoft 365 Admin Center, these licenses: Are not user‑assignable Do not show a Legacy vs NCE distinction Based on Microsoft Partner Center and NCE documentation, it appears that Dynamics 365 embedded licenses are service‑provisioned, and that entitlement is governed by the subscription lifecycle, not by user‑level license assignment. We are trying to confirm the following for Dynamics 365 embedded licenses: No reassignment in Microsoft 365 Admin Center is required when transitioning from Legacy CSP to NCE, as long as sufficient NCE capacity exists. Entitlement will automatically continue or transition at legacy expiration or renewal based on the subscription lifecycle. Partner Center (and CSP billing systems) are the authoritative source for Legacy vs NCE status, rather than the customer Admin Center UI. Is there is an official Microsoft document that explicitly confirms this behavior for embedded licenses? Microsoft Support has unfortunately not been helpful in this process. Thank you.Solved