New files uploaded to Microsoft 365 connected Yammer communities are now stored in SharePoint

Published 02-12-2020 08:00 AM 18.2K Views

It’s taken us some time—but we’re excited to share that all new photos and files uploaded through Yammer in Microsoft 365 connected communities are now stored in the communities’ default SharePoint document library.  


This ensures that your files adhere to the rich security and compliance features policies that you’ve implemented for SharePoint and extends that to encompass more files in Office 365. This means that eDiscovery, data loss protection, in-geo residence for files at rest, and other custom policies are available for new files uploaded in Microsoft 365 connected communities. 


The Files tab allows you to navigate and manage your Yammer files stored in SharePointThe Files tab allows you to navigate and manage your Yammer files stored in SharePoint


Benefits for end users 

Going forward, users can use the familiar SharePoint document library for file navigation and management for their Yammer communities. This announcement also means that files can now be easily discovered and accessed via Yammer, SharePoint, Delve, Microsoft Search, your Recent Files in Office ProPlus apps, and beyond. Users can even keep a saved copy of your community’s files when you’re offline by syncing the folder in the document library


Using SharePoint for file storage gives admins and users more access and controlUsing SharePoint for file storage gives admins and users more access and control

Some changes to Yammer Files APIs 

With the change to new Yammer files to be uploaded to Microsoft 365 for connected communities complete, we’re also going to be harmonizing the Yammer files APIs. We will be deprecating the /pending_attchments API, which always uploads files to Yammer storage,  in favor of the new /smallFileUpload API. The new API will prefer to upload files to the SharePoint document library if the community is a Office 365 connected, while continue to upload to Yammer storage otherwise. 


Wrapping up 

This is just one part of how we’re bringing Yammer closer together with the rest of Office 365. We recently launched Native Mode for new Yammer tenantsmeaning all groups will be connected and have their files uploaded to SharePoint- and for existing tenantsthe ability to migrate to Native Mode. As a part of that migration, we will move your existing files stored in Yammer to SharePoint. 


Stay tuned—we will have more to share on files inside the new Yammer! 


Learn more about how files in Yammer:  
Getting started with Yammer File Storage 

Attached a file or image to a Yammer Message 

Edit documents directly from Yammer  

How do I tell where my Yammer files being stored?  


Ethan Li 
Ethan is a PM on the Yammer Team 


Hi @Ethan Li ... 


We have been using Yammer for quite a while. What happens to the files we uploaded before this functionality was introduced?




Hi @Mike Dumka,


At this point, previously uploaded files remain unchanged. However, if you migrate your network to Native Mode, then files will also be moved as a part of the migration to Native Mode. 


Is migration to native mode available yet?  I am not seeing any references within the documentation that indicates where this tool is located.

Frequent Visitor

Why is there no option to link a Yammer group with an existing Sharepoint site or Team? It gets confusing enough when Teams' default file storage location is in a General folder in the root of the Sharepoint site (so unless you explicitly add a link to the root, Teams users have no idea that a larger folder structure may exist). Now with the new Identity Enforcement mode, creating a similarly named Yammer group creates a whole new site to store files?

I find it hard to believe that was not considered to be an issue...

Occasional Contributor

@Jeff4543 Been asking for that feature on UserVoice for years... I can only surmise that it's technically very difficult / impossible somewhere in the provisioning pipeline... because it's been consistently ignored. It's the one issue that's keeping us paying for FB Workplace when we already pay for Yammer through MS365!


This week I took my 'dormant' Yammer network into Native Mode. It only has one Yammer community (and only one user for that matter: me!) and going native dutifully created a SP site called All Company. One saving grace: at least it didn't activate that SP site for Teams too.


As we've been using Teams for years, we already have an 'All Company' team site that's Org-Wide.

  • Can I wire that SP site up to the 'All Company' Yammer community? Nope.
  • Can I create a new Yammer community out of any of the existing team sites I've already got? Nope.
  • Will I be activating Yammer for the rest of my tenant? Nope.


The new Yammer has really stepped up to the plate. It's just a shame that it forgot its shoes.

Occasional Contributor

@Rob Hardman  I'm in the exact same position. Our business moved to Facebook Workplace last year, previously were using Yammer. We also have teams with a Business wide team. So what benefit does Yammer or Facebook Workplace have over teams? Nothing. All it does is create a information fragmentation and cause confusion for users. The whole inner loop and outer loop talk means nothing if they cannot explicitly state when to use one software over another. Adding the ability to upload files into Yammer communities and not being able to link to a shared SharePoint site with the teams group just causes more confusion now.


Teams is rapidly becoming the go to area for everything within business so why shouldn't it encompass all features of Yammer and Workplace?


For Teams to completely encompass all of Facebook Workplace / Yammer and make them obsolete all they need to do is:

  • Have a embedded media player, to play Youtube, Microsoft Stream, etc. videos without having to open a different application (as Yammer has)
  • A Personalized feed same as what Yammer or Facebook Workplace has (surely can't be that difficult seeming Microsoft have it within Yammer)


Then all information is in one place, all tasks will be in one place (new teams tasks app, when it finally gets released), all internal calls/meetings and comms in one place (bar email for external users), workflows in one place through power automate linked to teams, SharePoint site linked to a org wide group and team for its intranet, all associated files stored in one place linked to the team.


Yammer and Teams are apart of the same subscriptions so why does Microsoft waste development costs on Yammer when they aren't getting any more subscriptions from it. Put all of the development into Teams and incorporate the only two features Yammer or workplace has that differentiate them, then it becomes the powerhouse for everything a business does and needs.




Hi @Todd_Edwards ...


I have to admit, in the past I have struggled with the differences between Teams and Yammer/Workplace by Facebook. 


But as I have worked with more and more people, it comes down to what is the tool best for? From my perspective Teams is for getting work done, should be collaboration that requires a timely response. 


Yammer (or a community like this) you can participate then leave ... it doesn't have to be timely, you come and go as you please. Nothing 'critical' should happen here, this is for knowledge sharing.


These are the 2 big differences I see between Teams and Yammer. Getting work done vs knowledge sharing. 


Now don't get me wrong, having something like a SharePoint back end where people can work on files does send a bit of the wrong message, but I would bet it has something to do with making things easier on the engineers. 



Occasional Contributor

Hi @Mike Dumka 


Thanks for your reply but again it still doesn't get down to the root of what I was saying.


If teams has pretty much the exact same functionality (i.e. only differences being the two mentioned above, which can be rectified through the UserVoices linked below, please vote), why not create the exact same communities that are in Yammer in Teams. Have a org wide team, have all the smaller communities people would join, just in teams. Then they can come and go as they please from those teams. For getting work done they still then have all of their normal project teams or department teams etc. there as well. Why have two platforms which again confuses people. Its almost as if there is no point in public groups within teams as all those end up being are communities in Yammer and generally work the same way.


Can some one please provide some direct functional differences between the platforms that cause Yammer / Workplace better for general community communication (other than the two previously mentioned). Because from what I have seen and from all my experience with the platforms there are pretty much none. So why not just create the functionality of Yammer / Workplace (i.e. knowledge sharing communities) within teams.



Senior Member

When will the smallFileUpload API be available?

Occasional Visitor

Is there any reason why when I add a file to the Yammer folder in SharePoint it does not show up in the files section on the Yammer Community?  It works when I create a new file in Yammer, it becomes visible in the SharePoint Document library.  Seems really odd that it is not showing up when files are folders are created on the Sharepoint site.  

Version history
Last update:
‎May 26 2020 03:42 PM
Updated by: