Microsoft Dynamics 365 For Operations On-Premises, Enterprise Edition Licensing Guide
Microsoft Dynamics 365 For Operations On-Premises, Enterprise Edition Licensing Guide
for Operations
on-premises,
Enterprise edition
Licensing Guide
June 2017
Contents
How to License Microsoft Dynamics 365 for Operations on-premises ................................................................................. 1
Basic Licensing Requirements ......................................................................................................................................................... 1
Microsoft Dynamics 365 for Operations CAL License Types ............................................................................................... 5
Microsoft Dynamics 365 for Operations ........................................................................................................................................................... 5
Microsoft Dynamics 365 for Operations Team Members .......................................................................................................................... 5
Dynamics 365 for Operations Activity ................................................................................................................................................................ 6
Retail Deployments.............................................................................................................................................................................. 7
Customization ........................................................................................................................................................................................ 7
Additional Services and Software .................................................................................................................................................. 8
Software Assurance ............................................................................................................................................................................. 8
On-Premises Upgrades, Downgrades and Migration ............................................................................................................ 8
Transitioning from On-Premises to Cloud Deployment .................................................................................................... 11
Availability by Language ................................................................................................................................................................. 12
Trials........................................................................................................................................................................................................ 12
Product Deployment ........................................................................................................................................................................ 13
Software Fulfillment.......................................................................................................................................................................... 13
License Keys and Product Activation ......................................................................................................................................... 13
Links for Additional Information ................................................................................................................................................. 13
Appendix A: Ensuring Accurate Licensing ............................................................................................................................... 15
Appendix B: Microsoft Dynamics 365 for Operations Security Roles by User CAL Level ..................................... 16
Appendix C: Operations Customization and Licensing Requirements......................................................................... 29
Appendix D: Change Log ............................................................................................................................................................... 31
Using this Guide
Use this guide to improve customers’ understanding of how to license Microsoft Dynamics 365 for
Operations on-premises, Enterprise edition (Microsoft Dynamics 365 for Operations on-premises).
Microsoft Dynamics 365 for Operation on-premise is the newest version of Microsoft’s current ERP on-
premises product. Microsoft Dynamics 365 for Operations on-premises offers choices to license
employees who need to use much of the rich functionality in the business application, and other users
who consume and share information and complete small or targeted tasks in the application.
This document does not apply to Microsoft Dynamics NAV, Microsoft Dynamics GP, Microsoft Dynamics
SL, Microsoft Dynamics AX 2012, Microsoft Dynamics CRM 2016, or prior versions of any of these
products. This guide also does not apply to Microsoft Dynamics 365 cloud services, Microsoft Dynamic
CRM Online, or Microsoft Dynamics AX cloud. This guide is not intended to influence the customer’s
purchase decisions on Microsoft Dynamics 365. The examples presented in this guide are illustrative.
Microsoft reserves the right to review or update this document at any time without notice.
For help determining the right technology for any given organization, including the license requirements
for a specific product or scenario, consult with the customer’s Microsoft Dynamics Certified Partner or
their Microsoft account team.
This guide does not supersede or replace any of the legal documentation covering use rights for
Microsoft products. Specific product license terms are detailed in the Software License Terms (SLT)
document, which is available on the Lifecycle Services (LCS) legal website and the Product Terms (PT)
found on the Volume Licensing website.
Server Licenses
Before a customer runs any instance of the Microsoft Dynamics 365 for Operations on-premises software,
they must obtain a Dynamics 365 for Operations Server license for each of their servers. For each
Microsoft Dynamics 365 for Operations Server license the customer obtains, they may run, at any one
time, one instance of the server software in one physical or virtual operating system environment (OSE) on
the licensed server. A hardware partition or blade is considered to be a separate server. The server license
includes one application object server. If customers want additional application object servers or
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e |1
additional server instances, they may purchase additional Microsoft Dynamics 365 for Operations Server
licenses.
Reassigning CALs
Named CALs (either User or Device) cannot be shared. CALs can be reassigned only in specific cases as
follows:
• Permanently reassigning a CAL from one user or device to another, due to permanent personnel
or device replacement.
• Temporarily reassigning a CAL to a temporary worker while the assigned user is absent or to a
temporary loaner device while an assigned device is out of order.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e |2
Dynamics 365 for Operations on-premises has two types of CALs:
• User CALs are assigned on a “named user” basis, meaning each user requires a separate CAL; User
CALs cannot be shared, but an individual with a User CAL may access the service through multiple
devices without need for separate Device CALs. Purchasing User CALs might make more sense if
the organization’s employees need to have roaming access to the corporate network using
multiple devices, or from unknown devices, or if there are simply more users than devices in the
organization.
• Device CALs grant access to the Microsoft Dynamics 365 for Operations Server from a device.
Any user may access a licensed device without the need for a separate User CAL. The Device CAL
has restrictied functionalify but may make more economic and administrative sense if its
organization has employees who share devices, such as for shift-based work.
A user or device licensed with a CAL may access any number of instances of Microsoft Dynamics 365 for
Operations Server or earlier versions of the software running on the organization’s servers.
Note: Since Microsoft Dynamics 365 for Operations on-premises may be licensed with a User or Device CAL, only the
user or device requires a CAL but not both. If the user of a device is licensed with a CAL, then the device does not
need a Device CAL. Likewise, if the device is licensed with a Device CAL, then the user does not need a CAL. Customers
can mix both User and Device CALs .
Figure 4: Accessing multiple instances
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e |3
Figure 2: Internal vs. external users
Multiplexing
Multiplexing refers to the use of hardware or software that a customer uses to pool connections, reroute
information, or reduce the number of devices or users that directly access or use Microsoft Dynamics 365
Operations Server. Multiplexing does NOT reduce the number of CALs of any type required to access the
Microsoft Dynamics 365 Operations Server. Any user or device that accesses Microsoft Dynamics 365
Operations Server —whether directly or indirectly—must be properly licensed.
Microsoft Dynamics 365 for Operations on-premise CALs are required for users or devices that directly
input, query, or view data from the Microsoft Dynamics 365 Operations Server. Similarity, Microsoft
Dynamics 365 for Operations on-premises CALs are required for users or devices that input data into,
query, or view data from Microsoft Dynamics 365 Operations Server through a pooling device. Pooled
connections use a non-interactive user account in Microsoft Dynamics 365 that can access the system but
only via the web service layer. Internal users and devices accessing Microsoft Dynamics 365 data indirectly
through a portal or via an API to a separate software such Microsoft Outlook must also be properly
licensed, regardless of if they are set up as a Dynamics 365 user in the server software. For example:
• Internal users and devices access Microsoft Dynamics 365 for Operations on-premises data
indirectly through a third party application must still be properly licensed for Microsoft Dynamics
365 for Operations on-premise.
• Users or devices that access the software files, data, or content provided by the product that is
made available through an automated process require Microsoft Dynamics 365 for Operations
on-premise CALs.
• The number of tiers of hardware or software between the Microsoft Dynamics 365 Operations
Server and the users or devices that ultimately use data, software, or functionality does not affect
the number of CALs required.
For additional information about multiplexing refer to the Microsoft Volume Licensing Brief
Multiplexing—CAL Requirements.
Note: Licensed users may manually rekey information (when coming from non-licensed users) into the Dynamics 365
Operations Server. This scenario is not considered multiplexing.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e |4
Figure 4: Multiplexing
Full users are the users whose work requires use of the feature rich business applications functionality.
Examples of full users are sales people, customer service representatives, finance employees,
controllers and supply chain managers. These users have been referred to in the past as Pro users or
Power Users. These full users are licensed with a Microsoft Dynamics 365 for Operations CAL.
Other users often represent a large percentage of users in an organization and may consume data or
reports from line of business systems, complete light tasks like time or expense entry and HR record
updates or be heavier users of the system, but not require full user capabilities. These other users are
licensed with either Microsoft Dynamics 365 for Team Members or Microsoft Dynamics 365 for
Operations Activity CALs.
There is also Microsoft Dynamics 365 for Operations Device CAL licensing available for shared device
scenarios. See the Microsoft Dynamics 365 for Operations Device section in this document for more
information.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e |5
Team Member use rights for Microsoft Dynamics 365 for Operations
The Microsoft Dynamics 365 for Team Members user CAL grants a user the following Microsoft Dynamics
365 for Operations rights for their own use and not for, or on behalf of, other individuals:
(i) To record any type of time
(ii) To record any type of expenses
(iii) Manage personal information
(iv) Manage direct employee activities in Human Resources
(v) Create requisitions
(vi) Create or edit the items related to the following capabilities: quality control, service orders
and departmental budgets
(vii) Approval of time, expense, invoices
Please review Appendix B for a list of the out-of-the box Microsoft Dynamics 365 for Operations roles and
their associated user types.
Microsoft Dynamics 365 for Operations Device
With the Microsoft Dynamics 365 for Operations Device CAL multiple users can access through a device to
operate a point of sale device, shop floor device, warehouse device or store manager device.
• “Point of Sale Device” means one device located in the commerce location, used by any
individual, for completing customer facing sales of goods or services transactions.
• “Store Manager Device” means one device located in the Commerce Location, used by any
individual, dedicated to performing the following tasks solely for that Commerce Location (i)
managing and replenishing inventory, (ii) balancing cash registers and processing daily receipts,
(iii) configuring and maintaining menu options displayed by the ISV Devices, (iv) purchasing
supplies and services required to run the Commerce Location operations, (v) managing
Commerce Location staff, (vi) processing reports required to analyze and manage Commerce
Location results, and (vii) managing master data related to Commerce Location operations.
• “Commerce Location” or “Store” means a physical location (static or itinerant) operated by
customers when closing goods or services transactions with their clients.
• “Shop Floor Device” means one device dedicated to performing manufacturing shop-floor
functions and that device may not be used for other purposes.
• “Shop Floor Functions” means clock-in and clock-out, starting and finishing production jobs
(including project activities carried out on the shop floor), reporting progress, materials
consumption and completion, viewing documents and instructions related to production jobs,
and viewing worker holiday balances.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e |6
• “Warehouse Device” means one device dedicated to performing warehousing functions, and that
may not be used for any other purposes.
• “Performing Warehousing Functions” means receiving, putting-away, doing internal stock
transfers, picking, packing, capturing product attributes, and shipping goods plus performing
inventory count checks in the context of a warehouse management system and posting output
and materials consumption against production orders when captured as transfers of raw materials
and finished goods between a warehouse and a production line (all other types of transactions
are excluded).
Note: Microsoft Dynamics 365 for Operations Device CAL use rights are also available to Microsoft
Dynamics 365 for Operations Activity users. When multiple users who only require these use rights
work exclusively on shared devices, generally it will be more cost effective to license those devices
with the Microsoft Dynamics 365 for Operations Device CAL. When a single user utilizes one or more
dedicated personal devices, it will be more cost effective to license that user with a Microsoft
Dynamics 365 for Operations Activity CAL.
Retail Deployments
Retail scenarios using Microsoft Dynamics 365 for Operations on-premises are licensed through a
combination of the following:
• Microsoft Dynamics 365 for Operations Server license
• Microsoft Dynamics 365 for Operations, Microsoft Dynamics 365 for Operations Activity and
Microsoft Dynamics for 365 Team Members users CALs
• Microsoft Dynamics 365 for Operations Device CALs
Please see the use rights above to determine the appropriate licensing for a given server, user or device.
Retail deployments may also utilize the Retail Store Scale Unit, which is a retail server, cloud POS website
and channel database deployed locally in a Store. It maintains connectivity with and extends a Dynamics
365 for Operations deployment, providing improved performance, business continuity and hybrid
capabilities in the store.
The Retail Store Scale Unit installation and use rights are included with the Dynamics 365 for Operations
Server license and may be downloaded and installed at no additional cost. All users and devices accessing
the Retail Store Scale Unit must be appropriately licensed. The Retail Store Scale Unit is not available as a
standalone license. Required hardware, windows client, or windows server, and SQL licenses must be
acquired and licensed separately.
If downgrade rights are utilized to downgrade to Microsoft Dynamics AX 2012, the Retail Store Server is
not an included use right and appropriate licensing must be obtained. Please see AX 2012 Retail Licensing
Guide and refer to the AX downgrade mappings table in this licensing guide to determine appropriate
licensing.
Customization
Customizations may be based on security roles included in Microsoft Dynamics 365 for Operations on-
premises or created by a customer or partner. If the customization is based on or replicates the
functionality of security roles included in Microsoft Dynamics 365 for Operations on-premises or if the
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e |7
entity links to security roles included in Microsoft Dynamics 365 for Operations on-premises, then users
accessing the customization must also be licensed to access the included or replicated security role.
Please review Appendix C for more details about customization use rights.
View Implementation Guide and System Requirements for Microsoft Dynamics 365 for Operations on-
premises on TechNet. The Microsoft License Advisor Tool can help determine the licenses needed.
Software Assurance
Software Assurance includes a core set of benefits to help improve workforce productivity, streamline
software deployment, and reduce costs. A distinctive set of benefits, such as new software versions,
planning services, 24x7 phone and Web support, training, and more—all designed to help the
customer get the most from their organization’s Volume Licensing purchase.
The customer’s specific Software Assurance benefits vary according to the Volume Licensing program.
Refer to the resources and tools below to learn more about the Software Assurance benefits available
to their organization.
To learn more about the Software Assurance benefits for Microsoft Dynamics 365 for Operations on-
premises customers, visit https://www.microsoft.com/en-us/licensing/licensing-programs/software-
assurance-default.aspx to view an interactive benefit chart detailing the benefits of the Software
Assurance benefits for Microsoft Dynamics 365 for Operations on-premises or
https://www.microsoft.com/en-us/licensing/licensing-programs/software-assurance-default.aspx#tab=3
to check customers benefits post-purchase.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e |8
Qualifying Licenses purchased before March 30, 2017
Customers who purchased Qualifying Licenses before March 30, 2017 may upgrade to and use the the
following Migration License.
Qualifying License(s) Migration License(s)
Microsoft Dynamics AX Enterprise CAL (User) Microsoft Dynamics 365 for Operations On-premises CAL, or
Microsoft Dynamics 365 for Operations Activity On-premises CAL, or
Microsoft Dynamics 365 for Operations Device On-premises CAL
Microsoft Dynamics AX Enterprise CAL (Device) Microsoft Dynamics 365 for Operations On-premises CAL, or
Microsoft Dynamics 365 for Operations Device CAL
Microsoft Dynamics AX Functional CAL (User) Microsoft Dynamics 365 for Operations On-premises CAL, or
Microsoft Dynamics 365 for Operations Activity On-premises CAL, or
Microsoft Dynamics 365 for Operations Device On-premises CAL
Microsoft Dynamics AX Functional CAL (Device) Microsoft Dynamics 365 for Operations On-premises CAL, or
Microsoft Dynamics 365 for Operations Device CAL
Microsoft Dynamics AX Task CAL (User) Microsoft Dynamics 365 for Operations Activity On-premises CAL, or
Microsoft Dynamics 365 for Team Members On-premises CAL, or
Microsoft Dynamics 365 for Operations Device On-premises CAL
Microsoft Dynamics AX Task CAL (Device) Microsoft Dynamics 365 for Operations Activity On-premises CAL, or
Microsoft Dynamics 365 for Operations Device CAL
Microsoft Dynamics AX Self Serve CAL (User) Microsoft Dynamics 365 for Team Members On-premises CAL
Microsoft Dynamics AX Self Serve CAL (Device) Microsoft Dynamics 365 for Team Members On-premises CAL
Microsoft Dynamics AX Server Microsoft Dynamics 365 for Operations Server
Microsoft Dynamics AX Store Server NA
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e |9
License Upgrade Path for Dynamics Price List (DPL)
Customers who are current on their Software Assurance Plan as of June 1, 2017 are entitled to upgrade
the licenses from Microsoft Dynamics AX 2012 R3 to Microsoft Dynamics 365 for Operations on-
premise as shown below upon renewal.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 10
Customers who license Microsoft Dynamics 365 for Operations on-premises as of June 1, 2017 are
entitled to downgrade the software from Microsoft Dynamics 365 for Operations on-premise server to
Microsoft Dynamics AX 2012 R3 server.
The license rights for a particular Add-on or From SA User SL are identical to those of equivalent Full User
Subscription License (Full USL).
Device CALs purchased as part of an Enterprise Agreement or Enrollment qualify for these User Add-On or
From SA options on a 1:1 basis: One Device CAL qualifies for one From SA or Add-on User SL.
From SA option is available for purchase through the Microsoft Volume Licensing Enterprise Agreement,
Enterprise Subscription Agreement and Enrollment for Education Solutions (under a Campus and School
Agreement) programs.
Add-on option is available for purchase through the Microsoft Volume Licensing Enterprise Agreement,
Enterprise Subscription Agreement, Microsoft Product and Service Agreement, and Enrollment for Education
Solutions (under a Campus and School Agreement) programs.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 11
Microsoft Dynamics 365 Cloud Add-on
Microsoft Dynamic 365 add-ons to move to cloud are ideal for customers who are not ready to move entirely
to the cloud, or are in the middle of their agreement. The Cloud Add-on gives credit for the customers ongoing
SA payments.
The Add-on User SL must be used for the same user of the User CAL. The User SL cannot be subsequently
transferred to another user unless the corresponding CAL is also transferred to the new user.
These licenses are designed for current Microsoft customers who want to transition to the cloud and are
licensed to on-premises products. From SA USLs recognize the on-premises investment and thus are offered at
a discounted price for customers. In order to purchase From SA USLs, customers must have fully paid qualifying
licenses, namely the corresponding on-premises licenses from which the customer is transitioning or more than
3 years of a qualifying software subscription license. The qualifying licenses are detailed in the Product Terms.
Availability by Language
Country and language localization availability for Dynamics 365 for Operations on-premises, Enterprise
edition is available here.
Trials
Trials for Microsoft Dynamics 365 for Operations on-premises are available. Requests for the trial
enviorment can be made by sending email request to [email protected]. Include company account
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 12
number and company name in the request. The trial environments are to be used for evaluation
purposes only (not production use). A customer owned/managed Azure subscription is required to
deploy the trial environments to the cloud. A local VM is also available for downloaded from the
Lifecycle Services project.
Product Deployment
For details around existing customer migration options please see the Microsoft Dynamics 365 for
Operations on-premises, Enterprise edition Transition Guide document.
Software Fulfillment
The Volume Licensing Service Center (VLSC) is an online platform made to make managing the customer’s
Microsoft Volume Licensing agreements simple. Within the VLSC, the customer can access their licensing
information, view agreements and purchases for their organization, and access licensing summaries of all
entitlements by product and version. The customer can also view all assigned product keys and download
products in the VLSC.
Customers who have licensed Microsoft Dynamics 365 (Online) who do not have access to VLSC, but would
like to leverage Dual Use Rights for a hybrid deployment may obtain the software through CustomerSource
or PartnerSource.
Note: If the customer cannot see Registration keys in PartnerSource Business Center they will need to ensure
that their PartnerSource Business Center Profile has “Can See Registration Keys” set to yes.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 13
On-Premises Licensing Guides:
AX 2013 R3 http://aka.ms/Jswgcc
CustomerSource https://mbs.microsoft.com/customersource/
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 14
Appendix A: Ensuring Accurate Licensing
Microsoft Dynamics customers have asked for easier ways to implement Software Asset Management
(SAM) across their organization, because they realize that SAM can help them:
• streamline IT resources and improve visibility and control of the customer’s environment now and
in the future,
• increase awareness of the organization’s overall software purchasing needs and better work with
software vendors to meet those needs, and
• get greater insight into how to manage the organization’s assets, helping them to make more
informed decisions to reduce risk and plan for the future.
To help the customer navigate through the product flexibility and its impact on licensing, we have created
a report within the application that looks at all of the Menu Items associated to each user directly
accessing Microsoft Dynamics 365 for Operations Server and computes the assigned number of users by
user type. The customer is responsible for determining the number and CAL level of third party users
directly accessing Microsoft Dynamics 365 for Operations Server and subtracting these users from the
report generated by the system. The customer is also responsible for determining the number and CAL
level of internal users indirectly accessing Microsoft Dynamics 365 for Operations Server and manually
adding these users to the report generated by the system.
By comparing this to the customer’s license purchase information from the Volume Licensing Service
Center (if purchasing through Volume Licensing) or CustomerSource (if purchasing through BVL), the
customer can identify discrepancies in their licenses. A customer not currently on a plan can get their
license purchase information by contacting their partner.
The customer is advised to check licensing by running the report whenever they make a change, but are
required to run the report at least annually per the Software License Terms. the customer may voluntarily
share the results of the Usage Report with Microsoft or any other third party, but are not required to do
so. Running the report before and after changing Roles, security, and user permissions will help confirm
the impact of changes to the license requirements.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 15
Appendix B: Microsoft Dynamics 365 for Operations
Security Roles by User CAL Level
Overview of Security Roles
Providing users with access to the product functionality is done by assigning each user one or more
Security Roles. Microsoft Dynamics 365 for Operations Security Roles combine meaningful packages of
product functionality and access rights required to perform actions relevant to that role.
To make it easier to understand the licenses required, each Microsoft Dynamics 365 for Operations
Security Role has a pre-determined user type. When the customer assigns Security Roles to users, they
then know what User CAL those users require.
For example, in a manufacturing organization, the Accountants and Field Service Technicians require
different use rights. By assigning those user groups to the appropriate Security Role, they get the
functionality they need, and the customer knows the User CAL type that is required.
Notes:
• Customers can assign multiple Security Roles to one user, in which case the highest User CAL type required
covers all the user rights.
• Customers have the flexibility to configure or customize Security Roles. This may impact the license required
for the new/modified Security Roles. Please refer to the Appendix C for more information about how such
customization can impact licensing requirements.
Out of the box security roles for Dynamics 365 for Operations
Role Description User SL
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 16
Compensation and Documents compensation and benefit events,
benefits manager responds to compensation and benefit inquiries and
●
records the financial consequences of compensation
and benefit events
Retail warehouse clerk The retail warehouse clerk performs picking, receiving,
● ● ●
and stock counting in a store or warehouse
Retail store manager The retail store manager performs store management
functions at the store, such as managing sales reports, ● ●
inventory movements, and inventory counts
Retail catalog manager At the head office, the retail catalog manager
●
maintains and publishes retail catalogs
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 17
Budget clerk Documents budget events and responds to budget
● ●
inquiries
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 18
Tax engine functional Create and manage generic tax engine components ●
consultant (taxable document and tax document)
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 19
Customer Service Team Members Activity Operations
Field service technician Visits customers in the field to perform service orders ● ● ●
Service delivery manager Reviews and enables the service order process ●
Time registration user Worker enabled to use advanced features for time
● ● ●
registration
Production manager Reviews the production plan and ensures the proper
●
resources are available
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 20
Materials manager Enables and reviews processes, maintains master data,
and responds to inquiries within logistics and material ●
management.
Cost accounting Sets the overall strategy for how cost accounting is
●
manager performed in the Enterprise.
Quality control manager Enables and reviews processes, maintains master data,
●
and responds to inquiries within quality control
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 21
only perform data activities for a restricted set of
entities
Data Management Super user for the data management activities in the
Administrator system. In addition to the capabilities of the
DataManagementMigrationUser and
DataManagementOperationsUser, this role provides ●
access to the DataManagementITWorkspace - an
operational workspace to monitor all data
management activities
Note: Management Reporter functionality is included in the Microsoft Dynamics 365 for Operations. To get the use
rights, the Management Reporter Designers require an Operations CAL and Management Reporter Viewers require a
Microsoft Dynamics for 365 Team Member.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 22
Appendix C: Operations Customization and Licensing
Requirements
Microsoft Dynamics 365 for Operations is fully customizable to provide customers with the right
experience for every user. Microsoft Dynamics 365 for Operations has over 10,000 Menu Items which are
mapped to the three user types. To make it faster and easier to deploy the product and determine
licensing requirements, these Menu Items are associated with certain Security Roles.
The required SL for a given user is determined by the highest user type classification of the Menu Items to
which the user will have access. For example, if the customer assigns an Accountant to a Role that
includes access to a Menu Item classified as “Operations App”, then that person requires a Dynamics 365
for Operations SL. Menu items that are classified at the “Team Members” level are available to all users to
which the customer has assigned a Team Members User or higher level User.
For an even better fit in their organizations, customers can change which actions may be performed by
specific individuals or Roles. When customizing, it is important to remember that the license required is
determined by the highest-level Menu Item to which that individual has access.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 29
Creating Menu Items
Partners and customers may also create Menu Items to fit specific customer scenarios. When doing so,
those new Menu Items must be mapped to the User SL type that best matches the type of use based on
the definitions of user SLs found in this document.
Notes:
• Roles in Microsoft Dynamics 365 for Operations are not the same as job titles.
• “Menu Item” means an object that allows users to display or view a form, sub-form, or URL in a
browser application; run a task that triggers a system class, function, workflow or web-action
initiated by a user; or cause an output in the product or a separate device.
Menu Items are classified at one of the User SL types. Users with a given SL have access to each Menu
Item classified at—or below—that User SL type.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 30
Appendix D: Change Log
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. This information is provided to help guide your
authorized use of products you license; it is not your agreement. Your use of products licensed under your license agreement is governed by the terms and conditions of that agreement.
In the case of any conflict between this information and your agreement, the terms and conditions of your agreement control. Prices for licenses acquired through Microsoft resellers
are determined by the reseller.
The Microsoft Dynamics 365 for Operations on-premises, Enterprise edition Licensing Guide | June 2017 P a g e | 31