New answers tagged single-sign-on
You might check mod_lua since it permits writing login hooks in lua language. That might give you a way to programatically add what is missing.
The issue is that the domain that was required for the SignInAccelerationDomain wasn't the domain used as the UPN for office 365 but the full domain name of the Windows domain. So i had to enable in my example the acceleration for "corp.B.com" and not for "B.com".
Did you use the Set-SPOTenant commandlet? Set-SPOTenant -SignInAcceletationDomain “mydomain.com” Set-SPO Tenant -EnableGuestSignInAcceleration $true There must also be only one identity provider in your AD. SharePoint Online must have a specific site to target when accelerating. The organization can have multiple domains as long as there is a single AD ...
You need to add your external domain (email domain) as an alternate UPN suffix for internal Active Directory users. To add UPN suffixes (from TechNet) Open Active Directory Domains and Trusts. To open Active Directory Domains and Trusts, click Start , click Administrative Tools , and then click Active Directory Domains and Trusts. In the console tree, ...
When you sync with Office 365 your internal domain must be a routable address and this should be assigned to users UPN suffix. When you sync users you will then use the same logon as you would internally (email@example.com) to login to Office 365. it's fine to have your Federated endpoint accessible from external.com (i.e. sts.external.com), as the server ...
Top 50 recent answers are included