Using classic Outlook for Windows in business environments
Test sending from the shared mailbox in Outlook on the web first: failure there points to mailbox delegation or provisioning, while success there limits the problem to Classic Outlook’s local configuration.
1. Test outside Classic Outlook
- Open Outlook on the web with your normal work account.
- Open the shared mailbox and send a new test message using its address in From.
- Check the result:
- Sending fails in both web and Classic Outlook: continue with the permission check below.
- Sending works on the web: skip to Classic Outlook-only fixes.
The error does not prove by itself that permission was removed; Microsoft has also documented the same error for certain corrupted Outlook profiles.^1^
2. Have an administrator verify Send As
Being able to read and organize the mailbox confirms Full Access, but Full Access does not permit sending. To send with only the shared mailbox address displayed, your account also needs Send As.^2^
An Exchange administrator should:
- Open the Exchange admin center.
- Go to Recipients → Mailboxes.
- Select the shared mailbox.
- Open Mailbox permissions → Manage mailbox delegation.
- Under Send As, verify that your user account is listed.
- If it is missing, select Add, choose your account, and save.
- Allow the change to propagate, restart Outlook, and send another test message.
These are the documented delegation controls for Full Access and Send As.^3^
Also verify that the shared mailbox is not hidden from address lists. In Outlook desktop, Send As and Send on Behalf do not work when HiddenFromAddressListsEnabled is True, because Outlook needs to resolve the mailbox through the Global Address List.^3^
3. If Send As is already assigned but web sending still fails
Do not immediately repair the Outlook profile, because the web failure indicates the problem is not limited to Classic Outlook.
As a provisioning fallback, the administrator can remove your Send As delegation, wait at least 15 minutes, add it again, wait for propagation, and retest. In one closely matching case, the permissions appeared correctly assigned in the admin interfaces but sending resumed only after delegation was reprovisioned; that case required a second remove/add cycle and another wait.^4^
If reprovisioning does not work, the Microsoft 365 administrator should:
- Check Microsoft 365 admin center → Health → Service health for an Exchange Online incident.
- Open a Microsoft support request so tenant audit and Exchange transport logs can be examined. Those backend logs are needed to identify why apparently assigned permissions are not being honored.^4^
4. Classic Outlook-only fixes
If web sending works, first recreate the cached sender selection:
- Start a new message in Classic Outlook.
- Select From → Other Email Address → From.
- Select the shared mailbox from the organization’s Global Address List rather than typing the address.
- Send a test message.
If it still fails, create a fresh Outlook profile:
- Close Outlook.
- Open Windows Control Panel → Mail → Show Profiles.
- Select Add, configure your work account, and allow the shared mailbox to appear.
- Start Outlook with the new profile and test again.
Microsoft documented profile recreation as the repair for profiles left corrupted by a specific Outlook Version 2202 incident that produced this same NDR. That incident was fixed in 2022, so on other versions this is a desktop-only troubleshooting step—not confirmation that your profile has the same historical corruption.^1^
References