Self-service data access with Copilot Studio: the agent takes requests, never makes decisions
adnan_hashmi · x · 2026-10-20
Marco Österlin walks through a self-service data product access flow on Microsoft Fabric / Microsoft 365 / Entra ID, combining five pieces: Copilot Studio for the request conversation, SharePoint as the data product register and request log, Power Automate for approvals, Teams Approvals for the owner's decision, and Entra ID security groups to grant access. The same pattern works with Databricks Unity Catalog.
The core design principle: the agent never makes an access decision. It only asks which product the user wants and why; identity comes from the M365 session, and owner/access group are looked up from the register. Responsibilities split four ways — the agent takes requests, the register defines products and owners, the owner approves, Entra ID grants.
More from coding & agent
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23
- Capy 0.5.0 lets Claude Pro/Max subscribers reuse their plan quota, adds OIDC cloud access — garrytan · 2026-10-23
- You.com CEO Richard Socher: legacy code is human slop, let AI clean it up — RichardSocher · 2026-10-23
- Let agents design a single-line glance component so you can track them from the sidebar — blixt · 2026-10-23