Prepare a queue mailbox for incoming email
A support address can become a reliable Customer Service intake point only when the queue and its mailbox are configured for the same purpose. The queue defines how Customer Service organizes incoming work. The mailbox connects that queue address to the email system and records whether server-side synchronization can process messages.
Treat these components as one design boundary. A valid address on a queue doesn't prove that Customer Service can receive its messages. Likewise, a successfully tested mailbox doesn't determine which messages the queue converts to activities. Both parts must be ready before automatic case creation or routing can process the email.
Connect the queue to its mailbox
In Copilot Service admin center, a basic queue includes an Incoming Email address and a Convert Incoming Email To Activities setting. The address identifies the mailbox that customers use. The conversion setting defines which received messages become email activities in Microsoft Dataverse.
Finalize the conversion decision from the intake plan before you prepare the mailbox. Choose the setting according to the address's purpose. A dedicated support address commonly needs to capture new requests from customers who don't yet have a related Dynamics 365 record. An address used only for ongoing communication can use a narrower tracking boundary. If the setting excludes the initial customer message, later stages never receive an email activity to evaluate.
When you save a queue, Customer Service creates and associates a mailbox record. One queue has one associated mailbox. The mailbox doesn't store the email activity itself. Instead, it stores the configuration and processing status that server-side synchronization uses for the queue address.
Key responsibilities remain separate:
| Component | Responsibility |
|---|---|
| Queue | Defines the support address, activity-conversion behavior, membership, and work-management settings. |
| Mailbox | Defines the email server profile, synchronization methods, approval state, and processing status for the address. |
| Email activity | Stores the synchronized message and its relationships in Dataverse. |
| Queue item | Places the email activity or another record in a queue for processing. |
This distinction helps you avoid a common design mistake: troubleshooting an automatic case creation rule before confirming that the queue mailbox created the source email activity.
Select the synchronization configuration
Server-side synchronization connects Microsoft Dataverse with the organization's email system. For Exchange Online in the same tenant, environments normally include a Microsoft Exchange Online server profile. Other supported email systems require an appropriate profile and authentication model.
The queue mailbox must use a server profile that can reach the actual mailbox. Its incoming email synchronization method must allow server-side synchronization to receive messages. Outgoing synchronization also matters when the design sends automatic acknowledgments or representatives reply from the queue address.
Review these dependencies with the email administrator:
- The published support address exists in the email system and matches the queue address.
- The email server profile supports the organization's email service and authentication requirements.
- The mailbox uses the intended incoming and outgoing synchronization methods.
- Email settings permit the required queue mailbox to process messages.
- Attachment limits and blocked file types support the organization's service scenarios.
This module doesn't replace the broader planning required for Exchange or another email service. The functional consultant owns the Customer Service intake design and coordinates with the administrators who own the tenant, mailbox, licensing, security, and mail flow.
Account for mailbox approval
Environment email settings can require approval before server-side synchronization processes email for users or queues. Queue mailboxes have different approval considerations from a user's own mailbox, and the person who approves an address needs the required administrative role and Approve Email Addresses for Users or Queues privilege.
Don't treat approval as an optional troubleshooting step. Determine during design whether the environment requires approved queues, identify the approver, and include approval in the deployment sequence. If approval is required but missing, testing can fail or the mailbox can remain disabled for processing.
Organizations can change environment settings so that unapproved queue mailboxes are processed. That choice changes a security control for the environment, not just one intake flow. Evaluate the governance effect instead of disabling the requirement only to make a mailbox test pass.
Test and enable the mailbox
Use Test & Enable Mailbox after the address, server profile, synchronization methods, and approval requirements are ready. The operation tests the mailbox configuration and enables successful directions for processing. It runs asynchronously, so allow time for the results to update.
Review the status fields that apply to the intake flow:
- Incoming Email Status indicates whether server-side synchronization can receive email for the mailbox.
- Outgoing Email Status indicates whether the mailbox can send email, which is necessary for queue replies and automatic responses.
- Appointments, Contacts, and Tasks Status applies to other synchronization workloads and isn't the proof that support email intake works.
A successful configuration test confirms connectivity and configuration for the tested direction. It doesn't confirm that queue conversion, automatic case creation, or routing behaves correctly. Those stages require separate functional tests.
If a test fails, open the mailbox and review its alerts. An alert can identify an approval, authentication, server-profile, permission, or connection issue. Depending on the failure, the service can retry later or disable a processing direction. Correct the underlying configuration and run Test & Enable Mailbox again rather than moving ahead with a disabled mailbox.
Establish the intake baseline
Before you configure downstream automation, send a controlled message to the queue address and verify the earliest outcomes:
- Confirm that the message reaches the mailbox in the email system.
- Confirm that Incoming Email Status is successful.
- Confirm that server-side synchronization creates an email activity in Dataverse.
- Confirm that the expected queue contains a queue item for the email.
Record the sender, recipient fields, subject, timestamp, and expected queue for the test. This baseline gives later tests a known source message and separates mailbox processing from case-creation and routing behavior.
For more information, see Create and manage basic queues for cases, Connect to Exchange Online, and Set up server-side synchronization.