System architecture and integration
Running Head: MIGRATING TO OFFICE 365 1
MIGRATING TO OFFICE 365 20
Migrating to Office 365
Riaad Kamaludeen
ITCO425
Date: 11/13/18
Table of Contents Project Information 3 Description of Enterprise 3 Overall Project Objectives 3 Business and Technical Needs 3 Major Components 3 Boundaries of Project 4 Project Plan 4 Work Breakdown Structure (WBS) 4 System Integration Best Practices 7 RFP Process 7 Requirements Specifications 8 Requirements 8 Stakeholders 8 Layers of integration 10 Functional requirements 11 Non-Functional requirements 11 Assumptions 12 Pros and cons of proceeding with the project 12 Enterprise System Integration Analysis 13 List of quality assurance considerations 13 Three (3) potential options 14 Systems Integration Approach Evaluation and Selection 15 Criteria Matrix 15 Matrix Table 16 Option A 16 Proposed System Integration Components Architecture 16 Implementation Framework 16 System Integration Implementation Plan 17 References 17
Project Information
Description of Enterprise AIM is a non-profit organization providing residential and community-based services to people with disabilities, including those with traumatic brain injuries and those who are looking for a nursing home transition or diversion. It offers services in Saratoga, Warren, and Washington County. Our Self Direction program provides services in additional areas; Capital District, Long Island, Taconic, Hudson, and Sunmount regions. Moreover, it provides services through the New York State Office of People with Developmental Disabilities (OPWDD) and the New York State Department of Health (DOH) (Inc., 2018).
Overall Project Objectives
Migrate AIM Services Inc. from Exchange 2013 to Office 365 cloud service by May 11th, 2019.
Business and Technical Needs
· Access from anywhere
· Reduce losing email data
· Decrease procurement of new license for Microsoft Office suite
· Backup and decommission Exchange 2013
Major Components
· Setup Office 365
· Migrate users’ mailbox, calendar, and rules
· Skype for Business
· SharePoint
· Email security (encryption)
· Setup anti-spam and anti-malware filtering options
· Setup a secure channel to and from Outlook 365 (TLS)
Boundaries of Project
The project will not address traveling, installing Office 2016 suit to clients’ workstations, laptops, and mobile device. Moreover, there will be a flexible budget allocated to help with any additional and unexpected cost incurred during the migration to assist with project completion.
Project Plan
Work Breakdown Structure (WBS)
Figure 1. Showing a detailed Work Breakdown Structure (WBS)
|
Task Name |
Duration |
Start |
Finish |
Resource Names |
|
|
|
|
|
|
|
DESIGN, PLAN |
115 days |
10/9/2018 |
2/10/2019 |
|
|
Hold project kickoff meeting |
1 day |
10/9/2018 |
10/9/2018 |
PM, MT, STKH, SEC, QA |
|
Document all namespaces and domain names moving forward - UPN, SIP domain |
3 days |
10/10/2018 |
10/13/2018 |
PM, MT, SEC, SNA |
|
Plan DNS entries for O365 |
7 days |
10/14/2018 |
10/21/2018 |
PM, MT, SEC, SNA |
|
Plan DNS entries for Exchange- Autodiscover, Outlook Anywhere |
7 days |
10/22/2018 |
10/29/2018 |
PM, MT, SEC, SNA |
|
Document all DNS entries and URL's |
2 days |
10/30/2018 |
10/31/2018 |
PM, MT, SEC, SNA |
|
Identify mailbox size and item counts |
1 day |
11/1/2018 |
11/1/2018 |
PM, MT, SEC, SNA |
|
Plan for mail-enabled applications |
1 day |
11/2/2018 |
11/2/2018 |
PM, MT, SEC, SNA |
|
Plan & Document for user identity and account provisioning |
10 days |
11/3/2018 |
11/13/2018 |
PM, MT, SEC, SNA |
|
Identify Active Directory preparation and remediation requirements |
5 days |
11/14/2018 |
11/19/2018 |
PM, MT, SEC, SNA |
|
Identify current network links, user concentration, and current utilization |
10 days |
11/20/2018 |
11/30/2018 |
PM, MT, SEC, SNA |
|
Identify versions of Exchange infrastructure and service packs |
1 day |
12/1/2018 |
12/1/2018 |
PM, MT, SEC, SNA |
|
Identify on-premises infrastructure server requirements for O365 compatibility |
3 days |
12/2/2018 |
12/5/2018 |
PM, MT, SEC, SNA |
|
Identify the operating systems and client applications |
1 day |
12/6/2018 |
12/6/2018 |
PM, MT, SEC, SNA |
|
Identify the mobile platform that the organization will use |
1 day |
12/7/2018 |
12/7/2018 |
PM, MT, SEC, SNA |
|
Develop an end user and administrator training schedule and delivery mechanism |
21 days |
12/8/2018 |
12/29/2018 |
PM, MT, SEC, SNA |
|
Schedule Local IT /end user training |
15 days |
12/30/2018 |
1/13/2019 |
PM, SEC, SNA |
|
Define user migrations in batches and document managers and administrators |
15 days |
1/14/2019 |
1/29/2019 |
PM, MT, SEC, SNA |
|
Develop end-user communications strategy |
10 days |
1/30/2019 |
2/8/2019 |
PM |
|
Executive Agenda Overview - handled by Pgm Mgr and Sponsors |
1 day |
2/9/2019 |
2/9/2019 |
PM, STKH |
|
Communicate plans to the team and get sign off from the sponsors - handled with deliverables |
1 day |
2/10/2019 |
2/10/2019 |
PM |
|
|
|
|
|
|
|
CONFIGURE |
54 days |
2/11/2019 |
3/29/2019 |
|
|
Identify desktop OS versions and service packs |
5 days |
2/11/2019 |
2/15/2019 |
MT, SEC, SNA |
|
Define temporary migration domain & create MX records for routing |
3 days |
2/16/2019 |
2/18/2019 |
MT, SEC, SNA |
|
Add O365 licenses |
3 days |
2/19/2019 |
2/21/2019 |
MT, SEC, SNA |
|
Add Global O365 admins |
1 day |
2/22/2019 |
2/22/2019 |
MT, SEC, SNA |
|
Add hosted domains in Office 365 |
1 day |
2/23/2019 |
2/23/2019 |
MT, SEC, SNA |
|
Verify O365 hosted domains |
1 day |
2/24/2019 |
2/24/2019 |
MT, SEC, SNA |
|
Analyze AD objects for issues |
5 days |
2/25/2019 |
3/1/2019 |
MT, SEC, SNA |
|
Clean up AD user objects - unsupported length and characters |
5 days |
3/2/2019 |
3/6/2019 |
MT, SEC, SNA |
|
Update all users with correct UPN - part of cleanup activities |
5 days |
3/7/2019 |
3/12/2019 |
MT, SEC, SNA |
|
Setup O365 Exchange Online/Skype Online |
1 day |
3/13/2019 |
3/13/2019 |
MT, SEC, SNA |
|
Skype SIP domain - define valid SIP domains based on logon UPN |
1 day |
3/14/2019 |
3/14/2019 |
MT, SEC, SNA |
|
Client connectivity firewall port changes from Internal to O365 |
2 days |
3/15/2019 |
3/16/2019 |
MT, SEC, SNA |
|
Infrastructure firewall port changes from internal & DMZ to O365 |
2 days |
3/17/2019 |
3/18/2019 |
MT, SEC, SNA |
|
Configure Azure AD |
3 days |
3/19/2019 |
3/21/2019 |
MT, SEC, SNA |
|
Prepare the on-premises Active Directory for directory synchronization to Azure |
5 days |
3/22/2019 |
3/27/2019 |
MT, SEC, SNA |
|
Install the Directory Synchronization Tool and perform synchronization |
5 days |
3/28/2019 |
3/21/2019 |
MT, SEC, SNA |
|
Validate Dir Sync |
1 day |
3/24/2019 |
3/24/2019 |
MT, SEC, SNA |
|
Resolve open DirSync issues |
2 days |
3/25/2019 |
3/26/2019 |
MT, SEC, SNA |
|
Configure O365 Exchange - Connectors, mail flow, mobile |
3 days |
3/27/2019 |
3/29/2019 |
MT, SEC, SNA |
|
Testing Outlook, F/B and Mail Flow |
9 days |
3/30/2019 |
4/7/2019 |
MT, SEC, SNA |
|
Test Outlook Auto discover with existing config |
2 days |
3/30/2019 |
3/31/2019 |
MT, SEC, SNA |
|
Test Outlook Anywhere with existing config |
2 days |
4/1/2019 |
4/2/2019 |
MT, SEC, SNA |
|
Configure of Outlook Anywhere/Auto discover if necessary |
2 days |
4/3/2019 |
4/4/2019 |
MT, SEC, SNA |
|
Test mail flow |
3 days |
4/5/2019 |
4/7/2019 |
MT, SEC, SNA |
|
Testing Admin and Functional |
8 days |
4/8/2019 |
4/16/2019 |
MT, SEC, SNA |
|
Create administrative and functional test scripts |
2 days |
4/8/2019 |
4/9/2019 |
MT, SEC, SNA |
|
Validate administrative and functional test scripts |
2 days |
4/10/2019 |
4/11/2019 |
MT, SEC, SNA |
|
Test and validate email migration and coexistence |
3 days |
4/12/2019 |
4/14/2019 |
MT, SEC, SNA |
|
Configure Skype and enable all users with SIP URI |
1 day |
4/15/2019 |
4/15/2019 |
MT, SEC, SNA |
|
Deploy client applications and the Office 365 desktop setup globally to all end users |
12 days |
4/17/2019 |
4/29/2019 |
MT, SEC, SNA |
|
Software deployment |
4 days |
4/17/2019 |
4/20/2019 |
MT, SEC, SNA |
|
Move users from Exchange to O365 in batches |
30 days |
4/2/2019 |
4/30/2019 |
MT, SEC, SNA |
|
Communicate Development completed tasks to team and sponsors - Covered in meetings |
1 day |
4/2/2019 |
4/3/2019 |
PM |
|
IMPLEMENTATION, MIGRATION |
39 days |
4/2/2019 |
5/11/2019 |
|
|
Send out initial communications to users with dates - four weeks, two week, one week |
|
|
|
|
|
Reminder migration date and Instructions on first use sent to users |
28 days |
4/2/2019 |
4/30/2019 |
PM, MT, SEC, SNA |
|
Cut Over |
|
|
|
|
|
Perform final mailbox sync, make DNS record changes, internal and external points, etc. (Night Before Migration) |
1 days |
5/1/2019 |
5/1/2019 |
PM ,MT, SEC, SNA |
|
GPO Setting to change user mailbox, configure to point to Office 365, users walkthrough, Preform QA |
3 days |
5/2/2019 |
5/5/2019 |
PM, MT, SEC, SNA, QA |
|
Project Close |
5 days |
5/6/2019 |
5/11/2019 |
PM, STKH |
Notes:
Project Manager (PM): Riaad Kamaludeen
Migration Team (MT): Kevin Calvin, Andre Williams, Brain Hass, John Williams
Stakeholders (STKH): June Friday, Chis Irwin
Security Engineer (SEC): Adam West
Quality Assurance Testers (QA): Dave Hall
System/Network Administrator (SNA): Tommy Taylor
System Integration Best Practices
RFP Process
Using request for proposal (RFP) process will help the company to outsource qualified and experienced professional who deals with Office 365 migration on a daily basis. It will avoid downtime and ease the process of migration from Exchange 2013 to Office 365. As shown in figure 2, it first goes about planning the project which includes requirement, scope, budget and so forth. After which the RFP process moves to the drafting and issuing stages and completes when AIM Services Inc. reviews the proposals and award the contract to the best-suited vendor. In summary, a request for proposal (RFP) is a document that describes what AIM Services Inc. needs are and asks for a proposed solution from qualified vendors to complete the migration from Exchange 2013 to Office 365 (Ferriere, 2017).
Figure 2. showing RFP process workflow.
Requirements Specifications
Requirements
Before implementing Office 365 to AIM Services Inc. infrastructure, it is essential that requirements gathering is conducted because it is used to capture the request of the project. By eliciting the requirements, it leads to a fruitful completion and outcome of the project. A few methods for gathering the requirement for the said project includes interviews and questionnaires. Interviews – this is one of the most commonly used methods of eliciting requirements, However, for this project, it goes about first, by conducting an unstructured interview with the CEO, IT Director, and Administrator to get an understanding of the work environment and problems. After an unstructured interview, the next step is a structured interview which involves questions design for technical personnel like the IT Director, and Administrator to gather technical information about the existing Exchange server like mailbox sizes and amount, DNS information, server information, software change or upgrades and so forth. Questionnaires – This is useful for AIM Services Inc. because it gathers information from all employees about their technical knowledge and how familiar are they with Office 365 and Microsoft Outlook.
Stakeholders Figure 3. showing stakeholders.
|
Stakeholder |
Role/Responsibilities |
|
Executive sponsor |
· Encourage Office 365 usage and emphasize that it is supported for the organization · Articulate value proposition across the executive team · Serve as a role model in the community · Participate in a network engagement event to help launch an effort
|
|
Project Manager |
· Define project scope, goals, timeline and milestones, and review with other stakeholders · Assign responsibilities to rollout team and clearly communicate expectations · Ensure coordination of launch, communications, training, and end- user engagement activities · Coach, mentor, motivate, and supervise project team members and resolve rollout issues/conflicts
|
|
System/Network Administrator |
· Technically onboard the organization to Office 365 · Identify and involve all required IT personnel · Work with the project manager on integration timing/logistics · Communicate any technical issues or queries
|
|
Migration Team |
· Implement Office 365 · Decommission Exchange Server · Backup Exchange Server · Communicate technical issues with Project Manager or Administrator · Provide technical support on the day of cutover |
|
Security Engineer |
· Implement security standards for Office 365 · Implement Security tunnels · Monitoring and verify the security posture of Office 365 implementation
|
|
Quality Assurance Testers |
· Define Pass/Fail criteria · Define milestones and success criteria’s · Identify roles and responsibilities · Outline risks, assumptions, and constraints, if any · Define test cases
|
Layers of integration
In this project, a three-tier architecture designed is used to show how Office 365 can be embedded into AIM Services Inc. infrastructure. The three-tier architecture design, consist of a presentation tier, application tier and a data tier. Firstly, the presentation tier is the front end layer which consists of the user interface that is accessible via a web browser or a web-based application that display the content and information to end users. It also involves user devices like laptops, tablets, and smartphones. As shown in figure 3. below, the front end user interface is Office 365 Portal which gives access to Office 365 cloud services through multiple end-user devices that supports strong security standards (JReport, 2018). Secondly, the application tier is where all information is passed between tiers and is where most of the configurations, computing, and customizations are done. However, this project does not use an in-house custom built application but uses computing resources and applications that are housed by the cloud vendor (Microsoft). The applications include Word, Excel, PowerPoint, SharePoint, Teams, Azure AD Connect, DirSync to name a few (JReport, 2018). Thirdly, the Data tier is comprised of one or more databases, bid data sources, or another type of database system hosted in the cloud for end users to access and retrieve information and content. It also provides reporting and analytical information for users’ mailboxes and so forth (JReport, 2018).
Figure 3. showing an infrastructure design for Office 365 implementation.
Functional requirements: These are business needs that Office 365 needs to satisfy (Eriksson, 2012). Some of these requirements includes:
· Security to keep company data safe (Certificates, TLS).
· On-premise and Cloud email access.
· Office 365 services like teams, SharePoint, Skype for Business.
· Manage and maintain mailboxes online using Office 365 portal.
Non-Functional requirements: A non-functional requirement which is also known as technical requirements is technological considerations that are already existing or compatible with technology already in AIM Services Inc. (Eriksson, 2012). Some of these requirement includes:
· Microsoft Office 2016 Suite
· Redundant WAN Links
· Email encryption
· Email Filtering
· Usability
· Availability
· Reliability
Assumptions
· The schedule is adhered to. This includes vendor selection, tasks, and subtasks (Espy, 2018).
· Project teams will follow team governance guidelines and requirements (Espy, 2018).
· Flexible budget for an unexpected cost (Espy, 2018).
· The scope of the project will not change once signed off (Espy, 2018).
Pros and cons of proceeding with the project
Cloud services from Microsoft such as Office 365 offer many advantages to AIM Services Inc. Some of these advantages include Teams and SharePoint which give employees the ability to collaborate and be more productive, cloud and on-premise email access from any device with internet access, management and reporting, and more importantly free licenses for a non-profit agency. Nevertheless, as with all technology, there are disadvantages. Office 365 is no exception if the internet is down then the services are down, and this can have a significant impact on the business. However, implementing a secondly WAN link can mitigate the risk. Another disadvantage is AIM Services Inc., or any company that chooses to implement Office 365 should get or already have an anti-spam filtering solution because Office 365 anti-spam solution is not robust as a solution design for that purpose. For example, Barracuda anti-spam appliance.
Enterprise System Integration Analysis
List of quality assurance considerations
· Performance, load, and stress testing - Performance testing is how the system behaves under an increased load. For example, increase user and resource utilization. Loading testing is verifying that application operates at a defined response time when the application is subjected to an extreme load, and stress testing is finding points of failure for the application under unfavorable conditions/load (Inflectra, 2018).
· Security, vulnerability testing – Previously security was done after the implementation of software, but in today’s technological advances and the rise of cybercrimes testing is done at the same time of development and implementation. Security testing test the software for confidentiality, integrity, authentication, and availability. Testing is also done to prevent authorized access to resources and application vulnerabilities.
· Usability testing – takes a look at the end user usability aspect of the software it focusses on learnability, efficiency, satisfaction, memorability, and errors (Inflectra, 2018).
· Compatibility Testing – Testing the software or product to check if it is compatible with the operating systems, hardware, web-browsers, and mobile devices. This ensures the application works across all the different hardware /software and that all the functionality is consistent across devices.
· Acceptance testing – Making sure all the project requirements are met, and end users have tested the system to ensures it operates as expected (Inflectra, 2018).
Three (3) potential options
Cloud Solution
Cloud Computing or often referred to as “The Cloud” which is a metaphor for the internet. It is the delivery of computing services like storage, Servers, networking, software, and databases to name a few all over the internet, to offer innovation, and flexible resources to companies. However, application like Microsoft Exchange can be challenging, time-consuming, and costly for many organizations to support as such cloud services like Office 365 was born to alleviate the problems of licensing, deployment, and maintenance of Exchange. Office 365 provides many features for businesses to enjoy, primarily Exchange Online which dramatically reduces the capital expenditure on licenses, support, and maintenance. Moreover, each user mailbox is 25GB of storage and is accessed from anywhere dependent on the internet connection. Also, Office 365 can be used on many devices like tablets, smartphones and so forth, it is reliable with 99.9% uptime, secure, and for a non-profit agency its free (Bigelow, 2018).
On-Premise Solution
Microsoft Exchange Server hosted onsite has many advantages to the company especially control, data security and privacy which when moving data to a public cloud vendor like Microsoft companies are usually skeptical because of potential implication of data privacy and so forth. However, with Exchange on-premise it increases capital expenditure on licenses, maintenance of Servers, and many more. It requires administrators to manage and update servers, manage backups, troubleshoot and fix issues, security implementations and vulnerability testing, and disaster recovery to ensure the operation of Exchange goes smoothly (Venter, 2017).
Hybrid Solution
Like the name, it is a hybrid deployment which offers organizations the ability to extend the feature-rich experience and administrative control they have with their existing on-premises Microsoft Exchange organization to the cloud. A hybrid deployment provides the seamless look and feel of a single Exchange organization between an on-premises Exchange organization and Exchange Online in Microsoft Office 365. Besides, a hybrid deployment can serve as an intermediate step to moving entirely to an Exchange Online organization (Venter, 2017).
Systems Integration Approach Evaluation and Selection
Criteria Matrix
A criteria matrix or decision matrix is a chart that is used to assess, and rank options based on a specific criterion. It is also especially useful for assessing each relative factor importance. Moreover, it is used to evaluate the alternative solution to problems. By using this chart, it treats the criteria independently helping avoid the over influence or emphasis on a specific individual criterion (Lucid, 2018). The Matrix itself is constructed with options listed along one side and the review criteria along the other. Then a box is inserted the assigned weight along each criterion. The total is then calculated and used in ranking or to determine the best option.
Matrix Table
Figure 4. showing a criteria matrix table.
|
Objective |
Weight (0.0 – 5.0) |
OPTION A Cloud |
OPTION B Hybrid |
OPTION C On-premise |
|||
|
|
|
Score (0,1,2,3) |
Weighted Score (W×S) |
Score (0,1,2,3) |
Weighted Score (W×S) |
Score (0,1,2,3) |
Weighted Score (W×S) |
|
Robust Security anti-spam and anti-malware filtering |
5 |
2 |
10 |
3 |
15 |
3 |
15 |
|
Future proof Exchange |
5 |
3 |
15 |
2 |
10 |
1 |
5 |
|
Skype for business, SharePoint and Teams |
5 |
3 |
15 |
2 |
10 |
1 |
5 |
|
Email Security |
5 |
3 |
15 |
3 |
15 |
2 |
10 |
|
Access from anywhere |
5 |
3 |
15 |
2 |
10 |
1 |
5 |
|
Redundancy and Backup |
4 |
3 |
12 |
2 |
10 |
1 |
5 |
|
Maintenance and Licenses |
4 |
3 |
12 |
2 |
10 |
1 |
5 |
|
Total |
94 |
80 |
50 |
Option A
By analyzing the matrix chart provided above, it can be determined that option A is the best suited for the system integration project and it meets the requirements of the project in question. The reasons include robust security features, access to SharePoint, Skype for Business and Teams, provides redundancy and backups automatically, maintenance and license free and most importantly its future proof. Moreover, using the cloud makes it easier for employees to access their emails via multiple devices and from anywhere. Also, employees can download the latest version of Microsoft Office products without the need to purchase new licenses when newer editions are out.
Proposed System Integration Components Architecture
Description of software architecture
Using the software architecture design shown in figure 5. shows how Office 365 and other cloud related services offered by Microsoft can be integrated into AIM Services Inc. this three (3) tier design consist of a presentation, business logic, and data layer. Although there are more complex and details architectural designed for a cloud-based system.
Firstly, the presentation layer is the front-end layer which consists of the user interface that is accessible via a web browser or a web-based application that display the content and information to end users. It also involves user devices like laptops, tablets, and smartphones. As shown in figure 3. below, the front-end user interface is Office 365 Portal which gives access to Office 365 cloud services through multiple end-user devices that supports strong security standards (JReport, 2018). Secondly, the business logic layer is where all information is passed between layers and is where most of the configurations, computing, and customizations are done. However, this project does not use an in-house custom-built application but uses computing resources and applications that are housed by the cloud vendor (Microsoft). The applications include Office 365 application suite, SharePoint, DirSync, and Skype for business (JReport, 2018). These SaaS applications is accessible to license users and is accessible when users sign in using their front-end devices. SharePoint is a document management and collaboration tool developed by Microsoft, while skype for business, office 365, DirSync and many other are also services provided by Microsoft and can be accessible with the proper licenses. Thirdly, the Data layer is comprised of one or more databases, bid data sources, or another type of database system hosted in the cloud for end users to access and retrieve information and content. It also provides reporting and analytical information for users’ mailboxes and so forth (JReport, 2018).
Lastly, security, encryption and email filtering are security mechanisms designed to enforce stick standards on protecting company data and its integrity.
Software architecture
Figure 5. showing a software architecture of office 365.
Components
When integrating a cloud solution into a network no hardware cost is incurred providing that the cloud solution is cloud based and not a hybrid solution. Software is provided as a services to customers and requires cost for licenses. The cloud services provided by Microsoft allows administrators to easily integrate the system with not much overhead and cost attached for equipment such as servers, COTS, switches, firewall and so forth.
Implementation Framework
TBD
System Integration Implementation Plan
TBD
References Bigelow, S. J. (2018, November 12). Microsoft Exchange Online explained. Retrieved from https://searchwindowsserver.techtarget.com/feature/Microsoft-Exchange-Online-explained Eriksson, U. (2012, April 5). Functional vs Non Functional Requirements. Retrieved from https://reqtest.com/requirements-blog/functional-vs-non-functional-requirements/ Espy, L. (2018, February 21). How to Create a Project Assumptions List: Examples and Template Included. Retrieved from https://projectbliss.net/project-assumptions-list/ Ferriere, T. (2017, August 28). RFP: Everything You Need to Know About the RFP Process. Retrieved from https://tenderspage.com/everything-need-know-rfp-process/ Inc., A. S. (2018, October 26). About Us. Retrieved from https://www.aimservicesinc.org/about-us/ JReport. (2018, November 06). 3-Tier Architecture: A Complete Overview. Retrieved from https://www.jinfonet.com/resources/bi-defined/3-tier-architecture-complete-overview/ Lucid. (2018, November 9). Criteria Matrix. Retrieved from https://www.lucidmeetings.com/glossary/criteria-matrix Venter, J. (2017, March 17). Exchange: On-Premises vs Exchange Online. Retrieved from http://www.firstforcloud.com/exchange-on-premises-vs-exchange-online/