Yammer file storage overview

As of May 2019, Yammer is rolling out changes to file storage for files uploaded to Yammer in Office 365 connected Yammer groups. Formerly, all files uploaded to Yammer were stored in Yammer cloud storage. Once your organization gets these changes, all new files uploaded through Yammer in Office 365 connected Yammer groups will be stored in the group's default SharePoint document library. These files can still accessed from within Yammer.

For information about using Yammer files stored in SharePoint, see the following topics:

Benefits

For network and tenant administrators:

  • SharePoint has a rich set of security and compliance features that will now apply to files uploaded in Yammer for Office 365 connected Yammer groups, including eDiscovery, data loss protection, and in-geo residence for files at rest. 

For end users:  

  • A familiar user interface for file navigation and management in SharePoint.   

  • Greater discoverability and easier access via Microsoft search. 

    Users with appropriate permissions can find and access the files through Yammer, and can also access the files through SharePoint and other Office 365 resources by using browse or search in SharePoint and Delve.     

  • Offline access to files by syncing a SharePoint folders to a folder on their computer. 

What determines where a file is stored   

Files are stored in SharePoint when they are uploaded to an Office 365 connected Yammer group. This includes:   

  • Files that are attached to a message in an Office 365 connected Yammer group. 

  • Files that are uploaded to a group from the Files page of an Office 365 connected Yammer group. 

  • Files that are attached to an email that is sent to an Office 365 connected Yammer group.  

Files will continue to be stored in Yammer cloud storage in the following instances:   

  • If the Yammer network does not use Office 365 connected groups. This includes:

    • Office 365 tenants that have more than one Yammer network 

    • Yammer networks that don't enforce Office 365 identity 

    • Yammer Basic networks   

  • When the location the file is being uploaded to is not an Office 365 connected Yammer group:

    • Groups that are not Office 365 connected groups, including All Company, external groups, and secret groups.  

    • Yammer private messages. 

    • Existing files stored in Yammer legacy storage will not be moved to SharePoint.  

  • If your organization is using a third-party app that uses Yammer Files APIs:

    • If we detect that you are currently using the Yammer Files APIs, even if you're using connected groups, files for your tenant will be stored in legacy storage until your app is updated to be an Azure Marketplace app that calls Yammer APIs. We’ll share details on how to create an Azure Marketplace Yammer app soon. If you're a developer and have questions about this change, please email api@yammer-inc.com.

      [NOTE] If you create a third-party app that uses Files APIs after your organization has received the Yammer files in SharePoint feature, file calls will fail. Users will see an HTTP 401 error (unauthorized client error) because the Yammer OAuth token does not include claims from Azure Active Directory, which is required for accessing files stored in SharePoint.

Note

Moving a conversation to an Office 365 connected Yammer group will not change where the file is stored.  

Where files are stored in SharePoint

  Files that users upload in Office 365 connected groups are saved in the Apps > Yammer subfolder of the SharePoint document library for the Office 365 connected group. The SharePoint document library can be accessed from Yammer under Office 365 Resources on the right side of an Office 365 connected Yammer group, as well as through SharePoint itself.    

Guest and external user access to files

  The following table shows how each type of guest and external user can access files uploaded in Yammer and stored in SharePoint.

Type of user Access to group files
Conversation-level guest that is in your network Private group: can view files that have been shared in the conversation, but can't upload files.
Public group: Can view, edit, and upload files.
Network-level guest that is also an Azure B2B guest, and also a member of the group in Office 365 Can view, edit and upload files.
Azure B2B guest, but not a member of a the group
Network-level guest
Conversation-level guest that is not in your network
No file access by default. These users can request access to specific files.
Can't upload files.
Network-level guest, but not Azure B2B guest No file access. These users must become an Azure B2B guest and a member of the group in Office 365. Alternatively, other group members can grant access to specific files or the entire document library via one of many SharePoint external sharing methods.

Note

Membership in the group for guests in Azure Active Directory (AAD) and Yammer are completely separate. Deleting a network-level guest from an Office 365 connected Yammer group or from the tenant in AAD does not remove the user in Yammer, and deleting a user from Yammer does not delete the user from an Office 365 group or AAD.

For more information about Azure B2B guests, see Guest user access in an Azure Active Directory B2B.

Requirements

  • Yammer version requirements

    Ensure your users are using the most recent Yammer versions. At a minimum, users should be using the following or newer versions:

    • Yammer on iOS - 7.33.0

    • Yammer on Android - 5.5.84

    • Yammer desktop on Windows or Mac - 3.4.2

  • Cookie and browser requirements

    To store Yammer files in SharePoint, we use the ADAL library and use Azure Directory (AAD) tokens for authentication. If browsers don’t have third party cookies enabled or if the security zone settings are incorrect in Internet Explorer 11 or Edge, the ADAL library used to refresh AAD tokens can't send information needed to AAD.

    When a token refresh call fails, users will see:

    • On the Yammer page for a connected group, Office 365 Resources will be grayed out

    • File operations will fail

    • Yammer live events can't be created

    For more information see A silent sign-in request was sent but no user is signed in.

    To avoid problems:

    • Ensure there aren’t any extensions that block or prevent reading of cookies, such as Ghostery.

    • In Internet Explorer 11 or Edge, ensure protected mode is disabled for the trusted zone.

      Yammer.com and related URLs should be a part of trusted zone. For more information, see Office 365 URLs and IP address ranges

    • In complex environments, especially those using wildcard configurations such as *.fabrikam.com, additional effort may be required to find the right configuration. URLs may need to be moved between zones, or replaced with the absolute versions in some cases.

    • Users shouldn’t access Yammer by using incognito or InPrivate mode or equivalent modes in other browsers.