Home

"Failed to send" and "We can't access your content"

%3CLINGO-SUB%20id%3D%22lingo-sub-276549%22%20slang%3D%22en-US%22%3E%22Failed%20to%20send%22%20and%20%22We%20can't%20access%20your%20content%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276549%22%20slang%3D%22en-US%22%3E%3CP%3ETeams%20has%20been%20down%20for%20dozens%20of%20our%20users%20today%20and%20I%20cannot%20find%20anything%20pointing%20to%20why.%26nbsp%3B%20Been%20on%20the%20platform%20for%20months%20and%20today%20complaints%20started%20that%20people%20were%20getting%20%22failed%20to%20send%22%20on%20every%20message%20%26amp%3B%20trying%20via%20web%20just%20posted%20%22we%20can't%20access%20your%20content%22.%26nbsp%3B%20I%20have%20not%20found%20any%20solution%20to%20this%20and%20there%20is%20no%20logging%20to%20help%20diagnose%20anything.%26nbsp%3B%20Singing%20out%20and%20back%20in%2C%20restarting%20apps%2Fcomputers%2C%20nothing%20brings%20them%20back%20to%20sending%20messages.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-276549%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EChat%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EConversations%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276690%22%20slang%3D%22en-US%22%3ERe%3A%20%22Failed%20to%20send%22%20and%20%22We%20can't%20access%20your%20content%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276690%22%20slang%3D%22en-US%22%3ELooks%20like%20there%20was%20an%20issue%20with%20an%20update%20earlier%20that%20caused%20sign%20in%20issues.%20And%20it%20probabaly%20was%20causing%20the%20other%20issues%20as%20well.%20Says%20it%E2%80%99s%20been%20fixed%20thou%20so%20not%20sure%20if%20you%20are%20still%20having%20the%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276686%22%20slang%3D%22en-US%22%3ERe%3A%20%22Failed%20to%20send%22%20and%20%22We%20can't%20access%20your%20content%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276686%22%20slang%3D%22en-US%22%3EYeah%20modern%20auth%20shouldn%E2%80%99t%20affect%20the%20issue.%20Most%20likely%20service%20issues%20or%20your%20tenant%20node.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276572%22%20slang%3D%22en-US%22%3ERe%3A%20%22Failed%20to%20send%22%20and%20%22We%20can't%20access%20your%20content%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276572%22%20slang%3D%22en-US%22%3EEnabled%20modern%20auth%20on%20SFB%20a%20week%20ago%20has%20been%20the%20only%20recent%20change.%20Opened%20ticket%20waiting%20on%20a%20response%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276567%22%20slang%3D%22en-US%22%3ERe%3A%20%22Failed%20to%20send%22%20and%20%22We%20can't%20access%20your%20content%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276567%22%20slang%3D%22en-US%22%3ENothing%20changed%20infrastructure%20wise%3F%3CBR%20%2F%3ECan%E2%80%99t%20see%20there%20have%20been%20any%20disturbances%20in%20the%20service%20but%20check%20your%20portal%20and%20your%20service%20status!%3CBR%20%2F%3EAlso%20create%20a%20ticket%20with%20Microsoft%20from%20the%20admin%20portal!%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E
Richard Nelson
Occasional Contributor

Teams has been down for dozens of our users today and I cannot find anything pointing to why.  Been on the platform for months and today complaints started that people were getting "failed to send" on every message & trying via web just posted "we can't access your content".  I have not found any solution to this and there is no logging to help diagnose anything.  Singing out and back in, restarting apps/computers, nothing brings them back to sending messages.

4 Replies
Nothing changed infrastructure wise?
Can’t see there have been any disturbances in the service but check your portal and your service status!
Also create a ticket with Microsoft from the admin portal!

Adam
Enabled modern auth on SFB a week ago has been the only recent change. Opened ticket waiting on a response
Yeah modern auth shouldn’t affect the issue. Most likely service issues or your tenant node.
Looks like there was an issue with an update earlier that caused sign in issues. And it probabaly was causing the other issues as well. Says it’s been fixed thou so not sure if you are still having the issue.
Related Conversations