Skip to main content

Be Careful Deleting Users in Microsoft Dynamics 365

Deleting users and reassigning licenses in Microsoft Dynamics 365 requires some planning and consideration.  Otherwise, you may experience undesired consequences.  Deleting and deactivating users can be complex and involve multiple administrators.

For Dynamics 365 deployed on premises, you can disable a user, but online you need to remove the license to disable.

Here are some top considerations:
  1. Reassign records in CRM. Do you want to reassign record ownership for cases, opportunities, accounts, contacts and other entities?  If so, deleting a user will not do this automatically so you should update with Advanced Find or another approach. 
  2. Does the user own workflows?  If so, new system jobs will fail when you disable or delete the user.  This is a good reason to use system accounts that are not subject to change as the owner for these processes. 
  3. Deleting users in Dynamics is not the same as deleting them in Office 365.   Some organizations have different administrators for Dynamics and Office 365, so you need to have a process to coordinate these actions.
  4. Auditing may require you to keep track of who did what to which records. Do not change a user name to misrepresent the actors in past transactions. 
You can run into trouble when users own personal views that they've shared with others.  Another wrinkle can occur if you decide to delete a user and then create a new user later with the same name.  This is more likely for common names and in large organizations, but can also happen with admin and test accounts. 

Popular posts from this blog

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

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

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend 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