Possible Microsoft Graph API Permission/Endpoint Issue Affecting Teams–Exchange Integration

Question

In Microsoft Teams where I cannot create teams or schedule meetings. I’m also seeing the error “UserMailboxEndpointFetchFailed: Could not fetch user exchange mailbox endpoint using AutoDV2.” This suggests Teams is unable to reach my Exchange mailbox. I want to confirm whether the root cause may be related to Graph API access.

Could this problem be caused by missing or misconfigured Microsoft Graph API permissions or blocked endpoints?

Specifically, is Teams failing to connect to my Exchange mailbox because required Graph permissions (such as Calendar.Read, Mail.Read, or EWS.AccessAsUser.All) have not been granted admin consent or are restricted within my tenant or app registration?

Answer 1

Dear @Holmes Shanquaneta

Welcome to Microsoft Q&A Forum!

Based on your description, I can see that if you’re signed in to Microsoft Teams but unable to create new teams or schedule meetings, and you see the error “UserMailboxEndpointFetchFailed” with the message “Unable to import user Exchange mailbox endpoint using AutoDV2,” this typically indicates a connectivity issue between Teams and your Exchange mailbox.

This error occurs because Teams relies on Autodiscover Version 2 (AutoDV2) to locate Exchange Web Services (EWS) for calendar and scheduling features. When AutoDV2 fails, core functionalities like meeting scheduling and team management are impacted. Common causes include:

• Incorrect or restrictive EWS policies
• Missing application permissions
• Outdated hybrid configuration settings
• Network or firewall rules blocking OAuth authentication

For more details, refer to Microsoft’s official guidance in the Troubleshooting interaction between Teams and Exchange Server article.

Therefore, from the document page, if you’re an administrator in your tenant, here are some steps you can try to see if they can help you in this issue:

1.Verify the Exchange Server version: launch the Exchange Management Shell, then run this command:

Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion

If your server isn’t running the most recent CU, download and install the latest version to ensure compatibility and stability.

2.Permit Teams to access Exchange Web Services (EWS): use Exchange PowerShell to make sure the parameter is set to across your organization:EwsApplicationAccessPolicyEnforceAllowList

Get-OrganizationConfig | Select-Object Ews*

If the parameter is set to EnforceAllowList, only the clients listed in EwsAllowList can access EWS.

Make sure MicrosoftNinja/*, Teams/*, and SkypeSpaces/* are included as array members of the EwsAllowList parameter. If they aren’t present, add them with the following command.

Set-OrganizationConfig -EwsApplicationAccessPolicy EnforceAllowList -EwsAllowList @{Add="MicrosoftNinja/*","*Teams/*","SkypeSpaces/*"}

If the EwsEnabled parameter is set to False, change it to True or set it to Null (empty).

3. Verify that Teams is not blocked from EWS access for the user:

Run the following Exchange PowerShell check to confirm the user’s mailbox has the EwsApplicationAccessPolicy parameter set to EnforceAllowList

Get-CASMailbox <UserPrincipalName> | Select-Object Ews*

If the parameter is set to EnforceAllowList, only the clients listed in EwsAllowList can access EWS.

Make sure MicrosoftNinja/*, Teams/*, and SkypeSpaces/* are included as array members in EwsAllowList. If any are missing, add them using the following command:

Set-CASMailbox <UserPrincipalName> -EwsApplicationAccessPolicy EnforceAllowList -EwsAllowList @{Add="MicrosoftNinja/*","*Teams/*","SkypeSpaces/*"}

If the EwsEnabled parameter is set to False, change it to True. Otherwise, Teams will block EWS access.

Additionally, you can use Teams meeting delegation to verify whether the Teams Calendar app connectivity test succeeds.

---

As a forum moderator, I have limited in my resources and do not have the right to access to your environment to assist directly. So, if the issue still isn’t resolved after trying the methods above, I highly recommend requesting direct support from Microsoft via the Teams Admin Portal based on the guidance. By proceeding as outlined below, you can receive more in‑depth assistance.

I hope this information can help you in this case and if you are not Admin, you can try to clear cache first at a user level. Also, please feel free to let me know for further assistance. Wish you a pleasant day!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

The issue you are experiencing with Microsoft Teams not being able to create teams or schedule meetings, along with the error "UserMailboxEndpointFetchFailed: Could not fetch user exchange mailbox endpoint using AutoDV2," may indeed be related to Microsoft Graph API permissions or blocked endpoints.

If the required Graph API permissions such as Calendar.Read, Mail.Read, or EWS.AccessAsUser.All have not been granted admin consent or are restricted within your tenant or app registration, this could prevent Teams from accessing the necessary Exchange mailbox endpoints.

Additionally, if there are any EWS application policies in place that restrict access, this could also lead to similar issues. It is advisable to check the permissions assigned to the app registration and ensure that they comply with your organization's policies to allow Teams to connect to Exchange successfully.

For further troubleshooting, you may want to verify the EWS application access policies and ensure that your application's User-Agent is correctly configured in the allowlist or blocklist as needed.