In line with our Yammer and Office 365 roadmap, we’re releasing a new feature that more deeply integrates Yammer and Office 365: user mapping. When you opt into Yammer as your default social experience in Office 365, Office 365 users are mapped to their existing Yammer accounts. This means that when you click Yammer from your Office 365 global navigation bar, you do not need to authenticate again. Office 365 users without existing Yammer accounts are taken to a streamlined sign-up and verification process.
Enable user mapping to save your Office 365 users time signing in to Yammer
Administrators can enable user mapping between Office 365 and Yammer in the Office 365 tenant in just a few steps. Sign in to Office 365 using an Office 365 global administrator account. Select Admin, and then select SharePoint. Once you’re in the SharePoint admin center, select Settings. On the Settings page, under Enterprise Social Collaboration, select Use Yammer.com service. Now you’re all set. When you click Yammer from Office 365, you won’t have to log in again. You can start connecting with people using Yammer right away.
You can apply Yammer as your organization’s social network in the SharePoint admin center, on the Settings page, to simplify Yammer login for your Office 365 users.
If you previously made Yammer the primary social experience for your organization, we will automatically backfill your Office 365 tenant with this new behavior and notify you about the update by April 2014. But you can manually enable the behavior today by reapplying Yammer as your primary social experience:
In the SharePoint admin center, select Settings. On the Settings page, under Enterprise Social Collaboration, click the Use SharePoint Newsfeed button to clear it, and then select Use Yammer.com service and click OK to apply the changes. Each of these two updates might take up to 30 minutes to complete. Once the updates have completed, Yammer replaces Newsfeed in the Office 365 navigation. You can still access the SharePoint Newsfeed through Sites.
For additional information, please see the article Make Yammer your default social network in Office 365.
User mapping saves time but it is not a complete single sign-on solution
User mapping does not provide a complete Yammer single sign-on (SSO) solution. With user mapping, you do not need to log in again when you click Yammer in Office 365. However, when you browse to Yammer.com directly or use the Yammer mobile apps, you still need to log in with your Yammer.com credentials.
Compare this to Yammer single sign-on, where you log in using single credentials (typically your company credentials), whether you go through the Office 365 global navigation, use the Yammer mobile apps, or browse directly to Yammer.com. To secure all the entry points to Yammer, we still recommend Yammer directory sync and Yammer single sign-on.
Moving forward
User mapping is just the latest step in integrating Yammer with Office 365, as we continue to move toward a unified identity across Office 365 and Yammer. We’re looking forward to seeing you atSharePoint Conference in March to share more!
– Christophe Fiessinger @cfiessinger
FAQ
Q: Do I need to turn on user mapping explicitly?
A: Yes, you need to turn on Yammer as the default social experience in the SharePoint tenant admin center.
For additional information, see Make Yammer your default social network in Office 365.
Q: I turned on Yammer as my social experience before this post. Why don’t I see the behavior?
A: If you previously made Yammer the primary social experience for your organization, we will automatically backfill your Office 365 tenant with this new behavior and notify you about the update by April 2014. But you can manually enable the behavior today by reapplying Yammer as your primary social experience. Please follow the steps listed above.
Q. We already implemented Yammer Active Directory sync and single sign-on. Does this new feature have an impact?
A: No, this new user mapping feature between Office 365 and Yammer does not impact your existing Yammer Active Directory Sync and single sign-on (SSO) implementations.
Q: If I enable user mapping, do I need to use Yammer’s Active Directory sync, too?
A: Yammer’s Active Directory sync is not required for user mapping. However, it does provide streamlined user management (adding and removing network members), which you can use in addition to user mapping to enhance your user management.
To get started with Yammer’s Active Directory tool and to authenticate users from your on-premises Active Directory, check out Synchronize and authenticate users from your on-premises Active Directory to Yammer and Office 365.
Q: How is user mapping different from Yammer single sign-on (SSO)?
A: User mapping does not provide a complete Yammer single sign-on solution. Users that can be mapped do not need to log in again when they click Yammer in the Office 365 global navigation. However, when they browse to Yammer.com directly or go to the Yammer mobile apps, then they will still need to log in with their Yammer.com credentials.
Implementing Yammer single sign-on allows you to log in using single credentials (typically your company credentials), whether you go through the Office 365 global navigation, use the Yammer mobile apps, or browse directly to Yammer.com.
Q: How can I implement Yammer single sign-on (SSO)?
A: For full Yammer single sign-on integration information, refer to the single sign-on implementation guide: http://success.yammer.com/integrations/single-sign-on
Q. How can I manage user access to my company’s Yammer network?
A. Only users with a valid and verified company email address can join your Yammer network. In a free Yammer network, users can invite their colleagues with the same email address suffix to collaborate. Users can also suspend other users from having access to the Yammer network. In Yammer Enterprise, administrators have the ability to provision and remove users in bulk (using a .csv file), and also to synchronize with Active Directory to automatically add users not already on Yammer and remove users from Yammer if their Active Directory account is disabled or deleted.
For more information on Bulk Update, see http://success.yammer.com/integrations/admin-guide. For more information on Active Directory Sync, seehttp://success.yammer.com/integrations/directory-sync.
Q: Does this user mapping update impact Yammer and SharePoint 2013 on-premises deployments?
A: No, it doesn’t. SharePoint on-premises customers can leverage both Yammer Active Directory Sync and single sign-on to manage users and secure access to their Yammer network.
For information on how to integrate Yammer and SharePoint 2013 on-premises, please see Integrate Yammer with on-premises SharePoint 2013 environments (white paper).
No comments:
Post a Comment