| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
DirSync and ADFS provides a single sign on experience. As well it allows users to reside both on premises as well as in the cloud.
...
The external certificate is used to authenticate any requests coming into the ADFS server.
Installing DirSync
To begin setting up DirSync log into https://login.microsoftonline.com/ with your administrator account. Next go to the Dashboard->Active users and click on Setup next to Active Directory Synchronization.
Next the DirSync wizard will begin to ask you questions. In order to install DirSync select at-least 51-250 as shown below and then click Next.
Click Next at the welcome screen.
Review the check list quickly and then click Next to download the app that will verify the check list for you.
Click Start Scan to begin the check.
Click Run Checks at this screen to continue the automatic check.
Once the Security Warning pops up click Run the Run the application.
Once the check is completed you should see a empty list as shown below. If there is issues on this list review and correct them before proceeding.
Next a scan will be done to check how many objects and domains you have to sync using DirSync.
You will get a summary such as the one below. Typically of course more users/groups and contacts will be populated.
On the Get your domains ready page click Next.
At this point review the domains you are syncing and click next.
The domains are now ready at this point, but there is a warning here since in this example we are using a .local domain. This will simply convert these users to .onmicorosoft.com domain.
Download the IDFix to ensure there is no issues lingering around.
In most cases once you run IDFix the output should be empty as shown below.
Next Azure Active Directory Connect wil need to be installed. Click Next to continue.
At the welcome splash screen click Continue.
Click use Express settings to continue.
Next log in with your Azure AD administrator account.
Then enter your local AD administrator account details.
Ensure Start the Synchronization process as soon as the configuration completes is checked and then click Install.
Installing Active Directory Federation Services
...
Next go into the Server Manager and the Post-Deployment Configuration warning will be displayed. Click Configure the Federation Service on this Server link.
Click Next at the Welcome screen.
Specify the AD domain administrator account you would like to use. Then click Next to continue.
At this point important your public SSL certificate. Then ensure your Federiation Service name is correct.
At this point enter in a new account name for the Group Managed Service Account.
Next continue through the wizard by clicking Next. Once the Wizard completes verify everything was succesful. If any issues occurred ensure they are resolved.
...
Create a domain administrator account in the on premise active directory. Wait until this account is synced to Azure. Once it is sync it will show up in the Active users list as shown below. Select the account and click Edit Users Roles.
On the next page you will see the following admin role options. Select Global Administraor and click save. This user is now a local domain administrator and an Office 365 administrator.
At this point now run the commands below.
$cred = get-Credential
- Enter domain administrator account from steps #1-2. I.E. jenny@sfbsangoma.onmicrosoft.com which is a administrator on premise and in Office 365.
Connect-MsolService -Credential $cred
Convert-MsolDomainToFederated -DomainName sfbsangoma.com -SupportMultipleDomain
- Substitute sfbsangoma.com for your own domain
...
Next run the command Get-MsolFederationProperty -DomainName sfbsangoma.com to verify the domain has been federated.
Before testing the first user ensure the Windows domain is configured as a FQDN. If you are using a Windows domain name such as "sfbsangoma.local" then simply edit Active Directory Domains and Trusts. Click on Adviace Directory Domains and Trust in the left plane. Next right click in the main plane and click Properties.
At this point enter the FQDN domain that is being used for Office 365. In this case "sfbsangoma.com" and then click OK.
At this point edit the user and go to the Account tab. Change the domain part of the UPN to the FQDN domain "sfbsangoma.com".
At this point go to https://testconnectivity.microsoft.com/ to run the Office 365 Single Sign-On Test.
On this page enter a valid user account to validate.
Once the test passes then Single Sign On has been completed. If there is any issues resolve these before continuing.
...
Run the commands below to configure federation with Skype For Business Online.
Set-CSAccessEdgeConfiguration -AllowOutsideUsers 1 -AllowFederatedUsers 1 -UseDnsSrvRouting -EnablePartnerDiscovery 1
Get-CsHostingProvider
Remove-CsHostingProvider -Identity "Skype For Business Online"
New-CSHostingProvider -Identity LyncOnline -ProxyFqdn "sipfed.online.lync.com" -Enabled $true -EnabledSharedAddressSpace $true -HostsOCSUsers $true -VerificationLevel UseSourceVerification -IsLocal $false -AutodiscoverUrl https://webdir.online.lync.com/Autodiscover/AutodiscoverService.svc/root
Next log into the Office 365 admin center and select the user you wish to move to Skype For Business Online. Then click Edit next to Assign License.
On the next page check Office 365 Enterprise E3 license.
Run the commands below to set the SIP shared address space.
Import-Module LyncOnlineConnector
$cred = Get-Credential
$CSSession = New-CsOnlineSession -Credential $cred
Import-PSSession $CSSession -AllowClobber
Get-CsTenantFederationConfiguration
Set-CsTenantFederationConfiguration -Share dSipAddressSpace $true
Next since sfbsangoma.local is the on premise domain then we will need to add sfbsangoma.com as an alternative UPN suffix. To do this go to into Active Directory Domains and Trusts and right click on the domain. Then select properties.
At this point enter the FQDN sip domain sfbsangoma.com is used in this example.
Once this is completed edit the user you are going to move to the cloud and change the domain from sfbsangoma.local to sfbsangoma.com.
