Deciphering the licensing model
in your project solution
Dynamics 365
Bootcamp
• Nico Fernández
• Microsoft MVP x2 & MCTx2
• +13 years exp. CRM & No Code solutions,
• +8 years exp. Dynamics CRM/365 CE & Power
Platform
• +6 years exp. In Pre-Sales
• Solution Director – HCL EMEA Pre-Sales Team
• Co-Founder – Power 365 Initiatives
About me
You can find me in…
• Web: nfernandezba.com
• Twitter: @nfernandezba
• LinkedIn: /in/nfernandezba
• Instagram: /nfernandez.ba or nametag
• nicolas@nfernandezba.com
• nicolas.fernandez@hcl.com
First steps in Dynamics 365 Licensing
Introduction
01
Identify the right licensing model
Where to begin
02
Licensing guide and more…
Learning resources
03
Agenda
License types
Tenant
User
Device
Customer Insights, Customer Voice, Marketing
Sales enterprise, Customer Service Enterprise, etc.
Sales enterprise, Customer Service Enterprise, Field Service.
User License
01
02
Main user license
Base
Additional user license
Attach
User License
Base Licenses
Sales Enterprise Customer Service
Enterprise
Field Service Project Operations
Sales Professional Customer Service
Professional
MRSSP Sales Premium
User License
Attach Licenses
Sales Enterprise Customer Service
Enterprise
Field Service Project Operations
Sales Professional Customer Service
Professional
Guides Remote Assist
User License Rights
Base license vs Attach license Matrix
User License
Add-ons
Digital Messaging Chat Voice RSO
Sales Insights
User License
Sales Enterprise
Customer Service
Enterprise
Field Service
Digital Messaging
Chat
Base Licenses Attach Licenses Add-ons
Team Member License
Team Member Power Apps
• Only three native apps with limited customisation
• No Power Apps rights
• Limited privileges on restricted tables
• Supports full D365 users
• Limited/unlimited apps
• No CUD privileges on restricted tables
• Access custom processes / apps
Custom tables use rights
Device Licenses
Sales Enterprise Customer Service
Enterprise
Field Service
Unlimited users in one device
Multiplexing
Enterprise vs Professional Licenses
Tenant Licenses
Marketing Customer Insights Customer Voice
And Power Platform licenses and add-ons…
Power Apps Power Automate Power Virtual Agents Power BI
AI Builder Power Pages Dataverse Capacity
Building the licensing model
1
2
3
4
5
Type of user
Is it an internal or external user?
Quotas
Number of marketing contacts, CI profiles, CV responses.
Power Platform Capabilities
Do we need to build a bot? Do we need a flow to be
triggered for anyone in the organization?
Functional area
Opportunity Management, Case management,
Work order management, etc.
Additional capabilities
AI, Mixed reality, custom apps,
social selling
Identify the right licensing model
When we analyze our customer’s requirements, and when we
start designing, we need to take a few things in consideration in
order to propose the right licensing model
Licensing Guide
Get Licensing Ready
Get Licensing Ready
Availability of licenses
Let's keep in touch
• Web: nfernandezba.com
• Twitter: @nfernandezba
• LinkedIn: /in/nfernandezba
• Instagram: /nfernandez.ba or nametag
• nicolas@nfernandezba.com
• nicolas.fernandez@hcl.com
Nico Fernandez
THANKS!
Dynamics 365
Bootcamp

Deciphering the licensing model in your project solution

  • 2.
    Deciphering the licensingmodel in your project solution Dynamics 365 Bootcamp
  • 3.
    • Nico Fernández •Microsoft MVP x2 & MCTx2 • +13 years exp. CRM & No Code solutions, • +8 years exp. Dynamics CRM/365 CE & Power Platform • +6 years exp. In Pre-Sales • Solution Director – HCL EMEA Pre-Sales Team • Co-Founder – Power 365 Initiatives About me
  • 4.
    You can findme in… • Web: nfernandezba.com • Twitter: @nfernandezba • LinkedIn: /in/nfernandezba • Instagram: /nfernandez.ba or nametag • nicolas@nfernandezba.com • nicolas.fernandez@hcl.com
  • 5.
    First steps inDynamics 365 Licensing Introduction 01 Identify the right licensing model Where to begin 02 Licensing guide and more… Learning resources 03 Agenda
  • 6.
    License types Tenant User Device Customer Insights,Customer Voice, Marketing Sales enterprise, Customer Service Enterprise, etc. Sales enterprise, Customer Service Enterprise, Field Service.
  • 7.
    User License 01 02 Main userlicense Base Additional user license Attach
  • 8.
    User License Base Licenses SalesEnterprise Customer Service Enterprise Field Service Project Operations Sales Professional Customer Service Professional MRSSP Sales Premium
  • 9.
    User License Attach Licenses SalesEnterprise Customer Service Enterprise Field Service Project Operations Sales Professional Customer Service Professional Guides Remote Assist
  • 10.
  • 11.
    Base license vsAttach license Matrix
  • 12.
    User License Add-ons Digital MessagingChat Voice RSO Sales Insights
  • 13.
    User License Sales Enterprise CustomerService Enterprise Field Service Digital Messaging Chat Base Licenses Attach Licenses Add-ons
  • 14.
    Team Member License TeamMember Power Apps • Only three native apps with limited customisation • No Power Apps rights • Limited privileges on restricted tables • Supports full D365 users • Limited/unlimited apps • No CUD privileges on restricted tables • Access custom processes / apps
  • 15.
  • 16.
    Device Licenses Sales EnterpriseCustomer Service Enterprise Field Service Unlimited users in one device
  • 17.
  • 18.
  • 19.
    Tenant Licenses Marketing CustomerInsights Customer Voice
  • 20.
    And Power Platformlicenses and add-ons… Power Apps Power Automate Power Virtual Agents Power BI AI Builder Power Pages Dataverse Capacity
  • 21.
    Building the licensingmodel 1 2 3 4 5 Type of user Is it an internal or external user? Quotas Number of marketing contacts, CI profiles, CV responses. Power Platform Capabilities Do we need to build a bot? Do we need a flow to be triggered for anyone in the organization? Functional area Opportunity Management, Case management, Work order management, etc. Additional capabilities AI, Mixed reality, custom apps, social selling Identify the right licensing model When we analyze our customer’s requirements, and when we start designing, we need to take a few things in consideration in order to propose the right licensing model
  • 22.
  • 23.
  • 24.
  • 25.
  • 26.
    Let's keep intouch • Web: nfernandezba.com • Twitter: @nfernandezba • LinkedIn: /in/nfernandezba • Instagram: /nfernandez.ba or nametag • nicolas@nfernandezba.com • nicolas.fernandez@hcl.com
  • 27.

Editor's Notes

  • #6 So, Customer insiights in an hour. What can you expect from this sesión? We’l start making a quick introduction to the Customer Data Platform and customer Insights. Then we’ll make also a quick review of the solution architecture. We’ll review step by step how to start working with customer insights And at the end we’ll talk about the integration scenarios with Power platform and Dynamics 365. So let’s get started.