SOLVED

Yammer Mobile App Login

%3CLINGO-SUB%20id%3D%22lingo-sub-52569%22%20slang%3D%22en-US%22%3EYammer%20Mobile%20App%20Login%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52569%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20sure%20this%20will%20have%20a%20simple%20answer...I%20just%20can't%20work%20it%20out%20in%20my%20head%20and%20we%20can't%20test%20it%20yet.%3C%2FP%3E%3CP%3EWe%20have%20O365%20E3%20and%20a%20strict%20no%20BYOD%20policy%3B%20access%20via%20the%20on-premises%20network%20or%20via%20vpn%20and%20company%20owned%20laptops.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20someone%20installs%20the%20Yammer%20Mobile%20app%20on%20their%20own%20smartphone%2C%20how%20will%20it%20behave%20when%20they%20try%20to%20log%20into%20Yammer%20with%20their%20company%20email%20address%20and%20password%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-52569%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApp%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAuthentication%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECommunity%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65077%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Mobile%20App%20Login%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65077%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20also%20setup%20an%20IP%20whitelist%20to%20only%20allow%20connections%20from%20your%20network%20in%20the%20Security%20section%20of%20the%20Yammer%20admin%20area.%26nbsp%3B%20The%20result%20is%20that%20users%20can%20login%20fine%20while%20on%20the%20network%2C%20but%20recieve%20an%20error%20%22Network%20Error%3A%20Sorry!%26nbsp%3B%20Something%20went%20wrong.%26nbsp%3B%20Please%20wait%20a%20moment%20and%20try%20again.%26nbsp%3B%20Error%3A%20-1011%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou'll%20want%20to%20educate%20your%20users%20what%20this%20error%20means%20and%20remind%20them%20to%20use%20their%20corporate%20device%20and%20enable%20VPN%20if%20necessary.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52592%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Mobile%20App%20Login%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52592%22%20slang%3D%22en-US%22%3E%3CP%3EJared%2C%3CBR%20%2F%3EThat's%20right%2C%20it's%20up%20and%20running%20in%20the%20early%20stages%20and%20but%20not%20live%20for%20users%20yet.%3CBR%20%2F%3EGreat%20answer%2C%20thank%20you%20for%20responding%20to%20my%20question%2C%20I%20appreciate%20your%20time.%3CBR%20%2F%3ERegards%3CBR%20%2F%3EMark%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52573%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Mobile%20App%20Login%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52573%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20assuming%20that%20your%20company%20policies%20are%20written%20and%20not%20actually%20implemented%20in%20your%20Office%20365%20tenant.%20Therefore%2C%20by%20default%20users%20would%20be%20able%20to%20access%20Yammer%20from%20their%20smartphones%20or%20home%20computers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20believe%20what%20you%20might%20be%20looking%20for%20is%20Azure%20Active%20Directory%20Conditional%20Access%20-%20where%20you%20would%20have%20to%20load%20in%20your%20corporate%20subnets%20including%20the%20VPN%20pool%20addresses%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-conditional-access%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-conditional-access%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEssentially%20what%20you%20would%20be%20doing%20is%20blocking%20users%20from%20%22untrusted%20networks%22%20which%20in%20your%20case%20would%20be%20your%20corporate%20subnets.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello all,

 

I'm sure this will have a simple answer...I just can't work it out in my head and we can't test it yet.

We have O365 E3 and a strict no BYOD policy; access via the on-premises network or via vpn and company owned laptops.

 

If someone installs the Yammer Mobile app on their own smartphone, how will it behave when they try to log into Yammer with their company email address and password?

 

Thanks

 

3 Replies
best response confirmed by Mark Thompson (New Contributor)
Solution

I'm assuming that your company policies are written and not actually implemented in your Office 365 tenant. Therefore, by default users would be able to access Yammer from their smartphones or home computers.

 

I believe what you might be looking for is Azure Active Directory Conditional Access - where you would have to load in your corporate subnets including the VPN pool addresses:

https://docs.microsoft.com/en-us/azure/active-directory/active-directory-conditional-access

 

Essentially what you would be doing is blocking users from "untrusted networks" which in your case would be your corporate subnets.

Jared,
That's right, it's up and running in the early stages and but not live for users yet.
Great answer, thank you for responding to my question, I appreciate your time.
Regards
Mark

You can also setup an IP whitelist to only allow connections from your network in the Security section of the Yammer admin area.  The result is that users can login fine while on the network, but recieve an error "Network Error: Sorry!  Something went wrong.  Please wait a moment and try again.  Error: -1011"

 

You'll want to educate your users what this error means and remind them to use their corporate device and enable VPN if necessary.