Skip to main content

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances

If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365.

In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365.

This post explains three administrator roles:

  • Office 365 Global Administrator
  • Dynamics 365 System Administrator
  • Dynamics 365 Service Administrator

You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises deployment.  The Global Administrator is the only role to create new user accounts and assign subscription licenses for Dynamics 365 (and other Office 365 apps such as Skype, Power BI and SharePoint).    The Global Administrator can also assign other admin roles, and is automatically a Dynamics 365 system administrator.  You can have more than one person assigned as Office 365 Global Administrator.

The Dynamics 365 system administrator may assign roles and permissions to the Dynamics 365 user within an instance of Dynamics 365.  The Dynamics 365 system administrator also controls all the settings in Dynamics 365.

In 2017, Microsoft introduced a new administrator role called Dynamics 365 Service Administrator to Office 365.  This is a customized administrator role with fewer permissions than the Global Administrator.  It may be configured at the app level.

Dynamics 365 Service Administrator
Office 365 role / featureBackup & restoreSandbox copyConfigure new instancesManage an instanceAdd Dynamics 365 licensesApprove Dynamics 365 emails1Access support requestsAccess Service healthAccess Message center
Office 365 global adminYesYesYesYesYesYesYesYesYes
Exchange adminn/an/an/an/an/aNon/aYesYes
Office 365 service adminNoNoNoNoNoNoYesYesYes
Office 365 userNoNoNoNoNoNoNoNoNo
Dynamics 365 service adminYesYesYesYesNoYesYesYesYes


The Dynamics 365 service administrator can manage Dynamics 365 instances, such as performing backup and restore, copy and reset actions.  These actions are often used to promote development instances to test or production.  

The service administrator may open and view support tickets with Microsoft and view the service dashboard and message center.  

Before you go live with Dynamics 365, be sure that your users, help desk and administrators understand their roles, how they can communicate, and when and how to get help from Microsoft. 

Popular posts from this blog

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun