If you’ve been keeping an eye on the Microsoft Entra roles lately, like I do with my own MicrosoftDocsTracker, you might have noticed a new addition to the built-in roles called AI Reader.
The AI reader role is designed to provide specific reader access to components relating to AI within Microsoft 365, without providing complete administrative access or multiple specific reader roles. Lets explore what the role does.
Page Contents
Who is this role for?
Sometimes it is not always clear which role is suitable for who in Microsoft Entra. So, this role is perfect for users who need to monitor AI adoption and health but don’t need to change any configurations. You should assign the AI Reader role to users who need to perform the following tasks:
Read all aspects of Microsoft 365 Copilot.
Read AI-related enterprise services, including extensibility and copilot agents.
Read and configure Azure and Microsoft 365 service health dashboards.
View usage reports, adoption insights, and organisational insights.
If a user just needs to read usage reports in Microsoft 365 relating to Copilot, instead of assigning them the AI reader role, which would also allow them to read other configurations, you can just assign them the Reports Reader role.
Important: It is a Privileged Role
Something to consider is that even though this is a “Reader” role, Microsoft has officially marked it as privileged (similar to the Global reader role), as the information it allows you to read could otherwise be used to manipulate users which could lead to a breach. Ultimately, it reveals is sensitive information, such as seeing how your staff uses AI, which agents are active, Agent configuration and viewing detailed usage reports, together this provides a high level of insight into your company’s inner workings.
Because it’s a privileged role, you should treat it with the same security mindset as other privileged roles. Use Privileged Identity Management for “just-in-time” access rather than leaving it assigned permanently.
What can the AI Reader actually do?
The role comes with a specific set of permissions, or “Actions”, which can be extracted using the Graph API. Here is a breakdown of what the technical “Allowed Actions” built into the role actually mean:
| Permission Group | Explanation |
|---|---|
| Service Health | View and manage health alerts for Azure and M365. |
| Directory Objects | Read-only access to users, groups and admin units. |
| Application Info | View details of registered apps, owners and policies. |
| Entitlement & Roles | View role assignments and license details. |
| Copilot & AI | Full read access to Copilot properties and entities. |
| Message Center | Read official updates and announcements from Microsoft. |
| Usage Reports | Access all M365 usage and adoption data. |
| Portal Access | Read-only access to the M365 admin web portal. |
Summary
The AI Reader role is a welcome addition for organisations who want to delegate Copilot reporting and monitoring without giving away the “keys to the kingdom.” Just remember to audit its use regularly, as the privileged tag means it carries more weight than your standard reader role.

