About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A user who has Send As permission to a distribution group clicks Send in Outlook and gets: "This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000]". Microsoft's page for this exact text says the issue "may occur if the address book in Outlook isn't updated." Update the address book, and if that does not work, clear the Offline Address Books folder.
Two other faults are also worth ruling out, because they stop a user sending as a mailbox too: the permission is missing, or it was granted so recently that it has not replicated. They are not the cause Microsoft gives for 0x80070005, and the replication one produces a different message, described below.
What the error means
Microsoft's page describes the case as follows: a user "who has Send As permission to a distribution group tries to send an email message to other users by using Microsoft Outlook in Microsoft 365", and receives the non-delivery report containing the text above. The page applies to Exchange Online, and the steps use classic Outlook with the Send/Receive tab.
Microsoft says the issue "may occur if the address book in Outlook isn't updated." The permission itself may be fine. Send As is the permission that lets a user "send messages that appear to come from the specified mailbox, mail contact, mail user, or group", according to the Add-RecipientPermission page. Microsoft's example is a user with SendAs on a Help Desk mailbox.
A separate message appears in the shared mailbox overview: "This message could not be sent. You do not have the permission to send the message on behalf of the specified user." Microsoft says this appears when Microsoft 365 "is experiencing a replication latency problem", goes away "in about an hour", and the advice is to "Wait an hour and then try again to send a message." That page speaks of a new shared mailbox or an added user.
It helps to know which permission your users actually need. Microsoft's Create a shared mailbox page separates three. Full Access lets a user open the mailbox and act as its owner, but "a user with Full Access permission can't send email from the shared mailbox unless they also have Send As or Send on Behalf permission." Send As makes the message look as if the mailbox itself sent it. Send on Behalf shows the real sender, for example "John on behalf of Reception Building 32". An error about sending is therefore a question about the second or third permission, not the first.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Outlook address book out of date | 0x80070005 error when the From address is a group or mailbox. Expected symptom, not stated on Microsoft's page: it is more likely right after the address changes |
Download the address book and retry; Microsoft's first step |
| Offline Address Books folder damaged | Download does not help | Clear the folder and restart Outlook; Microsoft's second step |
| Permission added within the last hour | "You do not have the permission to send the message on behalf of the specified user." | Expected check, not stated on Microsoft's page: the permission appears in PowerShell but sending fails; Microsoft's advice is to retry after an hour |
A place to look (not on Microsoft's 0x80070005 page): Send As not granted at all |
A refusal for one user only | Get-RecipientPermission does not list that user |
| Mailbox hidden from address lists | Send As fails in the Outlook desktop client | HiddenFromAddressListsEnabled is True |
Prove the cause before changing anything
- Read the exact error text. Match it to
0x80070005(address book) or to "You do not have the permission to send the message on behalf of the specified user" (replication). - List who holds Send As on the group or mailbox. Microsoft's example form is:
Get-RecipientPermission sales@contoso.com.au
The output lists the users who have SendAs permission on that mailbox. If the affected user is not in the list, the cause is the missing permission, not the address book.
- If the From address is a mailbox, check whether it is hidden. (This check does not apply to a distribution group; skip it for a group.) Microsoft says Send As and Send on Behalf "do not work in the Outlook desktop client with the HiddenFromAddressListsEnabled parameter on the mailbox set to True, since they require the mailbox to be visible in Outlook via the Global Address List":
Get-Mailbox -Identity sales@contoso.com.au | Format-List HiddenFromAddressListsEnabled
The cmdlet is on Microsoft's Get-Mailbox page; the property name and its values are on the Set-Mailbox and Create a shared mailbox pages. Record the value shown. The hidden-mailbox fix below applies to a mailbox only.
- Ask when the permission was granted. If it was within the hour, wait before changing anything.
Fix
Update the address book. Microsoft's steps: on the Send/Receive tab, select the down arrow next to Send/Receive Groups, then Download Address Book. In the Offline Address Book dialog box, make sure "Download changes since last Send/Receive" is selected and Offline Global Address List is the address book, then select OK.
Test by sending a message as the group, filling the From field from the global address list. Microsoft's page says to "use the global address list (GAL) to populate the From field" for the test.
Clear the Offline Address Books folder. This is Microsoft's second step if the first does not help.
Save first: exit Outlook, then copy the folder to a safe place, so you can put it back. The page gives the Windows 8 and Windows 7 path \Users\<UserName>\AppData\Local\Microsoft\Outlook\Offline Address Books, with your own user name in place of the placeholder. The folder may be hidden. Microsoft's way to show it is Folder Options, then the View tab, then Show hidden files, folders, and drives.
Disruptive step: delete the contents of the Offline Address Books folder, not the folder itself. Impact: Outlook has no local address book until it rebuilds it. Microsoft says "The contents of the folder are re-created when you restart Outlook." Back-out: close Outlook and copy the saved contents back, or simply restart Outlook and let it rebuild them.
Then start Outlook, wait for the address book download, and test again.
Grant Send As (only if step 2 showed it missing).
Save first: keep the output of Get-RecipientPermission for that mailbox.
Risk: the command below lets the named user send messages that appear to come directly from the mailbox or group. Impact: recipients cannot tell who actually sent the message from the From line. Back-out, per Microsoft's Remove-RecipientPermission page, is the second command.
Microsoft's form for the grant is:
Add-RecipientPermission "Sales" -AccessRights SendAs -Trustee "Ayla Kol"
The page's own example uses "Help Desk"; here the names match the example below. The back-out:
Remove-RecipientPermission "Sales" -AccessRights SendAs -Trustee "Ayla Kol"
Wait about an hour before retesting a new grant, using the replication note above.
Hidden mailbox. If HiddenFromAddressListsEnabled is True, Microsoft's Set-Mailbox page describes $false as "The recipient is visible in address lists", which is the default.
Save first: record the value shown by the step 3 command (here True) in a text file, with the mailbox name, and get the mailbox owner's agreement to make it visible.
Disruptive step: the command below makes the mailbox visible in address lists to every user, so people can start addressing mail to it.
Make the mailbox visible in address lists:
Set-Mailbox -Identity sales@contoso.com.au -HiddenFromAddressListsEnabled $false
To undo it, run the same command with the recorded value, -HiddenFromAddressListsEnabled $true.
Confirm the fix
Send a test message as the group or mailbox, with the From field filled from the global address list, to an outside address and to an inside address. Confirm the message is delivered with the expected sender. Test from a second user who has the same permission, so you know the fix was not specific to one profile.
Example (illustrative): Ayla is given Send As on sales@contoso.com.au at 09:10 on Tuesday. She tries at 09:20 and gets "You do not have the permission to send the message on behalf of the specified user." Applying Microsoft's hour-long wait, she retries after 10:10 (09:10 plus 60 minutes) and the message goes. A colleague who was granted permission last month still sees 0x80070005 on her own laptop; she downloads the address book, which fixes it.
What to watch afterwards
- After each new group or shared mailbox, allow an hour before declaring the permission faulty.
- Keep a list of who holds Send As on each shared address and update it when staff leave.
- If many users see
0x80070005after a mail-system change, check the address book download on one laptop first. - Avoid hiding a mailbox that people send as from Outlook.
- If the error returns for one user only after a successful address book download, repeat Microsoft's two address book steps on that PC. Microsoft's page does not say why it would return.
Read next
Related articles you may want next.
- TroubleshootingShared mailbox sent mail lands only in my own Sent Items: saving a copy in the shared mailboxShared mailbox replies saved only in your own Sent Items? Microsoft's page names MessageCopyForSentAsEnabled and ...OnBehalfEnabled as the fix.Read article
- TroubleshootingOutlook can't set up a profile after a move to Microsoft 365: 'An encrypted connection to your mail services is not available'Outlook says an encrypted connection to your mail services is not available after a Microsoft 365 move? Check the Autodiscover CNAME and user attributes.Read article
- Troubleshooting550 5.1.10 RESOLVER.ADR.RecipientNotFound: a Microsoft 365 user can't email a hybrid user whose address existsMicrosoft 365 user gets 550 5.1.10 RESOLVER.ADR.RecipientNotFound sending to a hybrid user? Check the on-premises object and ExchangeGuid, then fix.Read article
Risks and limits
These commands have not been run or lab-tested. Microsoft's page for 0x80070005 is written for a distribution group and for older Windows folder paths; the steps still apply to the Outlook folder, but the path may differ on newer Windows. Microsoft's page does not say how long the address book takes to download, and it does not cover Outlook on the web.
Remove Send As promptly when someone leaves the team, because anyone holding it can send mail that appears to come directly from the mailbox.
Sources
- This message could not be sent NDR when an approved user sends mail in Microsoft 365 — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
- About shared mailboxes in Microsoft 365 — Microsoft Learn, page dated 2026-03-13, accessed 20 November 2026
- Create a shared mailbox — Microsoft Learn, page dated 2026-02-03, accessed 20 November 2026
- Add-RecipientPermission — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-RecipientPermission — Microsoft Learn, date not shown, accessed 20 November 2026
- Remove-RecipientPermission — Microsoft Learn, date not shown, accessed 20 November 2026
- Set-Mailbox — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-Mailbox — Microsoft Learn, date not shown, accessed 20 November 2026
This article was originally published on .