I am trying to also Claude to access my email and it can not do it.

Carol Giles 0 Reputation points
2026-11-19T06:44:51.8+00:00

I have used the connector and all it can do is read. I want it to be able to read and write. how do I do that?

here is my information

  • Account: ******@gilesgroup.com
  • Tenant ID: ff9d3420-746c-43b9-9efb-453332350fd9
  • App (client) ID: 07c030f6-5743-41b7-ba00-0a6e85f37c17
  • Specifically needed: Calendars.ReadWrite and Mail.ReadWrite (delegated)
Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-19T06:46:30.4433333+00:00

    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:

    1. Open Microsoft Entra admin center → Entra ID → App registrations → All applications.
    2. Search using the client ID.
    3. Check Overview → Publisher domain/ownership.
    4. Also check Entra ID → Enterprise apps → All applications, then search by that client ID.
    5. 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^

    1. Go to Entra ID → App registrations → All applications → your app → API permissions.
    2. Select Add a permission → Microsoft Graph → Delegated permissions.
    3. Add only the operations the integration implements:
      • Mail.ReadWrite to create, read, update, and delete mail.
      • Calendars.ReadWrite to create, read, update, and delete calendar events.
      • Mail.Send if it must actually send email.
      • offline_access if it requires refresh tokens for continued access when the user is not actively present.
    4. Select Grant admin consent after reviewing the requested access.
    5. 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

    1. Claude for Outlook (zerotrust)
    2. Grant tenant-wide admin consent to an application (portal)
    3. Microsoft Graph permissions reference
    4. Manage app consent policies (ms-graph)
    5. Developer’s guide to requesting permissions and consent in Microsoft Identity Platform
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.