You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The manifest description for upnSuffixToDomainMappings has a typo. Below shows the correction.
In some Active Directory environments, users do not use username@domain to login; they use a UPN suffix to make the username easier to use. This settingssetting maps the UPN suffix to the correct AD domain name. For example, if you have an AD domain of foo.com but want users to sign in as [email protected], a UPN suffix of foo.com is created in AD and the user account is set to [email protected]. This setting then would map foo.com to bar.com by setting the key upn to foo.com and the domain key to bar.com.
The text was updated successfully, but these errors were encountered:
In build 8145 the change does not look right. Correct version should be:
In some Active Directory environments, users do not use username@domain to login; they use a UPN suffix to make the username easier to use. This setting maps the UPN suffix to the correct AD domain name. For example, if you have an AD domain of foo.com but want users to sign in as [email protected], a UPN suffix of foo.com is created in AD and the user account is set to [email protected]. This setting then would map foo.com to bar.com by setting the key upn to foo.com and the domain key to bar.com.
v5.2b8111
The manifest description for
upnSuffixToDomainMappings
has a typo. Below shows the correction.In some Active Directory environments, users do not use username@domain to login; they use a UPN suffix to make the username easier to use. This
settingssetting maps the UPN suffix to the correct AD domain name. For example, if you have an AD domain of foo.com but want users to sign in as [email protected], a UPN suffix of foo.com is created in AD and the user account is set to [email protected]. This setting then would map foo.com to bar.com by setting the key upn to foo.com and the domain key to bar.com.The text was updated successfully, but these errors were encountered: