Versions Compared

Old Version 3

changes.mady.by.user Roar Hansen (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Mateusz Bednarz (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Release Notes

Microsoft Yammer Connector Release Notes

Released Versions

  • SDK 1.3 4 (viaworks 2.8)
  • SDK 1.5 (Locator 2.79)
  • SDK 1.4 6 (viaworks Locator 2.810)

Limitations

Messages in the Yammer framework do not have a modified date set. Furthermore, Deleted messages do not have the 'deleted' flag set, as they are simply removed.

...

All Other Resources: 10 requests in 10 seconds.

Prerequisites

  • A license for the Yammer Connector.
  • A User account in the Yammer network is required. A service user access token is needed for indexing.

Authentication

Users are authenticated via Active Directory with the use of their User Prinicipal Names (UPN). The UPNs are matched against the User's email address, which is defined in the User object.

Authorization

Items are marked with a list of Yammer-related Group and / or User SIDs during fetching time.
At search time, User SIDs are matched against the SIDs marked on the items, and only items available to the User are returned as search hits.

Crawl Methods

Full Crawl: The Yammer Connector supports scheduling periodic full scans of the source system.

Incremental Crawl: The Yammer Connector supports ChangeSet functionality for Messages. All messages newer than the latest saved message, are retained. 

DocumentHandler

The ViaWorks Locator Document Handler is NOT required on the clients in order to be able to open search hits.

Custom Templates

No custom templates are required for this connector.

Hover: Default

Item: Default

Other information

Multiple connections can be configured, with similar or different content targets and Security options.

Conditional Access:

Make sure that you don't have any conditional access rules which disable access to Office365 applications. Check if there is no restrictions for index user's location, device etc...
Also in 'Grand' tab under Access Control "MFA" shouldn't be checked, because connector doesn't support it.

For more info see: https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-policy-block-access