Tools
WHD Microsoft 365 Modern Authentication: Incoming Emails Not Processed into Tickets, Graph API Access Denied (403) for Mail.Read
This article describes the “Graph API access denied (status 403). Check Mail.Read permissions.” error and the issue where incoming emails are not processed into WHD tickets after setting up Microsoft 365 Modern Authentication.
First published date
Last published date
Overview
For Microsoft 365 mailboxes, only modern authentication is supported in WHD.
With that, it is necessary to have the API permissions of Azure APP for WHD correctly configured in order for WHD to manage the mailboxes and turn them into tickets.
Product section
Cause
- WHD Azure APP Registration API permission is missing
- Granting admin consent for {your tenant} is not configured.
Resolution
- On the Home page under Azure services, click Azure Active Directory.
- In the navigation pane under Manage, click App registrations.
- Select the App registration created for WHD
- In the navigation menu, click API Permissions.
- In the Request API permissions sidebar, search for and enable the required permissions.
The following table lists the permissions to enable on this screen.Permission Access Description Mail.ReadWrite Read and write access to user mail Allows the app to create, read, update, and delete email in user mailboxes. Does not include permission to send mail. email View the user's email address Allows the app to read your users' primary email address. offline_access Access the user's data anytime Allows the app to read and update the user's data, even when the user is not currently using the application. User.Read Sign-in and read user profile Allows users to sign in to the app, and allows the app to read the profile of signed-in users. It also allows the app to read basic company information of signed-in users. Mail.Send (if the incoming email is the same as outgoing email) Send mail as a user Allows the app to send mail as you. - Click Grant admin consent for {your tenant}, which allows an admin to grant admin consent to the permissions configured for the application. When you select the button, a dialog requests that you confirm the consent action.
-
After you have granted consent, the permissions that required admin consent are shown as having consent granted.
If you are not the tenant admin or if no permissions have been configured for the application, the Grant admin consent button is disabled.
If permissions were granted but not yet configured, the admin consent button prompts you to handle these permissions. You can add them to configured permissions or remove them.
- Remove any other preexisting permissions from the remaining permission drop-down menus.