Learn how to configure and run Power Automate flows using Service Principal (Application User) — the enterprise-grade approach for secure, scalable, and non-human automation in the Power Platform.

In this step-by-step session, Dhruvin (Microsoft MVP) explains every stage of setting up and using Service Principal with Power Automate, including licensing, permissions, and Dataverse integration.

✨ In this video, you’ll learn:

🔹 What is Service Principal and when to use it

🔹 How to register an App in Microsoft Entra ID (Azure AD)

🔹 Setting up Client ID, Secret, and Tenant ID

🔹 Adding Application User in Power Platform Admin Center

🔹 Assigning Roles and Permissions

🔹 Creating Power Automate Flow with Service Principal

🔹 Testing and verifying Dataverse entries

🔹 Understanding Licensing Requirements (Per Flow vs Process License)

💡 Why this matters: Service Principal ensures no dependency on user credentials, avoids license expiry issues, and enables true enterprise governance in Power Platform.

📚 Best suited for:

✅ Power Platform Admins & Architects

✅ Enterprise Developers working with ALM

✅ Power Automate Professionals using Dataverse or Dynamics 365

👉 Watch till the end to understand licensing implications and real-world use cases.

🧭 Chapters (Without Timestamps)

⚙️ Introduction to Service Principal

💡 When to Use Service Principal in Power Automate

🏗️ Creating Service Principal in Azure Entra ID

🔑 Setting Client ID, Secret, and Tenant ID

🧱 Adding App User in Power Platform Admin Center

👨‍💼 Assigning System Administrator Role

🔗 Connecting Service Principal in Power Automate Flow

🧩 Creating Dataverse Flow using Service Principal

📊 Testing and Comparing Flow Executions

💰 Understanding Licensing Requirements

✅ Summary and Key Learnings

💎 Key Takeaways

✅ Service Principal = Non-Human Identity for secure automation

✅ Ideal for mission-critical or enterprise-wide flows

✅ Requires Client ID, Secret, Tenant ID for authentication

✅ Add as Application User in Power Platform environment

✅ Needs System Administrator or custom security role

✅ Works best with Dataverse (not SharePoint or standard connectors)

✅ Requires Per Flow or Process License, not user license

✅ Eliminates dependency on personal credentials