Viva Amplify Publishing Error in Outlook

Copper Contributor

Hello,

I am getting the following error message when trying to publish via Viva Amplify for Outlook.

'We have encountered an unexpected issue while publishing to one or more distribution channels.  Select Retry to publish again'

The emails are all internal to our company and I have tried to individual and shared email addresses and get the same error, even when click Retry several times.  Is anyone else having the same issue or know how to fix this error?

3 Replies
A few troubleshooting questions for you:

1. Are you changing the sender address to someone else's name or a shared mailbox? If you don't have access to send from a mailbox, Amplify would likely throw this error for Outlook distribution.

2. If you're not changing the sender address, do you get any errors when sending to a Teams channel or SharePoint site?

3. Has anyone else experienced this error while trying to distribute from Amplify to Outlook?

4. Was it working before and were any system changes made between then and now that might have caused this?

Hi @RobSoto,

The problem I am experiencing is with the recipients address, I am not changing the sender address, it is just coming from me.

It is publishing fine to SharePoint and Teams it is just Outlook and I get the same issue if I am only sending to Outlook as well.

I have check and we haven't made any system or security changes, and it was working fine on 24 September just not since. 

I am in the process of logging a job with the Microsoft Service Portal as well to see if they can look at this for me.

 

Thanks again

Thanks for the response!

One more question - Have you tried sending a publication from you to yourself? Same result?

I tested Amplify distribution to Outlook in two tenants today and didn't see any errors.
 
Glad you're opening a case with Microsoft. Please let us know if you reach a resolution.

There was a change in August for Viva Amplify that could have rolled out to your tenant in September. The change was an improvement to the page load speeds when drafting a publication within Amplify. It's a long shot in terms of root cause, but it was the most recent change to the application before your issue began.

https://www.microsoft.com/en-us/microsoft-365/roadmap?featureid=398980