System and application users
There is a list of special system and application users that is created when the system is provisioned. Special system users are created for integration and support scenarios. Application users are created during system provisioning for setup and configuration management. Application users can also be used for performing back-end services and their data access is managed by the special security role that is assigned. These security roles are managed by the system and might not be modifiable. See other system predefined security roles.
Most of these users are hidden from user views but they can be found by using the Advanced Find on the Users table. Do not delete or modify these users including changing or reassigning security role.
|User type||Full name||User name||Purpose||Security role assigned|
|Support firstname.lastname@example.org||To allow Microsoft support staff to have restricted/limited access to any customer environment for customer support.||Support user (does not have privilege to customer data)|
|Delegated email@example.com||See For partners: the Delegated admin.||System admin|
|Application||Business Application Platform Service firstname.lastname@example.org||To setup Power Apps system and configurations.||System admin|
|App Management Useremail@example.com||To allow App Management Services to query tenant details such as Tenant country||System admin|
|Dataverse Dataverse search||RelevanceSearch@onmicrosoft.com||To fetch table data and metadata for Dataverse search feature||System admin|
|Dynamics 365 Office Data Servicefirstname.lastname@example.org||Service Application to perform data integration between Microsoft Dataverse and Microsoft 365.||DataLakeWorkspaceAppAccess|
|Dynamics 365 Athena-CDStoAzuredatalake||Dynamics365Athena-
|Service application to perform data integration between Microsoft Dataverse to Azure Data Lake.||DataLakeWorkspaceAppAccess|
|Dynamics 365 Athena2-CDStoAzuredatalake||Dynamics365Athena2-
|Service application to perform data integration between Dataverse to Azure Data Lake.||DataLakeWorkspaceAppAccess|
|EnterpriseSales||EnterpriseSales@onmicrosoft.com||Service application to perform data integration between Dataverse (Sales) to Azure Data Lake.||N/A|
|Finance and Operations Runtime Integration User||FinanceandOperations
|Service application to perform dual-write data integration between Dataverse and finance and operations apps.||Finance and Operations Integration User|
|# SIAutoCapture||SIAutoCapture@onmicrosoft.com||To be used for Auto Capture solution business requirements to perform data query and execute plugins from backend services.||SalesInsights AutoCapture Admin|
|# Dynamics 365 Sales||Dynamics365Sales@onmicrosoft.com||To allow Dynamics 365 Sales to communicate with Dataverse and Azure Data Lake for analysis and data updates.||Sales system data sync and EAC App Access|
|Microsoft Project||Project@microsoft.com||Allow Project for the Web and Roadmap Service to communicate with Dataverse.||Project System and Portfolio User|
|Power Apps Checker Application||Pacheckerapp@microsoft.com||To perform static analysis of Power Apps solutions to assist in identifying performance and stability risks.||Export customizations and Solution checker|
|Service application to perform data query between Dataverse and Azure Data Lake.||N/A|
|Provision Useremail@example.com||To perform Application installation from AppSource or System updates from Microsoft.||System admin|
|DataLakeStorage||DataLakeStorage@onmicrosoft.com||To allow solutions to manage workspaces, workspace permissions and the discovery of workspaces.||DataLakeWorkspaceAppAccess|
|Enable satellite services to schedule and dispatch messages to independently built workloads with guaranteed delivery of messages based on service-defined policies.||System admin|
|JobServiceProd||JobServiceProd@onmicrosoft.com||Enable satellite services to schedule and dispatch messages to independently built workloads with guaranteed delivery of messages based on service-defined policies.||System admin|
|# CCADataAnalyticsML||CCADAAdmins@onmicrosoft.com||To allow AI insights in customer care apps like Customer Service, Field Service, etc.||System Customizer and System admin|
|# CDSReportService||CDSReportService@onmicrosoft.com||To allow user to run reports.||N/A|
|Power Platform Dataflowsfirstname.lastname@example.org||Power Platform Dataflows service application to perform data preparation and loading into Dataverse and Azure Data Lake.||System Administrator|
|AIBuilderProdemail@example.com||To perform authentication for AI Builder.||System admin|
|To allow Process Advisor service to interact with Dataverse.||Environment Maker, Process Advisor Application|
|AriaMdlExporter||AriaMdlExporter@onmicrosoft.com||To export data from Engagement Insights to Managed Data Lake.||DataLakeWorkspaceAppAccess|
|CDSFileStorage||CDSFileStorage@onmicrosoft.com||To perform background operations like Organization Lifecycle (OLC) operations, file reconciliation and migration.||FileStoreService App Access|
|To provision and synchronize users into Dataverse from Active Directory.||System Administrator|
|To validate which environments that users can access.||Global Discovery Service|
|BAP||BAP@onmicrosoft.com||To perform administrative operations on Dataverse linked environments: fetch user roles, provision users, assign roles in Power Platform portals.||N/A|
|Microsoft Forms Pro||enterprisesurveyappuser
|To perform data integration between Dynamics 365 Customer Voice and Dataverse||System Administrator|
|To manage the PVA capabilities within environments||CCI Admin, System Customizer, and Environment Maker|
|BizQA||BizQA@onmicrosoft.com||To access search telemetry to improve search experience||BizQAApp|
|ProductInsights||ProductInsights@onmicrosoft.com||To export data from Customer Insights to Engagement Insights||DataLakeWorkspaceAppAccess|
|To fetch table data and metadata for forecasting feature||ForecastAppUser|
|# Omnichannel||Ominichannel@onmicrosoft.com||To perform data integration between Omnichannel for Customer Service and Dataverse||System admin|
|# Flow-RP||Flow-RP@onmicrosoft.com||To allow Power Automate to integrate with Dataverse||Flow-RP Role, Service Reader|
|To read data for Azure Data Lake sync||Data Sync Service|
|# DataSyncFramework-<REGION>||DataSyncFramework-<REGION>@onmicrosoft.com||To read data for Azure Data Lake sync||Data Sync Framework|
|# Sharepoint Syntex||SharepointSyntex@onmicrosoft.com||To allow Sharepoint to use AI Builder document processing models||Basic User|
The purpose of the system account?
- The System user is a built-in user account that is used to allow customers to perform system updates via plug-ins.
- The primary usage of this user account is to meet special business requirements that require elevation of privileges; for example, running background processes to integrate with other applications.
- It can also be used to handle rollup scenarios where individual users do not have the required privilege. For example, the priority of a Case is automatically set to the highest priority of an individual user’s tasks and individual users can only update their own task priority but not the Case priority.
Technical details on permissions?
- This user account can perform any actions and has all system privileges.
- Records created/updated by this user account are audited.
Technical details on the security?
- This user account can't sign in to Dynamics 365 apps.
- Administrators have the option to use this user account when registering their plug-ins.
- This user account doesn't have a mailbox, so they can't be used to send or receive emails.
- Since you can't log into the apps using this user account, it doesn't have any related entities (user settings, queues, calendar, team membership, internal address, etc.).
- The details of this user account can't be modified from the User Form interface.
- This user account doesn't show up in any views.
The purpose of the application users?
- The application user is a built-in user account that is used to perform integration and system back-end service to support a particular feature.
- Since these are built-in user accounts, they can't be updated. The security role that is assigned to these accounts cannot be updated either. This is to prevent any service outages.
- These users do not consume any service licenses.
Submit and view feedback for