Home > Articles

Keys to the Design Process of SharePoint 2013's Underlying Technical Architecture

One of the first questions you should ask yourself when designing your SharePoint 2013 site is, “What are my organization’s compliance policies?” That question is typically not asked until later on in an initiative, but it should be at the forefront of your planning and architecture design from both a technical and business perspective. SharePoint expert Errin O’Connor shows you how to ensure your organization’s intellectual property, as well as the ability to adhere to regulations and laws such as PHI, PII, FISMA, and HIPAA. Factoring in compliance is a top requirement and an inherent capability of any architecture consideration for SharePoint 2013.
Like this article? We recommend

As a baseline, how do you currently protect sensitive and very important data that exists in your enterprise? It is important when developing compliance policies to actively look for ways to reduce any exposure risks that may exist. Depending on the size of your organization, you may have designated resources for litigation, eDiscovery, and maintaining your current “compliance status.” Small to mid-size businesses, though, will more than likely have resources that wear “many different hats,” and SharePoint Server 2013 will provide you with many industry-leading capabilities to manage compliance.

It is also important to ask questions of your organization, such as these:

  • How does your organization quickly find information?
  • How does your organization ensure policy consistency?
  • How does your organization scale the compliance solution to the enterprise?
  • What is the current strategy on cost control and information management or compliance?

As you consider the questions asked in the previous sections, also consider the following list of technical architecture design process points. This is a proven checklist of items that should be followed:

  • Business requirements of the organization
  • Functional requirements of the organization
  • User experience and devices from which SharePoint 2013/Office 365 will be accessed
  • Logical design
  • Boundaries of SharePoint 2013/Office 365
  • Information architecture design
  • Technical architecture
  • Define, iterate, and revise
  • Outcome
  • Server counts
  • Database design
  • Server roles
  • Storage requirements

Ensure That You Start with What You Currently Know

Ensure that this process first takes into consideration the items that have already been uncovered and are known to the project team. These items also take into consideration any roadblocks or lessons learned that you may have gained from previous IT initiatives within your organization.

The following is a list of items you should consider that you may already have a good deal of insight into:

  • Legal and compliance requirements
  • Constraints
  • Cost
  • Data center utilization goals
  • Evolving business needs
  • Risks
  • “Undersizing”
  • “Oversizing”
  • Unknown limits and workload patterns

Several factors influence an organization’s decision regarding which architecture (that is, on-premises private cloud, public cloud, or hybrid cloud) they are going to design and implement for their short-term and long-term SharePoint roadmap needs, such as these:

  • The overall size of the organization and user base
  • Security issues
  • Legal and compliance issues
  • Any project or deployment time constraints
  • Complexity of customers’ current environment
  • Physical locations
  • Current identity infrastructure
  • Current IT infrastructure model and future IT roadmap
  • Network bandwidth issues
  • Software/hardware issues
  • Any vendor service level agreement (SLA)
  • High-availability/backup issues
  • Internal resource issues and related training
  • Support alignment
  • Service reporting
  • Standards adoption and management
  • Development alignment
  • Infrastructure alignment
  • Development platform management
  • Governance
What Is a SharePoint “Private Cloud?”

What Is a SharePoint “Private Cloud?”

To first describe and baseline a private cloud deployment, you should first understand the elements that will typically be considered and implemented.

When you host SharePoint as an infrastructure for a specific workload or combination of workloads, you must consider the following factors:

  • Application platform for line-of-business (LOB) applications
  • Business intelligence implementations
  • Collaboration, community, and/or project sites
  • Internet/intranet publishing portal
  • Personal sites
  • Enterprise search
But Should I Prepare for a Hybrid SharePoint Platform?

But Should I Prepare for a Hybrid SharePoint Platform?

Obvious differences exist between SharePoint 2013 on-premises (private cloud) and hosted (public cloud), as well as a hybrid SharePoint 2013 deployment, which allows for a middle ground for you to tailor based on specific requirements, concerns, security requirements, and custom development strategies.

There is an inherent trade-off between complete control of your SharePoint environment and customization strategy and a managed service or SLA that you will adhere to for your environment.

As detailed in the preceding section, major considerations must be vetted by both the business and technology sides of the company and the review of content or intellectual property and even governing laws at a state, province, or country level. There are also considerations related to business intelligence and the organization’s requirements to connect to other LOB systems and how the cloud or hybrid cloud may affect or work with this other data and related permission strategies.

Nine key architectural areas should be considered within a SharePoint 2013 deployment:

  1. Deployment architecture
  2. Network architecture
  3. Infrastructure and server architecture
  4. Permission architecture
  5. Cloud architecture
  6. Software architecture
  7. Business architecture
  8. Data architecture
  9. Information architecture

A hybrid SharePoint 2013 environment enables your organization to be flexible and provide for the capability to store sensitive and highly confidential content on-premise within your own data center while storing collaboration or non-sensitive data within a public cloud such as Office 365, Microsoft Azure, or AWS. The issues that have continued to compile in the news with the NSA’s IT administrator Edward Snowden’s leakage of classified data has undoubtedly hurt the reputation of the public cloud. The NSA’s PRISM data mining program has also piled on concerns around organization’s asking itself, “How safe is the cloud?”

One of the largest impacts that EPC Group has seen around this issue has been with some clients or potential clients who have offices in the EU and whose executive management or IT leaders have absolutely refused to store data within cloud storage facilities based within the U.S. This is another key reason I believe that the hybrid cloud model will continue to take hold as it gives organization’s options around where specific types of data are stored while still giving them secure “identify management” options to access it in a seamless manner.

SharePoint 2013/Office 365 hybrid deployments also provide organizations with robust options for business intelligence (BI) initiatives, because the private side of the hybrid cloud will more than likely already exist on the company’s network in its Active Directory (AD) forest, which will allow BI initiatives to securely access other line-of-business (LOB) systems within the organization. Office 365’s Power BI capabilities also allow cloud-based data the analytical and robust reporting required which can be seamlessly federated via Azure Active Directory, a REST-based (REpresentational State Transfer) service that provides identity management, to your on-premises data to allow you to architect and tailor the security model that will work best for your organization.

One major concern of organizations in past releases of SharePoint was how some “Test” or “Development” environments that were not properly implemented, that were not backed up or under the organization’s disaster recovery strategy, or that duplicated the effort of the organization’s central SharePoint deployment quickly became a “Production”-like environment.

In SharePoint 2010, 2007, or 2003 implementations, there is concern about the risk that these types of environments (that is, Development environments that quickly became a SharePoint production environment with a great deal of content) can bring when they are not following the company’s overall IT strategy, SharePoint roadmap, and governance policies, and are causing additional effort, risk, and concern about document security.

At the very beginning of your organization’s SharePoint 2013 initiative, a company-wide SharePoint Governance and Communication strategy message must be established and communicated to all team members, both non-IT and IT, because an employee or team member who would like a place to store and access content without going through the proper channels can establish an unapproved SharePoint site by sending an email or placing a phone call to a very long list of hosting providers.

This user who may not know or understand the organization’s SharePoint roadmap and/or governance strategy could unknowingly be putting the organization at great risk in a number of areas. This team member may not understand the implications of storing data in an environment that he or she knows little or nothing about.

This is a key reason that preparing this strategy and a SharePoint hybrid-capable type of corporate communication message can be extremely valuable without ruling out possible hybrid needs of future projects, vendors, and so forth.

Understanding SharePoint 2013’s System Architecture

Understanding SharePoint 2013’s System Architecture

SharePoint implementations can be best approached by categorizing the underlying servers and hardware regardless of virtual versus physical, by categorizing the system architecture to cover these underlying components. The SharePoint system architecture roadmap components must be developed by the business and functional requirements of the information architecture, which contains the planning for sites, document libraries, and ultimately the content.

SharePoint 2013’s underlying system architecture must take into consideration the needs of the organization in terms of metrics such as these:

  • Number of SharePoint users as well as any possible future estimates if expansion is on the horizon
  • Amount of content to be stored by individual departments, business units, and users
  • Size of that content and considerations for large files such as CAD drawings or media files such as large videos
  • Performance requirements of these users, as well as their location
  • Number of data centers and their locations
  • Onsite deployment, cloud deployment, or hybrid (mixture of both onsite and cloud)
  • Immediate requirements of the business (that is, company intranet), as well as longer-term requirements (that is, business intelligence and analytical SharePoint service) that may require security around federation or other access needs
  • Disaster recovery strategies
  • Network security, Active Directory, performance, acceleration needs, and so on
  • Development environment and related Visual Studio/Team Foundation Server (TFS) strategy

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020