Home

Teams - Single sign on / Automatic login / Pass through auth

%3CLINGO-SUB%20id%3D%22lingo-sub-37975%22%20slang%3D%22en-US%22%3ETeams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37975%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20rolled%20out%20Teams%20in%20our%20organisation%20and%20our%20biggest%20complaint%20is%20it%20doesn't%20login%20automatically%20for%20users.%20We're%20running%20Azure%20AD%20connect%20with%20Pass%20Through%20Auth%20and%20SSO.%20All%20other%20Office%20365%20apps%20sign%20in%20automatically%20for%20users.%20I%20really%20think%20this%20would%20help%20the%20uptake%20of%20Teams%20in%20our%20organisation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20Skype%20for%20Business%20we%20created%20a%20proxyAddress%20entry%20for%20the%20user%20which%20auto%20populates%20the%20login%20field.%20Is%20there%20anything%20similar%20for%20Teams%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ECraig.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-37975%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369526%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369526%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20pretty%20much%20what%20I%20ended%20up%20doing%2C%20thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-368036%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368036%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F216697%22%20target%3D%22_blank%22%3E%40Brian%20Giguere%3C%2FA%3E%26nbsp%3Bit%20doesn't%20look%20like%20this%20is%20being%20updated%20anytime%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20working%20around%20this%20by%20setting%20a%20custom%20UPN%20in%20AD%20and%20updating%20the%20user%20portion%20of%20the%20UPN%20to%20match%20the%20email%20address.%20This%20way%20it's%20pre-populated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20we%20still%20log%20on%20to%20Windows%20with%20DOMAIN%5Cusername%20this%20is%20the%20only%20way%20we%20have%20found%20to%20make%20this%20easier.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-365616%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-365616%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F172585%22%20target%3D%22_blank%22%3E%40Ben%20Grinsted%3C%2FA%3E%26nbsp%3Bany%20luck%20with%20this%3F%26nbsp%3B%20Running%20into%20the%20same%20issue%20with%20the%20wrong%20username%20being%20populated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327184%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327184%22%20slang%3D%22en-US%22%3E%3CP%3EAccording%20to%20this%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fidentity%2Fad-fs%2Foperations%2Fconfiguring-alternate-login-id%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fidentity%2Fad-fs%2Foperations%2Fconfiguring-alternate-login-id%3C%2FA%3E%20Teams%20supports%20Alternate%20Login%20ID%2C%20but%20I'm%20still%20seeing%20the%20UPN%20populated%20in%20the%20Teams%20app%20when%20logging%20on%20for%20the%20first%20time.%20Can%20this%20either%20be%20removed%20or%20set%20to%20use%20the%20Alternate%20Login%20ID%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-301500%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-301500%22%20slang%3D%22en-US%22%3E%3CP%3EShould%20single%20sign-on%2Fpass%20thru%20work%20if%20we%20are%20logged%20into%20our%20local%20Active%20Directory%20on-prem%2C%20but%20have%20our%20AD%20synchronizing%20with%20Azure%20AD%3F%26nbsp%3B%20In%20other%20words%3A%3C%2FP%3E%3CP%3E1.%20I%20log%20into%20Windows%20with%20my%20on-prem%20AD%20account%2Fpassword%3C%2FP%3E%3CP%3E2.%20I%20launch%20Microsoft%20Teams%3C%2FP%3E%3CP%3E3.%20it%20asks%20me%20to%20login%3C%2FP%3E%3CP%3E4.%20I%20use%20the%20same%20account%2Fpassword%20as%20in%20%231%2C%20and%20I%20get%20logged%20into%20Teams%20succesfully%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EShouldn't%20%233%20be%20bypassed%20because%20i'm%20using%20the%20same%20AD%20account%20on%20Windows%20as%20I%20am%20on%20Teams%3F%26nbsp%3B%20They%20are%20just%20coming%20from%20two%20different%20places%20(local%20AD%20on-prem%3B%20Azure%20AD).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206588%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206588%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37137%22%20target%3D%22_blank%22%3E%40Ansuman%20Acharya%3C%2FA%3E%26nbsp%3BI%20receive%20a%20proxy%20authenication%20prompt%20when%20I%20start%20up%20Teams%20everyday.%20Is%20there%20a%20way%20to%20automatically%20bypass%20the%20prompt%3F%20It%20saves%20my%20credentials%20from%20the%20previous%20use%2C%20but%20will%20not%20bypass%20automiatically.%20I%20tried%20this%20string%20in%20the%20shortcut%20for%20Teams%20%3A%20%22--proxy-server%3Dproxyus.ourcompany.int%3A8080%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-86151%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-86151%22%20slang%3D%22en-US%22%3EI'm%20still%20seeing%20the%20same%20behavior%20where%20SSO%20is%20not%20working%20yet.%20I%20have%20a%20synchronized%20account%20on%20my%20traditional%20domain%20joined%20machine.%20Also%2C%20we%20are%20using%20Alternative%20ID%20as%20well.%20Also%2C%20I%20don't%20see%20the%20team%20I'm%20part%20of%20yet%2C%20not%20sure%20if%20it%20is%20due%20the%20same%20problem.%20The%20first%20prompt%20comes%20from%20Azure%2C%20the%20second%20prompt%20comes%20from%20ADFS.%20Is%20this%20configuration%20supported%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-73381%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-73381%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20sure%20if%20anyone%20is%20monitoring%20this%20thread%20because%20I'm%20a%20bit%20late%20to%20the%20party...%20but%20I%20am%20wondering%20if%20I%20can%20set%20up%20SAML%20SSO%20for%20Teams%20with%20a%203rd%20party%20IDP%20such%20as%20Okta%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59521%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59521%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Liz%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20have%20MFA%20on%20your%20account%20you%20should%20be%20able%20to%20use%20an%20app%20password%20for%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20create%20an%20app%20password%2C%20login%20to%20portal.office.com%2C%20click%20your%20name%20in%20the%20upper%20right%20corner%20and%20choose%20'View%20Account'.%3C%2FP%3E%3CP%3EThen%20go%20to%20'Security%20and%20Privacy'%20-%20'Additional%20Security%20Verification'%20and%20click%20the%20link%20'Update%20your%20phone%20numbers%20used%20for%20account%20security'.%20Click%20'app%20passwords'%20and%20create%20one.%20Copy%2Fpaste%20that%20in%20your%20password%20field%20in%20the%20MS%20Teams%20client%20and%20you%20should%20be%20good%20to%20go.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%3C%2FP%3E%3CP%3ESteve%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59500%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59500%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CSPAN%3EAnsuman%20-%20Actually%20looks%20like%20it's%20already%20working%20for%20some%20of%20our%20users!!%20yay!!.%20but%20I%20get%20an%20error%20every%20morning%20since%20i%20have%20MFA%20enabled%20on%20my%20Office365%20account.%20When%20MS%20Teams%20launches%20in%20the%20morning%2C%20i%20get%20an%20error%20and%20have%20to%20manually%20enter%20my%20credentials%20and%20the%20code%20texted%20to%20me.%20(We're%20also%20working%20on%20getting%20Pass%20Through%20enabled%20in%20our%20Amazon%20Workspaces%20EC2%20environment).%20Any%20thoughts%2Fsuggestions%20would%20be%20appreciated!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59498%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59498%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CSPAN%3EAnsuman!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20currently%20running%3CSPAN%3E%26nbsp%3B%22Microsoft%20Teams%20Version%201.0.00.8201%20(32-bit).%20It%20was%20last%20updated%20on%203%2F30%2F17%22%20and%20just%20ran%20the%20update%20but%20it's%20showing%20I'm%20on%20the%20same%20version.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIs%20it%20MS%20Teams%20that%20the%20update%20will%20come%20through%20or%20in%20Windows%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20Windows%2C%20will%20it%20come%20through%20in%20the%20Windows%20updates%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Eliz%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59497%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59497%22%20slang%3D%22en-US%22%3E%3CP%3EGuys%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20Ansuman%20from%20the%20Teams%20PM%20Team.%20We%20have%20rolled%20out%20SSO%20and%20you%20should%20be%20seeing%20it%20on%20your%20latest%20Windows%20Desktop%20Client%20builds.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIdeally%2C%20the%20behavior%20should%20be%20just%20the%20same%20as%20other%20Office%20Apps.%20If%20you're%20logged%20into%20Windows%20thru%20AAD%20Credentials%2C%20it%20should%20just%20go%20through%20and%20silently%20login.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20a%20case%2C%20where%20your%20users%20do%20receive%20the%20SSO%20Login%20screen%2C%20please%20do%20ask%20them%20to%20login%20for%20the%20first%20time%20and%20not%20cancel%20out%20(this%20is%20the%26nbsp%3Bfallback%20option%20to%20the%20older%20web-auth%20but%20will%20be%20removed%20soon).%20After%20that%20it%20should%20just%20continue%20to%20login%20silently%20without%20requiring%20entry%20of%20crendentials.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELet%20us%20know%20if%20you%20see%20anything%20bad.%20We're%20listening.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F28055%22%20target%3D%22_blank%22%3E%40Swati%20Jhawar%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheers%2C%3C%2FP%3E%0A%3CP%3EAnsuman%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54061%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54061%22%20slang%3D%22en-US%22%3EMy%20MS%20Teams%20desktop%20app%20got%20an%20update%20yesterday%20and%20since%20then%20the%20login%20process%20acts%20the%20same%20as%20SfB%20in%20the%20sense%20that%20when%20I%20log%20on%20to%20my%20machine%2C%20both%20SfB%20and%20Teams%20automatically%20login%20using%20the%20cached%20credentials.%3CBR%20%2F%3ENot%20entirely%20SSO%20since%20you%20still%20have%20to%20login%20the%20first%20time%20manually%20but%20much%20better%20than%20before%20where%20you%20had%20to%20sign%20in%20every%20time%20Teams%20app%20launched.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53787%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53787%22%20slang%3D%22en-US%22%3EHi%2C%20I%20was%20looking%20as%20well%20for%20SSO%20with%20MS%20Teams%20and%20stumbled%20upon%20this%20thread%20%3CA%20href%3D%22https%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%2Fmsoffice_o365admin-mso_teams%2Fms-teams-how-to-enable-the-sso%2F1030c4b3-2854-4a1e-8426-bd1dc803b9d4%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%2Fmsoffice_o365admin-mso_teams%2Fms-teams-how-to-enable-the-sso%2F1030c4b3-2854-4a1e-8426-bd1dc803b9d4%3C%2FA%3E%20Basically%20it's%20in%20the%20works%20but%20no%20timeframe%20for%20release%20yet%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51664%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51664%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3849%22%20target%3D%22_blank%22%3E%40Carlo%20Reggiani%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3ESame%20issue%20for%20me%3A%20we%20have%20a%20federated%20domain%20for%20hybrid%20O365%20configuration.%3CBR%20%2F%3E%3CBR%20%2F%3EEvery%20application%20startup%20users%20must%20to%20digit%20user%20and%20password%2C%20very%20annoyning%20situation%3A%20a%20lot%20of%20user%20(90%25)%20not%20use%20Teams%20for%20this%20reason!%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20solution%20to%20integrate%20login%20credential%20(like%20Outlook%2C%20for%20example)%20%3F%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CBR%20%2F%3EWe%20have%20the%20same%20issue..%20we%20haven't%20officially%20rolled%20out%20Microsoft%20Teams%20yet%2C%20but%20no%20doubt%20this%20is%20going%20to%20be%20a%20hurdle%20for%20user%20adoption.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51663%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51663%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20the%20same%20issue..%20we%20haven't%20officially%20rolled%20out%20Microsoft%20Teams%20yet%2C%20but%20no%20doubt%20this%20is%20going%20to%20be%20a%20hurdle%20for%20user%20adoption.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-39430%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-39430%22%20slang%3D%22en-US%22%3ESame%20issue%20for%20me%3A%20we%20have%20a%20federated%20domain%20for%20hybrid%20O365%20configuration.%3CBR%20%2F%3E%3CBR%20%2F%3EEvery%20application%20startup%20users%20must%20to%20digit%20user%20and%20password%2C%20very%20annoyning%20situation%3A%20a%20lot%20of%20user%20(90%25)%20not%20use%20Teams%20for%20this%20reason!%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20solution%20to%20integrate%20login%20credential%20(like%20Outlook%2C%20for%20example)%20%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-728221%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-728221%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37137%22%20target%3D%22_blank%22%3E%40Ansuman%20Acharya%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wanted%20to%20jump%20in%20here%20and%20add%20a%20couple%20thoughts%20and%20to%20share%20what%20I'm%20experiencing%20with%20Teams.%3C%2FP%3E%3CP%3EWe%20have%20on%20prem%20ADFS%20servers%20NOT%20yet%20using%20%22Forms%20based%20Auth%22%20for%20Intranet...%3C%2FP%3E%3CP%3EWhen%20user%20first%20installs%20Teams%20app%20-%20they%20can%20logon%20fine%20-%20does%20not%20prompt%20for%20password%20-%20does%20SSO%20and%20it%20is%20perfect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20only%20after%20the%20initial%20logon%20we%20run%20into%20problems...and%20only%20if%20Forms%20based%20auth%20IS%20NOT%20checked%20on%20our%20ADFS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20just%20very%20curious%20why%20initial%20logon%20works%20-%20but%20after%20that%20the%20experience%20changes%20and%20it%20hits%20our%20ADFS%20and%20fails%20since%20Forms%20Based%20auth%20option%20is%20NOT%20available.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20if%20I%20could%20figure%20out%20a%20way%20to%20make%20every%20user%20logon%20behave%20like%20a%20first%20time%20logon!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20thoughts%20or%20tips%20would%20be%20appreciated.%26nbsp%3B%20BTW%2C%20when%20we%20turn%20on%20Forms%20based%20auth%20it%20breaks%20our%20SSO%20with%20our%20Remedy%20in%20the%20cloud!%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-SUB%20id%3D%22lingo-sub-822548%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-822548%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F172585%22%20target%3D%22_blank%22%3E%40Ben%20Grinsted%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20we%20could%20say%20that%20Microsoft%20Teams%20is%20the%20only%20O365%20app%20that%20doesn't%20support%20SSO%20for%20the%20first%20connection%20%26amp%3B%20token%20expiration%20(%20password%20expiration%20or%20changing%20password)%20%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-826574%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826574%22%20slang%3D%22en-US%22%3EYou%20could%20say%20that!%20Our%20setup%20works%20well%20until%20someone%20changes%20their%20password%2C%20at%20which%20point%20there's%20a%20lot%20of%20clearing%20out%20of%20credential%20caches%20and%20trying%20to%20fully%20log%20out%20of%20Teams%20before%20you%20can%20get%20back%20in%20again.%20It's%20not%20seamless!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-831502%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20-%20Single%20sign%20on%20%2F%20Automatic%20login%20%2F%20Pass%20through%20auth%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-831502%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F172585%22%20target%3D%22_blank%22%3E%40Ben%20Grinsted%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20this%20is%20the%20behavior%20of%20Microsoft%20Teams.%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20information%2C%20now%20when%20the%20user%20signs%20out%20from%20Microsoft%20Teams%2C%20et%20re-launch%20the%20app%20again%2C%20he%20doesn't%20need%20to%20enter%20the%20email%20%26amp%3B%20password%2C%20the%20app%20now%20will%20connect%20automatically.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Craig Ward
Occasional Visitor

Hi,

 

We've rolled out Teams in our organisation and our biggest complaint is it doesn't login automatically for users. We're running Azure AD connect with Pass Through Auth and SSO. All other Office 365 apps sign in automatically for users. I really think this would help the uptake of Teams in our organisation.

 

For Skype for Business we created a proxyAddress entry for the user which auto populates the login field. Is there anything similar for Teams?

 

Thanks,

Craig.

21 Replies
Same issue for me: we have a federated domain for hybrid O365 configuration.

Every application startup users must to digit user and password, very annoyning situation: a lot of user (90%) not use Teams for this reason!

Any solution to integrate login credential (like Outlook, for example) ?

We have the same issue.. we haven't officially rolled out Microsoft Teams yet, but no doubt this is going to be a hurdle for user adoption.


@Carlo Reggiani wrote:
Same issue for me: we have a federated domain for hybrid O365 configuration.

Every application startup users must to digit user and password, very annoyning situation: a lot of user (90%) not use Teams for this reason!

Any solution to integrate login credential (like Outlook, for example) ?


We have the same issue.. we haven't officially rolled out Microsoft Teams yet, but no doubt this is going to be a hurdle for user adoption.

Hi, I was looking as well for SSO with MS Teams and stumbled upon this thread https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_teams/ms-teams-how-to-enab... Basically it's in the works but no timeframe for release yet
My MS Teams desktop app got an update yesterday and since then the login process acts the same as SfB in the sense that when I log on to my machine, both SfB and Teams automatically login using the cached credentials.
Not entirely SSO since you still have to login the first time manually but much better than before where you had to sign in every time Teams app launched.

Guys,

 

This is Ansuman from the Teams PM Team. We have rolled out SSO and you should be seeing it on your latest Windows Desktop Client builds.

 

Ideally, the behavior should be just the same as other Office Apps. If you're logged into Windows thru AAD Credentials, it should just go through and silently login.

 

In a case, where your users do receive the SSO Login screen, please do ask them to login for the first time and not cancel out (this is the fallback option to the older web-auth but will be removed soon). After that it should just continue to login silently without requiring entry of crendentials.

 

Let us know if you see anything bad. We're listening.

 

@Swati Jhawar 

 

Cheers,

Ansuman

Thanks Ansuman!

 

 

I'm currently running "Microsoft Teams Version 1.0.00.8201 (32-bit). It was last updated on 3/30/17" and just ran the update but it's showing I'm on the same version.

 

Is it MS Teams that the update will come through or in Windows? 

 

If Windows, will it come through in the Windows updates?

 

Thanks!

 

liz

Hi Ansuman - Actually looks like it's already working for some of our users!! yay!!. but I get an error every morning since i have MFA enabled on my Office365 account. When MS Teams launches in the morning, i get an error and have to manually enter my credentials and the code texted to me. (We're also working on getting Pass Through enabled in our Amazon Workspaces EC2 environment). Any thoughts/suggestions would be appreciated!

Hi Liz,

 

If you have MFA on your account you should be able to use an app password for this.

 

To create an app password, login to portal.office.com, click your name in the upper right corner and choose 'View Account'.

Then go to 'Security and Privacy' - 'Additional Security Verification' and click the link 'Update your phone numbers used for account security'. Click 'app passwords' and create one. Copy/paste that in your password field in the MS Teams client and you should be good to go.

 

Kind regards

Steve

Not sure if anyone is monitoring this thread because I'm a bit late to the party... but I am wondering if I can set up SAML SSO for Teams with a 3rd party IDP such as Okta?

I'm still seeing the same behavior where SSO is not working yet. I have a synchronized account on my traditional domain joined machine. Also, we are using Alternative ID as well. Also, I don't see the team I'm part of yet, not sure if it is due the same problem. The first prompt comes from Azure, the second prompt comes from ADFS. Is this configuration supported?

@Ansuman Acharya I receive a proxy authenication prompt when I start up Teams everyday. Is there a way to automatically bypass the prompt? It saves my credentials from the previous use, but will not bypass automiatically. I tried this string in the shortcut for Teams : "--proxy-server=proxyus.ourcompany.int:8080"

Should single sign-on/pass thru work if we are logged into our local Active Directory on-prem, but have our AD synchronizing with Azure AD?  In other words:

1. I log into Windows with my on-prem AD account/password

2. I launch Microsoft Teams

3. it asks me to login

4. I use the same account/password as in #1, and I get logged into Teams succesfully

 

Shouldn't #3 be bypassed because i'm using the same AD account on Windows as I am on Teams?  They are just coming from two different places (local AD on-prem; Azure AD).

According to this https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/configuring-alternate-logi... Teams supports Alternate Login ID, but I'm still seeing the UPN populated in the Teams app when logging on for the first time. Can this either be removed or set to use the Alternate Login ID?

@Ben Grinsted any luck with this?  Running into the same issue with the wrong username being populated.

@Brian Giguere it doesn't look like this is being updated anytime soon.

 

We are working around this by setting a custom UPN in AD and updating the user portion of the UPN to match the email address. This way it's pre-populated.

 

Since we still log on to Windows with DOMAIN\username this is the only way we have found to make this easier.

That's pretty much what I ended up doing, thanks!

@Ansuman Acharya 

 

I wanted to jump in here and add a couple thoughts and to share what I'm experiencing with Teams.

We have on prem ADFS servers NOT yet using "Forms based Auth" for Intranet...

When user first installs Teams app - they can logon fine - does not prompt for password - does SSO and it is perfect.

 

It is only after the initial logon we run into problems...and only if Forms based auth IS NOT checked on our ADFS.

 

I'm just very curious why initial logon works - but after that the experience changes and it hits our ADFS and fails since Forms Based auth option is NOT available.

 

What if I could figure out a way to make every user logon behave like a first time logon!

 

Any thoughts or tips would be appreciated.  BTW, when we turn on Forms based auth it breaks our SSO with our Remedy in the cloud!

 

Thanks.

 

Hello @Ben Grinsted 

So we could say that Microsoft Teams is the only O365 app that doesn't support SSO for the first connection & token expiration ( password expiration or changing password) ? 

You could say that! Our setup works well until someone changes their password, at which point there's a lot of clearing out of credential caches and trying to fully log out of Teams before you can get back in again. It's not seamless!

Hello @Ben Grinsted 

Yes this is the behavior of Microsoft Teams. 

For information, now when the user signs out from Microsoft Teams, et re-launch the app again, he doesn't need to enter the email & password, the app now will connect automatically.  

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
16 Replies
flashing a white screen while open new tab
cntvertex in Discussions on
11 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
*Updated 9/3* Syncing in Microsoft Edge Preview Channels
Elliot Kirk in Articles on
217 Replies