![\"adfs30upnsuffix01\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/05\/adfs30upnsuffix01.jpg\" "\\"adfs30upnsuffix01\\"")
<\/p>\n<\/p>\n
To enable Single Sign-On with Office 365<\/strong>, ADFS 3.0 is the service to be configured to implement the federation process with Office 365.<\/p>\n The high availability<\/strong> concept becomes a key point in ADFS because once you are using SSO with Office 365, you rely on your local Active Directory<\/strong> for authentication.<\/p>\n <\/p>\n To keep the highest HA factor, ADFS components should be installed in different virtual servers<\/strong> of the virtual infrastructure and in different hosts to prevent loss of service due to hardware failure.<\/p>\n <\/p>\n ADFS 3.0 setup UPN suffix for Office 365 SSO - pt. 1 <\/p>\n To run ADFS 3.0 enabling Single Sign-On feature for Office 365, three core components need to be configured:<\/p>\n <\/p>\n The schema to setup the ADFS environment<\/strong> to enable SSO service is the following:<\/p>\n An improved design should include a load-balanced configuration<\/strong> in order to better distribute the load across the ADFS servers.<\/p>\n <\/p>\n If the used internal LAN domain name doesn\u2019t match the domain to federate<\/strong> with Office 365, a custom UPN suffix<\/strong> must be added in order to match the external name space.<\/p>\n Internal:\u00a0 nolabnoparty.local<\/strong> Open Active Directory Domain and Trust<\/strong> snap-in, right click the item Active Directory Domain and Trust and select Properties<\/strong> option.<\/p>\n Type in the Alternative UPN suffixes<\/strong> field the domain name to match the external domain used to federate with Office 365 then click Add<\/strong>.<\/p>\n Click OK<\/strong> to save the configuration and close Active Directory Domain and Trust window.<\/p>\n The new UPN suffix must be assigned to the users in order to perform the authentication<\/strong> with federated domain.<\/p>\n Open Active Directory Users and Computers<\/strong> and select the users to configure. Right click the selection and choose Properties<\/strong> option.<\/p>\n Thick UPN suffix<\/strong>, select the correct domain name and click OK<\/strong> to save the configuration.<\/p>\n Looking at the user's properties, the User logon name<\/strong> field is now set with the UPN suffix just configured.<\/p>\n The UPN suffix is set and both domains (internal and external) match.<\/p>\nBlog series<\/h2>\n
\nADFS 3.0 SSL certificate signing request - pt. 2<\/a>
\nADFS 3.0 install ADFS Server - pt. 3<\/a>
\nADFS 3.0 install WAP Server - pt. 4<\/a>
\nADFS 3.0 federating Office 365 - pt. 5<\/a>
\nADFS 3.0 install Directory Sync tool - pt. 6<\/a>
\nADFS 3.0 deploy Office 365 - pt. 7<\/a><\/p>\nPrerequisites<\/h2>\n
\n
Schema<\/h2>\n
![\"adfs30upnsuffix02\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/05\/adfs30upnsuffix02.jpg\" "\\"adfs30upnsuffix02\\"")
<\/p>\nSetup UPN suffix<\/h2>\n
\nExternal: \u00a0nolabnoparty.com<\/strong><\/p><\/blockquote>\n![\"adfs30upnsuffix03\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/05\/adfs30upnsuffix03.jpg\" "\\"adfs30upnsuffix03\\"")
<\/p>\n![\"adfs30upnsuffix04\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/05\/adfs30upnsuffix04.jpg\" "\\"adfs30upnsuffix04\\"")
<\/p>\n![\"adfs30upnsuffix05\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/05\/adfs30upnsuffix05.jpg\" "\\"adfs30upnsuffix05\\"")
<\/p>\n![\"adfs30upnsuffix06\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/05\/adfs30upnsuffix06.jpg\" "\\"adfs30upnsuffix06\\"")
<\/p>\n![\"adfs30upnsuffix07\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/05\/adfs30upnsuffix07.jpg\" "\\"adfs30upnsuffix07\\"")
<\/p>\n![\"adfs30upnsuffix08\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/05\/adfs30upnsuffix08.jpg\" "\\"adfs30upnsuffix08\\"")
<\/p>\n
![\"firma\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" "\\"\\"")
<\/p>\n","protected":false},"excerpt":{"rendered":"