Yammer bulk user update - update action

%3CLINGO-SUB%20id%3D%22lingo-sub-21064%22%20slang%3D%22en-US%22%3EYammer%20bulk%20user%20update%20-%20update%20action%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-21064%22%20slang%3D%22en-US%22%3E%3CP%3EHello.%20%26nbsp%3BI've%20been%20running%20a%20process%20for%20almost%202%20years%20now%20where%20if%20we%20inadvertenly%20have%20a%20user%20who%20signs%20up%20on%20Yammer%20with%20their%20%3CSTRONG%3EnetID%3C%2FSTRONG%3Eaddress%2C%20we%20run%20a%20%3CU%3Ebulk%20user%20update%3C%2FU%3Eto%20basically%20%22%3CEM%3Erename%3C%2FEM%3E%22%20it%20to%20their%20%3CSTRONG%3Efirst.last%3C%2FSTRONG%3Ealias%20without%20them%20losing%20content%20or%20group%20memberships.%20%26nbsp%3BAs%20soon%20as%20I%20run%20it%2C%20I%20can%20pull%20them%20up%20in%20Yammer%20and%20verify%26nbsp%3Bthat%20the%20email%20address%20was%20updated.%20%26nbsp%3BAlthough%20the%20update%20fails%20if%20I%20run%20it%20on%20the%20same%20day%20they%20sign%20up%2C%20this%20process%20has%20always%20worked%20for%20me%20-%20even%20up%20until%20last%20Friday.%20%26nbsp%3BHowever%20just%20now%26nbsp%3Bwhen%20I%20ran%20a%20bulk%20update%20on%20about%2018%26nbsp%3Busers%2C%20it%20left%20the%20netID%20accounts%20on%20the%20system%20and%20they%20all%20now%20appear%20to%20have%20a%20second%20%22pending%22%20stub%20for%20their%20first.last.%20%26nbsp%3BThis%20is%20not%20what%20I%20intended.%20%26nbsp%3BAnyone%20have%20any%20idea%20as%20to%20what%20could%20have%20changed%20since%20Friday%20and%20how%20I%20can%20fix%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-21064%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBugs%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-23443%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20bulk%20user%20update%20-%20update%20action%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-23443%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20you%20say%20%3CSTRONG%3EnetID%3C%2FSTRONG%3Edo%20you%20mean%20%3CSTRONG%3EOrgID%3C%2FSTRONG%3E(as%20in%20their%20Office%20365%20account)%3F%20And%20is%20%3CSTRONG%3Efirst.last%40%3C%2FSTRONG%3Ethe%20format%20of%20their%20email%20address%20which%20differs%20from%20their%20login%3F%3C%2FP%3E%3CP%3EIf%20that%20is%20the%20case%20(I'm%20dangerously%20assuming%20it%20is)%20best%20practice%20from%20a%20user%20perspective%20is%20actually%20to%20have%20their%20Office%20365%20login%20match%20their%20email%20address.%20This%20is%20generally%20a%20bigger%20piece%20of%20work%20and%20something%20I%20advice%20all%20clients%20before%20they%20start%20their%20Office%20365%20journey%20-%20their%20UPN%20%2F%20Active%20Directory%20login%20should%20match%20their%20email%20address%20to%20keep%20things%20simple%20for%20end%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello.  I've been running a process for almost 2 years now where if we inadvertenly have a user who signs up on Yammer with their netID address, we run a bulk user update to basically "rename" it to their first.last alias without them losing content or group memberships.  As soon as I run it, I can pull them up in Yammer and verify that the email address was updated.  Although the update fails if I run it on the same day they sign up, this process has always worked for me - even up until last Friday.  However just now when I ran a bulk update on about 18 users, it left the netID accounts on the system and they all now appear to have a second "pending" stub for their first.last.  This is not what I intended.  Anyone have any idea as to what could have changed since Friday and how I can fix this?

1 Reply

When you say netID do you mean OrgID (as in their Office 365 account)? And is first.last@ the format of their email address which differs from their login?

If that is the case (I'm dangerously assuming it is) best practice from a user perspective is actually to have their Office 365 login match their email address. This is generally a bigger piece of work and something I advice all clients before they start their Office 365 journey - their UPN / Active Directory login should match their email address to keep things simple for end users.