Office 365, the cloud-based version of the ubiquitous enterprise enablement apps is often misunderstood as a single use case with a single form of implementation. However, a variety of factors result influence this use case, resulting in four primary deployment models. Today’s post reviews the available deployment models and highlights the variables to help you determine how to implement Office 365.
Introduction to Office 365
Office 365 is an offering from Microsoft’s comprehensive cloud-based stack, the Azure platform.
The move from an on-premise infrastructure to the cloud provides the following benefits:
Office 365 is Microsoft’s cloud approach to content collaboration and email services. It provides a complete office experience…completely in the cloud! Available services include:
Office 365 Deployment Models
Even though companies use most of the same Office 365 services, every use case is unique. This leads to four typical deployment models for O365.
Azure AD Pure Cloud
- Master User Location – Azure Active Directory
- User Credentials – Azure Cloud user credentials
- Functionality – Delivers available Azure functionality
Azure AD Connect
- Master User Location – On-Premises Active Directory
- User Credentials – Password hash sync for user credentials
- Functionality – Delivers available Azure functionality
Azure AD Federation
- Master User Location – On-Premises Active Directory
- User Credentials – On-Premises user credentials
- Functionality – Delivers most Azure functionality
Pass-through Authentication
- Master User Location – On-Premises Active Directory
- User Credentials – On-Premises user credentials
- Functionality – Delivers most Azure functionality
Office 365 Deployment Model Components
The post Office 365 Deployment Models appeared first on VMware End-User Computing Blog.