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 . SharePoint Server 2013 can integrate with cloud-based solutions such as Office 365 and/or SharePoint Online in a secure and federated manner that will allow a user with proper permission’s search to return results from both on-premises in SharePoint Server 2013 as well as in Office 365 in the cloud, as shown in image below. Hybrid Cloud (Hybrid SharePoint 2013 & Office 365) Architecture Summary Overview The following is a summary of a hybrid SharePoint Server 2013 and Office 365 search integration and the related components: The remote SharePoint Index allows for the search to be federated between the on-premises SharePoint Server 2013 environment and the cloud-based Office 365 environment for a hybrid cloud environment architecture This sample configuration provides query capability and additional configurations can be implemented to support crawl Hybrid Cloud Architecture Overview The hybrid cloud architecture requires: Configuration of an OAuth trust between your on-premises SharePoint 2013 farm and your Office 365 tenancy The creation of a result source for the remote farm An externally addressable endpoint for the on-premises farm (reverse proxy) that can be reached via the Office 365 sites This sample configuration allow you to query the result source directly or create a query rule to also allow for user queries to the cloud-based Office 365 or remote farm when needed A token is created for the user and security trimmed results are returned which requires 2-way AD synchronization between the SharePoint Server 2013 on-premises environment and Office 365 By using a query rule you can integrate the results from both farms into a single display for users and tailor the UI as desired The results of a hybrid cloud search from a user searching both SharePoint Server 2013 and Office 365 : Search Web Parts in SharePoint 2013, Office 365 and/or SharePoint Online There are several new web parts for Search in this latest release of SharePoint that allow users an entire new experience when conducting search
Office 365 Hybrid - A Deep-dive from EPC Group The project stakeholders within IT may have a total understanding of the Office 365 offering but the organization’s legal and compliance stakeholders may still be unclear or hesitant because of the similar naming of products and their past understanding of SharePoint
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
Understanding On-Premises, Cloud, and Hybrid Environments in SharePoint 2013 & Office 365 The on-premises versus cloud environment debate about SharePoint started several years ago
Understanding Operating in the Hybrid Cloud - EPC Group Case Study This blog post will provide "from the consulting trenches" ( Hybrid Cloud ) strategies and granular details of EPC Group’s approach to the new Hybrid Office 365 and/or SharePoint 2013 architecture's growing proliferation and how it may affect your organization. New Hybrid (Office 365) Governance Fundamentals Users that Ignore Governance and Planning for the Real World If it’s easy to get around it, they will: To ensure it will happen, enforce it transparently If it’s to complex, it won’t happen Strike a balance between: Note: Always consider compliance around HIPAA, PHI, and PII related data in Office 365 and/or SharePoint 2013. EPC Group’s Hybrid Governance Framework Step 1 – Understand what to Enforce Step 2 – Balance the enforcement Step 3 – How and where to enforce Step 4 – Prioritize the enforcement solutions Step 5 – Continue to Review and Enforce When and What to Enforce - EPC Group Framework Governance Feature Enforce Nothing Enforce Something Enforce Everything PII Policy Document (‘here’s our policy on exposing PII’) Monthly Audit (manual or physical ; random or comprehensive) Automated Audit on Upload Site Quota No Quotas or Suggested Quotas Tiered Options; business rules Chargeback model Site Creation Training on Where it Goes IT creates for you Fully automated with workflow Site Expiration At owner discretion Manual email sent to site owners asking
Development Tools and Related Strategies for Public, Private, and Hybrid Environments There have been many improvements as well as options added to Visual Studio 2013 to address the new technology releases of SharePoint 2013 , Office 365 , SharePoint Online , and Microsoft Azure
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
Understanding REST APIs in Office 365, SharePoint 2013 & Custom Development The REST APIs are very straightforward and easy to use and allow for a platform-agnostic development approach
A Deep-Dive of SharePoint 2013 & Office 365 Proven Development Strategies This blog post will cover the latest tools and technologies for performing custom development on SharePoint Server 2013 , Office 365, SharePoint Online and Microsoft Azure environments. I will also discuss development strategies for organizations who plan to have these technology assets deployed both on-premises as well as in the cloud and require applications that are compatible as well as secure in a hybrid cloud environment
The CSOM provides for: .NET Framework redistributable assemblies Office 365 API Tools JavaScript library Silverlight redistributable assemblies REST APIs Windows Phone assemblies The following image is an overview of underlying interactions in CSOM within SharePoint 2013: Office 365 API Tools Microsoft has recently introducing the next step in the evolution of the Office 365 platform by delivering the "preview" release of the Office 365 API tools, as shown in the image below. This continues to extend the platform and will open up a more possibilities around the hybrid cloud with the ability to not only access SharePoint 2013 on-premises but also extends the platform in Office 2013 by adding the ability for both sites and native applications to consume Office 365 data
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