The team at EPC Group approaches the architecture and design of SharePoint 2013 and/or Office 365’s Information Architecture using a the three-prong approach that provides placeholders for the requirements that must be documented but also sets expectations for the SharePoint project team to design an IA that is scalable and has organization’s long-term SharePoint roadmap in mind
Ensuring Your System & Information Archiecture Architecture Strategy Aligns with Your SharePoint Roadmap When an organization is near the point of kicking off and performing a upgrade and/or migration initative to SharePoint 2013 and/or Office 365 , it is key to ensure core elements have been designed and put in place to meet not only the current needs of the organization over the next 12 months but for at least the next 24-36 months via a SharePoint roadmap
Understanding the Underlying System Architecture Behind My Sites & Communities in Office 365 & SharePoint 2013 When an organization’s deploys My Sites for their users, the underlying SharePoint 2013 system architecture create a web application, a My Site host site collection, an individual site collection, and several SharePoint service applications and features. Note: The Office 365 | SharePoint Online architecture does differ from that of an on-premise SharePoint 2013 deployment but I have covered the major topical areas for both below
Key Cloud Terms You will hear many different technical references within an Office 365 architectural or business planning conversation, so it is key to understand the core terms as detailed in the sections that follow
Storage Design of SharePoint 2013 and Hybrid Office 365 Environments When looking at storage in terms of the actual system architecture design perspective , the following initial items should start this conversation: • How has storage been allocated for this effort or what may be available for this initiative?
This post is meant to provide you with a visual overview of the underlying scalability considerations and related best practices for a Hybrid SharePoint 2013 and Office 365 Environment . SharePoint Farm Resource Hierarchy SharePoint 2013 | Hybrid Office 365 Web App Resource Hierarchy Deployment Impact Examples - IIS Reset (EPC Group Example) Deployment Impact Examples- App Pool Reset (EPC Group Example) Maintenance Windows (Backup, code promotion, etc.) Understanding Isolation Modes in SharePoint 2013 & Office 365 Hybrid Deployments In SharePoint 2013: Each “customer” = one site collection under managed path Similar to today Each Web Application = one app pool Similar to today Each Web Application = one URL Similar to today Exception Process for Host Header named site collections (vanity URL’s) Along Side or in an Office 365 Hybrid Deployment: BYO Servers Leverage existing architecture Hybrid Considerations (Seamless SharePoint 2013 On-Prem \ Office 365 Cloud Search Integration) Scaling Web Front-ends and Understanding When to Scale App Scale and Tipping Points EPC Group’s Nationally Recognized Practice Areas EPC Group leading SharePoint , Office 365 , Infrastructure Design and Business Intelligence Practice areas continue to lead the way in providing our clients with the most up-to-date and relevant information that is tailored to their individual business and functional needs. Additional "From the Consulting Trenches" strategies and methodologies are covered in EPC Group's new book, " SharePoint 2013 Field Guide: Advice from the Consulting Trenches" covering not only SharePoint 2013, Office 365 and SharePoint Online but Information Management, ECM\RM and overall compliance strategies in this ever changing world of " Hybrid IT
Hybrid Search Deep-dive: SharePoint Server 2013 & Office 365 Integration One of the most common configurations that is starting to emerge into today’s IT landscape is that of a hybrid cloud architecture and is something you must plan for in your organization's long-term SharePoint and/or Office 365 roadmap
Security Governance Best Practices for SharePoint 2013 & Office 365 | SharePoint Online EPC Group understands that security has never been a hotter topic in IT, but in most cases, even though it is being discussed by members of the organization and dominates a good deal of technology news coverage, it is still often not properly addressed in many SharePoint deployments. In many SharePoint deployments, the organization’s Active Directory (AD) deployment may have a good deal of duplication, custom groups, or old and expired information that have been created and stored over many years. Implementing a best practices SharePoint security strategy requires in-depth planning and knowledge of the overall information architecture (IA) design as well as an understanding and awareness of the capabilities available
Security & Identity Management "From the Consulting Trenches" There are a number of security, identity management and authentication considerations when developing custom applications and related features in SharePoint 2013, Office 365, SharePoint Online and Microsoft Azure. You should always keep in mind SharePoint 2013’s “claims first” authentication architecture during your development as well as in discussions with the business about their custom requirements
Workflow Development "From the Consulting Trenches" There has been a complete update to SharePoint 2013 ’s workflow capabilities and overall workflow architecture, as shown in image below, with new features as well as the underlying workflow engine itself receiving a major overhaul. In this post, EPC Group's SharePoint and Office 365 hybrid development team will walk you through new best practices and strategies regarding workflow development
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Fax: (301) 587-2711Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use