Glossary
Service principal
By Emil Björk · Microsoft business apps consultant, Gothenburg
An identity for non-human callers in Microsoft Entra — used by integrations and automated processes to authenticate to Dataverse and other services.
A service principal in Microsoft Entra ID (formerly Azure AD) is an identity for non-human callers — applications, services, scripts, pipelines, integrations — that need to authenticate without a user. The service principal is created from an app registration with a client ID, client secret (or certificate), and configured permissions. Integrations between systems (Power Automate calling Dataverse, Azure Functions writing to Dataverse, CI/CD pipelines deploying solutions) authenticate as service principals. Service principals are granted appropriate Dataverse security roles or specific table permissions. Managed Identity is the recommended Azure-hosted variant — eliminates credential management because Azure handles the rotation. Always prefer service principals over user accounts for automation; they're auditable, manageable, and don't break when employees leave.
Related terms
Mentioned in these guides
- ALM with GitHub Actions for Power Platform
- Azure Data Factory with Dynamics 365
- Azure Functions for Dynamics 365 integrations
- Isolated storage and secrets in AL
- Center of Excellence Starter Kit
- Connection references best practices in Dataverse
- Impersonation in Dataverse plug-ins
- Dataverse secrets and Azure Key Vault integration
- Dataverse Web API errors explained
- Dynamics 365 and Conditional Access
- GraphQL and Dynamics 365
- Integrating Copilot Studio with MCP servers
- Integrating Dynamics 365 with custom mobile apps
- Integrating Dynamics 365 with Zapier and Make
- Power Automate flow failures explained
- Power Platform ALM with Azure DevOps
- Data integration for real-time marketing
- Tenant-to-tenant migration scenarios
- Webhooks vs events in Dataverse