A cloud-based identity and access management service for securing user authentication and resource access
The published Claude for Outlook connector cannot be changed through Microsoft Entra to autonomously send email or create calendar events; only Anthropic can add those capabilities and request the corresponding Microsoft Graph permissions.
Microsoft’s listing shows that Claude for Outlook currently uses:
-
Calendars.Read—calendar events are read-only, and new events open as user-controlled draft appointments. -
Mail.ReadWrite—Claude can read/search messages and perform limited triage such as marking messages read or moving them. - It does not send through Microsoft Graph; replies open as user-controlled drafts. ^1^
Therefore, neither a tenant administrator nor Microsoft Support can turn on autonomous calendar writing or sending for Anthropic’s published connector. Submit the request to Anthropic Support through Anthropic’s official Help Center or its Claude connector feature-request channel.
Check which application you configured
The client ID included in the question is not the Microsoft-documented app ID for the published Claude for Outlook application. Do not add permissions until its ownership is confirmed:
- Open Microsoft Entra admin center → Entra ID → App registrations → All applications.
- Search using the client ID.
- Check Overview → Publisher domain/ownership.
- Also check Entra ID → Enterprise apps → All applications, then search by that client ID.
- If it is not an application that your organization developed and controls, do not modify it or add credentials.
Tenant and client IDs identify resources and are not secrets. However, revoke or rotate any client secret, authorization code, or access/refresh token immediately if it was exposed to an untrusted party.
If this is your own custom integration
These steps apply only if your organization owns the app registration and can change the integration’s OAuth configuration and code. Adding permissions alone does not implement write operations.
An administrator with an appropriate Entra role must perform or approve the consent operation. Microsoft documents Cloud Application Administrator or Application Administrator as sufficient for these delegated Graph permissions; Privileged Role Administrator can grant consent for any API permission. ^2^
- Go to Entra ID → App registrations → All applications → your app → API permissions.
- Select Add a permission → Microsoft Graph → Delegated permissions.
- Add only the operations the integration implements:
-
Mail.ReadWriteto create, read, update, and delete mail. -
Calendars.ReadWriteto create, read, update, and delete calendar events. -
Mail.Sendif it must actually send email. -
offline_accessif it requires refresh tokens for continued access when the user is not actively present.
-
- Select Grant admin consent after reviewing the requested access.
- Disconnect and reconnect the Microsoft account so the application completes a new authorization flow and obtains a new token.
Mail.ReadWrite explicitly does not include sending email; Mail.Send is separate. Calendars.ReadWrite supports creating, reading, updating, and deleting events. ^3^
Although these delegated permissions do not inherently require administrator consent, Microsoft’s recommended tenant consent policy prevents ordinary end users from consenting to mail and calendar permissions such as Mail.ReadWrite and Calendars.ReadWrite. An administrator may therefore need to approve them. ^4^
The custom integration’s authorization request must include the delegated scopes, for example:
openid profile offline_access
https://graph.microsoft.com/User.Read
https://graph.microsoft.com/Mail.ReadWrite
https://graph.microsoft.com/Mail.Send
https://graph.microsoft.com/Calendars.ReadWrite
Delegated scopes are requested through the OAuth scope parameter and operate on behalf of the signed-in user. ^5^
After reconnection, inspect the new access token and verify that its scp claim contains the required scopes. Then test actual Graph operations for creating an event, updating a message, and sending mail. If the token contains the scopes but the integration still only reads or opens drafts, the missing functionality is in the connector/application implementation rather than Entra consent.
References