Deployment scenarios for Office 365 with single sign-on and Azure

 

Applies to: Office 365

Topic Last Modified: 2015-04-27

Summary: Introduces Office 365 deployment scenarios that use single sign-on and Azure Virtual Machines.

We're listening to your feedback and consolidating all our Office 365 deployment content. On July 1st, 2015, all information in this guide will be moved to https://support.office.com/, and these pages will be removed from TechNet. As you review the content still on TechNet, you'll notice many have links pointing to the new content already on https://support.office.com/.

To explore content available on https://support.office.com/, start with the Office 365 for business - Admin Help page.

When you deploy all the Office 365 federation components on Azure Virtual Machines, you get some advantages over an on-premises deployment. These advantages include rapid implementation, predictable costs, and no additional on-premises servers being required. Alternatively, you can host a subset of the federation components in Azure while deploying some components on-premises.

Although additional options are possible, there are three optimal deployment scenarios:

  • Scenario 1: All Office 365 SSO integration components deployed on-premises. This is the traditional approach; you deploy directory synchronization and Active Directory Federation Services (AD FS) by using on-premises servers.

  • Scenario 2: All Office 365 SSO integration components deployed in Azure. This is the new, cloud-only approach; you deploy directory synchronization and AD FS in Azure. This eliminates the need to deploy on-premises servers.

  • Scenario 3: Some Office 365 SSO integration components deployed in Azure for disaster recovery. This is the mix of on-premises and cloud-deployed components; you deploy directory synchronization and AD FS, primarily on-premises and add redundant components in Azure for disaster recovery.

 
Show: