Using Service Accounts To Build Copilot Agents

Question

Using Service Accounts To Build Copilot Agents

Siyanda Ncube 0

I’d like to understand the best practices when creating a Copilot agent that will be used individually by employees in my company. Should I use a service account so that the connection references isn’t tied to my own company email, or is it recommended to use a normal user account? I’m also concerned about any potential risks or compliance implications of using a service account with Copilot. What is the recommended and secure approach for this scenario?”

0 comments

1 answer

Your answer

Answer 1

You should not use a service account for Copilot agents that will be used by employees individually. Instead, use user-delegated authentication (normal user accounts) so that each employee’s actions and data access are performed in their own security context.

Why?

Security & Compliance: Service accounts can bypass individual user permissions, making it difficult to audit actions and increasing the risk of unauthorized data access.
Auditability: Using user accounts ensures all actions are traceable to the actual user, supporting compliance and audit requirements.
Least Privilege: Each user only gets access to what they are permitted, reducing risk.

Risks of service accounts:

Shared credentials can be misused.
Difficult to enforce least-privilege access.
May violate organizational compliance or Microsoft licensing terms.

Thanks,

Prasad Das

*************************************************************************

If the response is helpful, please click on "upvote" button. Your feedback is important to us. Please rate us: 🤩 Excellent 🙂 Good 😐 Average 🙁 Needs Improvement 😠 Poor

Share via

Using Service Accounts To Build Copilot Agents

1 answer

Your answer