Skip to content

Commit eb71895

Browse files
authored
some changes
1 parent faecd86 commit eb71895

2 files changed

Lines changed: 26 additions & 25 deletions

File tree

Lines changed: 24 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,51 +1,50 @@
11
---
2-
title: Test and Enable fails due to unrecognized Microsoft 365 User Email Address
3-
description: Provides solution information for Test and Enable failures caused by unrecognized email addresses.
4-
ms.date: 08/27/2025
2+
title: Test And Enable Failed Because No User Was Found Error
3+
description: Explains how to resolve Test and Enable failures in Dataverse caused by unrecognized Microsoft 365 email addresses.
4+
ms.date: 09/05/2025
55
ms.custom: sap:Email and Exchange Synchronization\Set up and configuration of server-side synchronization
66
author: debrau
77
ms.author: debrau
8+
ms.reviewer: debrau
89
---
9-
# Test and Enable fails due to unrecognized Microsoft 365 User Email Address
10+
# "Test and Enable failed because no user was found" error when configuring mailbox synchronization
11+
12+
This article explains how to resolve the "Test and Enable failed because no user was found" error that occurs when you configure mailbox synchronization in Dataverse with Microsoft 365.
1013

1114
## Symptoms
1215

13-
When attempting to perform Test and Enable on a mailbox in Dataverse, users may encounter the following error message:
16+
When you attempt to [test and enable a mailbox](/power-platform/admin/connect-exchange-online#test-the-configuration-of-mailboxes) in Dataverse, you might receive the following error message:
1417

15-
>Test and Enable failed because no user was found with the email address "<[email protected]>" in the Microsoft 365 tenant associated with this mailbox's Email Server Profile. Verify the user exists in [...]
18+
> Test and Enable failed because no user was found with the email address "`<[email protected]>`" in the Microsoft 365 tenant associated with this mailbox's Email Server Profile. Verify the user exists in [...]
1619
1720
## Cause
1821

19-
This error typically occurs when:
22+
This error occurs if:
2023

21-
- The specified email address does not exist in the Microsoft 365 tenant linked to the mailbox's Email Server Profile.
22-
- The email address is not properly configured as a User Principal Name (UPN), SMTP address, or Mail address on the user object.
23-
- The mailbox belongs to a different Microsoft 365 tenant, and a Cross Tenant Email Server Profile has not been configured.
24+
- The specified email address doesn't exist in the Microsoft 365 tenant linked to the mailbox's email server profile.
25+
- The email address isn't properly configured as a User Principal Name (UPN), SMTP address, or mail address on the user object.
26+
- The mailbox belongs to a different Microsoft 365 tenant, and a cross-tenant email server profile isn't configured.
2427

2528
## Resolution
2629

27-
**Step 1: Validate User Existence and Email Address Configuration**
28-
2930
An administrator should verify that the user exists in the correct Microsoft 365 tenant and that the email address is properly configured.
3031

31-
To validate UPN, SMTP, or Mail address:
32+
To confirm the UPN, SMTP, or mail address for the user:
3233

3334
1. Sign in to the Microsoft 365 Admin Center.
34-
2. Navigate to **Users > Active Users**.
35-
3. Search for the user using the email address in question.
36-
4. Open the user profile and confirm the user has at least one email address matching the email address in the Dataverse mailbox record:
37-
- User Principal Name (UPN) or Username matches the email address.
38-
- In the **Mail** tab, click **Edit Exchange properties**. In **Manage mailboxes**, open the mailbox. On the **General** tab, confirm the **User ID** or the **Email addresses** properties contain the email address.
39-
- **Note:** If a matching address is found in the **Email addresses**, click **Manage email address types** to confirm the address type is “SMTP”.
4035

41-
If the user exists in the same tenant as your Dataverse instance but does not have a matching UPN, SMTP, or Mail email address, update the Dataverse mailbox record to a valid email address for the user.
36+
2. Navigate to **Users** > **Active Users**.
4237

43-
If the user does not exist in the same tenant as your Dataverse instance, proceed to **Step 2**.
38+
3. Search for the user using the email address in question.
39+
40+
4. Open the user profile and confirm the user has at least one email address matching the email address in the Dataverse mailbox record:
4441

45-
**Step 2: Configure Cross Tenant Email Server Profile**
42+
- **User Principal Name (UPN)** or username matches the email address.
43+
- Under the **Mail** tab, select **Edit Exchange properties**. In **Manage mailboxes**, open the mailbox. On the **General** tab, confirm the **User ID** or **Email addresses** fields contain the email address.
4644

47-
If the mailbox resides in a different Microsoft 365 tenant, you must configure a Cross Tenant Email Server Profile.
45+
> [!NOTE]
46+
> If a matching address is found in the **Email addresses**, select **Manage email address types** to confirm the address type is **SMTP**.
4847
49-
Refer to the following documentation:
48+
If the user exists in the same tenant as your Dataverse instance but doesn't have a matching UPN, SMTP, or mail address, update the Dataverse mailbox record to use a valid email address for the user.
5049

51-
[Configure cross-tenant synchronization](/power-platform/admin/connect-exchange-online-server-profile-oauth)
50+
If the user doesn't exist in the same tenant as your Dataverse instance, you should [configure a cross-tenant email server profile](/power-platform/admin/connect-exchange-online-server-profile-oauth).

support/power-platform/dataverse/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -150,6 +150,8 @@
150150
href: email-exchange-synchronization/troubleshooting-monitoring-server-side-synchronization.md
151151
- name: '"Tracked to Dynamics 365" category is added to a mailbox'
152152
href: email-exchange-synchronization/tracked-to-dynamics-365-category-added.md
153+
- name: "Test and Enable failed because no user was found" error
154+
href: email-exchange-synchronization/test-enable-fails-for-unrecognized-email-address.md
153155
- name: Test Connection fails from Email Server Profile
154156
href: email-exchange-synchronization/test-connection-fails-email-server.md
155157
- name: '"The account does not have permission to impersonate the requested user" error'

0 commit comments

Comments
 (0)