How to configure Skype for Business on-premises to use Hybrid Modern Authentication
Modern Authentication, is a method of identity management that offers more secure user authentication and authorization, is available for Skype for Business server on-premises and Exchange server on-premises, as well as split-domain Skype for Business hybrids.
Important Would you like to know more about Modern Authentication (MA) and why you might prefer to use it in your company or organization? Check this document for an overview. If you need to know what Skype for Business topologies are supported with MA, that's documented here!
Before we begin, I call:
Modern Authentication > MA
Hybrid Modern Authentication > HMA
Exchange on-premises > EXCH
Exchange Online > EXO
Skype for Business on-premises > SFB
and Skype for Business Online > SFBO
Also, *if a graphic in this article has an object that's 'grayed-out' or 'dimmed' that means the element shown in gray is not included in MA-specific configuration. *
Read the summary
This summary boils the process into steps that might otherwise get lost during the execution, and is good for an overall check-list to keep track of where you are in the process.
First, make sure you meet all the prerequisites.
Since many prerequisites are common for both Skype for Business and Exchange, see the overview article for your pre-req checklist. Do this before you begin any of the steps in this article.
Collect the HMA-specific info you'll need in a file, or OneNote.
Turn ON Modern Authentication for EXO (if it is not already turned on).
Turn ON Modern Authentication for SFBO (if it is not already turned on).
Turn ON Hybrid Modern Authentication for Exchange on-premises.
Turn ON Hybrid Modern Authentication for Skype for Business on-premises.
Note These steps turn on MA for SFB, SFBO, EXCH, and EXO -- that is, all the products that can participate in a HMA configuration of SFB and SFBO (including dependencies on EXCH/EXO). In other words, if your users are homed in/have mailboxes created in any part of the Hybrid (EXO + SFBO, EXO + SFB, EXCH + SFBO, or EXCH + SFB), your finished product will look like this:
As you can see there are four different places to turn on MA! For the best user experience we recommend you turn on MA in all four of these locations. If you can't turn MA on in all these locations, adjust the steps so that you turn on MA only in the locations that are necessary for your environment.
See the Supportability topic for Skype for Business with MA for supported topologies.
Important Double-check that you've met all the prerequisites before you begin. You'll find that information here.
Collect all HMA-specific info you'll need
After you've double-checked that you meet the prerequisites to use Modern Authentication (see the note above), you should create a file to hold the info you'll need for configuring HMA in the steps ahead. Examples used in this article:
- Ex. contoso.com (is federated with Office 365)
- The GUID that represents your Office 365 tenant (at the login of contoso.onmicrosoft.com).
SFB 2015 CU5 Web Service URLs
You will need internal and external web service URL's for all SfB 2015 pools deployed. To obtain these, run the following from Skype for Business Management Shell:
Get-CsService -WebServer | Select-Object PoolFqdn, InternalFqdn, ExternalFqdn | FL
If you are using a Standard Edition server, the internal URL will be blank. In this case, use the pool fqdn for the internal URL.
Turn on Modern Authentication for EXO
Follow the instructions here: Exchange Online: How to enable your tenant for modern authentication.
Turn on Modern Authentication for SFBO
Follow the instructions here: Skype for Business Online: Enable your tenant for modern authentication.
Turn on Hybrid Modern Authentication for Exchange on-premises
Follow the instructions here: How to configure Exchange Server on-premises to use Hybrid Modern Authentication.
Turn on Hybrid Modern Authentication for Skype for Business on-premises
Add on-premises web service URLs as SPNs in Azure AD
Now you'll need to run commands to add the URLs (collected earlier) as Service Principals in SFBO.
Note Service principal names (SPNs) identify web services and associate them with a security principal (such as an account name or group) so that the service can act on the behalf of an authorized user. Clients authenticating to a server make use of information that's contained in SPNs.
First, connect to AAD with these instructions.
Run this command, on-premises, to get a list of SFB web service URLs.
Note that the AppPrincipalId begins with
00000004. This corresponds to Skype for Business Online.
Take note of (and screenshot for later comparison) the output of this command, which will include an SE and WS URL, but mostly consist of SPNs that begin with
Get-MsolServicePrincipal -AppPrincipalId 00000004-0000-0ff1-ce00-000000000000 | Select -ExpandProperty ServicePrincipalNames
If the internal or external SFB URLs from on-premises are missing (for example, https://lyncwebint01.contoso.com and https://lyncwebext01.contoso.com) we will need to add those specific records to this list.
Be sure to replace the example URLs , below, with your actual URLs in the Add commands!
$x= Get-MsolServicePrincipal -AppPrincipalId 00000004-0000-0ff1-ce00-000000000000 $x.ServicePrincipalnames.Add("https://lyncwebint01.contoso.com/") $x.ServicePrincipalnames.Add("https://lyncwebext01.contoso.com/") Set-MSOLServicePrincipal -AppPrincipalId 00000004-0000-0ff1-ce00-000000000000 -ServicePrincipalNames $x.ServicePrincipalNames
- Verify your new records were added by running the Get-MsolServicePrincipal command from step 2 again, and looking through the output. Compare the list / screenshot from before to the new list of SPNs (you may also screenshot the new list for your records). If you were successful, you will see the two new URLs in the list. Going by our example, the list of SPNs will now include the specific URLs https://lyncweb01.contoso.com and https://lyncwebext01.contoso.com/.
Create the EvoSTS Auth Server Object
Run the following command in the Skype for Business Management Shell.
New-CsOAuthServer -Identity evoSTS -MetadataURL https://login.windows.net/common/FederationMetadata/2007-06/FederationMetadata.xml -AcceptSecurityIdentifierInformation $true -Type AzureAD
Enable Hybrid Modern Authentication
This is the step that actually turns MA on. All the previous steps can be run ahead of time without changing the client authentication flow. When you are ready to change the authentication flow, run this command in the Skype for Business Management Shell.
Set-CsOAuthConfiguration -ClientAuthorizationOAuthServerIdentity evoSTS
Once you enable HMA, a client's next login will use the new auth flow. Note that just turning on HMA won't trigger a re-authentication for any client. The clients re-authenticate based on the lifetime of the auth tokens and/or certs they have.
To test that HMA is working after you've enabled it, sign out of a test SFB Windows client and be sure to click 'delete my credentials'. Sign in again. The client should now use the Modern Auth flow and your login will now include an Office 365 prompt for a 'Work or school' account, seen right before the client contacts the server and logs you in.
You should also check the 'Configuration Information' for Skype for Business Clients for an 'OAuth Authority'. To do this on your client computer, hold down the CTRL key at the same time you right-click the Skype for Business Icon in the Windows Notification tray. Click Configuration Information in the menu that appears. In the 'Skype for Business Configuration Information' window that will appear on the desktop, look for the following:
You should also hold down the CTRL key at the same time you right click the icon for the Outlook client (also in the Windows Notifications tray) and click 'Connection Status'. Look for the client's SMTP address against an Authn type of 'Bearer*', which represents the bearer token used in OAuth.
Do you need to know how to use Modern Authentication (ADAL) for your Skype for Business clients? We've got steps here.
Would you like to read these steps as they appear for Exchange Server, on-premises, running without SFB? Those steps are available here.