web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Shared mailbox email works for one user but fails for others in Business Central

(4) ShareShare
ReportReport
Posted on by 215
Hi everyone,
 
We are experiencing an issue in Dynamics 365 Business Central (SaaS) when sending emails using a shared mailbox configured as an Email Account. The same shared mailbox works correctly when emails are sent by one user, but fails when the exact same action is performed by other users.

Specifically, sending emails from user1 works without any issues. However, when sending from user2, the process fails with the error “Cannot submit message. Status code: 403”. When sending from user3, the error returned is “The mailbox is either inactive, soft-deleted, or is hosted on-premise. Status code: 404”. Both errors occur when using the same shared mailbox and the same Business Central email setup.

We have reviewed the email account configuration in Business Central and it appears to be correct. We do not see any differences in the Business Central setup that would explain why the behavior changes depending on the user, and the shared mailbox itself is active and available in Microsoft 365.

Additionally, since 2026-05-04, several email accounts that were previously working in Business Central have stopped working unexpectedly, which makes us wonder if there has been a recent change related to permissions, authentication, or the email integration used by Business Central.

Could anyone clarify why a shared mailbox might work for one Business Central user but return 403 or 404 errors for others, and whether there are any known changes or considerations that could explain why multiple email accounts stopped working suddenly from that date?
 
Thank you in advance for any guidance.
I have the same question (0)
  • Suggested answer
    OussamaSabbouh Profile Picture
    17,586 Super User 2026 Season 1 on at
    Hello,
    This is most likely not a Business Central setup problem, because the same shared mailbox works for user1; with the Microsoft 365 Connector, Exchange still validates the actual BC user who sends the email, so user2/user3 must also have a valid paid Exchange Online mailbox/license and proper delegation on the shared mailbox, especially Send As permission, not only Full Access. The 403 usually points to Exchange/Graph refusing the send action because of missing permission, invalid mailbox/license, quota/policy, or access restriction; the 404 usually means the sender mailbox Exchange is trying to use is not a valid Exchange Online mailbox, inactive/soft-deleted, or hosted on-prem/hybrid. I would compare user1 vs user2/user3 in Microsoft 365/Exchange admin center: Exchange license, mailbox status, guest/delegated admin status, Send As delegation on the shared mailbox, and any Conditional Access or Exchange policy changes around 2026-05-04. If many accounts stopped on the same date, also check Microsoft 365 Service Health and tenant-side Exchange/Graph/authentication changes, because Microsoft Learn does not indicate a Business Central-specific setup change for that exact date.
     
    Regards,
    Oussama Sabbouh
  • PL-28101044-0 Profile Picture
    215 on at

    Thank you for your detailed reply and for taking the time to explain the possible Exchange and Microsoft 365 angles.

    That said, it does not fully make sense to us that this is purely a user- or permission-related issue. No changes have been made on the tenant, Exchange, or user configuration side, and yet starting on 2026-05-04 the problem suddenly began to occur, affecting only certain users. Until that date, the same users were able to send emails from Business Central without any issues.

    In addition, we are seeing similar problems at other customers with completely different setups and email configurations, where email sending from Business Central also started failing around the same date. This makes it harder to attribute the issue to a specific Exchange or permission misconfiguration in a single tenant.

    What is also striking is that these failures coincide in time with errors reported in standard Business Central behavior and with the postponement of the SaaS updates to version 28. Because of this timing, we are wondering whether there may have been any change or adjustment on Microsoft’s side related to Business Central, the Microsoft 365 connector, or the underlying authentication/Graph flow that could explain this behavior.

    Have you heard of any changes, incidents, or known issues introduced around that time that could be related to this?

    Thanks again for your input and insights.

    Best regards,
  • Verified answer
    Gerardo Rentería García Profile Picture
    27,087 Most Valuable Professional on at
    Hi, good day
    I hope this can help you, and give you some hints.

    Analyzing Email Telemetry (administration content)

    Best Regards
    Gerardo

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,222 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,603 Super User 2026 Season 1

#3
Grigorios Mavrogeorgis Profile Picture

Grigorios Mavrogeorgis 1,186 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans