Bringing new Yammer Users into Active State

Published Sep 12 2019 06:00 AM 28.7K Views
Microsoft

As Yammer continues to integrate more deeply with the Office 365 suite, we’ve set our sights on creating a consistent and coherent user state experience. We’re excited to share that we will soon be making "active" as the default state for new users when you deploy Yammer in your organizations or when new users join your organization. This would mean that from this point onwards, when you add a new user (say a new employee in your company) to AAD that user is Active Yammer user by default. 

Note: existing Pending users in your organization can become Active by logging in to Yammer.com. In the coming months, we will be running an automated process to convert any/all pending users for Yammer to Active. We will post an update here once that process is complete.  


A simpler state
Currently, Yammer is the only service within Microsoft 365 that uses the pending state concept, creating inconsistency with Azure Active Directory, access and integration issues with SharePoint and Microsoft Teams, and possible confusion for Office 365 admins. This change will make Yammer user state consistent with AAD user states and by extension, the rest of Office 365 apps such as Teams and Outlook. It will also allow new users to properly receive communication digests from Yammer and make deployment, data migration, and user onboarding with Yammer simple and frictionless. This is especially integral for customers migrating their data from US to EU since the user needs to be ‘active’ before their data can be migrated.


Timeline
The default Active state for all new users will be rolled out by end of September. In the coming months, we’ll begin the automated conversion of pending users to active users in your organization. This phase will be rolling out soon and expected to be completed by second half of 2020. Please share any feedback that you have during this time.

 

You’ll soon see a Message Center post in the admin center stating that no action will be required from admins for this change and users will no longer need to activate themselves to use Yammer or its integrations in Teams and SharePoint.

 

We’re excited to continue building Yammer into Office 365 and Microsoft 365. Stay up to date with our latest news and roadmap by subscribing to the Yammer blog and following us on Twitter.

 

- The Yammer Team

16 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-848028%22%20slang%3D%22en-US%22%3EBringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-848028%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20Yammer%20continues%20to%20integrate%20more%20deeply%20with%20the%20Office%20365%20suite%2C%20we%E2%80%99ve%20set%20our%20sights%20on%20creating%20a%20consistent%20and%20coherent%20user%20state%20experience.%20We%E2%80%99re%20excited%20to%20share%20that%20we%20will%20soon%20be%20making%20%22active%22%20as%20the%20default%20state%20for%20new%20users%20when%20you%20deploy%20Yammer%20in%20your%20organizations%20or%20when%20new%20users%20join%20your%20organization.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EA%20simpler%20state%3C%2FSTRONG%3E%3CBR%20%2F%3ECurrently%2C%20Yammer%20is%20the%20only%20service%20within%20Microsoft%20365%20that%20uses%20the%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fyammer%252Fmanage-yammer-users%252Fadd-block-or-remove-users%26amp%3Bdata%3D02%257C01%257Cv-chrkar%2540microsoft.com%257Ccdd3b0efe5194400917308d7366ac6b9%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637037704533721393%26amp%3Bsdata%3DRM09Hx%252BjB5kXmOTJj02gTaNwnBzgWrOLiz98lmyEdHk%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%3CEM%3Epending%3C%2FEM%3Estate%3C%2FA%3Econcept%2C%20creating%20inconsistency%20with%20Azure%20Active%20Directory%2C%20access%20and%20integration%20issues%20with%20SharePoint%20and%20Microsoft%20Teams%2C%20and%20possible%20confusion%20for%20Office%20365%20admins.%20This%20change%20will%20make%20Yammer%20user%20state%20consistent%20with%20AAD%20user%20states%20and%20by%20extension%2C%20the%20rest%20of%20Office%20365%20apps%20such%20as%20Teams%20and%20Outlook.%20It%20will%20also%20allow%20new%20users%20to%20properly%20receive%20communication%20digests%20from%20Yammer%20and%20make%20deployment%2C%20data%20migration%2C%20and%20user%20onboarding%20with%20Yammer%20simple%20and%20frictionless.%20This%20is%20especially%20integral%20for%20customers%20migrating%20their%20data%20from%20US%20to%20EU%20since%20the%20user%20needs%20to%20be%20%E2%80%98active%E2%80%99%20before%20their%20data%20can%20be%20migrated.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3ETimeline%3C%2FSTRONG%3E%3CBR%20%2F%3EIn%20the%20coming%20months%2C%20we%E2%80%99ll%20begin%20converting%20pending%20users%20to%20active%20users%20in%20your%20organization.%20This%20phase%20will%20be%20rolling%20out%20soon%20and%20expected%20to%20be%20completed%20by%20the%20end%20of%20August.%20Please%20share%20any%20feedback%20that%20you%20have%20during%20this%20time.%20We%E2%80%99ll%20then%20continue%20with%20the%20next%20phases%20by%20previewing%20the%20migration%20functionality%20with%20a%20select%20list%20of%20customers%20to%20monitor%20infrastructure%20needs%20and%20user%20needs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%E2%80%99ll%20soon%20see%20a%20Message%20Center%20post%20in%20the%20admin%20center%20stating%20that%20no%20action%20will%20be%20required%20from%20admins%20for%20this%20change%20and%20users%20will%20no%20longer%20need%20to%20activate%20themselves%20to%20use%20Yammer%20or%20its%20integrations%20in%20Teams%20and%20SharePoint.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%E2%80%99re%20excited%20to%20continue%20building%20Yammer%20into%20Office%20365%20and%20Microsoft%20365.%20Stay%20up%20to%20date%20with%20our%20latest%20news%20and%20roadmap%20by%20subscribing%20to%20the%20Yammer%20blog%20and%20following%20us%20on%20Twitter.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-%20The%20Yammer%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-848028%22%20slang%3D%22en-US%22%3E%3CP%3EWe%E2%80%99re%20excited%20to%20share%20that%20we%20will%20soon%20be%20making%20%22active%22%20as%20the%20default%20state%20for%20new%20users%20when%20you%20deploy%20Yammer%20in%20your%20organizations%20or%20when%20new%20users%20join%20your%20organization.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-848028%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%20Admin%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-852324%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-852324%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3572%22%20target%3D%22_blank%22%3E%40Ravin%20Sachdeva%3C%2FA%3E%26nbsp%3BHow%20do%20we%20find%20out%20how%20many%20and%20which%20users%20in%20our%20Yammer%20environment%20are%20currently%20in%20a%20pending%20state%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-852607%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-852607%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20the%20end%20of%20August%20time%20frame%20accurate%3F%20We%20are%20now%20midway%20into%20September%20and%20this%20post%20was%20added%203%20hours%20ago.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-852744%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-852744%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4271%22%20target%3D%22_blank%22%3E%40Eric%20Davis%3C%2FA%3E%20-%20you%20could%20try%20doing%20a%20GDPR%20export%20which%20should%20give%20you%20a%20breakdown%20of%20what%20is%20in%20your%20DB.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-852845%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-852845%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F167462%22%20target%3D%22_blank%22%3E%40Ryan%20Schouten%3C%2FA%3E%26nbsp%3B--%20this%20planned%20switch%20got%20moved%20back%20to%20give%20admins%20more%20heads%20up.%20Just%20edited%20the%20date.%20Thanks!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-852850%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-852850%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F13%22%20target%3D%22_blank%22%3E%40Michael%20Holste%3C%2FA%3E%26nbsp%3Bthanks.%20I%20wanted%20to%20make%20sure%20I%20can%20communicate%20the%20correct%20time%20frame%20to%20my%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-852930%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-852930%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3572%22%20target%3D%22_blank%22%3E%40Ravin%20Sachdeva%3C%2FA%3E%2C%20I%20ran%20the%20Yammer%20data%20export%20as%20you%20suggested%20using%20these%20directions%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fcompliance%2Fgdpr-dsr-office365%23yammer.%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fcompliance%2Fgdpr-dsr-office365%23yammer.%26nbsp%3B%3C%2FA%3E%20%26nbsp%3BI%20looked%20at%20the%20Users.csv%20file%2C%20and%20I%20did%20not%20see%20any%20way%20to%20find%20the%20pending%20users.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20provide%20more%20details%20on%20how%20to%20find%20who%20our%20pending%20users%20are%20who%20will%20be%20affected%20by%20this%20upcoming%20change%20you%20have%20announced.%26nbsp%3B%20Thank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-857555%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-857555%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4271%22%20target%3D%22_blank%22%3E%40Eric%20Davis%3C%2FA%3E%20-%20thanks%20for%20your%20patience%20for%20us%20to%20get%20back%20to%20you.%20Here's%20a%20guide%20that%20should%20have%20more%20info%20on%20interpreting%20the%20export%3A%26nbsp%3B%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Faskyammer.github.io%2Fpost%2F2016-04-28-interpreting-a-yammer-user-export%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faskyammer.github.io%2Fpost%2F2016-04-28-interpreting-a-yammer-user-export%2F%3C%2FA%3E.%20Hope%20this%20resolves%20your%20query.%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-858639%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-858639%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3572%22%20target%3D%22_blank%22%3E%40Ravin%20Sachdeva%3C%2FA%3E%26nbsp%3B%2C%20will%20all%20the%20pending%20users%20receive%20an%20email%20when%20they%20become%20active%3F%26nbsp%3B%20What%20will%20their%20experience%20be%20once%20the%20change%20takes%20effect%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-885954%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-885954%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3572%22%20target%3D%22_blank%22%3E%40Ravin%20Sachdeva%3C%2FA%3E%26nbsp%3Bcan%20you%20please%20provide%20an%20update%20on%20when%20this%20new%20active%20state%20experience%20is%20going%20to%20be%20rolled%20out%3F%26nbsp%3B%20Your%20blog%20post%20stated%20this%20was%20%22%3CSPAN%3Eexpected%20to%20be%20completed%20by%20the%20end%20of%20September.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-946661%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-946661%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20confirmed%20for%20me%20today%20this%20work%20was%20done%20between%20Oct%202%20-%2010.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-962649%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-962649%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20further%20update%20on%20actual%20timelines%20for%20this%2C%20now%20entering%20November!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-963161%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-963161%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F99259%22%20target%3D%22_blank%22%3E%40Bernie%20Murtagh%3C%2FA%3E%20-%20this%20change%20has%20been%20rolled%20out.%20Any%20new%20user%20that%20you%20add%20in%20your%20tenants%20would%20be%20added%20as%20Active%20by%20default.%26nbsp%3B%3C%2FP%3E%20%3CP%3E%26nbsp%3B%3C%2FP%3E%20%3CP%3EFor%20any%20specific%20questions%20about%20your%20organization%20or%20if%20you%20have%20any%20feedback%2C%20feel%20free%20to%20send%20me%20a%20private%20message.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1017526%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1017526%22%20slang%3D%22en-US%22%3EHi%20-%20You%20mention%20new%20users%20will%20automatically%20be%20made%20active%20but%20what%20about%20existing%20members%20that%20are%20still%20in%20pending%20status%3F%20I%20have%20some%202000%20users%20that%20don't%20seem%20to%20be%20active%20in%20Yammer%20but%20have%20an%20O365%20licence%3F%20Appreciate%20any%20advice%20you%20can%20give%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1017555%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1017555%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F462073%22%20target%3D%22_blank%22%3E%40aclark_1%3C%2FA%3E%20-%20if%20you%20could%20send%20me%20a%20private%20message%20here%20with%20your%20tenant%20details%2C%20we%20can%20work%20towards%20making%20your%20existing%20users%20active.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1024345%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20new%20Yammer%20Users%20into%20Active%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1024345%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3572%22%20target%3D%22_blank%22%3E%40Ravin%20Sachdeva%3C%2FA%3E%2C%26nbsp%3BI%20sent%20you%20a%20message%20on%20November%2010%20and%20now%20again%20today.%20Can%20you%20please%20check%20your%20inbox%3F%20Thx.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jun 24 2020 05:06 PM
Updated by: