呢個Topic，自己絕對會評定為今年做過，繼多年前SharePoint 2010後，最難，最好玩嘅一樣。
基如ADFS 3.0已有，拍Microsoft O365/Azure 嘅SSO 亦係兩日內起身。諗唔出有啲咩理由唔去做埋佢
整個setup進行左三日.當中要提最難,係一路失敗當中research / adjustment.
而令到咁長時間嘅原因係以下……
1. Exchange Server 2013：避免問題（亦發現太耐無更新，由SP1 upgrade 去 CU10）
2. ADFS Server Signing Token Certificate : 絕對係一個意外收穫嘅做法。 同時亦證明只需要Update Azure AD 一次就得，唔會影響舊有 Federation Trust
“Update-MSOLFederatedDomain –DomainName”
https://azure.microsoft.com/en-us/documentation/articles/active-directory-aadconnect-o365-certs/
http://hazelnest.com/blog/blog/2015/07/05/exchange-2013-using-adfs-to-authenticate/
3. Exchange Server Internal/External Url ： Reference URL 無一個係用 .local Domain……而係Exchange configure ECP/OWA (一定要 ECP 先， OWA 後）用ADFS 前。
$uris = @(” https://mail.contoso.nl/owa”,”https://mail.contoso.nl/ecp“)
Set-OrganizationConfig -AdfsIssuer “https://adfs.contoso.nl/adfs/ls/” -AdfsAudienceUris $uris -AdfsSignCertificateThumbprints “FD6C58A0589F398FBDAE144EA0A1A1EDC718EC11“
Get-EcpVirtualDirectory | Set-EcpVirtualDirectory -AdfsAuthentication $true -BasicAuthentication $false -DigestAuthentication $false -FormsAuthentication $false -WindowsAuthentication $false
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -AdfsAuthentication $true -BasicAuthentication $false -DigestAuthentication $false -FormsAuthentication $false -WindowsAuthentication $false
兩者define 嘅URL 一定要係Internal。不然就係失敗收場…………
Reference
http://nilsvanwoensel.azurewebsites.net/?p=137
PS.。 後話… 基於比M＄ 班人挑機話ADFS Server 唔用埋MFA 唔Pro。 下一個大Change就係 Azure MFA On Premises Server with ADFS