Episode Details

Most organizations think “HR automation” means a chatbot glued to a SharePoint folder full of PDFs. They’re wrong. That setup doesn’t automate HR. It accelerates confident nonsense — without evidence, without control, and without a defensible decision trail. Meanwhile the real costs compound quietly:

• Screening bias you can’t explain
• Ticket backlogs that never shrink
• Onboarding that drags for weeks
• Audits that turn into archaeology

This episode is about shifting from passive HR data to deterministic HR decisions. No magical thinking.
No “prompt better” optimism. We’re building governed workflows — screening, triage, onboarding — using Copilot Studio as the brain, Logic Apps as the muscle, and evidence captured by default. If it can’t survive compliance, scale, and scrutiny — it doesn’t ship. Subscribe + Episode Contract If you’re scaling HR agents without turning your tenant into a policy crime scene, subscribe to M365 FM. That’s the contract here: Production-grade architecture.
Repeatable patterns.
Defensible design. This is not a feature tour.
Not legal advice.
And definitely not “prompt engineering theater.” We’ll walk three governed use cases end-to-end: • Candidate screening with bias and escalation controls
• HR ticket triage with measurable deflection
• Onboarding orchestration that survives retries and long-running state But first — we need to redefine what an HR agent actually is. Because it’s not a chatbot. HR Agents Aren’t Chatbots A chatbot answers questions. An HR agent makes decisions. Screen or escalate.
Route or resolve.
Approve or reject.
Provision or pause. The moment an LLM executes decisions without controlled action-space and an evidence trail, you don’t have automation. You have conditional chaos. The lever isn’t “smarter AI.” The lever is determinism:

• What actions are allowed
• Under which identity
• With which inputs
• With which guardrails
• Logged how

If the system can’t prove what it did and why — it didn’t do HR work. It generated text. Target Architecture Copilot Studio = Brain
Logic Apps Standard = Muscle
MCP = Tool contract
Dataverse = Durable memory
Azure Monitor = Operational truth
Entra = Identity boundary Conversation reasons.
Tools enforce.
State persists.
Logs prove. If you collapse those layers, you lose governance. If you separate them, you get scale. Governance = Action Control Governance in agentic HR isn’t a committee. It’s action control. Action-space is everything the agent can do. Not say.
Do. Every tool must have:

1. Identity
2. Policy gates
3. Telemetry

No identity → no ownership
No policy → no constraint
No telemetry → no defensibility HR doesn’t run on hope. Human-in-the-Loop = Circuit Breaker Human-in-the-loop isn’t humility. It’s a circuit breaker. Confidence drops?
Policy risk triggered?
Irreversible action pending? Stop. Create an approval artifact.
Package evidence.
Record reason code.
Proceed only after decision. If the workflow keeps running, it isn’t HITL. It’s a notification. Observability If someone asks what happened, you should not investigate. You should retrieve. Audit-grade observability means:

• Prompt context captured
• Retrieval sources logged
• Tool calls correlated
• State transitions recorded
• Human overrides documented

Correlation IDs across Copilot, MCP, Logic Apps, and Dataverse. No reconstruction theater. Just evidence. Three Workflows, One Control Plane All workflows follow: Event → Reasoning → Orchestration → Evidence 1. Candidate Screening High-risk decision system. Structured rubric.
Proxy minimization.
Confidence gates.
Recorded approvals.
Defensible shortlist. 2. HR Ticket Triage High-volume operational system. Deterministic classification