Concept
A service account is a shared non-human account used to run automation under one set of credentials; for AI agents it lacks per-agent attribution, ownership, lifecycle and policy enforcement, which is why dedicated agent identities are recommended instead.
| Type | Concept |
|---|
2025-11-23 · Video on YouTube
Your Power Automate email flows aren’t clever automations, they’re HR risk wrapped in HTML. You wire a flow to a “service account,” fight through MFA once, get it working, and decide it’s done. It’s not done. It’s brittle, over-privileged, impossible to audit…
2025-12-21 · Video on YouTube
Security drift in Active Directory and Azure AD isn’t a single bug — it’s the slow, invisible decay of identity, permissions, and governance posture that happens when environments aren’t routinely managed and remediated. Over time, this drift increases risk…
2026-06-29 · Video on YouTube
Artificial Intelligence is entering a new phase. The real opportunity is no longer deploying a single Copilot—it is transforming how organizations operate through an Agentic Operating Model. In this episode of the M365.fm Podcast, we explore why the future of…
2026-04-26 · Video on YouTube
This episode explains why Power Automate often creates more problems than it solves when used at scale. While it works well for simple, user-driven tasks, it breaks down with complex workflows due to throttling, weak error handling, and limited scalability.…
2026-05-12 · Video on YouTube
Learn why personal accounts create automation risk and how service principals, managed identities, least privilege, and monitoring improve cloud security.
2026-03-12 · Video on YouTube
This episode challenges one of the most common assumptions in the Microsoft ecosystem: 👉 “If it’s Microsoft, it must already be secure.” The reality is the opposite. Power Platform is enterprise-grade secure by design—but becomes risky the moment governance…
2026-06-30 · Video on YouTube
This episode explores why Computer-Using Agents (CUA) could fundamentally change the future of enterprise software. Instead of humans navigating dashboards, menus, and forms, AI agents will increasingly interact with applications on our behalf. The user…
A service account is still a user, so MFA, password expiry and conditional access apply. The episode says flows become brittle, over-privileged and impossible to audit cleanly. · From the episode: Service Accounts vs App Registrations for…
Flows wake up, find nothing valid and either fail or thrash. The episode says they can send duplicates like a jammed label maker, because a robot cannot approve an MFA prompt at 2:14 a.m. · From the episode: Service Accounts vs App Registrations for…
Flows run under a user identity that is over-privileged and hard to audit. The episode frames email flows built this way as HR risk wrapped in HTML, since a service account is still a user. · From the episode: Service Accounts vs App Registrations for…
App registrations, as compared in the episode title. They avoid human-oriented authentication behavior and give a cleaner, more auditable identity for unattended automation. · From the episode: Service Accounts vs App Registrations for…
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated:
EN
Deutsch
Español
Français
Italiano
Português
Nederlands
Polski
Bahasa Indonesia
Русский
Українська
العربية
עברית
日本語
한국어