Forum Discussion
Using AD Job Title to direct Copilot Agent Responses
Hopefully, the following makes sense:
TL; DR: How do I use AD attributes to tailor Copilot Agent Responses?
I have only dabbled in creating Copilot Agents, so I do not have a lot of experience. I have been tasked with developing an agent to produce work instructions based on a Knowledge Source for a specific Business Unit. We want to tailor the responses to specific Job Titles, e.g. we want to avoid using permissions if possible. However, we want to be able to tailor the responses within the one agent.
Can an AD attribute be used to achieve tailored responses?
Yes, you can use AD attributes to tailor responses within a single Copilot agent. For example, the jobTitle attribute from Azure AD can be pulled in when a user signs in. Copilot Studio can pull Azure AD (Entra ID) attributes into the conversation if the user is authenticated through your tenant. That value can then be mapped into a variable in Copilot Studio and used to influence the way responses are generated.
So instead of building multiple agents or relying on permissions, you can just have one agent that adapts its answers based on the user’s role.
The only thing to keep in mind is that some attributes might not surface by default — if you want custom ones, you may need to expose them through Entra ID (Azure AD) claims. But for common attributes like job title or department, it works out of the box.
Please let me know if you need more assistance.
2 Replies
Yes, you can use AD attributes to tailor responses within a single Copilot agent. For example, the jobTitle attribute from Azure AD can be pulled in when a user signs in. Copilot Studio can pull Azure AD (Entra ID) attributes into the conversation if the user is authenticated through your tenant. That value can then be mapped into a variable in Copilot Studio and used to influence the way responses are generated.
So instead of building multiple agents or relying on permissions, you can just have one agent that adapts its answers based on the user’s role.
The only thing to keep in mind is that some attributes might not surface by default — if you want custom ones, you may need to expose them through Entra ID (Azure AD) claims. But for common attributes like job title or department, it works out of the box.
Please let me know if you need more assistance.
Thanks, Pradejain. Is it best to use a Copilot Agent Tool, or just allow it to natively search for the current users details?
